Thank you very, very much. I will implement all your suggestions over the weekend. I was trying to make the app work with mobile devices, hence, skimpy use of the real estate.
- If you click on the graph you get the definitions.
- if you click at the link below graph is sends you to HN.
- the time is calculated on the client side and it should be Your local time - let me know if it's not the case (JSON data has UTC epoch time, though)
And yes: it is a catch-22 ;-)
EDIT: I don't like clutter on a web page. You can put a lot of information on what is what but you just need it ONE time, then it should go away. Maybe someday I will find a jquery plugin that will do the trick.
One more suggestion: Do label the time zone. even if it correctly detects the user's time zone, that's unexpected on the internet. Plus you don't label 'current' time... for all I know it's a Time Zone ahead but only updates once an hour. Anyway, all confusion goes away with a label.
Edit: Took out references to my personal time zone
Even better, draw a vertical line on the x-offset location of the graph that represents the current time. That will let everyone calibrate to their own time zone intuitively.
On my Nexus S I couldn't scroll at all in either direction, and the right side of the graph was cut off.
Slightly relevant data point of approximated anecdotal evidence: I submitted a "Show HN" for my Android app at about 2 PM on a weekday and got 1 or 2 upvotes within about an hour, so I deleted it and resubmitted it later at about 9 PM (exact same title and everything - I felt bad about resubmitting it but I was really disappointed, sorry if this was a faux pas) and it hit the front page within 5 minutes and hit #1 in about half an hour and then stayed there for 12+ hours. Pretty astounding difference...
- If you click on the graph you get the definitions.
- If you click at the title you get the visual analysis of the data (http://hnpickup.appspot.com/hnpickup_ratio_visual_analysis.p...)
- if you click at the link below graph is sends you to HN.
- the time is calculated on the client side and it should be Your local time - let me know if it's not the case (JSON data has UTC epoch time, though)
And yes: it is a catch-22 ;-)
EDIT: I don't like clutter on a web page. You can put a lot of information on what is what but you just need it ONE time, then it should go away. Maybe someday I will find a jquery plugin that will do the trick.