Hacker News new | ask | show | jobs
by pdimitar 701 days ago
Honestly, why are people so bad at devising two phrases saying who is this for and what problem does it solve?

I don't want to do homework just to know whether this is useful for me. Though it's also probably true that if you have the problem this thing solves you'd recognize it right away. Still, I feel most projects suck at making a proper sales pitch.

1 comments

This is great feedback, I'll strongly consider updating the description to help people make this decision faster.

Would love to get your feedback on this description, is it clear? what is missing:

Hoop.dev keeps sensitive data safe and checks important changes to make sure they're done right. It hides sensitive data in databases automatically and turns repeated tasks into easy, automatic ones. It also helps teams fix problems quickly by connecting with chat tools like Slack and MS Teams.

It's a small improvement but not nearly enough for me at least, as an outsider.

Admittedly I don't know what an access gateway is. So at the top of the README I'd have something like this:

---

- Hoop.dev is an access gateway, which $insert_what_it_does_here (one phrase or two).

- The API for packet manipulation solves $insert_problem_here.

- Hoop.dev is better than $insert_competition_here by doing (insert your feature list that you already have in the README here).