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

The numbers suggest that more and more users are going to be hitting the web on mobile devices (numbers vary a bit, but the consensus seems to be close to doubling annually and around 10% at the moment).

It seems to me that it's not a question of responsive design or not; and it's not a question of responsive design vs. separate sites (completely or substantially separate code). Rather, it becomes a question of how much time do my analytics numbers suggest I should spend making my mobile presentation better?

It definitely cuts both ways, and for some using a decent responsive framework will certainly be fastest, for others, a quick mobile-only lander that directs to a native app might be more well-suited. This problem isn't going away anytime soon, and I'm keeping an interested eye on the almost classic 'responsive vs. mobile-specific vs. native' debate (and all of its variations).




I'm interested in how accessibility fits in here.

Does it get built in at the beginning whether people chose a responsive design or separate pages? Or does it get kludged in at the end, if at all?

I had really hoped that the adoption of smart phones would mean that more sites would have either simpler pages, or would have a minimal version of the page. For example; most sites could get away with a read-only, html+css tiny version of the page. But I accept that I'm wrong and that very few people share that vision and most people want everything on a handheld device.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

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

Search: