I got told my positioning didn't make sense. Here's what I changed.
A few weeks back I posted Apives here and got some honest feedback — main one being: nobody could tell what "API discovery + testing" actually meant. It sounded like just another directory.
That stung a bit but it was fair. So I spent the last week fixing exactly that instead of adding more features.
What changed:
- Killed the generic "discover APIs" tagline, replaced it with the actual promise: test if an API works before you integrate it
- Added use-case based search — most devs don't search by API name, they search by problem ("I need to send an SMS"), so now you can do that
- Cleaned up the homepage so the live-test feature is the first thing you see, not buried under a directory list
It's a small thing but framing apparently matters more than I thought. Still figuring out a lot — would love more eyes on it if anyone has 2 minutes: [apives.com]
What's a piece of feedback that changed how you talk about your own product?
Trending on Indie Hackers
This is exactly the kind of feedback that changed how I talk about Tokens Forge. When I led with AI research features, people read it as another AI app. The sharper promise is cheaper AI token access with a single compatible API surface, model-route visibility, and clear Credit/RMB ledgers; the trading research agent is a useful free workflow, but not the headline. Framing the homepage around the job users are already trying to do made the product much easier to explain.