In January 2026, I officially launched Flowstate Industries. No funding, no employees, no office—just me, my Mac, and a belief that I could build software worth using. This is the story of how I got here and what I've learned along the way.
Going Solo in the Age of Funded Startups
The default path for starting a tech company involves pitch decks, investor meetings, and equity negotiations. You're supposed to raise a seed round, hire quickly, and chase hockey-stick growth.
I chose a different path.
Bootstrapping a solo software company in 2026 might seem contrarian, but it's actually increasingly viable. The tools available to individual developers today—Swift, Xcode, cloud services, AI assistants—would have required entire teams just a few years ago.
More importantly, staying solo aligns with the kind of company I want to build. No investors means no pressure to prioritize growth over user experience. No employees means every decision reflects my values. No runway means building sustainably from day one.
This isn't the right path for every business. But for building thoughtful, privacy-focused apps? It's ideal.
From Idea to First Launch
Worldly started as a personal frustration. I wanted to track my travels without creating another account, syncing to another cloud, or trusting another company with my location data. Nothing on the market met that simple requirement.
So I built it myself.
The first version took several months of nights and weekends. iOS development with SwiftUI has a steep learning curve, but it rewards investment. Once you understand the platform, building native apps that feel right becomes surprisingly achievable.
The hardest part wasn't the code—it was scope management. Every feature spawns three more feature ideas. Learning to say "not yet" to good ideas is essential for actually shipping.
I launched Worldly in early 2026 with core features:
- Track countries, states, and cities
- Visualize travels on an interactive 3D globe
- Store trip photos as a visual journal
- Five different map visualization styles
Everything else could wait. The goal was to get something useful into people's hands, learn from real usage, and iterate.
The Reality of Running a One-Person Company
Running Flowstate Industries means wearing every hat: developer, designer, marketer, support rep, accountant, legal counsel, and janitor. Some days I write Swift. Other days I answer support emails. Sometimes I'm filing business paperwork while waiting for builds to compile.
Here's what a typical week looks like:
Development (40-50%): Building features, fixing bugs, refactoring code. This is the core work and what I protect most aggressively.
Design (15-20%): UI work, user research, planning new features. Design and development blur together with SwiftUI—you're often doing both simultaneously.
Operations (15-20%): Business admin, legal compliance, finances, app store management. Necessary but not directly valuable to users.
Marketing (10-15%): Writing (like this post), social presence, ASO. I deliberately keep this minimal—the work should speak for itself.
Support (5-10%): Answering user questions, investigating bug reports. Actually one of my favorite parts—direct user feedback is invaluable.
The ratio varies wildly week to week. Some weeks are pure development. Others disappear into admin work. Finding rhythm takes constant adjustment.
Lessons Learned in Year One
1. Ship Early, Iterate Constantly
My perfectionist tendencies wanted to polish forever. Reality demanded I ship. The apps I was embarrassed to release became the foundation for everything that followed. Users are surprisingly forgiving of rough edges if the core value is solid.
2. Constraints Enable Creativity
Limited time forces prioritization. Limited resources prevent over-engineering. Being unable to do everything means doing the most important things well. What felt like disadvantages became advantages.
3. Revenue from Day One Matters
Charging for Worldly Pro from launch—even when downloads were tiny—established the business model early. It filtered for users who valued quality over free. Those early customers provided feedback that shaped the product.
4. Marketing is Showing Your Work
I dreaded "marketing" as a concept. What works for me is simply showing what I'm building and why. Blog posts about the process, behind-the-scenes details, honest discussions of tradeoffs. People interested in thoughtful software find their way here.
5. The App Store is a Mixed Blessing
Apple's ecosystem provides distribution, trust, and payment processing. It also takes 15-30%, enforces opaque rules, and gates access to your own customers. Understanding this tradeoff helps calibrate expectations.
Advantages of Being a Solo Founder
After months of solo operation, I've come to appreciate unique advantages:
Speed: Decisions happen instantly. There's no meeting to schedule, no stakeholder to convince, no process to follow. See a bug? Fix it. Have an idea? Prototype it. Ship updates on your timeline.
Focus: No communication overhead. No context switching between managing people and doing work. Deep focus for hours at a time is possible because nothing interrupts it.
Alignment: Every choice reflects your values. No compromises to appease investors, partners, or team members with different priorities. Build exactly what you believe should exist.
Learning: Handling every aspect of the business means learning every aspect of the business. Marketing, legal, finance, design—you understand the whole system, not just your piece.
Sustainability: Low overhead means low revenue requirements. Profitability becomes achievable at scales that would bankrupt venture-backed companies. Survival doesn't require exponential growth.
Advice for Aspiring Indie Developers
If you're considering the solo path, here's what I'd tell my past self:
Start before you're ready. The perfect moment doesn't exist. Begin with what you have, learn as you go.
Choose a problem you personally have. You'll be more motivated to solve it, more qualified to understand it, and more capable of judging solutions.
Ship something small first. Grand visions collapse under their own weight. Build a small, useful thing. Make it excellent. Then expand.
Charge money early. Free users behave differently than paying customers. Build for the audience you actually want.
Protect your development time. Admin work expands to fill available hours. Block time for building and defend it ruthlessly.
Connect with other indie developers. The solo path doesn't mean isolated. Communities like the iOS developer community offer support, advice, and camaraderie.
Play the long game. Overnight success is a myth. Sustainable businesses are built through consistent effort over years. Focus on showing up every day.
Looking Forward
Flowstate Industries is still early. Worldly continues to evolve based on user feedback. New app ideas are brewing. The foundation is solid, and the path forward is clear.
Being a solo developer in 2026 isn't easy, but it's more possible than ever. The tools are better, the distribution is available, and there's a growing audience of users who want alternatives to the venture-funded surveillance economy.
If you're building something similar, reach out. The indie developer community is stronger when we support each other. And if you're considering starting—do it. The world needs more software built by people who care.