What problem does it solve?
Building a hybrid Android app around Rails/Hotwire becomes complex when you need native navigation, URL-to-screen mapping, JS-to-Kotlin bridge UI, and secure authentication that works inside a WebView.
Core Features & Use Cases
- Hybrid navigation with path-based routing: map URL patterns to navigation behavior, including deep links and modal/presentation contexts for screens.
- Bridge components (JS ↔ Kotlin): build native UI capabilities (buttons, forms, menus) controlled from web content using a structured three-part pattern.
- Authentication that survives navigation: implement cookie-based and token-based authentication patterns, including token sync into WebView cookies and Rails-side cookie handling.
- Native screen integration: connect Hotwire web destinations to Android fragments using deep links and navigator host configurations.
Quick Start
Implement the Hotwire Native Android skeleton by wiring a navigator host in your Activity, loading path configuration rules, registering bridge components, and then adding token/cookie auth plus fragment deep links as you integrate your Rails app.
