Having used custom ROMs for years, it can get tiring to fight with SafetyNet, find root backup apps that still work, dealing with bugs the developer may not be able to reproduce and, of course, even finding decent phones that have decent ROMs. I refuse to buy a Pixel until they have a decent SoC and price.

So for my next phone I'm currently considering an OEM that supports phones for long and has decent customization by default - Samsung. As I've never owned Samsung phones before, I don't know whether I'll like their OS, but so far it looks good enough.

According to the article, that's due to more features and more updates.

Well, Firefox also plans to deprecate MV2 at some point (deadline to be announced at the end of this year), the difference is just that their implementation of MV3 is more flexible at the points Chrome was criticized for.

Vivaldi and Brave are planning to extend the deadline of MV2 by some extent, not sure if it means just like the enterprise policy or will they keep the implementation in code for longer.

I can understand that part, but not why providing such update timeline would be "excessive" or "crazy", if there are ways to achieve it.

How does it differ from buying a laptop at this point? The price is the same, the capabilities are similar, the form factor can be the same (Fold or tablets in general).

As long as the hardware can keep up with the software, and the manufacturer keeps building products, why should they ever end support? (a la Windows)

Remember that all apps need to target the almost-latest target API at least. That means Android 13 for all new apps and app updates since Aug 31.

https://support.google.com/googleplay/android-developer/answer/11926878

Unpopular opinion, but phones these days don't really need more buttons, but less. We have a huge touch screen after all, let's take better advantage of it!

• "Action button" - Android phones have had a long press of power button be the assistant button since Android 12, just set your "assistant" as whatever action you want (e.g. with Tasker).
• Sleep/wake button - can be the power button for now, but also don't forget double-tap on the home screen/lock screen/status bar.
• Power off/on - virtual button since Android 12, physical button for turning on. In case of emergency, I guess hold down for longer or do something like triple-tap.
• Volume keys - every video app should use onscreen gestures, same could be applied for music. In other contexts, statusbar or side swiping gesture could suffice, plus a notification shade slider like some OEMs already provide.

The parent may then be asked to consent to a scan of their face using a front-facing camera, which is then used to "accurately estimate the parent's age."

the only piece of information that is communicated to the company requesting [Verifiable Parental Consent] is a 'Yes' or 'No' determination as to whether the person is over the age of 25.

So that's settled, people under the age of 25 can no longer have children.

...and the blog owner can't use Let's Encrypt.