<p>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.</p>
<p>12 months later, I’ve built and published <strong>5 separate apps</strong> on both the <strong>App Store and Google Play</strong>.</p>
<p>Looking back at the commit history and the download metrics, one overwhelming realization stands out above all else: <strong>Building the software was the easy part. Marketing was the actual challenge.</strong></p>
<p>Here are the biggest technical and non-technical lessons I learned from a year of building solo.</p>
<h2>Part 1: Development (Where Developers Feel Safe)</h2>
<p>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 <em>how</em> I build software.</p>
<h3>1. Build a Personal Infrastructure Arsenal</h3>
<p>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:</p>
<ul>
<li><strong>Framework:</strong> React Native / Expo (with Config Plugins to automate native iOS/Android code).</li>
<li><strong>Architecture:</strong> Local-first storage (AsyncStorage) to eliminate backend complexity and cloud infrastructure costs.</li>
<li><strong>Integrations:</strong> Pre-abstracted hooks for native integrations like Apple HealthKit, Google Health Connect, and iOS Widgets.</li>
</ul>
<p>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.</p>
<h3>2. “Local-First” Isn’t Just Tech. It’s Freedom</h3>
<p>Every line of backend code you write is something you have to maintain, secure, and pay for while sleeping. Switching to a strict <strong>local-first architecture</strong> 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.</p>
<h3>3. Perfection is the Enemy of Shipping</h3>
<p>My biggest dev trap early on was polished edge cases. I spent days perfecting not important things or handling niche error states before I even knew if anyone wanted the app. By app four, I adopted a strict rule: <strong>Ship the core loop first.</strong> Polish comes <em>after</em> real users give you feedback.</p>
<h2>Part 2: Marketing (The Real Boss Fight)</h2>
<p>As engineers, we like to believe in a meritocracy: <em>“If I build a great product, users will naturally come.”</em></p>
<p><strong>They won’t.</strong> 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.</p>
<h3>1. Embracing Organic Distribution (X &amp; Reddit)</h3>
<p>As a solo developer without a massive ad budget, paid acquisition wasn’t an option starting out. I focused entirely on <strong>organic marketing</strong>, primarily across <strong>X (Twitter)</strong> and <strong>Reddit</strong>.</p>
<ul>
<li><strong>X (Twitter) for “Build in Public”:</strong> X became my lab notebook. 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.</li>
<li><strong>Reddit for Value-First Feedback:</strong> Reddit is brutally honest. If you drop a direct app link and run, you will be downvoted into oblivion. But if you write high-value posts, breaking down a complex technical problem you solved or sharing genuine lessons from your journey, the community responds with incredible feedback, constructive criticism, and early adopters.</li>
</ul>
<h3>2. “Hidden Marketing” Through Technical Writing</h3>
<p>One of my biggest marketing breakthroughs was writing technical case studies about features I built in my apps. Sharing <em>“How I built a unified Apple HealthKit / Google Health Connect hook”</em> 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.</p>
<h3>3. The 50/50 Rule</h3>
<p>If I could go back in time to Day 1, I would enforce the <strong>50/50 Rule</strong>: 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.</p>
<h2>Final Thoughts: The Mindset Shift</h2>
<p>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.</p>
<p>Building 5 apps in a year didn’t just make me a better developer, it completely changed how I look at software.</p>
<p><strong>To all the solo devs currently working in secret:</strong> Open up your editor, strip away the non-essential features, ship the app, and start talking about it today.</p>


Terminal

Vladislav Siumbeli

A solo developer reflects on shipping 5 mobile apps in 12 months across iOS and Android, sharing lessons from both the technical and marketing sides. On the dev side: building a personal boilerplate with React Native/Expo, adopting local-first architecture to avoid backend overhead, and shipping core loops before polishing. On the marketing side: the biggest revelation was that great code alone doesn't drive downloads. Organic distribution via X and Reddit, technical writing as hidden marketing, and a 50/50 time split between building and promoting are the key takeaways.

5 Apps in 12 Months: Building Was Easy, Marketing Was the Real Boss Fight

<p>Agree, though I’ll be honest — I’m still very much in the middle of this, not past it.</p>
<p>Built cloudrift, an open-source AWS waste-scanner CLI, solid architecture from day one. Spent the last while pushing distribution: Show HN, FinOps/DevOps Discord communities, PRs into awesome-lists, writing about specific technical decisions instead of link-dropping. And… it moved the needle some, but not nearly as much as I hoped. No paying users yet, and the name turned out to be more crowded/hard to search than I realized too late.</p>
<p>Code really was the easy 20%. Still figuring out the other 80% in real time, no clean lesson to hand out yet.</p>


<p>Did u forget to mentioned the apps?</p>


<p>I like the spirit of never giving up and the journey was impressive, Hope you get the best out it.</p>
