Mobile Designer will detect installations of Xcode as well as Android Studio and Android SDK automatically. However, if automatic detection fails or if you want to use different locations, update the according properties of the sdk.properties file in the root of your Mobile Designer installation. Note that on the Linux platform, the automatic detection is not supported and updating the sdk.properties file is mandatory for using Multi-Build or Run in Simulator features*.*

The new ConstraintLayout templates are not available for simulation in Phoney. For user interface preview, use the integrated preview in Outline or the Layout Builder for the template. To test the ConstraintLayout templates at run time, do a simulator Multi-Build and use the new Run in Simulator action available in the Mobile Tools context menu item.

As of Mobile Designer 10.1, the new run time does not use the Mobile Designer Midlet Thread that was used in all versions up to 9.12 for synchronizing user interface updates in the application. Instead, it now utilizes the main thread provided by the particular native platform for all user interface operations and synchronization. All operations now run on the (native) main thread. This is important for performance of the application and user experience. As in native applications, all heavy operations now need to run on new threads so as not to block the user interface during execution. A set of new APIs (runAsync() and ICallable) was introduced to make it easy to execute operations in new threads and synchronizing back to the main thread.

It is also important to note that in case the user interface is not updated automatically, running syncUI() on nUIViewDisplay will synchronize all changes and update the user interface