Introducing the Microsoft Dynamics NAV Universal App

The app displaying the Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone client is targeted at users in small and medium sized businesses that want to access data from a tablet or a phone. Some of the advantages of offering this solution are portability and flexibility, when the user is away from the desk, on the train, between meetings, passing time and so on.

The tablet is lighter than a laptop, and thereby provides portability. Most tablets have an on-screen keyboard, but the keyboard plays a less central role on the tablet, and this forces you to have to consider the touch experience.

The phone is a very light device and has an even smaller screen than tablets, which is why the tasks that usually make sense to perform using the phone are brief and typically reading of data or very lightweight data entry, such as approving an invoice or getting an overview of the business. Designing for the Microsoft Dynamics NAV Tablet client you are used to optimizing for the touch experience; when you design for the Microsoft Dynamics NAV Phone client it is only about touch optimization.

Studies show that design for phone apps must cater for one-hand use; and in some cases, when switching to a panorama view, users will use both hands. The Microsoft Dynamics NAV Phone client layout is designed to support these needs, which allows the important data and buttons to be available within thumbs reach.

Having a Dynamics NAV solution that runs on a smaller device brings it in the hands of many more users and your app is easy to distribute. Other advantages are that using a tablet or phone, you can capture data closer to the source, for example, at the customer site, and thereby improve accuracy and reduce end-to-end time.

The following illustration shows the intended use of the various Dynamics NAV clients.

As illustrated, the Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone client do not replace the Microsoft Dynamics NAV Windows client or Microsoft Dynamics NAV Web client. Instead, they offer a touch interface for a limited set of application scenarios compared to the Microsoft Dynamics NAV Windows client and Microsoft Dynamics NAV Web client. The Microsoft Dynamics NAV Windows client and Microsoft Dynamics NAV Web client support more complex business processes and heavier data entry than is possible on the Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone client.

Microsoft Dynamics NAV Windows client is optimized for intensive use, and the user can have multiple windows open at the same time, for example, to compare sales orders, or do more things at a time. This is not possible in either Microsoft Dynamics NAV Web client or Microsoft Dynamics NAV Tablet client.

In the following documentation, you will see mentions of Microsoft Dynamics NAV Tablet client, Microsoft Dynamics NAV Phone client, and Microsoft Dynamics NAV Universal App. Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone client describe the interface tailored to the category of mobile device, which is one of the tools available for developers for designing mobile solutions, whereas Microsoft Dynamics NAV Universal App is the common name for the app across all devices; the end result made with these tools.

Considering the User Scenarios

When you design your solution for the Microsoft Dynamics NAV Tablet client and the Microsoft Dynamics NAV Phone client, you must make sure that scenarios are simple enough to be meaningful and usable. The tablet and phone designs are meant for lighter tasks and useful, for example, for traveling salespeople or service technicians who need a portable, online, easy-to-use app that provides an overview, for example, of daily tasks and items in stock.

Depending on the scenarios that your tablet and phone solution will support, it will either make sense to create a new Role Center for tablet and phone only, or share the same Role Center across all of the client types. In some cases it can make sense to have a user sign in with two different profiles, one for a desktop client and one for mobile devices. In other cases, duplicating pages and designing specific duplicates to be device-oriented is the best solution.

If you have existing page objects that you want to make available on Microsoft Dynamics NAV Tablet client or Microsoft Dynamics NAV Phone client, we strongly recommend that you plan time to evaluate carefully which actions, sections, and fields will be needed for the user scenarios you want to enable. Fields and actions that are not needed should not be visible to users of your app. The UI must be simplified significantly to work well on a small device.

Supported Credential Types

Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone client support the same credential types as Microsoft Dynamics NAV Windows client and Microsoft Dynamics NAV Web client. For more information, see Users and Credential Types.

See Also

Developing for the Microsoft Dynamics NAV Universal App
Getting Started Developing for the Microsoft Dynamics NAV Universal App
Differences and Limitations When Developing Pages for the Microsoft Dynamics NAV Universal App