llms.txt
Compare with other sites' llms.txt files →# Ruby Native
> Turn your Rails app into iOS and Android apps. Any frontend framework. No Xcode or Android Studio required.
Complete docs as a single markdown file: https://rubynative.com/llms-full.txt
## Key pages
- [Homepage](https://rubynative.com/): What Ruby Native is and how it turns a Rails app into a native app.
- [Pricing](https://rubynative.com/pricing): Plans for shipping to the App Store and Google Play.
- [Showcase](https://rubynative.com/showcase): Every app built with Ruby Native that is live in the App Store or Google Play, with the monthly active device count.
- [Security](https://rubynative.com/security): What Ruby Native holds on your behalf, what it does with your App Store Connect key, where builds run, and how to revoke access.
- [Try Ruby Native](https://rubynative.com/try): Preview your own Rails app on your phone in minutes, no account required.
- [Integration guide](https://rubynative.com/guide): Step-by-step guide to adding Ruby Native to an existing Rails app.
- [Why Ruby Native](https://rubynative.com/why): A one-page overview for teams deciding on a mobile app: what Ruby Native does, what it asks of your team, what it costs, and how it handles security and ownership.
- [Launch review](https://rubynative.com/launch-review): An app store expert reviews your listing before you submit and answers any rejection until that version is approved.
- [Product updates](https://rubynative.com/updates): What changed in Ruby Native, newest first.
## Case studies
- [Equipe case study](https://rubynative.com/case-studies/equipe): How Equipe migrated a decade-old Hotwire Native app to Ruby Native, and why their founder now ships both stores himself.
- [StatusGator case study](https://rubynative.com/case-studies/statusgator): How StatusGator shipped iOS and Android from their Rails app after two years on the shelf, without hiring a mobile engineer.
## Documentation
- [Documentation](https://rubynative.com/docs.md): Learn how to get the most out of Ruby Native. These guides cover common features you can add after your first preview.
- [Setup](https://rubynative.com/docs/setup.md): Add the gem to your Gemfile and run the install generator.
- [Configuration](https://rubynative.com/docs/configuration.md): config/ruby_native.yml is the whole native configuration. Your app fetches it as JSON from /native/config.json on every launch, so a change reaches a running...
- [Tabs](https://rubynative.com/docs/tabs.md): Define your tab bar in config/ruby_native.yml with a title, path, and icon for each tab.
- [Icons](https://rubynative.com/docs/icons.md): Ruby Native uses native icon libraries for tab bar and button icons: SF Symbols on iOS and Material Symbols on Android. Think of either as Font Awesome or...
- [Navigation bar](https://rubynative.com/docs/navbar.md): You have two options for the navigation bar: a native one provided by Ruby Native, or your own web-based one. We recommend the native navigation bar for most...
- [Form handling](https://rubynative.com/docs/forms.md): When a user submits a form and the app navigates to a success page, tapping "back" should skip the form and return to the page before it. Ruby Native marks...
- [Keyboard](https://rubynative.com/docs/keyboard.md): By default, iOS renders a toolbar above the keyboard whenever a form field is focused, with previous and next arrows and a Done button. Disable it with the...
- [Inertia (React & Vue)](https://rubynative.com/docs/inertia.md): Ruby Native includes first-class support for Inertia.js apps using React or Vue. This guide covers the one-time setup. Once configured, all the feature...
- [Appearance](https://rubynative.com/docs/appearance.md): Customize your app's colors and layout in config/ruby_native.yml.
- [Error screen](https://rubynative.com/docs/error-screen.md): When the app fails to load a page it shows a native screen with an icon, a short message, and a retry button.
- [Authentication](https://rubynative.com/docs/authentication.md): Ruby Native reuses your existing sign in and registration screens in the native app. There's no need to build separate native auth flows. Your web forms,...
- [OAuth](https://rubynative.com/docs/oauth.md): Ruby Native handles the complete client-side OAuth flow for Sign in with Google, GitHub, and other providers. Users sign in through a secure system browser,...
- [Linked domains](https://rubynative.com/docs/linked-domains.md): Linking your domain to the app makes the website and the app act like the same thing. Tap a link to your site in Messages or Gmail and it opens in your app...
- [Back buttons](https://rubynative.com/docs/back-buttons.md): Ruby Native can show a back button when there is navigation history. The gem ships a small CSS file that handles showing and hiding the button automatically.
- [Root pages](https://rubynative.com/docs/root-pages.md): Force a page to appear as the first and only screen on the navigation stack, with no back button.
- [Floating action button](https://rubynative.com/docs/fab.md): Add a native floating action button (FAB) for a primary action on the page, like "new post" or "compose message". It sits above the tab bar, or at the bottom...
- [Menus](https://rubynative.com/docs/menus.md): Attach a native menu to any element on the page, like a list row, a card, or a status pill. Tapping the element opens the menu anchored right on it: a native...
- [Barcode scanner](https://rubynative.com/docs/barcode-scanner.md): Add a button that opens the native camera scanner. On a successful scan the value fills a field on your page and a ruby-native:scan event fires, so it works...
- [Haptics](https://rubynative.com/docs/haptics.md): Trigger device vibrations when users tap buttons, submit forms, or complete actions. Haptics add tactile feedback that makes your app feel more responsive...
- [Push notifications](https://rubynative.com/docs/push-notifications.md): Ruby Native sends push notifications from your Rails app to iOS and Android devices. The gem provides the native_push_tag helper to register devices and a...
- [Badges](https://rubynative.com/docs/badges.md): Update the app icon badge and tab bar badge from regular page loads. Badges stay in sync as users navigate, without needing to send a push notification.
- [Toasts](https://rubynative.com/docs/toasts.md): A toast provides simple feedback about an operation in a small, dismissable popup. They are like flash messages in Rails, but built with native elements. In...
- [In-app review](https://rubynative.com/docs/review.md): Ask the operating system to show the App Store or Google Play rating prompt right inside your app, without sending the user to the store. Render the signal...
- [In-app purchases](https://rubynative.com/docs/in-app-purchases.md): Add subscriptions to your Ruby Native app. Your users purchase directly in the app via Apple's StoreKit and your Rails app handles the rest. No third-party...
- [Permissions](https://rubynative.com/docs/permissions.md): Both iOS and Android require apps to declare which sensitive capabilities they need. Ruby Native uses one set of dashboard fields to configure permissions...
- [Debugging](https://rubynative.com/docs/debugging.md): Ruby Native reads your pages through signals: hidden elements carrying data-native- attributes that tell the app to show a tab bar, a navigation bar, a...
- [Continuous integration](https://rubynative.com/docs/continuous-integration.md): Once you've integrated Ruby Native you'll want to verify that the native side is correct before a build goes out.
- [Updating your app](https://rubynative.com/docs/updates.md): Once your app is live, most of what you change reaches your users the moment you deploy your Rails app. A new build is the exception, and this page covers...
- [Screenshots](https://rubynative.com/docs/screenshots.md): Both Apple and Google require screenshots before you can publish a production listing. They're often the first thing a potential user sees in store search...
- [CLI](https://rubynative.com/docs/cli.md): The Ruby Native CLI lets you deploy builds and manage your app from the terminal.
- [Advanced Mode](https://rubynative.com/docs/advanced-mode.md): Advanced Mode replaces web navigation with native screen transitions. Pages push and pop with the same animations users expect from any native app, complete...
- [Compared to other approaches](https://rubynative.com/docs/compared.md): Ruby Native is one of several ways to get a Rails app onto phones. Each of the others is a fine choice for some teams, so here is the trade-off in each...
- [A PWA](https://rubynative.com/docs/compared/pwa.md): A progressive web app installs from the browser and never touches the app stores. Ruby Native puts the same Rails app in the App Store and Google Play as a...
- [Capacitor](https://rubynative.com/docs/compared/capacitor.md): Capacitor wraps a web app in a native shell too. The difference is whose shell it is, and what it expects your frontend to be. Capacitor is built for a...
- [React Native](https://rubynative.com/docs/compared/react-native.md): React Native rebuilds your product's interface in React, rendered with native components, with Rails behind it as an API. Ruby Native ships the interface you...
- [Flutter](https://rubynative.com/docs/compared/flutter.md): Flutter is Google's toolkit for building an app's interface in Dart, drawn by Flutter's own engine on every platform. Ruby Native ships the interface your...
- [Hotwire Native](https://rubynative.com/docs/compared/hotwire-native.md): Hotwire Native is the open source framework from 37signals for building native apps around a web app, and Ruby Native's Advanced Mode runs on it. So this is...
- [An agent-written shell](https://rubynative.com/docs/compared/agent-written-shell.md): A coding agent can hand you a working Hotwire Native shell in an afternoon. That is true, and for the teams described on the Hotwire Native page it is a fine...
- [Wrapper services](https://rubynative.com/docs/compared/wrapper-services.md): Paste a URL, pick an icon, get an app. Website-to-app services have offered that for years, and for a lot of sites it is the right product. Ruby Native looks...
## iOS
- [iOS](https://rubynative.com/docs/ios.md): Step-by-step guides for configuring your Apple Developer account, shipping to TestFlight, and submitting to the App Store.
- [Apple Developer Program](https://rubynative.com/docs/ios/enrollment.md): You need an Apple Developer Program membership to distribute apps through TestFlight and the App Store. Ruby Native uses your membership to sign builds and...
- [Developer credentials](https://rubynative.com/docs/ios/credentials.md): Ruby Native needs three things from your Apple Developer account to sign your app and upload it to TestFlight: your Team ID, an App Store Connect API key...
- [App Store Connect](https://rubynative.com/docs/ios/app-store-connect.md): App Store Connect is where Apple manages your app's listing, TestFlight builds, and App Store submissions. Before Ruby Native can upload a build, your app...
- [Push notifications](https://rubynative.com/docs/ios/push-notifications.md): Configure APNs credentials so your Rails server can send push notifications to iOS devices. If you haven't yet, set up the Rails side first.
- [Go live](https://rubynative.com/docs/ios/go-live.md): A pre-flight checklist for getting your app approved on the App Store. Ruby Native handles the builds, signing, and uploads; this page is everything left,...
- [Payments](https://rubynative.com/docs/ios/go-live/payments.md): Whether your app needs in-app purchases is the most important decision to make before submission. Here's where things stand as of August 2026. Shipping...
- [In-app purchase setup](https://rubynative.com/docs/ios/go-live/in-app-purchase-setup.md): Create your subscription products in App Store Connect so users can purchase them in your app.
- [App privacy](https://rubynative.com/docs/ios/go-live/app-privacy.md): Apple requires every app to disclose what data it collects through privacy "nutrition labels." You fill these out in App Store Connect before your first...
- [Submission](https://rubynative.com/docs/ios/go-live/submission.md): Your build is on TestFlight, your screenshots are uploaded, and your privacy questionnaire is done. Time to submit.
- [App Store review](https://rubynative.com/docs/ios/go-live/app-store-review.md): Apple reviews every app before it goes live. If your app wraps a website without adding native value, it will be rejected under guideline 4.2 (Minimum...
- [App Review rejections](https://rubynative.com/docs/ios/rejections.md): Apple rejects most first submissions for the same handful of reasons, and each one has a known fix. This is one page per guideline: Apple's own text, what...
- [4.2 Minimum Functionality](https://rubynative.com/docs/ios/rejections/4-2-minimum-functionality.md): Guideline 4.2 is the rejection for an app that looks like a website in a frame. Ruby Native apps are built to clear it, with a native tab bar, push...
- [4.2.2 Web clippings](https://rubynative.com/docs/ios/rejections/4-2-2-web-clippings.md): Guideline 4.2.2 is the rejection for an app that opens on your marketing site or is mostly a list of links. The fix is to land native users inside the...
- [2.1 App Completeness](https://rubynative.com/docs/ios/rejections/2-1-app-completeness.md): Guideline 2.1 covers everything that stopped the reviewer from reviewing: a crash, a demo account that does not work, an error screen, placeholder content,...
- [2.3 Accurate Metadata](https://rubynative.com/docs/ios/rejections/2-3-accurate-metadata.md): Guideline 2.3 is the rejection for a listing that does not match the app: screenshots of the website, a description that mentions features the app does not...
- [5.1.1 Privacy and account deletion](https://rubynative.com/docs/ios/rejections/5-1-1-privacy-and-account-deletion.md): Guideline 5.1.1 is the rejection for a missing privacy policy link inside the app, or an account that can be created in the app but not deleted from it. Both...
- [3.1.1 In-App Purchase](https://rubynative.com/docs/ios/rejections/3-1-1-in-app-purchase.md): Guideline 3.1.1 is the rejection for an app that sells digital goods or subscriptions without Apple's in-app purchase, which for a SaaS app usually means an...
- [4.8 Login Services](https://rubynative.com/docs/ios/rejections/4-8-login-services.md): Guideline 4.8 is the rejection for an app that offers Google, GitHub, or another social sign-in without an equivalent privacy-focused option, which in...
## Android
- [Android](https://rubynative.com/docs/android.md): Step-by-step guides for configuring your Google Play Console account, shipping to internal testing, and promoting to the production Play Store.
- [Developer account](https://rubynative.com/docs/android/developer-account.md): You need a Google Play Developer account to distribute apps through the Play Store. Ruby Native uses your account to host your app listing and accept builds...
- [App listing](https://rubynative.com/docs/android/app-listing.md): Google Play Console is where Google manages your app's listing, internal testing tracks, and Play Store submissions. Before Ruby Native can upload a build,...
- [Invite Ruby Native](https://rubynative.com/docs/android/invite-publisher.md): Ruby Native uploads your Android builds using a Google Cloud service account created for your app. To grant the build pipeline permission to upload AABs,...
- [Push notifications](https://rubynative.com/docs/android/push-notifications.md): Configure FCM credentials so your Rails server can send push notifications to Android devices. If you haven't yet, set up the Rails side first.
- [Internal testing](https://rubynative.com/docs/android/internal-testing.md): Internal testing is the fastest Play track. Builds are available to up to 100 testers within minutes of upload, with no Play review. It needs almost nothing...
- [Go live](https://rubynative.com/docs/android/go-live.md): A pre-flight checklist for promoting your app from internal testing to the public Play Store. Ruby Native handles the builds, signing, and uploads; this page...
- [Payments](https://rubynative.com/docs/android/go-live/payments.md): Whether your app needs Play billing is the same decision you make for the App Store, under different rules. Here's where things stand as of August 2026.
- [Data safety](https://rubynative.com/docs/android/go-live/data-safety.md): Google requires every app to disclose what data it collects and how it's handled through the Data safety form. You fill this out in Google Play Console...
- [Submission](https://rubynative.com/docs/android/go-live/submission.md): Ruby Native uploads every Android build to the Internal Testing track. Internal testing skips Play review and needs almost nothing beyond a valid AAB, which...