Hacker News Reader

Comment by viraptor | Hacker News Reader

Looks really messy / disorganised on a mobile. Also I need to tap "back" twice to get out of that page. I'm not even at examples and I'm already not impressed.

View on HN

everything you click on adds an entry to the history. i had to "back" like 10 times to actually leave the page because i was clicking through the various samples..

This shouldn't be surprising; most sites do exactly what this site does (if you don't believe me, go to any Wikipedia article, click an entry in the TOC, and click the back button; you'll probably go back to the TOC, not all the way back out of the article). That's how it should work, and I was pleasantly surprised to see that this framework preserves that.

One thing NatUIve does appear to get wrong is that (at least with JS enabled) if you use the forward button too rapidly it'll get confused and renavigate to the page/tab you're on, thus preventing you from going further forward (because it adds an extra entry to the history). This doesn't happen when you turn off JS, so I'm pretty sure it has to do with the scroll effect.

Hi, this is a reference site. It's documentation for devs, not end customers. Not meant to be used on mobile.

So documentation for devs can somehow be poorer and we can throw out mobile-support for that audience too? Why? Why is it ok to sideline a group you’re presumably coveting?

Because you don't read docs on a phone.

I do. And the site instantly put me off.

And i do like to use my web browser non-maximized in my 1366x768 monitor yet every other site forces me to maximize because it thinks that since my browser's width is less than 1024 or whatever threshold they come up with, it is actually a mobile phone and switch to that, making the already overenlarged UI elements cover as much real estate as my entire fist.

Which sucks.

But that is the world we live in. The more tools we give the designers, the more they will abuse everything they can.

CSS was a mistake, the web should have stayed in HTML 3.2.

Hi, there is no threshold. What is the issue at 1024px? Thanks.

Sorry i wasn't clear, i was referring to other sites in general (e.g. YouTube) that switch to mobile UIs when my window is too narrow. Your site doesn't do that, although TBH i find the design too wasteful for screen real estate (e.g. too much space between elements in the sidebar). Here is how it looks on my browser (this is with the window maximized vertically but not horizontally since it is easier for me to read text - i cropped out the browser UI and taskbar, but this is Firefox running on Windows 10):

https://i.imgur.com/FLG0HiF.jpg

Hello, now I understand the main content area can be wider and the tabs are taking too much space on narrow screens. This can be improved in the future. Thanks

And the site allows that, it's just not very convenient.

It is also a front page for "Show HN" (which lots of people will read on their mobiles) and it is related to web design.

There are readable references: https://getbootstrap.com/docs/3.4/css/ https://vuejs.org/v2/api/ https://docs.python.org/3.7/reference/index.html

Even just saying in the page that it's not supposed to work well on my device would be better.

Reply on news.ycombinator.com