178
Samsung wants future phones to have no Settings menu at all
(www.androidauthority.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Oct 2024
178 points (85.6% liked)
Android
27940 readers
12 users here now
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
founded 1 year ago
MODERATORS
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.