Building an iOS app after work and learning that feedback matters more than features
I’ve been building a small iOS app after work, and one thing I’m slowly learning is that adding more features is not always the answer.
At first, my mindset was simple:
Build the app, improve the UI, add subscriptions, fix bugs, prepare the App Store page, and then people will understand it.
But after sharing it with a few people, I noticed something different.
Most feedback was not about the code or the design. It was more about:
- Is the problem clear enough?
- Do people understand the value in the first few seconds?
- Is the onboarding too much?
- Is the pricing easy to understand?
- Does the app feel useful before asking for payment?
As a developer, I usually want to solve things by building more. But I’m starting to realize that sometimes the better move is to explain less, simplify more, and listen carefully.
Right now, I’m trying to keep the app small and improve it based on real feedback instead of adding random features.
For other indie builders here:
How do you decide whether to add a new feature or simplify what already exists?
Would love to hear how you think about early feedback.
Posted Jul 9, 2026, 7:45 PM UTC