this post was submitted on 08 Aug 2024
1162 points (98.8% liked)
Microblog Memes
5388 readers
4199 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
- !whitepeopletwitter@sh.itjust.works
- !best_of_mastodon@sh.itjust.works
- !curatedtwitter@sh.itjust.works
- !curatedtumblr@sh.itjust.works
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It shouldn't really be just millennials who do this, and there's a simple reason for it. Just about every web developer uses a desktop for development work, so most of their testing is done in a desktop browser. So mobile-only bugs do slip through the cracks more often, I find. imo that is the reason that to this day, a lot of bugs get overlooked on mobile.
I feel like food ordering services are always the worst culprits for some reason. Many times I have tried to order food on my phone only to get stuck in a login loop or some other bug that makes it impossible. Open the same service up on my desktop and it works perfectly first try
Notably modern browsers can simulate phones, tablets, TVs, really all kinds of screens. I personally use that mode a lot to test the mobile variant, but nearly all bugs are purely CSS-related (at least in my experience) when it comes to a mobile-desktop discrepancy. Either way, for food delivery and stuff like that I'd really expect the devs to develop primarily for mobile, so that's surprising to hear.
Yeah I refuse to debug other people's sites lol so I don't know what's going on precisely but I've noticed this a few times.
We build things as mobile first in my shop but it's really hard to test everything on a real device on every build. I suspect these kinds of bugs are usually a "this small change should work the same everywhere" but doesn't for various reasons.
Oh yeah, that stuff is a pain and automated tests can only go so far. Also I know for me personally I do tend to neglect mobile a little just because I much prefer designing and developing for larger screens, and I doubt I'm the only one, so on mobile more will slip through the cracks when it comes to these tiny changes.