Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

The shift of screen sizes for computing devices from a single aspect ratio (4/3 monitors) to just about anything created a nightmare for UX, and web development is suffering from it. I still maintain that no-one should have to scroll to use software. Everything you need for a certain place in an application's workflow should be on one screen. If the size of the screen means that more steps are needed to complete a task using software, then that should be handled by the adaptability of the software (including larger text for visually impaired people). Scrolling was the work of the devil. As for accessibility, it makes a blind person able to become familiar with how many elements are available on any screen they use based on their own experience.


> I still maintain that no-one should have to scroll to use software. Everything you need for a certain place in an application's workflow should be on one screen.

Independent of whether you agree with that, it is just completely unrealistic to achieve, in a sane way.

Without using 7 levels of nested submenus, which is also horrible UX, it will never be possible to present all features of e.g. Word on my 4.7“ phone screen.


Where did you find a phone with a 4.7" screen? Do they still have some? (Please tell me it isn’t an iPhone...) Every time my phone’s battery fades into unusability, I struggle for a bit before resigning myself to having a larger phone than before.


Do you suggest then that HN show every page of every comment on a separate screen?

Rigid dogma does not make for good UI.


I've seen this referred to as something like "Scroll content, don't scroll the app".

And of course we now have Apple of all companies where they botched that even in native apps (like settings)


Do you have any reference resource where I can see something along the lines of "before with scrolling, after removing scrolling" examples?

I too hate scrolling, what can I do about long tables? Pagination is half the solution.

How to write documentation that fits one screen size, with images and tables?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: