I don't really follow the argument. If you are a commercial company, the Play store is pretty much all that matters in terms of business viability. At a commercial level, the fact a few geeks can side-load apps is next to irrelevant. Who builds a business on side-loaded apps?
True that. It's the blessing and curse of app stores. On iOS everyone complains there's only one App Store. On Android everyone complains the vendors and networks keep pre-loading their multifarious crappy app stores. People, eh?
An app store is really many things. It's client software for installing apps, it's a service for verifying apps, it's a hosting service for apps, it's a payment processor.
If you want to replace any piece of it you currently have to replace the whole thing, and do so all at once. Even if you create a good alternative app store, it has few apps in it, which matters if it's a separate client/interface than the main one. And you have to replicate every piece of it well for it to be any good.
So what's needed is better modularity. You don't have an "Amazon app store app", you just have a "software installer" app that shows all apps from enabled providers and then lists individual apps as "verified by Google", "verified by Amazon", etc. in the same software. When you buy one you get a list of enabled payment processors and choose "pay with Google" or "pay with Paypal" or "pay with Visa" etc. (the list being all the ones that the app developer accepts).
Then you can put your app in Google Play and let them do everything, or you can host it yourself and pay a verification service that charges a one time fee rather than a percentage and accept five different payment services but only the ones that charge less than a 5% commission, and either way it's not a significantly different experience for the user.
And whether or not Google would join in on something like that, at least Amazon/Samsung/F-Droid could do it with each other (and anyone else who shows up).
The thing you're ignoring is developer reputation. Google (or any app-store runner) doesn't want to allow you to use parts of their service—for which they could be held liable if those services take your money and give you nothing in return, or give you a virus—unless you're also using their identity system and thus their developer-reputation system.
And if you are using Google's identity system—in what way are you not just back to publishing on the Play Store? Through the identity system (and associated developer-reputation system) they can control who can or cannot publish on your app store. So it's really just their app store. It's your UX, but it's their guiding hand, just as if Google were on your board of directors.
Really, there's no point in them letting you have your own app store which relies on parts of their infrastructure, since they can tell that any implementation their legal dept would okay is a lose-lose that no dev would ever be interested in taking part in. To detach any liability for the results from them, you have to do it all the app-store stuff yourself. Which is exactly what mobile OEMs do.
> Google (or any app-store runner) doesn't want to allow you to use parts of their service—for which they could be held liable if those services take your money and give you nothing in return, or give you a virus—unless you're also using their identity system and thus their developer-reputation system.
Amazon doesn't require you to use their payment system with your customers to host your app on AWS. Paypal doesn't require you to host your apps with them to use their payment system. Mozilla doesn't try to stop you from using Firefox, or the Firefox-based Tor browser, to visit arbitrary "dark web" sites, and Debian doesn't try to stop you from adding arbitrary third party repositories to apt. Let's Encrypt doesn't even require you to use their own software to verify your site. This concept of "you can't just sell someone a screw driver because what if they kill someone and you were liable" has no basis.
Google could refuse your business for an individual component if you tried to use that component from them, but then you could just get that component from someone else. It would still be an advantage to be able to use one service for hosting and another for payments, even if zero of those services are Google.
And the problem with Google Play is the weak competition. If it was easier to use something else then they would lose more business from making poor refusal decisions (harming their reputation), by charging a high percentage, etc. Then they would either have to improve or lose their status as the dominant player. Reduced barriers, more competition.
By rooting and deleting apps , or any other modification of the /system partition, you are making it impossible to apply any patch released by the manufacturer (it is a binary delta of the volume).
Consider disabling the apps; if the manufacturer doesn't allow disabling the app through Settings, you can always do it via adb. When you disable the app, the system will ignore it and behave as if it wouldn't be there. You can't get any additional benefit from the deleting, you won't gain any additional free space, as no app can write to /system partition for the above reason anyway.
Yeah, exactly. I honestly wouldn't care much if they preloaded a bunch of crap so they can get kickbacks (which would probably translate to a slightly lower-priced phone, due to all the competition in the Android phone market), as long as I could just go delete it like any other app.
> The alternative to google play would presumably be the apple app store which, if they ban you, there is no side channel.
It depends on what you mean by "side channel". You can do a PWA instead, or use tools like Test Flight (up to 10,000 users), or leverage the Apple Developer Enterprise Program, etc.
It's very common in rural Asia. Users share apks via P2P file sharing. Typically one person in the village will set up everyone's phone for them. Usually with all apps preloaded, but they're actually quite savvy about adding and removing apps once they get going, since they're on phones with such low internal storage. If you want to make it into these markets, you need to make your app side-loadable
I actually would wish more companies had a repository that was compatible with F-Droid. F-Droid makes.it possible for anyone to make a repository and then it will handle all of the app store side of the house.
Amazon runs its own app store. It took years even with their resources to make it useful. Developers originally tossed up buggy, incomplete, and/or outdated versions of their Android apps just to say they had one on Kindle Fire.
A lot of companies do. I've actually found it's pretty difficult to get mobile apps deployed inside bigger companies WITHOUT delivering a custom build that enterprise IT rolls out on their own, even on iOS.
We do because we have android hand scanners for the production areas and handhelds for the drivers, side loading is the simplest way to get stuff onto them.
