Mobile Designer projects use parameters and properties to simplify the process of including and/or excluding features based on a target device. Mobile Designer predefines some parameter and property values, for example, the profile settings for devices. You can override the predefined settings for a specific mobile application project and/or for a specific target device.

When creating an application, typically you have common logic that works for all target devices. However, you might require branches in the logic to address the needs of a specific target device. For example, you might need to omit or alter a feature for a target device, or you might need to position an image relative to the screen dimensions for a target device. To accommodate device-specific logic, your application logic can branch based on parameter values that are set using the device profile settings.

Properties and parameters also drive how Mobile Designer builds applications for a target device. Mobile Designer drives builds using a combination of properties, parameters, and paths, all of which you can customize and override. For example, these properties, parameters, and paths control stubs against which to compile, packagers to use when making the final binaries, details about screen dimensions, the sound APIs and settings that are most appropriate for a target device, and other general and application-specific settings.