Edit: Here's the story. We occasionally hear from users who say that all of HN's problems on mobile could be fixed by adding one line of markup:
<meta name="viewport" content="width=device-width, target-densitydpi=medium-dpi">
We tried it several times and found it didn't work [1]. Last night, we tried again. It looked better than before, so we decided to leave it on for a while and wait to hear from you all [2].Unfortunately, what happened is what I feared most: total disagreement. Since it was far from a clear win, we've rolled back to the status quo ante. I'm sorry to disappoint those of you who felt it to be an improvement, but you shouldn't have to wait too much longer.
Why not keep it and improve on its problems, or at least do a poll about it? Because it was at best a stopgap until we can release the real solution we're working on, which involves totally different markup. If the stopgap worked well for most people, it would be worth keeping in the interim. But a stopgap that doesn't actually stop the gap will create confusion. I feel like it's our duty to be conservative here until we have something that actually works. It's a high priority, and it's coming.
1 https://news.ycombinator.com/item?id=7985687, https://news.ycombinator.com/item?id=7330107, https://news.ycombinator.com/item?id=6253835, https://news.ycombinator.com/item?id=6253403, and probably others.
2. https://news.ycombinator.com/item?id=9205798, https://news.ycombinator.com/item?id=9205893, and https://news.ycombinator.com/item?id=9205858.
Do you guys need a web developer or something? It's really not that difficult to make a basic site like HN responsive, and test it out on mobile devices (hint: Chrome dev tools let you simulate most mobile devices).
Also, this thread is going to get voted way up because the title just says HN: Mobile Site. But not necessarily because the op doesn't like it.
Occasionally, I've noticed scrolling performance degrades when viewing comments (only for articles with many comments (>100). But force closing seems to resolve the issue. Otherwise, it's rock solid and beautifully functional.
It actually gets ycombinator page, parses DOM and generates JSON that I can use in my app. I think that might be the reason.
I'm guessing that if the DOM is parsed completely prior to rendering the comments, that shouldn't be a bottleneck--unless the parsing step is re-run as scrolling occurs to render comments dynamically.
Or given that a forced restart resolves the issue, perhaps it's a memory issue; i.e. if the JSON data is held in memory for each article viewed, and it continues to grow. This is certainly not a showstopper, and it's a fantastic app! But figured you'd appreciate the info.
1) It wastes a lot of horizontal space with white paddings on both sides. It may be a stylistic decision but takes valuable space that could be used to show more words in a line, leading to less lines 2) There is no right padding in the text lines, the text touches the right side of the inner container.
All in all it would be better to simply serve the Desktop version, maybe with an slightly increased font size so it is more readable.
And please don't make the same mistake many sites (Slashdot among them) make: trying to ram an ill thought bad designed new version on their faithful userbase just for the sake of change and novelty.
There are things to improve but the best way to determine it is to actually test it beforehand in the same environment it will be used in production. These changes were definitively not tested on iPhone's Safari and it shows.
I agree with the earlier comments you make (re spacing) but this change isn't happening purely for the sake of it. Folks have been asking for a mobile-friendly HN for a long time. Even though I'm not overjoyed with the version I saw today, I'm glad it's progressing.
It is the desktop version with width adjusted.
>> ... new version on their faithful userbase just for the sake of change and novelty. A mobile version of the site has been requested over and over again. So, it is definitely not for the sake of change and novelty.
While it may not be perfect, it is still a better read on my OPO than the earlier desktop version.
I'd be happy to help improve, even working within the constraints of not changing any of the underlying markup. Feel free to message me.
Also what's with the '.rotate180' CSS class in the stylesheet, as much as I love reading upside down, I can't see why thats needed?
The menu doesn't fit the viewport and gets jammed if your username is more than a few characters long (or you have many karma points)
You still need to zoom to hit the up/down arrows, so not much is gained.
The menu even wraps on the iPad in landscape orientation: http://i.imgur.com/4ghJIufh.jpg
width: 100%; // Fixes white borders (browser default table width is normally something like 85%)
max-width: 750px; // Keeps columns from getting overly wide on desktopI do it because I think it maps better to text widths, which is what you ultimately want to prevent getting overly wide. It also handles different font sizes fine, making the site still accessible for people with big system-wide fonts.
I'd like to know, is there a downside to em or a reason to use px instead?
Edit: I take that back. Still unreadably large in portrait.
I don't see any changes to this one to make it responsive either.
And for the people thinking "How does that HackerWeb compare to the web app of Lim Chee Aun?": it's the same as http://cheeaun.github.io/hackerweb/.
This is absolutely awful, how do I fix this?
Edit: I guess that isn't so awful, but before you could see maybe 20% of the links and zoom in as needed. Now it's forcibly zoomed in so much you can only see one link and everything is squashed together.
The new front-page zoom is so pronounced that only seven items are displayed simultaneously (previously around 20 to 25). It is obviously easier to click on article links, but not notably easier to click on comment links or the voting arrows.
The comments page is the real problem. Where I used to see the whole width of the comments page and was able to read without adjustment, the page shows the left half of comments initially and I must zoom out every time.
I don't really want to see any mobile version on my iPad.
[0] User-Agent: Mozilla/5.0 (Android; Mobile; rv36.0) Gecko/36.0 Firefox/36.0)
Why not just use Bootstrap?