Hotwire Native

Iron Laws

1. Reuse web screens first - Build in HTML/CSS before reaching for native screens.
2. Use path configuration to control routing behavior declaratively.
3. Bridge components for native upgrade - Use Strada when the web isn't enough.
4. Keep native and web in sync - Version bridge components together.
5. Test on real devices - Simulators don't catch all native behaviors.
6. Handle offline gracefully - Native apps expect resilience.

Overview

Hotwire Native wraps your web app in a native shell (iOS/Android), providing:

• Native navigation transitions between web screens
• Access to native SDKs and APIs via Bridge Components
• Push notifications, camera, location, and other native features
• App store distribution with web-first updates
• Fallback to native screens when needed