I just discovered that you can tap the title of devRant app to load new rants instead of just scrolling to the beginning to make a pull to refresh :( FML

Pull-to-refresh is useless.

If you are a mobile app developer, please get rid of pull-to-refresh. Your users will thank you.

I have the impression that mobile app developers choose to implement the pull-to-refresh gimmick just in order to make their app comply with a design trend. It seems like a desperate attempt to appear "modern" and "fancy", not because of the actual usefulness of the gesture.

Pull-to-refresh is one of those things that are well-intended but backfire. It appears helpful on first sight, but turns out to be a burden.

It takes effort and cognitive strain to avoid triggering a pull-to-refresh. The user can't use the app relaxed but has to walk on eggshells.

Every unwanted refresh wastes battery power, mobile data (if it is an Internet-connected app), and can lead to the loss of form data.

To avoid pull-to-refresh, the user has to resort to finger gymnastics like a shorter swipe for scrolling up or swiping slightly up before down. Pull-to-refresh could even be triggered while pinch-zooming in or out near the top of a page, if the touchscreen does not recognize one of the two fingers.

Pull-to-refresh also interferes with the double-tap-swipe zoom gesture. If one of the two taps are not recognized, a swipe-down to zoom in can trigger a pull-to-refresh instead.

To argue "if you don't like pull-to-refresh, just don't use it" is like blaming a person who stepped on a mine, since the person moved and the mine was stationary.

A refresh button can be half a second away in the menu bar, URL bar, or a submenu, where it is unlikely to be pressed accidentally. There is no need for a gesture that does more harm than good.

Using a mobile app with pull-to-refresh feels like having Windows StickyKeys forcibly enabled at all times. The refresh circle animation sticks to the finger.

If the user actually wants to refresh, pull-to-refresh is slower than a refresh button in a menu if the page is not at the top, meaning pull-to-refresh is useless as a shortcut anyway if the page is in any other position than the top.

An alternative to pull-to-refresh is pull-for-details. Samsung did it in some of their apps. Pulling down against the top reveals additional information such as the count and total size of selected items.

If you own a website, add this CSS to make browsing your website on the pre-installed Android web browser not a headache:

html,body { overscroll-behavior: none; }

Why is this necessary? In 2019, Google took the ability to deactivate the pull-to-refresh gesture on their Chrome browser for Android OS away from users. On Chrome for Android, pull-to-refresh can only be disabled on the server side, not the user side. The avalanche of complaints? Neglected.

Good thing several third-party browsers let the user turn off this severe headache.

The interface for time input in outlook Web on mobile is driving me crazy!! It's not as if there was a built in control that is well supported in all modern browsers.... Right

1. You can't tap on an hour to select it
2. You can only select by scrolling
3. The scrolling is "smooth scrolling". So you have N O fucking chance to select the time slot you wanted. After too much time has passed you just give up and accept that your meeting will be at 09:57
4. In order to go up in time you constantly activate the"pull to refresh" feature of Chrome.

I'm definitely no mindless MS hater but this I cannot tolerate.

Why does it take a few seconds for the feed to show up when I pull down to refresh?

This is Android N on a Moto G5 plus.

> "A flat design UI reduces cognitive load!"

Oh really, Google? If that is your aim, then how come you increase cognitive load by making pull-to-refresh mandatory on your mobile web browser, which constantly has to be avoided by the user?

Omfgggggggggggggggggggg
Fuck you typescript.

A whole day wasted working on react native pull to refresh bug, wondering why the fucking hell shit doesn't even appear when u try to pull. And so many other weird shit like touchable opacity not showing up.

Guess what was the problem? Fucking typescript importing shit from react-native-gesture-handler.

Btw I live and breathe typescript. I appreciate typescript everyday but for today fuck you typescript.

It would be great if we can pull to refresh on a post because the refresh button seems like it's in Paris while I'm in Colorado. It's a commonly used action, so it's position should be well deserved.

Pull to Refresh on Notifications?

2005 called. It wants its numbered file names back.

While I am mostly satisfied with "celluloid" as a worthy successor to xplayer, the first major disappointment I stumbled upon is `celluloid-shot0001.jpg`. Are we in 2005?

Just like xplayer, Celluloid, the new default media player of Linux Mint, should use proper, i.e. time-stamped names such as `celluloid-2023-04-10T00-47-42.jpg` or `celluloid-video_file_name-2023-04-10T00-47-42.jpg` for screenshots taken from videos, to eliminate the possibility of file name conflicts if files are moved into other directories, to make screenshots searchable by video file name, and to retain the date and time information if the files are moved to a device that does not support date and time stamp retention such as MTP (Media Transfer Protocol), and to allow for date range selection using wildcards in the terminal (e.g. `celluloid-2023-04*` for all screenshots from April 2023). Besides, PNG screenshots should be supported too, but that's out of scope here.

As a reference, the gnome and mate screenshot tools also pre-fill time stamps into the file name field.

Numbered file names were useful in an era when there was no VFAT and file names needed to have 8.3 file names that could impossibly fit a date and a time, and compact cameras used such names, but those times are long over. Just like the useless and annoying pull-to-refresh gesture on mobile apps and the Media Transfer Protocol, numbered file names belong to the technological graveyard.

If numbers are really desirable, at least `celluloid-shot0001.2023-04-10T00-47-42.jpg` should be used, to include both a number and a date. The command to get this date format is `date +"%Y-%m-%dT%H-%M-%S"`. For compatibility across operating systems, dashes instead of colons have to be used to separate hours and minutes and seconds.

Numbered file names are a thing of the past. Use time stamps.

Sometimes in our personal projects we write crazy commit messages. I'll post mine because its a weekend and I hope someone has a well deserved start. Feel free to post yours, regex out your username, time and hash and paste chronologically. ISSA THREAD MY DUDES AND DUDETTES
--
Initialization of NDM in Kotlin
Small changes, wiping drive
Small changes, wiping drive
Lottie, Backdrop contrast and logging in implementation
Added Lotties, added Link variable to Database Manifest
Fixed menu engine, added Smart adapter, indexing, Extra menus on home and Calendar
b4 work
Added branch and few changes
really before work
Merge remote-tracking branch 'origin/master'
really before work 4 sho
Refined Search response
Added Swipe to menus and nested tabs
Added custom tab library
tabs and shh
MORE TIME WASTED ON just 3 files
api and rx
New models new handlers, new static leaky objects xd, a few icons
minor changes
minor changesqwqaweqweweqwe
db db dbbb
Added Reading display and delete function
tryin to add web socket...fail
tryin to add web socket...success
New robust content handler, linked to a web socket. :) happy data-ring lol
A lot of changes, no time to explain
minor fixes ehehhe
Added args and content builder to content id
Converted some fragments into NDMListFragments
dsa
MAjor BiG ChANgEs added Listable interface added refresh and online cache added many stuff
MAjor mAjOr BiG ChANgEs added multiClick block added in-fragment Menu (and handling) added in-fragment list irem click handling
Unformatted some code, added midi handler, new menus, added manifest
Update and Insert (upsert) extension to Listable ArrayList
Test for hymnbook offline changing
Changed menuId from int to key string :) added refresh ...global... :(
Added Scale Gesture Listener
Changed Font and size of titlebar, text selection arg. NEW NEW Readings layout.
minor fix on duplicate readings
added isUserDatabase attribute to hymn database file added markwon to stanza views
Home changes :)
Modular hymn Editing
Home changes :) part 2
Home changes :) part 3
Unified Stanza view
Perfected stanza sharing
Added Summernote!!
minor changes
Another change but from source tree :)))
Added Span Saving
Added Working Quick Access
Added a caption system, well text captions only
Added Stanza view modes...quite stable though
From work changes
JUST a [ush
Touch horizontal needs fix
Return api heruko
Added bible index
Added new settings file
Added settings and new icons
Minor changes to settings
Restored ping
Toggles and Pickers in settings
Added Section Title
Added Publishing Access Panel
Added Some new color changes on restart. When am I going to be tired of adding files :)
Before the confession
Theme Adaptation to views
Before Realm DB
Theme Activity :)
Changes to theme Activity
Changes to theme Activity part 2 mini
Some laptop changes, so you wont know what changed :)
Images...
Rush ourd
Added palette from images
Added lastModified filter
Problem with cache response
works work
Some Improvements, changed calendar recycle view
Tonic Sol-fa Screen Added
Merge Pull
Yes colors
Before leasing out to testers
Working but unformated table
Added Seperators but we have a glithchchchc
Tonic sol-fa nice, dots left, and some extras :)))
Just a nice commit on a good friday.
Just a quickie
I dont know what im committing...

