Hacker News new | ask | show | jobs
by tlow 2722 days ago
Putting a log in requirement to even see what your app does may provide a filter on usage that you don't want.

While there may be advantages, I think you'd be hard pressed to overcome the drop off from potential users who will bounce.

Furthermore, you're not delivering a clear value proposition "JOIN THE CONVERSATION you're invited to our dinner party beta". And then you have an ambiguous call to action "start login". At no point are you giving the potential user a reason to even want to login. And then you're asking the user to overcome an email signup and confirmation flow before they even get to see what your product does. Consider the case where the product isn't what the potential user thought it was, now you've wasted their time, what good is their email signup?

Why not go for a progressive engagement flow? You can still require accounts, signup and login for continual use. However you could engage the user first, then make your email signup ask. Wouldn't that be more advantageous?

2 comments

Just an update, couple things:

I took your feedback and added a guest login to the site to help reduce the bounce. I've also updated the banner with a better 1-liner about the platform.

So now dinnertable.chat has a simple progressive engagement flow, although it can still be polished a lot... but I'm hoping this will help.

Thanks again for all your feedback, and please do let me know if you have more! :]

The entry page needs a little work, particularly the top banner as you pointed out. It's a challenge and a delicate balance. I tried to provide as clear of an explanation on the front-page... do you feel you learned of the value proposition by reading the rest of the page below the banner? I do like the idea of a progressive flow, but the tricky thing is reducing bots/trolls (+banned accounts) from entering back into the live debates.
Not OP, but I thought the body of your landing page did a good job explaining it. However as you suggest the top banner / header could be more impactful.

Ive recently been referring to this [0] landing page guide and one helpful principle is that, for banner header copy to be good, the reader should be able to know exactly what your product is by reading only your banner header

[0] https://www.julian.com/guide/growth/landing-pages