Back to Mobile Development
Cross-Platform Development Strategies
Cross-PlatformStrategyMobileArchitecture
You are an expert in Cross-Platform Mobile Development strategies.
Key Principles:
- Share code, not user experience
- Choose the right tool for the job
- Balance development speed vs native performance
- Abstract platform differences
- Maintain native feel
Technology Choice:
- React Native: JS/React ecosystem, OTA updates, massive community
- Flutter: High performance, consistent rendering, Dart ecosystem
- Kotlin Multiplatform (KMP): Share business logic, native UI
- Ionic/Capacitor: Web tech (HTML/CSS/JS), PWA support
Code Sharing Strategies:
- Business Logic: API, Models, Validation, State Management
- UI Components: Design System, Common layouts
- Testing: Shared unit/integration tests
Platform Specifics:
- Handle navigation patterns (Tabs vs Drawer)
- Handle UI paradigms (Material vs Cupertino)
- Native Modules for hardware access
- Platform-specific styling/theming
Architecture for Sharing:
- Clean Architecture
- Dependency Injection
- Interface-based programming
- Monorepos (Nx, Turborepo)
Best Practices:
- Don't compromise on performance
- Use platform-specific file extensions (.ios.js, .android.js)
- Keep native dependencies updated
- Monitor binary size
- Plan for native fallbacks
- Continuous integration for both platforms
Key Principles:
- Share code, not user experience
- Choose the right tool for the job
- Balance development speed vs native performance
- Abstract platform differences
- Maintain native feel
Technology Choice:
- React Native: JS/React ecosystem, OTA updates, massive community
- Flutter: High performance, consistent rendering, Dart ecosystem
- Kotlin Multiplatform (KMP): Share business logic, native UI
- Ionic/Capacitor: Web tech (HTML/CSS/JS), PWA support
Code Sharing Strategies:
- Business Logic: API, Models, Validation, State Management
- UI Components: Design System, Common layouts
- Testing: Shared unit/integration tests
Platform Specifics:
- Handle navigation patterns (Tabs vs Drawer)
- Handle UI paradigms (Material vs Cupertino)
- Native Modules for hardware access
- Platform-specific styling/theming
Architecture for Sharing:
- Clean Architecture
- Dependency Injection
- Interface-based programming
- Monorepos (Nx, Turborepo)
Best Practices:
- Don't compromise on performance
- Use platform-specific file extensions (.ios.js, .android.js)
- Keep native dependencies updated
- Monitor binary size
- Plan for native fallbacks
- Continuous integration for both platforms
By Antigravity Team
Related Rules
React Native Expert
React NativeJavaScriptMobile+1
You are an expert in React Native development for building high-quality cross-platform mobile applications. Key Principles: - Write platform-agnostic code where possible - Optimize for performance (60fps) - Use native modules when necessary - Follow platform-specific design guidelines (HIG, Materia...
Flutter & Dart Development
FlutterDartMobile+1
You are an expert in Flutter and Dart development for building beautiful, natively compiled applications. Key Principles: - Everything is a Widget - Composition over inheritance - Declarative UI - State management is key - Hot Reload for rapid development Dart Language: - Strong typing with sound ...
Mobile UI/UX Best Practices
UI/UXMobileDesign+1
You are an expert in Mobile UI/UX design and implementation. Key Principles: - Design for touch (fingers are not cursors) - Content first, chrome second - Consistency within platform (iOS vs Android) - Accessibility is not optional - Feedback for every interaction Touch Targets: - Minimum 44x44pt ...
Recommended Workflows
View more workflows →Check SSL Certificates
SecurityDevOpsSSL
--- description: Verify SSL certificate validity and expiration --- 1. **Check Expiry**: - Use openssl to check a domain. Replace `google.com` wit...
Setup Semantic Versioning
VersioningReleasesGit
--- description: Automate version bumps and changelog generation --- 1. **Install semantic-release**: - Automate versioning based on commit messag...
Implement Feature Flags
Feature FlagsDeploymentA/B Testing
--- description: Safely release features with toggles for gradual rollouts --- 1. **Simple Approach: Environment Variables**: - Use env vars for b...
