Updates · v0.21 · November 17, 2026
Bank connections and multi-step modals
Joe Masilotti
Founder, Ruby Native
This release started with an email. A developer moving an app with Plaid bank connections to Ruby Native asked whether that could work without custom native code. Plaid's mobile SDKs were out, but Plaid also offers Hosted Link, a web flow that needs a secure browser to run.
So Ruby Native 0.21 opens one. And while that developer was moving over, they hit a second gap: their app presented about twenty flows as modals, and Ruby Native only knew about /new and /edit. That's fixed too.
#Connect a bank account with Plaid
Some providers refuse to load inside a web view. Mark the link with data-native-secure-session and your app opens it in the system's secure browser instead:
<%= link_to "Connect your bank", @hosted_link_url, data: { native_secure_session: true } %>
When the provider is done, it redirects to a completion URL. native_secure_session_completion_url builds one that closes the browser and lands people on the page you pick, still signed in. It returns nil outside the app, so browsers keep your existing flow:
hosted_link: {
completion_redirect_uri: native_secure_session_completion_url(return_to: bank_connected_path) || bank_connected_url,
is_mobile_app: true
}
Nothing sensitive comes back through the redirect, so you read the result from Plaid's webhook or API like you already do on the web. It works on iOS and Android, including banks whose own app takes over and hands back through a link on your domain. The secure sessions docs walk through the whole Plaid setup.
#Modals for any page
In Advanced Mode, /new and /edit pages have always slid up as modals. Now any page can. Mark the link that opens it:
<%= link_to "Add player", add_player_path, data: { native_presentation: "modal" } %>
Real flows rarely stop at one screen, though. You search, pick a result, fill in a form, and the later screens arrive by a form submit or a redirect, with no link to mark. Add the tag to those views and they stay in the same modal:
<%= native_presentation_tag :modal %>
The page declares itself, so your controllers can redirect wherever they need to. When the flow is done, redirect_to the record you created and the modal closes behind it. The presentation docs cover the details, including root pages, which now live on the same page.
#Modals people can't close
Some modals have to stay put, like a paywall after a payment lapses or a sign-in page. Add dismissible: false and there's no close button, no swipe down, and no back:
<%= native_presentation_tag :modal, dismissible: false %>
Only your server moves people on, by redirecting to a page without it once they've paid or signed in. Builds from before 0.21 ignore dismissible: false and show a back button, so keep your server-side check until people update.
The close button itself is now your call too. Android has always drawn an X on modals and iOS hasn't, so set modal_dismiss_button under appearance in config/ruby_native.yml to pick one behavior for both. A page can override it with dismiss_button: on the same tag.
#Smaller things
- Text on floating action buttons. Pass
title:tonative_fab_tagto show a label next to the icon, on both platforms. Older builds show the icon alone. The FAB docs have the React and Vue versions. - Centered titles on Android. Set
title_alignment: centerunderappearance.android.navbarto center plain titles like iOS does. Left stays the default, since it's the Material convention. - Your logo stays up at launch on iOS. The launch splash is now on by default, so your icon stays on screen with a spinner until the first page loads, like Android. Set
enabled: falseunderappearance.splashto turn it off. The appearance docs have the details. - More control over the navbar logo. Pass
logo: falsetonative_navbar_tagto show a page's title instead of the logo, and giveappearance.navbar.logoa{ light:, dark: }pair to swap it in dark mode. - Purchases are checked against your bundle ID. Set
ios.bundle_idinconfig/ruby_native.ymland a purchase made for any other app is rejected. It has to match App Store Connect exactly. Without it, purchases still work and your server logs a warning. - Android opens from the last config it loaded. The app starts right away and checks for a newer config in the background, so a server hiccup no longer shows the error screen to people who already use the app.
- Signing in and out on Android lands cleanly. Apps whose login page isn't a modal could load the first page twice after signing in, and signing out from the first tab could freeze the app.
- Sharper Android icons. Icons that fill the whole square no longer show a thin dark edge on phones that crop them to a circle. Your next Android build picks it up.
#Upgrading
There are no breaking changes. A minor version needs one change to your Gemfile, since bundle add pinned you to 0.20:
gem "ruby_native", "~> 0.21.0"
Then update the gem, deploy your site, and build:
bundle update ruby_native
bundle exec ruby_native deploy
Secure sessions and modals both need a new build. On older builds, marked links open in the web view like any other link, so nothing breaks while people update.
One thing to check if you use native_presentation_tag :root: older builds read the first data-native-presentation in the page, and a link marked as a modal counts. Until people update, render the root tag above any marked link, or those builds keep a back button on that page. The presentation docs show how.
See your Rails app on your phone
Try the demo app on your phone, then point it at your own Rails app. It takes a few minutes.
Try Ruby Native on your phoneQuestions, or want help getting to the app stores? Email me at [email protected].