Earlier quoted context omitted.
Please, on #hnmain: width: 100%; // Fixes white borders (browser default table width is normally something like 85%) max-width: 750px; // Keeps columns from getting overly wide on desktop
I usually specify my max-widths in em (empirically found the sweet spot at about 40-60em). I 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?
Ask HN: Mobile site
71–78 of 78 posts
Re: Ask HN: Mobile site
#72I've been using http://hn.premii.com with great success. Super slick UI and runs great as a full screen Chrome app. Missing features are adding comments and upvotes, but it provides direct link to real HN comments page where you can do that instead. Their Android app is good too, but web client feels faster on my phone.
Re: Ask HN: Mobile site
#73I've been using http://hn.premii.com with great success. Super slick UI and runs great as a full screen Chrome app. Missing features are adding comments and upvotes, but it provides direct link to real HN comments page where you can do that instead. Their Android app is good too, but web client feels faster on my phone.
Feels very heavy on Firefox in Android.
Re: Ask HN: Mobile site
#74I've been using http://hn.premii.com with great success. Super slick UI and runs great as a full screen Chrome app. Missing features are adding comments and upvotes, but it provides direct link to real HN comments page where you can do that instead. Their Android app is good too, but web client feels faster on my phone.
Author here: You can download iOS/Android app too. It supports upvoting. https://itunes.apple.com/us/app/hacker-news-yc/id713733435 https://play.google.com/store/apps/details?id=com.premii.hn
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.
Re: Ask HN: Mobile site
#75Earlier quoted context omitted.
Author here: You can download iOS/Android app too. It supports upvoting. https://itunes.apple.com/us/app/hacker-news-yc/id713733435 https://play.google.com/store/apps/details?id=com.premii.hn
I just wanted to extend my appreciation for your work. It's by far the most used app on my iPhone; even occupying a spot on the main navbar. 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.
Re: Ask HN: Mobile site
#76Earlier quoted context omitted.
I just wanted to extend my appreciation for your work. It's by far the most used app on my iPhone; even occupying a spot on the main navbar. 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.
iPhone 4s/5? I have 5s, and didn't notice that, but I also mostly use my Android device. 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.
Re: Ask HN: Mobile site
#77I use HackerWeb ( http://hackerwebapp.com ) on both my iPhone, iPad and Fire Phone (Firefox OS). It is a superbly executed HTML5 application.
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/.
Re: Ask HN: Mobile site
#78I posted about this three times last night before going to sleep, feeling sure that the info would get into circulation. Apparently not! Will explain shortly. 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: We tried it several times and found it didn't work [1]. Last night, we tried again. It looked better than before, so…
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).