In the last few years, mobile has grown so fast that it's now the leading digital platform. Users are spending more time on mobile devices than on their personal computers. Business applications are also impacted with this trend. Employees need mobile apps to create and submit their timesheet and expenses, managers need apps to approve workflow requests on the go, sales reps need customer information and can create orders on the go when they are visiting the customers. Dynamics 365 for Finance and Operations, Enterprise edition includes support for mobile phone apps on Android and iOS devices.

The following are the key highlights of the mobile app for Dynamics 365 for Finance and Operations, Enterprise edition:

• Offline capability: You can view, edit, and operate the mobile app when your device is connected to the network and while your mobile phone is completely offline. If a user creates or updates data while his or her device isn't connected to the Finance and Operations server, temporary records are created in the local cache. When your device reestablishes a network connection, your offline data operations are automatically synchronized. 
• Build and deploy: IT admins can build and publish mobile workspaces as per the organization's need. The app leverages your existing code, business logic, and security configuration. IT admins can easily design mobile workspaces using the point-and-click workspace designer that comes built in with the Dynamics 365 for Finance and Operations, Enterprise edition web client.
• Business logic extensibility: IT admins can optimize the offline capabilities of workspaces by utilizing the business logic extensibility framework. Using this, you can provide additional business logic and render support by adding a JavaScript file with the application workspace metadata.

The following screenshot provides an overview of the Dynamics 365 for Finance and Operations mobile application user interface:

The following diagram shows the basic architecture of the mobile application framework:

As shown in the diagram, mobile app metadata, forms, and data are all stored on the application object server. When the user logs in for the first time or pulls to refresh the dashboard, the mobile app requests the metadata and downloads and caches the workspaces and pages. When the user opens the page or pulls to refresh the data on the page, the mobile app opens the form, downloads the data for the page, and caches it. Any operation, such as editing the data or taking an action that results in a create, update, or delete operation, goes into the queue and is subsequently executed on the AOS, with the result synchronized.