Hangar 64 on Android, in one evening
I expected Android to take a week. It took an evening, because most of the work was already done, and the hard parts weren't where I thought.
Hangar 64 started as an iPhone app, and I kept Android for later on purpose. One platform meant one set of phones to test on and one store to deal with. But friends with Android phones kept asking, and at some point "later" needed a date. So at 5 PM one evening I sat down to find out how far Android really was.
Most of the work was already done
The app is built with Expo and React Native, which means one codebase can run on both platforms. Every screen, the Hangar, the Dex and the connection to the database were already shared. Card reading happens on the server, so it doesn't care what phone sent the photo. The app even had an Android name and icon from day one.
So the real question wasn't "how do I build Android?" It was "what did I write that only works on an iPhone?"
Finding the iPhone-only parts
I searched the code for every place that checks which platform it's on. There were only a few:
- Sign in with Apple. It only exists on iPhone, and the sign-in screen already showed it only there. On Android you sign in with Google.
- The year picker. On iPhone, picking a Dex year opens the native menu. Android has no equivalent, and its fallback pop-up shows at most three buttons. That meant Android users would have seen two years and a Cancel button, out of eleven years. I replaced it with a bottom sheet that lists every year.
- Keyboard and spacing. These were already handled for both platforms.
The wall I hit
For iPhone, I test everything in Expo Go, an app that loads my code instantly without a full build. On Android, Google sign-in worked right up to the end, then got stuck on a blank page. Expo Go on Android can't catch the special link that sends you back into my app after signing in. It's a known limit, not a bug in Hangar 64.
The fix was to skip the shortcut and build the real app. Expo's build service made an installable Android file in about 20 minutes. I installed it on an Android emulator, signed in, and Google sent me straight back into the app.
Testing it properly
On the emulator I went through every screen: Home, the new year picker, all four garages, the Dex and its cases, a car page with its series, the scanner and its help sheet, typing a code, and Profile. The emulator's camera only shows a fake room, so the last test had to be real: an Android phone, a real Hot Wheels card, one scan. It found the car.
Android went from "later" to working on a real phone in one evening.
How testers get it
The fastest way to share an Android beta isn't the Play Store. It's a direct install link: testers open it, allow the install once, and they're in. No store account, no review, same night. The trade-off is that updates mean installing again from a new link.
Next, Hangar 64 moves to Google Play's testing tracks, so updates arrive automatically. A new developer account also needs a closed test with at least 12 testers for 14 days before a public launch, so that clock starts soon.