hotwire-native

What problem does it solve?

Hotwire Native bridges web applications and native mobile shells so teams can reuse HTML/CSS while gaining access to native navigation, device APIs, and performant platform experiences. It removes ad-hoc, fragile integrations by providing declarative path configuration, versioned bridge components, and clear fallbacks for web-first workflows.

Core Features & Use Cases

• Declarative path configuration to control when URLs present as modals, native screens, or standard web pages.
• Strada bridge components for bidirectional web-to-native communication (datepicker, camera, location, share, alerts).
• Native screen fallbacks and upgrade paths so teams start with web screens and introduce native views only when necessary.
• Operational features including push notification token handling, offline resilience strategies, and device-oriented testing guidance.
• Use Case: Turn an event form into a web-first flow with a native datepicker and camera uploader by serving a path-configuration endpoint and registering a datepicker bridge component on iOS and Android.

Quick Start

Configure your Rails app to serve a native path-configuration and register the required Strada bridge components (eg. datepicker, camera) while providing web fallbacks.