Building Popplo in public 🎈
I always had small tasks I kept forgetting to do. A package to drop off, a plant to water, a message I still hadn’t answered.
They were too small for my calendar, but they still took up space in my head.
I also missed the feeling of crossing a task out in a notebook. Ticking a box on my phone never felt as satisfying. And I’ve always loved popping bubble wrap.
So I made Popplo, each task is a bubble inside an illustrated head. When it’s done, you hold it until it pops. It’s a small reward for doing a small thing.
Version 1.1 is live on the App Store.
I was building a different app for RevenueCat Shipaton, but it didn’t make it through App Store review in time. So I entered Popplo in the Design category instead. Results come out near the end of this month. 🤞🏻
Submitted two apps to the App Store! 👩🏻💻
While waiting for review, I’m focusing on organic content.
Made four videos today, but filming and editing took longer than expected. 😩
Any advice on building an organic audience without content becoming a second full-time job?
#buildinpublic
I tried a few different prompt-based AI app builders to build the first version of the app I’m making for RevenueCat’s Shipaton. 👩🏼💻
At first, it felt like the perfect solution.
I’m not a developer, I wanted to move fast, and these tools can turn an idea into something you can actually click through in a very short time.
But once I started building the real product, things got harder.
I wasn’t trying to make a simple MVP with a few screens that worked. I wanted to build an MLP (Minimum Lovable Product.)
For me, that means caring about more than just whether the screens work. I care about the design, animations, transitions, micro-interactions, and all the little details that make an app feel polished and actually nice to use.
And that’s where I started hitting the limits of the builder.
Every small UX change needed another prompt.
Fixing one thing sometimes broke something else.
And every iteration meant spending more credits.
I had already spent around 50 credits, but parts of the onboarding were still broken and the main AI feature wasn’t working properly.
I could keep putting more credits into fixing it, but I realized I would probably spend a lot more just trying to get the tool to match the product I already had in my head.
I still think AI app builders are great for getting a simple MVP out fast.
But if you want more control over the user experience and expect to iterate a lot, they can get expensive very quickly.
So I decided to stop fixing this version and start over with Claude Code.
More work upfront, but hopefully much more control over what I’m actually building.
Now I basically have to rebuild the app from scratch.
Time is running out, and I still don’t have a working app yet. 🫣
Let’s see how this goes.
#shipaton #buildinpublic #SoloDevs #mvp #mobileapp
I’m building an app for the RevenueCat Shipaton.
Days 1–3:
→ picked the challenge
→ researched the audience + competitors
→ mapped the first product flow
→ created the name + brand direction
→ started testing AI app builders
→ tried to enroll in the Apple Developer Program, but the identity verification kept failing, so I had to contact support
(anyone else had this issue? curious how long it took to get resolved 👀)
Trying to build this in public from idea → App Store.
#puildinpublic #shipaton #womenintech #SoloDevs #mobileapp #mvp