How to build a Rails app that’s ready for the app stores

Hey friends,A reader asked me a great question this week:Is there a good source for best practices in a Rails app to prepare it for going native?They gave two examples. One small: skipping Turbo to fix an annoying redirect on the web, which then breaks page transitions on mobile. One big: realizing his web app has a dozen top-level paths, but the mobile tab bar can only hold five.I’ve seen this pattern in almost every Rails codebase I review for clients. The code isn’t wrong. It’s just web-first in ways that make the mobile version harder than it needs to be.The good news: most of this is about decisions, not architecture. Make them early and you save yourself a rewrite six months in. This applies whether you ship with Hotwire Native or Ruby Native.Here are the five rules I’d hand to my past self.1. Design your information architecture around 3-5 entry pointsApple’s Human Interface Guidelines and Google’s Material guidelines both recommend 3-5 tabs. In practice, this isn’t a…