|Functionality||After||Before||Result of changes|
Mobile application builder.
|In the mobile platform, support of in-app billing services is added. This includes Apple In-App Purchase (for iOS) and Google Play In-App Billing (for Android). Support of in-app billing for Windows is not provided. The In-app purchases mobile application permission is implemented.
The InAppPurchases, InAppPurchase, InAppPurchaseReceipt, and InAppPurchasesValidation objects are implemented.
In the desktop platform, the InAppPurchasesValidation object is implemented. It is intended for testing in-app purchase algorithms.
In the mobile platform for developers, a service providing an API similar to Google Play In-App Billing is implemented for Android operating system. It is intended for debugging in-app purchase algorithms.
The option to test the full purchase cycle is implemented. This includes the purchase creation and the emulation of some related scenarios. The HTTP service (named PurchaseTest) and the testing tools are provided by the mobile application builder.
The mobile application builder supports building mobile applications with in-app purchases.
|This feature was not provided.||The option to implement purchases and subscriptions in mobile applications is available. You can create applications with paid features.|
Mobile application builder.
|For mobile applications, the option to display ads is implemented. It uses iAd service (for iOS) and AdMob service (for Android). Displaying ads on Windows is not supported.
The AdRepresentation object is implemented.
Mobile application builder supports applications that display ads.
|This feature was not provided.||The option to create mobile applications with advertising monetization model is available.|
||Exporting spreadsheet documents fo PDF format is implemented.||This feature was not provided.||More options for data presentation in mobile applications.|
||On Android version 4.1 or later, numbers are displayed correctly if the NG parameter of the Format function contains two groups.||On Android version 4.1 or later, numbers were displayed incorrectly if the NG parameter of the Format function contained two groups.||Eliminated unexpected system behavior.|
||In the mobile platform, support of asynchronous file operation methods is implemented (this includes global context methods and the File object).||This feature was not supported by the mobile platform.||Improved parallel code implementation for both mobile and desktop platforms.|
||On the mobile platform, support of FullTextSearchManager.CheckIndex() method is implemented.
In the Syntax Assistant, methods of FullTextSearchManager object are marked as available on the mobile platform.
|This feature was not supported by the mobile platform.
The Syntax Assistant erroneously stated that methods of the FullTextSearchManager object were not available on the mobile platform.
|Extended full-text search support on the mobile platform. The Syntax Assistant description is up-to-date.|
||On the mobile platform, when specifying request body as a string for an HTTPRequest or HTTPServiceResponse object, you have the option to include BOM characters to the request or exclude them.
On the mobile platform, the ByteOrderMarkUsage system enumeration is implemented.
|This feature was not supported by the mobile platform.||Simplified mobile application integration with systems that do not expect BOM characters in HTTP requests.|
||The MobileDeviceApplicationRun object is now available on iOS and Windows platforms. The MobileDeviceApplicationRun.RunningSupported method is implemented to test the availability of this feature. Developers can use this method to determine whether their mobile devices support running external applications.||The MobileDeviceApplicationRun object was not available on iOS and Windows platforms.||The platform behavior related to functionalities that are not available on some mobile devices or operating systems is unified across all platforms.|
||In the Syntax Assistant, more information is added to the descriptions of Activate by default and Default button managed form items.
The Unfilled selection mode property of managed form input fields is available in mobile platform forms.
The Row selection mode property of managed form tables is no longer available in mobile platform forms.
|The information in the Syntax Assistant was outdated.
The availability of some properties of managed form input fields did not match the capabilities of the mobile platform.
|Designer and Syntax Assistant now match the capabilities of the mobile platform.|
|Mobile application builder.
||Data storage structure implemented in the mobile application builder is modified. When the mobile application builder is started for the first time after the update, the data conversion may take significant time.||Data storage structure implemented in the mobile application builder was different.||Data storage structure implemented in the mobile application builder is now more efficient.|
||When a debug server that does not support HTTP is specified in a mobile application, the error message clearly explains the problem: The mobile platform only supports debugging over HTTP.||When a debug server that did not support HTTP was specified in a mobile application, the error message did not clearly explain the problem.||Better problem diagnostics during mobile applicatiobn development.|
||In the mobile platform, the design of the page setup form is changed:
||In the mobile platform, the design of the page setup form was different:
||Improved design of the page setup form.|
|Mobile device-specific features.
||On iOS devices, receiving location updates when an application is running in background is not supported.||The option to receive location updates when an application is running in background on iOS devices was not documented.||Clarified the specifics of using mobile applications on iOS devices.|