hotwire-native

Configure Hotwire Native path routing and Strada bridge components for Rails apps.

7|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill hotwire-native
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hotwire-native
Source: https://github.com/slbug/claude-ruby-grape-rails/tree/main/plugins/ruby-grape-rails/skills/hotwire-native
Command: npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill hotwire-native

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about hotwire-native

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I wrap my Rails web app into a native iOS and Android shell?▼

You can wrap Rails web apps into native iOS and Android shells using Hotwire Native and Turbo Native to gain native navigation and bidirectional bridge communication while reusing existing HTML/CSS interfaces.

How do Strada bridge components handle web-to-native communication?▼

Strada bridge components enable bidirectional web-to-native communication by registering message handlers on iOS and Android, allowing web interfaces to trigger native features like datepickers, cameras, location, and share dialogs.

How do I configure native path routing for Turbo web screens?▼

Declarative path configuration controls when URLs present as modals, native screens, or standard web pages by serving a path-configuration endpoint from your Rails backend to route Turbo web screens natively.

Can I start with web screens and add native views later?▼

Yes, Hotwire Native supports native screen fallbacks and upgrade paths so teams can begin with web-first screens and introduce native views only when necessary without breaking existing workflows.

Does Hotwire Native support push notifications and offline resilience?▼

Yes, Hotwire Native includes operational features for push notification token handling, backend device token management, and offline resilience strategies alongside device-oriented testing guidance for iOS and Android.

What's the best way to add a native datepicker and camera uploader to a web form?▼

Serve a native path-configuration endpoint and register datepicker and camera Strada bridge components on iOS and Android while providing web fallbacks to integrate native device features into web-first forms.