I've been reading about landing pages for my project, and the standard formula is apparently to place that front-and-centre, with what your product actually does second. So often, though, it seems like they're so eager to tell you how brilliant the product is, they forget to tell you what it actually does.

And maybe that appeals to some people? I went with "Learn a language while you browse the web" for https://nuenki.app, and interestingly I have much more success from HN readers (technical people who may be interested in languages) than people from Reddit's language subreddits (interested in languages, generally not technical).

So I wonder if it's a difference in attitudes based on different groups. The hacker news crowd is asking "What have you built?", and intend to work out whether they think it's worth it once they know what you made, while reddit users go "How can this help me?".

Perhaps I should create a second landing page, a/b test it, and collect some stats.

Edit: I'm anecdotally noticing that the "Social proof!" (testimonials) I added yesterday seems to have hurt conversion if anything. I'm not convinced of the standard advice here... definitely worth getting some data on.

Same with some projects' readme.md: it will have a change log and a few random details, but it doesn't tell me what it does.

Yeah, product websites have turned into pharmaceutical ads. "Ask your doctor about Blogprexa!"