Three Apps in Thirty Days, With a Day Job

In thirty days I put three apps on the store while holding down a full-time job. The Nice List, a Christmas gift planner. Mileway, a college-prep planner for families. Pit Stop, a car-maintenance app, right behind them in review. I want to tell you what that actually took, because the honest version is more useful than the highlight reel.

First, the part nobody tells you: the building was never the hard part. Each app is a single-file web app wrapped to ship natively — no heavy framework, no clever architecture, vanilla and boring on purpose. My AI partner writes the boilerplate; I make the calls. The scarce resource wasn't code. It was decisions, taste, and the willingness to hit submit before it felt ready.

What broke — every time — was the last mile. Apple rejected The Nice List on its first full review for a design guideline, and the cited reason ("text overlapping the status bar") turned out to mean an in-app progress bar, not the iOS status bar — you only learn that by opening the reviewer's screenshot instead of arguing with the words. Fixed it, resubmitted, approved same day. Pit Stop had a paywall that showed prices but didn't actually charge — an automatic rejection — so I made the call to ship it free now and add real subscriptions later, grandfathering the early users. And at least twice Xcode died on the export step with an empty error log; the fix is dumb and reliable (quit, clear the cache, clean, re-archive). None of that is in a tutorial. All of it is the job.

What never mattered: the things I used to agonize over. The perfect framework. A clever backend. Pixel-chasing a screen no one would scrutinize. Every hour I'd have spent gold-plating, I spent shipping the next thing instead. Polish is real, but it's a finishing pass, not a starting condition — and most "polish" is just fear wearing a nicer outfit.

Here's the cadence that made thirty days possible. One pipeline, reused: build the web app, wrap it, write the store listing, make the screenshots, submit. The second app was faster than the first because the pipeline was already paved. The third was faster than the second. That's the whole trick — you're not building three apps, you're building one machine that ships apps, and then you run it.

I'll be straight about the scoreboard, because this journal is the receipts and not the brochure: the downloads so far are small. Early-days small. A free app earning literal cents from a search-ad attribution, a paid one finding its first handful of buyers. Shipping is step one, not the finish line — distribution is the actual mountain, and that's a different Build Note. But you cannot distribute what you haven't shipped, and most people never get past the shipping. I did, three times, in a month, at night, with a partner that doesn't sleep.

The lesson I'd hand my younger self: lower the bar for starting and raise it for finishing, then ship on a metronome. The apps that exist beat the apps that are perfect in your head. Mine are on the store. Yours could be too.

One person. One machine. Three apps. Thirty days.

— MG