4 ms·
Don't bother with a landing page. I'm guessing that most visitors bounce right off it. Put the functionality on the home page, with a small amount of explanator
by joshwa 16y ago
Don't bother with a landing page. I'm guessing that most visitors bounce right off it. Put the functionality on the home page, with a small amount of explanatory text.
What do you need to do?
<< I need to _____ which will take me _____ <b>Remember</b> >>
When you have some time, tell us how much, and we'll give you something to do:
<< I have ___ available right now. <b>Give me something to do</b> >>
((grayed out until you've entered something above))
Also I'd recommend bolding the important text as indicated above-- users scanning the page will be able to at a glance exactly what the app offers. The arrows as buttons feel too much like hierarchical navigation (esp on the top navbar) and it isn't clear that I should be clicking them).
- famfam 16y agoI've definitely seen the light on the homepage thanks to you guys. (BTW, the bounce rate on '/' is 50% and time on page is 2 minutes. That's actually not too bad I think. But point is still taken. The homepage looks bad even to me now.) I'm not convinced I want to kill the home/landing page. I think it could still serve a purpose, just with extreme optimization. I could see putting something actionable on there (entering your first todo). Then of course at the extreme end is your idea. I'll have to think about this pretty hard. Maybe even A/B test it. I think the point about arrows as buttons is a really good one. I haven't seen any metrics that people aren't acting on them, but I think your intuition is spot on that you lose these kind of stand-out action verbs that reinforce what the app is all about. I think I just overdid it on trying to keep the design "slick" rather than abiding by long-standing conventions. Thanks for the feedback!