Ruby on Rails to App Store Without Swift: The Dirty Secrets

So, you want to ship a Rails app to the App Store. Great. You'll try responsive design, PWA, Hotwire Native, and native Swift – a classic "let's try everything" approach that ends with "well, at least it works."

If you've ever tried to befriend Rails with iOS, you know the pain: it's like assembling IKEA furniture without instructions – all parts are there, but how they fit together is a mystery. The author went through all four paths and honestly shared which rakes hurt the most.

Here's the gist:

• Responsive design – sounds cool, but in practice, the web view looks like a website from 2005, just squeezed into an iPhone.
• PWA – almost perfect until the user tries to send a push notification. Then iOS goes: "I don't know you, go away."
• Hotwire Native – fresh breeze, but requires dancing around native bridges.
• Native Swift – well, you know. It's like rewriting everything from scratch, but in a language you learned last week.

In the end, the author chose a hybrid approach: Rails on the backend, Turbo Native on the frontend, and minimal Swift code. Sounds like a compromise, but it works. The main lesson: don't try to build the "perfect native app" when you can build a working one.

METABYTE studio comment: We love Rails too, but when a client asks for "like Instagram," we have to explain that Hotwire isn't magic – it's just a convenient crutch. As long as the crutch doesn't break on day one of production.