Devs who've shipped on Google Play: how did you get through the 12 testers for 14 days rule?
MyBibleSpark is live on iOS. Android is next.
But Google wants a closed test with 12 people opted in for two weeks straight before I can even apply for production
The dinosaur app playbook works, but AI makes the rebuild easy for everyone, not just you
My own app took a few days to prototype with Claude. Yours will too. So will the 10 clones of yours
The part nobody can clone is an audience on X
Flutter vs React Native for MyBibleSpark. Flutter won because almost everything I needed was already built in.
With React Native I'd have been stitching together libraries from a bunch of different devs.
One codebase. iOS is live. Android is next!
Check your .env before you ship. A commented out API key is still a working API key
I left one in mine and someone found it and ran up $12 on my Claude bill before I noticed
Cheap lesson, but moving fast with AI means reviewing what it wrote too
Everyone says find a market first. I built my app for a market of one: me
I wanted to read and study the Bible more, so I built MyBibleSpark, where you answer a few questions and get a verse in seconds
5 App Store rejections later, it's live!
No guessing what the user wants
Dinner and an empty Claude code window. My favorite part of building is right before the first prompt
Stop switching tasks while you code. Every switch costs you the focus you just built
Heard that in a talk at Devnexus 2024 in Atlanta. Still think about it
I wonder if AI makes it worse. Prompt Claude, grab your phone while it works and come back with no idea what you asked 😅
Nobody tells you how strict Apple's App Store review is until you're the one getting rejected.
My app MyBibleSpark got rejected 5 times.
One reason was the "Sign in with Apple" button was missing the Apple logo 🤡
The review took 2 to 3 weeks. The prototype took a few days 😅
Nothing like realizing you shipped your code with an API key commented out and someone chose to use it and run up your Claude bill 🙃
Nobody tells you coding with AI is like managing a senior dev who can't think abstractly.
10 clear steps? Done before your coffee is.
Ask for the logo in the upper right corner and you'll get it in 5 seconds but in the wrong size, because the bot has no idea what the page is for.
The plan is your job. Prompting takes skill
I wonder if AI looks back at old code from like six months ago and think, “ugh what was I doing?” like us humans do
Programming with AI is like working with a senior dev who can't think abstractly. They are really good at executing tasks. Give them a list of instructions and it's done at lightning speed. But they can't understand at the human level what is being done.
For example when I say, "Place the text in the upper right corner." The bot will do it but it may not be exactly how you personally want it. Which is why writing good thought out prompts with details and actual knowledge of what you're doing is key to maximizing AI




