Here I am reading hn on a Droid and boy is it terrible. Text too small. Text poorly wrapped. Buttons misclicked all over the place. So bless you sir. With half a billion smart phones sold in just the last couple of years, this is overdue.
You still need to bump up the fonts on the FP about 2 points. On mobile, favor horsey big usable text over any concession to style.
For some reason I can not zoom on that page on my Nexus One. Is that intentional, and how is it done? I can zoom on other web sites.
I guess links could be bigger - I tend to zoom on web sites to hit the smaller links, and since it is not possible on your page, it might become an issue.
Yes that was some frustration with me too. I do this: if the connection times out (10 seconds) while reading HN, it'll serve the last successful scrape of HN. That's the reason I put the last fetched date on the page, I don't want anybody to be worried that they are receiving a stale version.
The comment pages don't yet serve cached pages if the fetch fails... working on that.
You're welcome. I'm happy to hear that it's useful.
I'm actually using that for a bigger project that I'm working on. While working on it, and having done so HTML processing with it, I realized that it wouldn't take me to long to wire up a mobile version of HN that uses it.
Like Jakob pointed out, I added the ability to pull the text of the linked article, which still needs some tweaking but works for most normal blog/news articles. It really makes articles readable on phones. It's based arc90's readability.
In addition, I added in the ability to read the comments and made them collapsible (like reddit).
But yes, if you only want the list of the front page links, the RSS will do.
I plan on adding more features soon:
-Make comments sortable by date or points
-More extensive caching of the comment pages along with the article text (in case either go down)
-Improve the overall look and feel
Would love to see the text displayed inversely - whether in traditional terminal style (green text on black background) or something similar to arc90's readability style.
Sounds great. I'll be looking forward to the settings update which I assume will be accessible via a different url (versus user controlled setting)? I.e. toadjaw.com/hninverse Again, nice implementation and it's become my default as of now.
Please add proper support for discussion (Ask HN, etc) posts. This is my #1 annoyance of iCombinator. Too many taps and backs to view the question then view the thread.
Done! Ask HN questions now work. You can also get to the "Ask HN" and "New" questions by clicking the link in the header. I'll work on the contrast problem. I noticed it too, I'm just a horrible designer.
It would be very nice someone purchased a more rememberable url... hnmobile.info is available, for example. I guess that would do the trick. No need of a .com tld here.
I really like icombinator but I wanted to address some problems and add new features (View the article text, collapse/expand comments, and return to the previous position when using the browsers back button).
I use a mobile browser (Atomic) which has great support for tabs- therefore I liked icombinator because it would by default open artcle links in a new tab.
Is there a way that you could have an option stored in a cookie that would determine whether or not to open those links in a new tab?
Very excited that you are working on this project and nice work so far!
I fixed the landscape problem. It turns out that adding -webkit-text-size-adjust:none; prevents the text from enlarging when rotating the phone to landscape. Adding that appears to have fixed it.
Looks nice! You should steal my favorite iCombinator feature, though: the Instapaper links. Also, the Article text links all return errors, but I'll take it on faith they produce or will produce in the future some easy to read version of article text.
For the home page, I request the HTML from HN, process it, and create a collection of elements that represent a HN news item: URL, Title, # of comments, ID, Posted By, Date, and so on. Then use that to generate the new HTML. I cache that for 200 seconds and store a copy in the event that I can't read the HTML from HN.
Works just about the same way for the comments , except it adds some additional functionality like collapsing comments. With the nature of comments being nested, a recursive function worked really well on rendering the output.
The article text functionality uses the algorithm from arc 90's readability project, which is in javascript. I used the main idea behind their readability algorithm for this, except mine runs server side (C#) where theirs is all done on the client.
I actually wish the main site stylesheet can be changed so that the white columns on left and right sides does not show up in mobile screen. This will save spaces, make the text bigger and make navigation/zooming easier on small screen.
I just removed it. I was wondering if that would turn people off. Thanks for the feedback. Now that you mention it, I really don't like links opening in a new window/tab either.
You still need to bump up the fonts on the FP about 2 points. On mobile, favor horsey big usable text over any concession to style.