True. Same for Android. I feel some form of that should be part of the approach. Splitting it carelessly would likely either:

A) result in no real change: ie. instead of allocating budgets within Google, they’ll just exchange money through deals and partnerships, as separate companies, but still having pretty much the same relationship between projects and level of control (Android & Chrome would continue favoring Google interests, even as independent companies), and they’ll keep being monopolies each within their own fields (I don’t see how that’s being addressed with the split).

B) result in independent projects that push for monetization and shady schemes to try and be profitable on their own (although, to be honest Mozilla has proven that being non-profit is not a shield against this either). This actually might be a good thing if the enshittification manages to get people to switch away from Chrome to a better alternative… but I wouldn’t be so sure of that (both that they would move, or that they’d choose a better one …as opposed to say MS Edge which has just as bad of a ruler).

Stock Android does not have tools to do that verification. Just verify it from the desktop and then send it to your Android device.

But I don’t see how verifying the apk signature would help if your concern is that “you have bare to none knowledge how it works”. The only thing that would fix that would be if you actually learn how it works.

Luckily, unlike other stores that are closed source and actively and purposefully hide from you what they do, F-Droid is open source, so anyone can go to the repo holding their source code and learn how it works, or build their own themselves, as long as they wanna spend that much effort.

The “.net” makes me think it would be some online service that runs on remote servers or ties you to some online platform without any real gain other than just to increase their level of control over the customer.