Skip to main content

Platform-specific configuration

FlowX.AI UI Designer provides platform-specific configuration and styling for components across Web, iOS, and Android platforms. Understanding platform differences and capabilities is essential for creating optimal user experiences.

Platform overview

Supported platforms

Web

Full Feature Support
  • Complete navigation area functionality
  • Zones with headers and footers
  • Wizard and single-page navigation
  • All UI component types supported

iOS

Mobile-Optimized
  • Stepper, Page, Modal and Tab Bar navigation areas (no Zones)
  • Screen title configuration for navigation bar
  • Scrollable property for root Card and Container components
  • Platform-specific property overrides

Android

Mobile-Optimized
  • Stepper, Page, Modal and Tab Bar navigation areas (no Zones)
  • Screen title configuration for navigation bar
  • Scrollable property for root Card and Container components
  • Platform-specific property overrides
  • Material design considerations

Web platform features

Full Navigation Support: Web platform provides the most comprehensive navigation features.
Web-Exclusive Features:
  • Zones with headers and footers
  • Complete navigation hierarchy
  • Advanced navigation patterns
Zones with headers and footers are exclusively accessible in web configurations. They are not supported as navigation areas for mobile development.

Component support

Full Component Library: Web platform supports all UI component types without restrictions.

Mobile platform features

iOS platform specifics

iOS-Specific Properties:Screen title: Set the screen title used in the navigation bar on mobile devices, in the Settings tab (available on a Card or Container that is the root component of a user task, or a direct child of a navigation area in a UI Flow)Scrollable Property: Define the desired behavior of the screen, specifying whether it should be scrollable or not (default: true), in the Styles tab. Applies to iOS and Android, on the same root components as the screen titleThe screen title is stored with the component properties and the scrollable flag with its style:

Android platform specifics

Android-Specific Features:Screen title: Set the screen title used in the navigation bar on mobile devices (available on a Card or Container that is the root component of a user task, or a direct child of a navigation area in a UI Flow)Scrollable Property: Define whether the screen should be scrollable, on the same root components as the screen titleMaterial Design Considerations: Android components adapt to Material Design principles where applicable
Android Ecosystem:
  • Multiple screen sizes and densities
  • Different Android versions
  • Manufacturer-specific customizations
  • Hardware capability variations

Platform override system

Configuration hierarchy

1

Generic Settings

Base Configuration: Properties available cross-platform (Web, Android and iOS), serving as the default for all platforms.
2

Platform Overrides

Specific Customizations: Override generic settings for individual platforms to optimize user experience.
3

Preview and Testing

Visual Validation: Preview changes across platforms, keeping in mind that iOS and Android previews are estimates.

Implementing overrides

To configure platform-specific overrides:
1

Access Platform Settings

Pick the platform in the UI Designer toolbar (Desktop, Mobile iOS, or Mobile Android), select a component, and open the Settings tab. It shows an overrides section for the selected platform, such as iOS overrides for Mobile iOS.
2

Add Override

Select + next to the overrides section and pick the type of override:
  • Properties: Override component properties (e.g., Title, Subtitle, Helper)
  • Expressions: Add a Hide condition for this platform only (platform overrides don’t offer a disable condition)
3

Configure Value

Enter the platform-specific value that differs from the generic setting.
4

Copy between platforms

Open the ⋮ menu next to <platform> overrides and pick Copy from <platform> or Copy to <platform> to share overrides between platforms when appropriate.

Available override types

Common Property Overrides:
  • Title: Shorter titles for mobile displays
  • Subtitle: Platform-appropriate subtitles
  • Helper: Context-specific help information
  • Label: Adapted for platform conventions
Example Use Case: Web title “Complete Application Process” → Mobile title “Complete App”

Platform limitations and constraints

Component availability

⚠️ = Limited functionality or platform-specific constraints
❌ = Not supported on platform

Styling and layout limitations

