Sounds like they're rolling back the mandatory verification flow:

Based on this feedback and our ongoing conversations with the community, we are building a new advanced flow that allows experienced users to accept the risks of installing software that isn't verified. We are designing this flow specifically to resist coercion, ensuring that users aren't tricked into bypassing these safety checks while under pressure from a scammer. It will also include clear warnings to ensure users fully understand the risks involved, but ultimately, it puts the choice in their hands. We are gathering early feedback on the design of this feature now and will share more details in the coming months.

▲

Ajedi32 2 hours ago | parent | next [-]

I'm a little nervous about what this advanced flow is going to look like, given that sideloading already requires jumping through a bunch of hoops to enable and even that apparently wasn't enough to satisfy Google.

I'm cautiously optimistic though. I'm generally okay with nanny features as long as there's a way to turn them off and it sounds like that's what this "advanced flow" does.

▲

gowthamgts12 2 hours ago | parent | prev | next [-]

> Sounds like they're rolling back the mandatory verification flow

absolutely no. this is for the user side. but if you're a developer who is planning to publish the app in alternative play store/from your website, you have to do verification flow. please read the full text.

	▲	rbits 3 minutes ago \| parent \| next [-]
		But it's not mandatory anymore because people can install it without it being verified.
	▲	Ajedi32 2 hours ago \| parent \| prev [-]
		That's only if you don't want your users to have to jump through whatever hoops are needed to bypass the verification requirement.

▲

silisili 5 hours ago | parent | prev [-]

I feel like if safety was really their top priority, they would have done this long ago and not bothered with this mandatory signing nonsense to begin with...

Still, it seems like good news, so I'll take it.