[qa-tari]

While this is nice for those who have a significant number of applications installed e.g. through F-Droid repositories, it won't make things easier for "standalone" third-party apps that only update themselves, since they will continue to be marked as originally installed by a browser or file manager app. I assume Epic Games already has a separate launcher app similar to that on the desktop that takes care of updating games.

[traspler]

What impact does being marked as "originally installed by a browser or file manager app" have? And how would that be different for Epic Games Launcher/Store?

The article mentions that even standalone apps can update themselves without user permission if they follow the requirements, Epic Games Launcher/Store is also a standalone app that needs to update itself at some point.

It doesn't change the initial installation dance with allowing "unknown sources" with all it's "scary" language and hoops a user has to jump through it seems; maybe that's what you meant? At least for Epic this will still be a problem as they see this as a clear disadvantage: https://www.theverge.com/2020/4/21/21229943/epic-games-fortn...

[Andrex]

> it won't make things easier for "standalone" third-party apps that only update themselves, since they will continue to be marked as originally installed by a browser or file manager app

I'm not 100% sure, but I think you're incorrect about this.

From TFA:

> However, user action won’t be required for an app install/update if all of the following conditions are met:

> ...

> The installer is either updating *itself* or installing an update to an app it first installed.

Emphasis added by me. If you request the new permission, target Android 10+, and update yourself, the user shouldn't be subsequently prompted.

(If my reading is correct.)