The Styles tab adapts its layout options to the selected platform:
  • Justify: Web offers Start, Center, End, Space Between, Space Around and Space Evenly. iOS and Android offer Start, Center and End.
  • Align: Web offers Start, Center, End and Stretch. iOS and Android offer Start, Center and End.
  • Wrap: shown on Web only.
  • Gap: measured in px on Web, pt on iOS and dp on Android.
The Custom CSS class field shows on every platform, but only the web renderer applies CSS classes. Native iOS and Android renderers don’t apply CSS.
Limitations:
  • No Zone navigation areas on mobile
  • No Navigation type setting on mobile: single page form and wizard apply to Web only
Workarounds:
  • Use Stepper and Step navigation areas for step-by-step flows on mobile
  • Use card-based layouts for mobile organization
  • Implement navigation through event handlers
  • Use platform-specific screen titles
Challenges:
  • Different navigation capabilities across platforms
  • Varying screen sizes and interaction methods
  • Platform-specific design conventions
Solutions:
  • Use generic settings as baseline
  • Apply strategic platform overrides
  • Test across all target platforms
  • Design for the most constrained platform first

Platform-specific best practices

Web platform optimization

Navigation Design

Use Web Capabilities:
  • Use full zone navigation with headers/footers
  • Implement wizard navigation for complex flows
  • Take advantage of larger screen real estate
  • Use single-page forms with card organization

Layout Strategy

Web-Specific Layouts:
  • Utilize horizontal space effectively
  • Implement complex grid layouts
  • Support both single-page and wizard navigation
  • Consider desktop interaction patterns

Mobile platform optimization

1

Screen Space Management

Mobile Constraints:
  • Smaller screen sizes require condensed content
  • Use shorter titles and labels
  • Prioritize essential information
  • Consider thumb-friendly interaction zones
2

Platform Integration

Mobile-Specific Features:
  • Configure screen titles for navigation bars
  • Set appropriate scrollable behavior (iOS and Android)
  • Consider platform design conventions
  • Test on actual devices when possible
3

Content Adaptation

Mobile Content Strategy:
  • Use platform overrides for mobile-optimized text
  • Simplify complex interactions
  • Ensure touch targets are appropriately sized
  • Test with realistic content lengths

Testing across platforms

Preview limitations

Important: The preview generated in the UI Designer for iOS and Android platforms is an estimate meant to help you visualize how it might look on a mobile view. Actual device testing is recommended for production applications.
The UI Designer has no option to send a preview to a physical device. To test on a device, run your project in a container app built with the iOS, Android, or React Native renderer SDK.

Testing Strategy

UI Designer Testing:
  • Use the platform selector in the toolbar to switch between Desktop, Mobile iOS, and Mobile Android
  • Compare layouts and content across platforms
  • Validate platform overrides are applied correctly
  • Check navigation behavior differences
Cross-Platform Content:
  • Verify text fits within mobile constraints
  • Test with longest expected translations
  • Ensure critical information is visible on all platforms
  • Validate platform-specific features function correctly
Feature Validation:
  • Test navigation flows on each platform
  • Verify platform-specific components work as expected
  • Validate hide/show expressions across platforms
  • Test conditional styling behavior

Migration and maintenance

Platform updates

Override Management: Settings overrides can always be copied from one platform to another with Copy from <platform> and Copy to <platform>, making it easier to maintain consistency while allowing for platform-specific optimizations.

Maintenance best practices

1

Regular Testing

Test your interfaces across all target platforms regularly, especially after making changes to generic settings or platform overrides.
2

Documentation

Document platform-specific decisions and overrides to help team members understand the rationale behind platform differences.
3

Consistency Monitoring

Regularly review platform overrides to ensure they still serve their intended purpose and maintain overall design consistency.
Understanding platform-specific considerations helps you create interfaces that work well across all target platforms while taking advantage of each platform’s unique capabilities and respecting their constraints.
Last modified on November 13, 2026