For months, I've been working on Scout without being able to actually see what we’re building in practice. The iOS build we’re iterating on lived on GitHub, and as a non-technical person, I could only rely on screen recordings. My own copy of Scout existed only on the App Store version everyone else uses.
On Monday, I decided to fix that.
Not to ship code. Not to write a single line. Just to get the newer versions of the Scout iOS app running on my own laptop, in Xcode Simulator, so I could open it and see it render.
If you've never tried to stand up a native iOS development environment from scratch, here's the short version: you need Xcode (the easy part), and then you need roughly seven things underneath Xcode that nobody tells you about — Homebrew, rbenv, a specific version of Ruby, CocoaPods, a working scheme configuration, the right branch of the repo, and a willingness to Google error messages that look like someone angry-typed in Klingon.
Each piece took me longer than it should have. If you’ve never opened up your Terminal and want to be quickly humbled, I’d recommend you give it a shot. I hit a wall at Ruby (wrong version). I hit a wall at CocoaPods (permissions). I hit a wall at the scheme (didn't exist on my machine and I had to create it from scratch). I slacked our developer more than I'd like to admit.
Then, somewhere mid-afternoon, the Simulator booted, and there was Scout— the version we’re releasing soon. Running locally. I opened the app on my own laptop for the first time.
Nothing about this was technically impressive. I didn't write code. I didn't fix anything that was broken for anyone but me. A mid-level engineer would have done the whole thing in twenty minutes.
But here's what it unlocked.
I can see what my team sees now. When a developer shows me a screen in Xcode, I can follow the wiring — where that screen lives, how it connects to the rest of the app.
I can poke at things without asking. The class of questions I need to ask just got smaller. That matters a lot at a small company, where every back-and-forth with an engineer is time they're not shipping.
And I proved something I half-suspected: "non-technical" is mostly a posture, not a ceiling. The actual work here was patient back and forth with Claude and a willingness to feel dumb for two hours. Most founders I know would rather do almost anything than feel dumb for a few hours — which is maybe part of why so few of us can actually run our own products.
One of Scout's values is do the harder, better thing. This was that. Not because running Xcode locally is some great feat, but because the easier thing would have been to stay a tourist in my own product. To keep asking devs for screenshots. To keep treating the codebase like something that belonged to other people.
It doesn't. It's mine. And now I can see it.
— Madeline