@dfox Feature request: could you add the "pull down to refresh" feature to the notifs and rant windows please? xox

So GitHub's "Repository Refresh" layout is live now and they haven't fixed the damn .repohead (with the repo name and the links to Issues, Pull Requests, etc.) stretchting across the entire screen instead of being constrained to the middle column :/

If it annoys you just as much as it does me, just wack this CSS into a user css extensions and it's fixed:

.repohead .d-flex:first-of-type {
max-width: 1280px !important;
margin-left: auto !important;
margin-right: auto !important;
}
.repohead nav.js-repo-nav {
max-width: 1280px !important;
margin-left: auto !important;
margin-right: auto !important;
}
.repohead .UnderlineNav {
/* Remove repohead bottom divider */
box-shadow: none;
background-color: transparent !important;
}
.repohead {
/* Add repohead bottom divider to repohead so it stretches across the entire screen */
box-shadow: inset 0 -1px 0 #e1e4e8;
}

Google is known for frequently removing features from its products and services. So much that they have been given the nickname "Gookill".

If only they removed the one feature that deserves to be removed.

Pull-to-refresh.

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.

Not sure if I'm sick or I'm actually in my full sense ....

I reached a point that I'm sick of all that million language to work with, maintain lots of shit, and started to consider using Flutter and get it done.

But I still don't like to build on these things because well, for the lots of trouble I went through in React Native, and yet again in Flutter having to modify several plug-ins because they don't support a simple feature as simple as Authentication header

I thought I'd give SwiftUI a go, but for a starter:
1. No pull to refresh
2. No proper grid (aka UICollectionView)
3. Comparing SwiftUI with Flutter, Google did a better job at keeping things simple
4. Only iOS 13+ supports SwiftUI, their statistics might show 90% using latest update, but that's their target audience, mine might be 90% not on latest update ...

Just some midnight thougts filled with frustration and wondering: How do web developers keep up with those "look ma! I made a new JS Framework!!" their life must be tougher ....

Like pull-to-refresh, auto-selecting the file name in "save as" dialogues is a design trend we are perpetuating without questioning its usefulness.

The "rename" feature of file managers and the file name fields in "Save as" dialogues and screenshot tools automatically select file names without the ending, expecting the user to want to replace it.

It would more sense to place the cursor between the file name and the ending ".png".

I can't remember the last time I replaced a file name. I almost always rename files to add a comment or time stamp at the end.

Adding a comment after the time stamp, for example, "Screenshot at 2024-02-04 12-04-37 progress bar.png", makes more sense than replacing the file name. A file name with a time stamp is more easily searched.

When you pull down the list in this app to refresh the content the big sad devRant logo appear and it looks like theres problem with connection :o