A year ago, I decided to go all-in on solo app development. My goal wasn't just to write code, but to build, ship, and run real products independently.
12 months later, I've built and published 5 separate apps on both the App Store and Google Play. Looking back at the commit history and the download metrics, one overwhelming realization stands out above all else: Building the software was the easy part. Marketing was the actual challenge.
Here are the biggest technical and non-technical lessons I learned from a year of building solo.
Part 1: Development (Where Developers Feel Safe)
When you're a developer, spending 10 hours in VS Code configuring state management or solving native build issues feels productive. It's inside our comfort zone. But shipping 5 cross-platform apps in a single year forced me to drastically rethink how I build software.
1. Build a Personal Infrastructure Arsenal
Building five separate apps back-to-back taught me never to solve the same problem twice. By app three, I had built my own internal boilerplate stack:
- Framework: React Native / Expo (with Config Plugins to automate native iOS/Android code).
- Architecture: Local-first storage (AsyncStorage) to eliminate backend complexity and cloud infrastructure costs.
- Integrations: Pre-abstracted hooks for native integrations like Apple HealthKit, Google Health Connect, and iOS Widgets.
If you are building solo, your velocity is your only leverage. Reusable architecture means you spend 80% of your time on core app value and only 20% on setup.
2. "Local-First" Isn't Just Tech. It's Freedom
Every line of backend code you write is something you have to maintain, secure, and pay for while sleeping. Switching to a strict local-first architecture meant zero database migrations, zero server uptime worries, and instant app performance for users. As a bonus, privacy-focused users love that their data never leaves their device.
3. Perfection is the Enemy of Shipping
My biggest dev trap early on was polishing edge cases before I even knew if anyone wanted the app. By app four, I adopted a strict rule: Ship the core loop first. Polish comes after real users give you feedback.
Part 2: Marketing (The Real Boss Fight)
As engineers, we like to believe in a meritocracy: "If I build a great product, users will naturally come."
They won't. The App Store and Google Play are graveyards of technically superior apps with 0 downloads. Realizing that code is only 20% of the indie hacking equation was my hardest lesson this year.
1. Embracing Organic Distribution (X & Reddit)
As a solo developer without a massive ad budget, I focused entirely on organic marketing:
- X (Twitter) for "Build in Public": Posting code snippets, UI design iterations, milestone screenshots, and technical struggles didn't just attract early users - it connected me with an incredible network of fellow builders.
- Reddit for Value-First Feedback: Reddit is brutally honest. If you drop a direct app link and run, you will be downvoted into oblivion. But write high-value posts breaking down a complex technical problem, and the community responds with incredible feedback and early adopters.
2. "Hidden Marketing" Through Technical Writing
One of my biggest marketing breakthroughs was writing technical case studies about features I built in my apps. Sharing "How I built a unified Apple HealthKit / Google Health Connect hook" on developer platforms served a double purpose: it gave real value to the dev community while naturally introducing my app to people who appreciated well-crafted software.
3. The 50/50 Rule
If I could go back in time to Day 1, I would enforce the 50/50 Rule: spend 50% of your time building the app, and 50% talking about it, writing about it, or improving store metadata. A good app with great marketing will beat an amazing app with zero distribution every single time.
Final Thoughts: The Mindset Shift
Going from a software engineer to a solo creator requires a total mindset shift. You have to stop viewing yourself purely as a "coder" and start operating as a product manager, marketer, designer, and customer support representative all at once.
Building 5 apps in a year didn't just make me a better developer - it completely changed how I look at software.
To all the solo devs currently working in secret: Open up your editor, strip away the non-essential features, ship the app, and start talking about it today.