5 ms·

I've been using http://hn.premii.com http://hn.premii.com with great success. Super slick UI and runs great as a full screen Chrome app. Missing features are ad

by ctrlrsf 12y ago

I've been using http://hn.premii.com 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.

anonbanker 12y ago
Feels very heavy on Firefox in Android.
- thekingshorses 12y ago
  Yes. Main problem is scrolling is not smooth. I told Mozilla mobile folks, but they think its smooth.
thekingshorses 12y ago
Author here: You can download iOS/Android app too. It supports upvoting. https://itunes.apple.com/us/app/hacker-news-yc/id713733435 https://itunes.apple.com/us/app/hacker-news-yc/id713733435 https://play.google.com/store/apps/details?id=com.premii.hn https://play.google.com/store/apps/details?id=com.premii.hn
- qubitcoder 12y ago
  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.
  - thekingshorses 12y ago
    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.
    - qubitcoder 12y ago
      It's an iPhone 5s. It only occurs after I've used the app for a while, then switching to an article with a large number of comments; scrolling can become laggy enough to render the app unusable (i.e. scrolling even a small amount takes over a second; lag seems to scale based on the comment count). 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.

by ctrlrsf 12y ago

anonbanker 12y ago

Feels very heavy on Firefox in Android.

thekingshorses 12y ago
Yes. Main problem is scrolling is not smooth. I told Mozilla mobile folks, but they think its smooth.

thekingshorses 12y ago

Author here: You can download iOS/Android app too. It supports upvoting. https://itunes.apple.com/us/app/hacker-news-yc/id713733435 https://itunes.apple.com/us/app/hacker-news-yc/id713733435 https://play.google.com/store/apps/details?id=com.premii.hn https://play.google.com/store/apps/details?id=com.premii.hn

qubitcoder 12y ago
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.
- thekingshorses 12y ago
  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.
  - qubitcoder 12y ago
    It's an iPhone 5s. It only occurs after I've used the app for a while, then switching to an article with a large number of comments; scrolling can become laggy enough to render the app unusable (i.e. scrolling even a small amount takes over a second; lag seems to scale based on the comment count). 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.