How I Learned to Adapt My Feedback Process While Building LoomLetter

When I quietly launched LoomLetter on the App Store, I had a clear goal: get it into as many hands as possible, gather feedback, and iterate quickly.

But there was one major problem—users were signing up, but I wasn’t getting any feedback. I tried everything: personalized emails, in-app messages, brainstorm sessions with ChatGPT Advance Voice Mode, even sent users offers. People claimed the offers, but I still got radio silence.

As a solo indie founder, this was tough. Feedback was supposed to guide my development process, but without it, I felt stuck and unsure of the next steps.

Out of frustration, I turned to Reddit (my indie dev go-to) and shared my struggle. Someone suggested adding a feature request page, and I thought, “Why not?” So I hacked together the simplest UI I could imagine—just a space for users to upvote, downvote, or suggest features.

And then, things finally started to click. Users began engaging, not by replying to my emails, but through the feature request page. They upvoted some ideas, shot others down, and even submitted new requests.

This experience taught me something important: every product attracts a different kind of user. In the past, I worked on products where users loved talking directly to the team, and I thought that was the standard. But with LoomLetter, users prefer a less personal way to contribute—but their input is just as valuable.

This realization was a game-changer. Building a product isn’t about forcing feedback through one channel. It’s about finding how your users want to engage and meeting them there.

Here’s my takeaway: Experiment. Try different methods. Sometimes, the simplest changes (like a feature request page) can unlock the insights you need.

How do you handle feedback from your users? Let’s swap ideas!