> I also have issues with most map apps and using them for navigation. It seems that the UI designers for these things never consider difficulty in seeing the crucial details on a small screen at high velocities with small glances. > > I need the remaining KM until that turn, in large numbers, Google.

OsmAnd has a nice design, IMO: https://imgur.com/a/oZJIZst

It also lets you change the widgets and colorschemes, that's the LightRS map style and route line.

> I also have issues with most map apps and using them for navigation. It seems that the UI designers for these things never consider difficulty in seeing the crucial details on a small screen at high velocities with small glances.

Enshittification. I don't know what is being taught in design schools but enshittification is definitely one of its subjects. Take a look at major products and how shitty they became, with poor design decisions that are unjustified.

Google Maps switched to a Apple-like color scheme months ago. Everyone hated it, the main roads were no longer highlighted and distinguished from normal roads. Google ignored. I had to drive back to the office 2 weeks ago and my friend setup the GPS, only to be confused about the route because the streets I should take were highlighted in blue, but due to high traffic in the area they became yellow. I was confused for a few minutes thinking "okay, this is a main road, where the hell should I go?" until my friend told me it's yellow because of traffic conditions.

Honestly, I think Samsung has one of the worst android interfaces. It looks approachable, but most any activity is harder than on others that are truer to the stock experience. That said, every manufacturer has some stupid things. My Moto phone always blanks the screen when you are talking, which is great, but then makes it difficult to actually get the screen to stay on if you need to use it while talking.

>I need the remaining KM until that turn, in large numbers, Google.

One thing with maps too is that it decided to default to auto mode when using the app, but auto mode won't bring up the keyboard, which sucks if you need to make changes to your route and aren't wanting to use the voice mode.

however they did say:

That’s because, in a rush to move to touchscreens and display-based electronics, every company has let go of the simplicity of buttons.

This is kind of maddening. Tesla is the worst. Their recent cars have very. few. buttons. They have NO stalks, and what hasn't gone to the touchscreen goes to a few touch buttons in the center of the (rotating) steering wheel. They "control" turn signals, wipers, lights, etc. It guesses the gear shift (forward or back).

The iPhone at the very least always has the slide to power off feature, even before the fingerprint reader was introduced.

Short and long presses of the power button are the STANDARD ways to control the power of a device, be it a PC, phone, tablet, or even random things like my sous vide cooker or an aircraft GPS.

Reliably being able to determine and set if a device or computer is running is a critical aspect of making sure that machines serve their users. If a device is doing shitty, undesirable things, I want to know that I can quickly and easily power it all the way off. That includes if the screen becomes unresponsive or otherwise damaged.

Considering that Google Assistant (and Gemini now, I guess - the distinction isn't clear) have somehow managed to get LESS functional and useful as time has gone on, I found it extremely irritating that some promo-chasing PMs and engineers at Google tried to hijack this basic, established device control to push a garbage product which I KNOW is getting discontinued, migrated, or cancelled in the next few months.

I'm not even much of a zealot for free or pro-user software, but this is an insane idea from Google that speaks to a deep misunderstanding about how much control I think they should have over my phone.

The author acknowledges normal users rarely power off their phone; but goes on to mention that they are a tech reviewer and constantly switching phones, applying updates, restarting to reproduce glitches, etc. So it is not a real problem.

In fairness, iOS does not call it a power button anymore. iOS uses the term "side button". That's, of course, its own other problem, because the volume buttons are also on the side, but still.

They’re also special in that the adverse outcome to powering them off accidentally is much more likely, though. Not many other devices are stored in our pockets and can be pressed accidentally.

Also, it probably would be best to call it a “sleep” button or “screen” button… or something like that. After all, that’s the primary single press function that is universal to all phones. It’s not actually a power button from a single press, it’s a button to toggle the screen on and off. The long press not resulting in a power off command is somewhat unusual, but also not ridiculous.

If you turn your phone off frequently then knowing what the “secret combination” for power off should not be difficult. We’re talking about holding down the power button and one of the volume buttons… it’s not rocket science.

You can argue whether or not the default behavior is good… but no phone “chooses its actions by the phase of the moon”. That’s very disingenuous. Either way, having the power button held down not force off the phone is a good thing for avoiding accidental power down.