Designing for Different Screen Sizes on a Tablet

  • Article

When designing application pages for Microsoft Dynamics NAV Tablet client, it is best practice to consider the size of the tablets your end-users have access to. It is an advantage if the solution works well on both small screen sizes in addition to, larger screen sizes, but we also recommend that you consider thoroughly the most commonly used screen sizes for your end-user experience. Designing for small screens can be a challenge, because pages will show fewer fields, columns, and tiles.

In many cases, end-users will have access to a broad range of devices having different screen sizes and resolutions. End-users may have one device at work, and a different device at home, and expect the experience on both devices to be equally good. A good way to identify issues on how your application pages will look is to test on the smallest supported screen size. Currently tablet sizes start in the 7” range.

Screen sizes of varying types

Form Factor Considerations

Users can scroll the content area of Microsoft Dynamics NAV for tablets to access all data for a given page. However, some elements of the screen, for example, the app bar cannot be scrolled. The app bar is the blue area of Microsoft Dynamics NAV for tablets and it is designed to provide easy access to important information and tasks that the user should not lose sight of when scrolling. The static elements will display only as much data as they can reasonably fit on the screen. Developers should design to make sure that the important static elements are displayed first, so that that these will be shown even on the smallest, available devices.

Guidance for Page Element Types on Smallest Devices

The following table provides a list of non-scrollable elements in the page content or the app bar.

Page Type Displays on smallest device

RoleCenter

4 tiles in 1 group, or 2 groups together with 2 tiles

List Pages

5 columns of type Text50 or 8 columns of type Text20

Card Pages
  • CardPage Factbox with up to 15 fields

  • 2 CardPage Factboxes with up to 6 fields each

  • Activities Factboxes with 4 tiles in 1 group, or 2 groups together with 2 tiles

Document Pages
  • CardPage Factbox with up to 15 fields

  • 2 CardPage Factboxes with up to 6 fields each

  • Activities Factboxes with 4 tiles in 1 group, or 2 groups together with 2 tiles

Testing Using a Browser

Using a browser you can test how your application pages will look on various device sizes. For more information, see How to: Open the Microsoft Dynamics NAV Tablet Client from a Browser. When running Microsoft Dynamics NAV Tablet client in a browser, you can use the Internet Explorer Developer Tools to emulate different screen sizes. For more information, see Using the F12 developer tools.

See Also

Concepts

Deciding on Your Tablet Strategy
Differences and Limitations When Developing Pages for the Microsoft Dynamics NAV Tablet Client