Last week I put four iOS apps, a macOS app, and an annotated Kindle classic into review queues. Solo. Total revenue so far: zero dollars — with one asterisk we’ll get to.
These are the notes from that week, written while most of the verdicts are still out — the timeline, the workflow, and what it cost me in lessons, if not in dollars.
The week, day by day
Wednesday — Cloister Ink for Mac submitted to Apple. $29.99, one-time.
Thursday — its iOS twin submitted. Both platforms shipped in about 30 hours.
Friday — Manresa (an iPhone + iPad journal) torture-tested and submitted in a single day. Retablo, a sacred art app, resubmitted the same night after a rejection round.
Saturday — ChartKeep 2.0, a family health-records app, submitted. Same day: built a complete annotated ebook — the Baltimore Catechism, with sixteen restorations of the original 1921 text that the modern reprint silently revised. Every restoration verified against page images.
Sunday — wired the newsletter machine you’re reading right now: signup automation, welcome email, the works.
Also submitted midweek: True Devotion to Mary (Annotated). And here’s the first plot development since these notes began — Amazon said yes. It went live on Kindle this Tuesday at $2.99. The studio’s first live product. The other five verdicts are still out.
Notice the shape of that list. It accelerated. That’s the actual story of the week.
Why it accelerated
Here’s the honest version, because the mythical one is a lie of omission: my first app took three days to build. Building was never the bottleneck.
What that app then did was lose five consecutive builds to App Store privacy-manifest rejections. Five archives, five uploads, five multi-day review waits — each one flying blind, because Apple tells you what failed, not what else is about to fail. The fix turned out to be one file. The failure tax cost several times more than the build did.
This week, the failure tax is what disappeared. Those five rejections became a pre-flight reviewer that simulates App Store review before anything gets archived. The book lane got its own reviewer that audits copyright clearance and formatting before upload. Every mistake becomes a checklist the next build runs automatically, and checklists don’t forget.
Proof it works isn’t zero rejections — one app still caught a real one this week. Proof is that it was diagnosed, fixed, and resubmitted the same night. The loop went from days to hours. Build speed stayed the same; the system around the build is what compounded.
The workflow
Three words: create, validate, ship.
Create the smallest version that’s actually real — not a demo, not a deck. A thing.
Validate it by hand before automating anything. If the manual version doesn’t survive contact, the automated version just fails faster.
Ship it into a queue, and start the next thing while you wait. Review queues are dead time you can’t compress — but you can overlap them.
Underneath all three: write every decision down, dated, in a file the next session reads first. Tomorrow-you should never relitigate what today-you already ruled on. In other words, what bit you today shouldn’t bite you again tomorrow. Codify it, frame it, hang it on a wall, or set it on your desk. Those are the bones of the acceleration, every lesson learned becomes a launchpad for the next creation.
Money, briefly
I keep a full ledger — every dollar in and out — but I’m keeping the numbers private for now. Three lessons from it are worth passing on anyway:
Domains quietly renew at two to three times the year-one price, with auto-renew on by default. Free trials auto-bill the moment they end — the day I start one, the end date goes on the calendar. And a $29.99 app is roughly $21 after the platform’s commission, before taxes. Year-two math is the real math; year-one pricing is marketing.
Sunk costs: those five lost builds were tuition. You pay tuition once — if you write down what it bought. I write everything down.
The pitfall that actually bites
It isn’t failure. It’s phantom success.
I once logged an app as “submitted” when the click never took — the confirmation I expected never came. Days lost before anyone noticed. The house rule that came out of it: a milestone is a status you verify on a fresh reload, never an effect of your click. That rule has caught real misses since, including one this week.
The honest bottom line
This newsletter has three subscribers. All three are me — two are test aliases from wiring the signup automation.
And the one product that’s already live? It has exactly one sale. It was me — I bought my own book to verify the buy flow end to end, which means the studio’s entire gross revenue is $2.99 of my own money, most of which Amazon keeps. That’s the asterisk. Revenue from people who aren’t me: zero. A live listing isn’t revenue; it’s a storefront with the lights on.
That’s what day one actually looks like. Everyone you follow started at “all three are me.” They just don’t show you.
The verdicts
The rest land this week. Apple has five apps, and statistically at least one comes back with a rejection. Amazon already said its yes. I’ll publish the real numbers either way — prices, platform cuts, first-day sales, including zeros. If it flops, you’ll see the flop.
— Christopher
P.S. — I’m building a writing app called Cloister Ink: one quiet place for everything you write, AI only when you ask. If that sounds like your kind of tool, the waitlist is at nexusbuilds.io/editor — and waitlist members get this letter’s build log of the app itself, decisions and mistakes included.
One question before you go: what’s the trap that cost you the most time this year — the silent failure, the auto-renew, the rejection loop? Hit reply. I read everything, and the best answers shape next week’s issue.