Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@exerceo Fair enough.
-
@cuddlyogre wait what? In more than 20 years computer experience it never occurred to me that backspace does that.
*checks web* oh apparently it was removed in Firefox 87 (2021). I never knew! -
@saucyatom Believe it or not, there was a vocal group of crazies that demanded it stay that way. Thankfully, the browser vendors didn't listen to them.
-
@cuddlyogre I knew it did but was never a problem for me. Not much of a conflict but not that practical either.
Pull-to-refresh is useless.
If you are a mobile app developer, please get rid of pull-to-refresh. Your users ...
If Google finally made pull-to-refresh optional on Chrome for Android, it would be an admission of failure.
The failure to realize four years earlier that pull-to-refresh is potentially annoying to users, and the failure to listen to the abundant feedback by users who lost submissions or who interrupted playing media due to refreshing accidents.
One can assume that Google has something like a "user experience team". Didn't even one of these "highly qualified" people remotely consider that assigning the same finger movement to scrolling up and to refreshing could be a potential annoyance? Didn't this possibility go through at least one of their IQ 130 brains?
Now guess which is the more frequent purpose of swiping down. Scrolling up or refreshing a page?
Only one of the two is wanted at a time. Either scrolling up or refreshing. Assigning the same finger movement to two things at once is a downright terrible idea.
By making the pull-to-refresh anti-feature impossible to deactivate, Google effectively is begging its users to leave for Opera Mobile or Samsung Internet.
rant
pull-to-refresh
design fail