Rusty Corgi ➡️ 
MFF
Rusty@cubhub.social
Hot take alert, but if the navigational hierarchy of your website or app relies on the user pressing the browser/system back button, you've made a bad app. 
You should always be able to navigate down and back up through every part of your app intuitively without needing a system back button.
It's honestly why I hate the Android SDK so much.
2
0
0
Rusty Corgi ➡️ MFF
Rusty@cubhub.social
@charlotte I don't mind a website's back button being in the top left because my mouse is usually up at the top of he browser window to mess with tabs or press buttons on the browser's toolbar. I *hate* how sticking toolbars on the top of mobile apps became the standard though. Windows Phone really got that right by sticking them on the bottom.
That said, iOS (and LibAdwaita, funny enough) figured this out by letting you drag from the left screen edge to go back with a really nice 1-to-1 drag gesture. If you're using the normal iOS SDK and a navigation controller, you don't have to reach for the back button. Similar story with the modals/bottom sheets and being able to just drag them back down. Meanwhile Android doesn't do this, and instead slaps the stupid back gesture on the screen edges where it's really easy to accidentally trigger when you're trying to use a hamburger menu, crop a photo, or using the in-app navigation that some apps build in despite it not being built into Android by default for *some* reason. Meanwhile the back gesture has really unpredictable behavior because, unlike iOS, Android apps aren't built with a single-point of entry informing their navigational hierarchy so half the time the back gesture just kicks you out of the whole app 
Gaaawwddd I hate it. 
0
0
0
BigBesmircha
BigBesmircha@mastodon.social
@Rusty back swiping (not fond of the buttons) is good actually but you're otherwise right
1
0
0
Rusty Corgi ➡️ MFF
Rusty@cubhub.social
@BigBesmircha It depends on what you mean. I feel like any swiping within an app should be handled by the app itself, like how iOS's navigation stack works where swiping from the left edge goes up a level in the stack, or how LibAdwaita lets you two finger swipe to go up a level in their navigation views. Android's universal back gesture, on the other hand, drives me insane. It's too easy to accidentally trigger it if you're trying to use a slide-out hamburger menu or crop a photo, and Android's back gesture being unpredictable where sometimes it sends you up a level, sometimes it sends you back to your previous app, and sometimes it kicks you out of your app entirely, makes accidental triggers 100x more annoying. As for swiping to go back on a browser, I'm a little iffy but I like Safari's one-to-one gesture for it alright enough since you have to be pretty purposeful with it, but Firefox's is too easy to trigger and looks kinda ugly.
1
0
0
BigBesmircha
BigBesmircha@mastodon.social@Rusty
trying to help an american understand bad ui: "imagine a hamburger menu that won't open"
1
0
0
