Indie devs ask what still hurts in AI coding tools
A small team has been building a new tool for almost a year. They now think they spent too much time guessing what need instead of asking real users earlier.
They are asking people who use every day to describe the exact moments when those tools got in the way. The main questions are what happened, what was annoying, what makes day-to-day coding hard, and where tools slow people down or fail to understand a project.
They also want to know what extra steps, workaround habits, or other tools people keep open to deal with those problems. Their concern is that many feel too heavy, too expensive, and too tied to the cloud.
Key points
- An indie team has spent almost a year building a new tool.
- They want direct feedback from people who use every day.
- They are asking for real moments when the tool blocked or slowed coding work.
- They care about project understanding, extra steps, workaround habits, and companion tools.
- They see current tools as heavy, costly, and too dependent on the cloud.