DEVELOPER STORIES

Creating an app as a solo developer can be highly rewarding, but it can also be a huge undertaking.

Frederik Riedel helps people spend less time on social media with his app OneSec. His friend Leo Mehlig created the daily planner Structured to ensure he took enough breaks. And former lawyer Kai Koch changed gears to become co-founder of the emotions coach Ahead.

We talked to all three about how they become app developers and the lessons theyve shared with others along the way.

Mehlig: I started coding when I was 14 years old, and met Frederick shortly after. We were both WWDC Scholarship winners (the precursor to the Swift Student Challenge), so I was meeting Apple engineers and other developers. I wanted to be part of that community.

Riedel: I'd always thought of creating apps as a hobby or a side project. Meeting professional developers motivated me to continue on that path.

Koch: I went into app development because you can build very large products both in terms of impact and revenue with very small teams.

Mehlig: I did everything in the beginning: design, coding, customer support, and marketing. It took me almost three years to have my first employee.

Riedel: The biggest struggle when you work on your own is when something doesnt work and you cant figure out why. I always try to build apps that are somehow related to myself, so they either solve a problem or are related to a hobby that I have. It helps to have a relationship with your project.

Mehlig: A great challenge for an indie developer is the limited amount of time, especially if youre working on your own or with a small team. You have to focus on whats important. The product becomes more focused, which in the case of consumer apps is usually a good thing.

Koch: The beauty and the crux of a small team is that you have to focus on the things that have the highest impact.

Mehlig: Ive built an app that reminds you that you have a limited amount of energy. When Im not focused, I try to stop working and go outside. I like going for a run, then coming back to fix a bug.

Riedel: You have to be very honest with yourself. If you notice that something doesnt make sense or youre not able to build something useful, you have to cut the ropes and start something new.

Mehlig: If something doesnt work, it doesnt mean that you did something wrong or youre a bad developer. Failure can be good as long as you learn something from it.

Originally published June 9, 2025