|
Also, after some reading on the stock firmware, there is a fair solution to third party apps and stock apps while maintaining a theme (more on themes later) or UI.
If you produced a system or app (lets call it "system default app handler" or "SDAP") that handles app defaults with an automated disable system, this would allow you to build a firmware with stock apps and additional apps.
The stock apps would be kept in "app" and "priv-app" and all other vendor apps made to be installed via "preload", allowing for removal and-or replacement of the app, a device wipe-reset will re-install them.
You may need to program the app to allow certain vendor signed "preload" apps to act as if they where in "app" or "priv-app", it's probably better to make them just installable as third party.
The SDAP will need to override the current "activity" shortcut, this allows the user to manage app defaults, and when a new default app is selected, all other apps get disabled.
If the current default app is disabled or uninstalled by the user, the SDAP will switch to the previously selected, next in list, or stock app.
In the event the device must be wiped or reset the SDAP will need defaults, which initially will be vendor based.
----
Themes:
Is is possible to design a system UI that allows the user to change the system wide theme, for example make the phone look like another version, by choice.
A good feature would be to make the system menu look like say Andoid 6, or custom, and the home screen say Android 7, or custom.
The app should have access to a store where users can generate thier own themes and submit them.
|
|