2 ms·
> - bringing in a giant JS framework to make sure a single type of input field works the same for a single buggy browser + OS + device combination (Firefox on A
by JMTQp8lwXL 6y ago
> - bringing in a giant JS framework to make sure a single type of input field works the same for a single buggy browser + OS + device combination (Firefox on Android on Samsung S-something) as for the others is bad UX, and
This is a business solution, not a UX problem. You've got a billion users. 0.01% use the buggy browser with the bad input field. You're losing $X per hour. The input pays for itself.
- l0b0 6y agoYour argument assumes that bringing in a giant JS framework has zero negative effects, but this should never be taken for granted: - The framework may well be buggy for a small percentage of users who happen to this time not include someone vocal. Result: you've lost users and you won't know it. - The framework might be the straw that breaks the camel's back in terms of load times or cost. For some reason it seems to be rare to test for slow devices on slow, unreliable, metered connections, even though it's pretty much a given that the UX designers' devices and connections will be in the top 1% in all of these. Result: you've lost users and you won't know it.