Hacker News new | past | comments | ask | show | jobs | submit login

> The problem is "mobile only" design.

Agree.

Actually, I think what happens is that the team adopts a "mobile-first" policy, which is reasonable, since most visitors wil be mobile. But they don't follow through with the "desktop-after" corollary, and they don't engage with the "progressive enhancement" philosophy, because that gets even more costly than simply having two websites.

I find phones impossible to use as web browsers. My eyesight is too poor, and my thumbs are too fat. I use phones for making phone-calls and for trading SMS messages; if I need a website, I use my laptop. But that's just me.

I think the real problem is that mobile phones make awful platforms for browsing websites. Native checkboxes and native select-boxes are often unusable, so developers use "frameworks" <spit> that replace them with Javascript monstrosities. Because that all depends on plugins and code, each website ends up with it's own idiosyncratic UX.

I think the correct solution is for phone makers to deliver platforms that can render HTML so it's useable. Then the only problem for devs is create responsive layouts, which isn't that hard.




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

Search: