FireMonkey Mobile Application
Go Up to File Menu
File > New > FireMonkey Mobile Application - Object Pascal
File > New > FireMonkey Mobile Application - C++
Types of FireMonkey Mobile Applications You Can Create
The wizard presents these choices:
- Blank Applicaton
- 3D Application
- Header/Footer with Navigation
- Tabbed with Navigation
- Phone Master-Detail
- Tablet Master-Detail
A mobile application template is a predefined mobile application, a project containing forms preconfigured with components. You can use these templates as a starting point when you create a new mobile application, so that you do not have to start your application "from scratch". The mobile application templates include Blank Application, 3D Application, Header/Footer, and so forth.
The FireMonkey mobile application templates are self-documenting. To display a short description of a template, move your mouse onto a template in the FireMonkey Mobile Application dialog box. See FireMonkey Mobile Application Templates for more information.
Templates are not generated dynamically in memory, but are copied from disk:
- When you create a new application from a template, the Browse for Folder dialog box appears, and you must choose the location to save your new application.
- After the application is open in the Project Manager, you might want to rename the project and the form file (using the Rename command, available in the context menu) instead of using the default names assigned by the wizard. For example, if you select the Tabbed template, the project is named TabbedApplication , the .pas file is named TabbedTemplate.pas, and the form file is named TabbedTemplate.fmx.
Target Platforms for FireMonkey Mobile Applications
- Android (to run on a connected Android device or an installed Android emulator; this is the default for the FireMonkey Mobile Application wizard).
- iOS Device (to run on the connected iOS device; also displays the detected or default iOS version).
- iOS Simulator (to run on the Mac).
- Note: You can also use the 32-bit Windows platform as a preliminary test platform for your mobile applications. For more information, see Mobile Preview.
For an iOS mobile app, the associated connection profile must have OS X (Mac) as the intermediate target platform. If only one OS X connection profile exists, it is automatically used as the profile for your iOS projects. If you have several OS X connection profiles, you should choose one OS X connection profile and activate it for your iOS project. The Project Manager displays the name of the connection profile in the associated platform node.
For example, after you create a connection profile for the OS X intermediate platform, the name of the active OS X connection profile is displayed in the iOS Device and iOS Simulator target platform nodes. So your iOS app has a connection profile that is also used for the Mac, like this: