13 ms·
I have an old WinPhone with a weak processor that only loads the current tab. This makes tabbing the browser functionally pointless. Heavyweight responsive we
by Pxtl 13y ago
I have an old WinPhone with a weak processor that only loads the current tab. This makes tabbing the browser functionally pointless.
Heavyweight responsive websites are unusable. I have to wait indefinitely for page to load, and there's no way to make it load in the background. In the rare cases where the pages progressively display, scrolling is still agony as elements jump around constantly.
While I realize I should probably get a new phone, I'd wager I'm not an edge-case and a lot of users with older or bargain-bin phones face this kind of frustration.
- gorkamolero 13y agoI completely agree. More than a few of the Web people (perhaps most?), though, are moving towards more complicate systems, more expensive design. To me the way forward should be optimization of sites. I don't know where you use your phone but most of the people using mobiles to access internet lack any sort of bandwidth. So, if you are a company, this people basically don't have access to your content
- enko 13y agoI believe mobile is currently about 18% of web usage market share, and windows phone is about 2% of mobile, so your situation is probably less than half of one percent of users - well below the level where specific support is economically viable, especially since it would probably require a lot of work. As you said, the solution is for you to get a new phone.
- deleted 13y ago[deleted]
- Pxtl 13y agoI don't mean literally supporting the dead-ended WP7, but the general category of "old/cheap smartphones that scream and fall over dead trying to render your page".
- enko 13y agoAh, I see what you mean. Yeah, that's a bit obnoxious, especially when it's something as gratuitous as a slideshow or something with CPU-hungry fading eye candy.