Samsung wants future phones to have no Settings menu at all

GreenEngineering3475@lemmy.world to Android@lemmy.world – 176 points – Samsung wants future phones to have no Settings menu at all
androidauthority.com

Samsung is working on a new AI experience for its devices that will help you use your phone without ever accessing the Settings menu.

103

You are viewing a single comment
View all commentsShow the parent comment

Most of the software updates you see are a result of CI/CD processes. The industry claims it makes good design patterns to get features our faster and more reliably. In reality it is just a rushed shitstorm that results in half-assed Friday releases that aren't fixed until the following week.

I've long turned off auto update of my apps. Too many times I'm on a trip or other scenario where my tool is meant to be a tool and not some tech bro's rented wet dream, and the tool is broken.

But here's the kicker. CI/CD exists for another reasons or so:

  • Frequent updates tend to reset review rankings in app stores. Not only does it offer plausible deniability to the app company, but it also screws with the review scores in their favor, as well as other rankings.
  • Great way to help nudge along planned obsolescence. All that pointless rewriting of flash storage on a daily basis.
  • Psychological manipulation, it gets notifications in your face to try and increase app engagement, which ensures it is fresh and running gathering user telemetry to sell as a side-hustle, as well as direct-interaction telemetry and getting more ads in your face.

It'd be better if we all just went back to landline phones some days. Modern tech is too noisy, abusive, and intrusive.

CI/CD processes.

What does this stand for, and what are these (in layman's terms anyway, not expecting a deep dive)?

Continous integration/ Continous delivery basically they keep pushing the latest developments as soon as it's avaliable and passes the tests.

You guys do tests (meme, I'm just too lazy to make)

My favorite podcast app, Overcast, recently had a huge overhaul and it went from working perfectly to being utter broken garbage for a couple months.

They definitely didn’t do tests. I think they just rushed it out to meet some deadline.

It’s usable now, but it was really gnar for a while.

Old software - Do an annual release but make that release as bug-free as possible

New software using CI/CD - Push software updates as fast as possible to show high productivity. Bugs? We will get them in the "next" update.