Project directory restructure (Build Flavors)

[fdocr]

Is your feature request related to a problem? Please describe.

We've recently felt that the current project directory structure is a little too complex for our needs.

Our currently modular project directory (data, buildSrc, baseui, app) feels more appropriate for native apps that benefit from Activity/Fragment/ect reuse. In our case we deal with very few moving parts.

Describe the solution you'd like

We're open at the moment to contributions where we can simplify our project directory structure. The ideal result is a minimal directory structure where we can easily work on enhancing our main Main Activity & browsing experience with the custom WebViewClient.

The suggested changes that we're looking to see in a PR for this are the following:

• Simplified directory structure
• Consider removal of databinding
• Keep integrations we already have in the project (i.e. refreshVersions)
• Configuration of Build Flavors: To reduce contributors friction to spin up their local development and start working on the app we can provide a google-services.json dummy file for debug/development (read more about this)

Additional context

PR's for this issue are very welcome. If you have a question or want to suggest alternatives feel free to leave a comment in this issue. We are open to hearing ideas on how to make our directory a minimal version of what we currently have.

[rt4914]

Closing this as it is not required now.