Can it be solved via creating single super-duper app that is runner some pieces of functionality that are plugins for the officially registered single “shell” app? The single purpose of shell app is to provide native android “environment” and “services”, which technically is some “browser” app, which supports some extensions to run some apps which are can not be run outside of that shell app, which would create shortcuts/icons to these plugins at the launch screen?
These plugins can use some exotic package format like zip with special structure, and use html or xml like files for UI and webassembly like files (or even standard Java class files but native android classes are never touched) for compiled code, or even bunch of js files, and json for preset data like localization files and other “textual/non-binary resources”?
I asking this in context of for example apps for DeltaChat. Would Google demand full registration flow for DeltaChat app, with developer identification, registration paperwork and related fee collection?
Registering such app via a NGO/foundation would keep a temporary sneakhole for Android, until free mobile devices, e. g. some mobile distros for linux (or some other compatible OS without systemd and US-compliant eerie code in kernel), able to start AOSP-compiled apps?) will get some wider adoption.
Sadly, due the nature of IT and how adoption of new OSes and other such stuff happens, such “plugin hole” is single way to go, as I see.
Leave a Reply