Angry engineers? How about taking to typical internet users?
How many loading spinners do they have to see just to get to what they're looking for? Between frontend frameworks, marketing analytics scripts (aka tracking) and crap UXs* we're moving sideways not forward. On a typical mobile device with a typical connection the internet has often become a health hazard (i.e., increase in stress and blood pressure).
* True story: Last month I went to pay a bill online for a major health insurance provider. After 3 or 4 tries with my Amex I concluded they don't accept Amex. But there was no icons to communicate what they did accept. No validation to say "we don't take that card", and no error msg either. But I bet it was built with Angular or React. I understand. That's not the engineeers' role. Perhaps. But if we're freeing up resources why are experiences like this happening? Why are sites like adidas and Home Depot so marginal on my mobile device?
I wish I could be angry. But I'm too beaten down to fight back at this point.
I called out a design agency for putting a loading spinner in a concept video a few months ago. They at least had the decency to look a bit ashamed, but claimed it made the concept feel more “real” facepalmemoji
"We promise to craft an experience that forces your users / customers to wait..."
Great selling point ;)
Sadly, somewhere there's a VP of Marketing losing sleep over the color of their spinner and how fast it spins. "What if we didn't have need for a spinner?" never crosses their mind.
That's pretty hilarious. But honestly I respect keeping expectations as realistic as possible. It's very likely the execution of it will have a loading graphic somewhere.
Well, pick your loading spinner. Either the screen has it for the fetch call, or the whole browser has it for the page-flip (sometimes with you just having a blank page while you wait).
A long loading spinner is a sign of a server-side problem in speed, not in the client.
and old-school MVC page-flipping code can be just as bad in error and validation reporting. Sometimes worse because maybe the form data was lost so you can't fix it.
You're talking about design problems that exist regardless of the layer that is involved in showing it. Nothing you've said here is a problem of the UX framework. I use react and we have very extensive error and validation reporting, because we made that a design requirement.
How many loading spinners do they have to see just to get to what they're looking for? Between frontend frameworks, marketing analytics scripts (aka tracking) and crap UXs* we're moving sideways not forward. On a typical mobile device with a typical connection the internet has often become a health hazard (i.e., increase in stress and blood pressure).
* True story: Last month I went to pay a bill online for a major health insurance provider. After 3 or 4 tries with my Amex I concluded they don't accept Amex. But there was no icons to communicate what they did accept. No validation to say "we don't take that card", and no error msg either. But I bet it was built with Angular or React. I understand. That's not the engineeers' role. Perhaps. But if we're freeing up resources why are experiences like this happening? Why are sites like adidas and Home Depot so marginal on my mobile device?
I wish I could be angry. But I'm too beaten down to fight back at this point.