31–40 of 59 posts
That doesn't make it a low priority (it's a high priority), but it means we have to do it as a background process.
Visiting /comments when someone has left a post with a very long unbroken line will break the site.
Browsers are oddly broken for mobile. Here's what text entry looks like on Chrome for iOS - http://imgur.com/gjLdS6A
I've found this site as one of the easier to use ones on mobile?
Hacker News does not have a responsive layout, which is generally what is considered "mobile friendly" in 2015.
In the meanwhile, this is super mobile and tablet-friendly: http://cheeaun.github.io/hackerweb/ I've been using it for more than a year now and I nearly never visit it Hacker News directly on mobile.
Have a look at this too - http://hn.premii.com/
There is a ton of HN apps on Android, but all I want is the ability to post comments, post stories, and possibly support the Android share API so I can just send URLs to HN directly from Chrome.
My flow is - I go through the submissions in a page, and when I like one, most of the time I open the story and its comments page both - in separate tabs. I read the story first and the switch to the next tab to read the comments. When I have completed all the tabs, I go to the next HN page. In mobile it's pretty cumbersome to navigate among tabs.
I seldom use the mobile site, I find the HN reader app by premii[1] the best suited for me.
[1] https://play.google.com/store/apps/details?id=com.premii.hn
Earlier quoted context omitted.
Making a one-column text-only website work on mobile is trivial with a meta tag and a few lines of CSS.
There are two columns: one for the text and one for the vote buttons. Does that affect your version? (What are those few lines of CSS btw?)
These max-widths etc. can be different based on available screen width: https://css-tricks.com/css-media-queries/
The meta tag can be used to set viewport width to device screen width. Without it, the mobile browser doesn't know what minimum screen width the webpage requires, so it assumes 800px (or 1024px), because rendering a random website with viewport width of 240px is not a good idea even in 2015.
My point is, browsers should be doing what the website code tells them to do. Websites that display nicely on desktop computers usually display fairly nicely on mobile as well. But HN shows 20-30 words per line on desktop, which is... suboptimal for readability, so it's only expected that mobile browsers produce similar results.