Monthly Deep Dives
Here’s where I cover the trickiest parts of building real Hotwire Native apps.
Each deep dive tackles a problem that almost every project runs into, things like push notifications, authentication, and other deceptively simple features that only sound straightforward. Instead of scattered notes or hand-wavy explanations, you get a complete walkthrough from first principles to production-ready code.
Every article is long enough to be genuinely useful but focused enough to save you hours (or days) of trial and error. Each is packed with code, context, and the hard-won insights I usually only share with clients.
My goal is to give you the confidence to ship faster, avoid the pitfalls, and understand how these pieces really fit together in Hotwire Native apps.
Hotwire Native deep dive: In-app purchases on iOS
If you’re selling digital content or subscriptions in your iOS app, Apple requires you to use in-app purchases. No way around it. And for Rails developers, this is one of the trickiest features to build: you need native Swift code to talk to StoreKit, webhook handlers to process Apple’s notifications, and a way to sync it all back to your server.
Hotwire Native deep dive: Native Polish
Over the years, I’ve noticed that the biggest UX wins in Hotwire Native apps come from the smallest changes. Not fully native screens or even bridge components. Just small, intentional decisions that make your Rails views feel at home on iOS and Android.
Hotwire Native deep dive: Push Notifications
Native push notifications are tricky because there's a ton of moving pieces to get right. Here's my step-by-step process to get them working in your Hotwire Native apps.
Hotwire Native deep dive: Authentication
Hotwire Native brings your mobile-web friendly Rails app to iOS and Android with just a few lines of code. And without any additional configuration (or even native code!) you get a lot for free.