29.4.2. Types of mobile platform applications

<< Prev   Next >>

Mobile platform application development can be divided into the following stages:

• At first, you need to select the mobile platform application type:
  • Independent of any applications on the remote system. In this case, the data structure of the mobile platform application is determined only by the application scope. Most likely, no data exchange is required.
  • Standalone workstation of some application located on a remote system. In this case, the data structure is mainly determined by the application, but there will be changes that are determined by both the scope and the features of the mobile platform application. The data exchange protocol is likely to be developed specifically for exchange between a specific application with a specific mobile platform application. Most likely, this protocol will not support exchange with other applications.
  • Universal standalone workstation. In this case, the data structure must consider the specifics of all applications with which the mobile platform application must interact. You must also consider the features of the mobile platform application. The exchange protocol must be sufficiently universal and standardized.
• Clarify whether the developed application must run only on a mobile device or it can also run on a personal computer (for example, on a laptop).
• Implement the mobile platform application and debug it on a personal computer (including data exchange algorithms). You also need to understand that the mobile platform has a number of differences and peculiarities, due to which it is impossible to completely test the performance of the developed application on a personal computer. However, the code in 1C:Enterprise language can be debugged using a personal computer.
• On the mobile device (one or several), perform the final check and debug the application interface and functionality.

When developing a data exchange algorithm, consider that applications with different exchange interface versions must exchange data. This must not cause problems during exchange. This is due to the fact that updating the application at once for the entire infrastructure is almost impossible. Note that data synchronization with an outdated exchange protocol version can be used to perform backup operations before updating the mobile application configuration.

When developing a mobile platform application, consider the restrictions imposed by the mobile platform compared to the 1C:Enterprise platform for personal computers:

• Limited list of available configuration objects and features
• Limited set of attribute properties
• Limited set of managed form items
• Simplified implementation of some features (for example, access rights or home page)
• Absence of ordinary forms and regular startup mode
• Lack of tools for mobile application debugging

Keep in mind that the mobile platform and the platform for personal computers have different functionalities in the same versions. Functional correspondence between the versions of the platform for mobile devices and personal computers is provided below:

Mobile platform	Platform for personal computers
8.3.9 or later	8.3.9 or later
8.3.8	8.3.7
8.3.7	8.3.6
8.3.6	8.3.5
8.3.5	8.3.4
8.3.4	8.3.2
8.3.3	8.3.2

In the documentation to be developed for a mobile platform application, the application developer does not have to describe the behavior of standard system features, but refer to the Mobile Application User Guide, which is located at http://v8.1c.ru/mobile_user_guide/.

<< Prev   Next >>