Time Line

The future

First

Design a wrapper for distribution of themes/overlays and handling updates so for the user, all they are doing is downloading a app and installing in through package manager and we keep the process as invisible and simple to them as possible.

Second

Redesign the layers app to card based views with defined categories that are a lot prettier, defined and simpler for the average user.

Third

Modular manifest tag between full themes and optional.

Example use case 1:

This will be a headache for the average user if they want to load a whole theme and be done with it. To make things easier we will give the user a choice to just load a theme all at once without even seeing the modular part unless they want to pick and choose. Here is where a full tag should come in handy to tell the layers app that is available as a full theme and give options accordingly

Now the other use for this and where optional tags should be used is where a whole set of different things can be chosen and put together.

Example use case 2:

A themer might want to put out a pure black theme and a dark gray theme as one play store listing to give users a choice, here he could distribute each in the same package to a user and then the user can pick which one they want.

Forth

Overlay downloader basically a webview that is community hosted showing off themes/overlays that the user can browse through that is also based off the same categories/filters as the app, they should be downloadable from there for free themes and link to the play store for paid themes

Fifth

Prompt that tells you what type of overlays you can use (A permissions XML was suggested and it is a brilliant idea that can be used for this purpose)