How to make your responsive mobile website hurt my heart
1–10 of 28 posts
Re: How to make your responsive mobile website hurt my heart
#2All of these are bad on the desktop web. After all, some people still have phone company DSL.
Re: How to make your responsive mobile website hurt my heart
#3The scroll hijacking one is a personal pet peeve. Whatever genius developer that thought of that should be taken out back and shot.
Either that or they should have been required to write the thing while allowing us to set their scroll wheel speed.
/rant
Re: How to make your responsive mobile website hurt my heart
#4I'm surprised he didn't mention sticky headers/footers. Those can be a huge waste of space, especially if you're browsing in landscape.
Re: How to make your responsive mobile website hurt my heart
#5I'm surprised he didn't mention sticky headers/footers. Those can be a huge waste of space, especially if you're browsing in landscape.
Excellent point, I completely forgot about those. Will add them now!
Re: How to make your responsive mobile website hurt my heart
#6I'm surprised he didn't mention sticky headers/footers. Those can be a huge waste of space, especially if you're browsing in landscape.
#1 complaint on every platform, for me. Sticky is very bad. Disappearing on scroll down but reappearing on scroll up is even worse. Just let the things scroll off screen, I can scroll to the top if I want to see anything on the header (spoiler alert: I won't). Old-school sticky sidebars (as in old frame layouts, for example) were totally fine on desktop, but are out of fashion now because they don't translate well to mobile.
I remove sticky elements with the dev console on anything I actually want to read that's longer than a few lines of text—though I can't do that on mobile, so it's worse there.
Re: How to make your responsive mobile website hurt my heart
#7Please add mystery-meat navigation to the list. It's so painful. I have no idea what those icons do and can't 'mouse over' like a desktop.
Re: How to make your responsive mobile website hurt my heart
#8Why having webfonts at all? Every computer and mobile phone has tons of
fonts already installed. Your fonts definitely don't look better.
Please don't waste my bandwith with it.
Why do you make mobile sites that can't be zoomed? This is so annoying. Then sometimes zooming is possible but the sticky headers/footers also zoom and hide the actual content.
Re: How to make your responsive mobile website hurt my heart
#9I'm surprised he didn't mention sticky headers/footers. Those can be a huge waste of space, especially if you're browsing in landscape.
My Safari Bookmarklet to kill stickies:
javascript:(function()%7B(function%20()%20%7Bvar%20i%2C%20elements%20%3D%20document.querySelectorAll('body%20*')%3Bfor%20(i%20%3D%200%3B%20i%20%3C%20elements.length%3B%20i%2B%2B)%20%7Bif%20(getComputedStyle(elements%5Bi%5D).position%20%3D%3D%3D%20'fixed')%20%7Belements%5Bi%5D.parentNode.removeChild(elements%5Bi%5D)%3B%7D%7D%7D)()%7D)()
My other one to re-enable proper scroll and zoom: javascript:document.queryselector('meta%5bname=viewport%5d').setattribute('content','width=device-width,initial-scale=1.0,maximum-scale=10.0,user-scalable=1');
These two can fix a lot of broken "responsive" garbage the front-end web dev community seems to really enjoy.
Re: How to make your responsive mobile website hurt my heart
#10Why having webfonts at all? Every computer and mobile phone has tons of fonts already installed. Your fonts definitely don't look better. Please don't waste my bandwith with it. Why do you make mobile sites that can't be zoomed? This is so annoying. Then sometimes zooming is possible but the sticky headers/footers also zoom and hide the actual content.
> Why having webfonts at all? Every computer and mobile phone has tons of fonts already installed. Your fonts definitely doesn't look better. Please don't waste my bandwith with it.
Designers are really in love with using literally any font that's not a system font and will throw a fit if they can't do that. It's all because branding, or something.
As a user I hate that crap. Quit wasting my disk and bandwidth with your cutesy garbage and just use system fonts. As a developer I hate that crap, because it's one more thing to worry about.
But the designers/marketers have won this one—they're willing to fight really hard for their special snowflake fonts and have sold it to the people who make decisions as being vital for branding, which is Super Important™.
Add allowing custom, downloaded fonts to the list of things the web is worse for supporting.