Sebastian offered to create a standard library template in the android-components repo[1] for the mobile SDK. Once we pick a name, this bug is about tracking the work needed to create the template. [1] - https://github.com/mozilla-mobile/android-components/

Hey Sebastian, in bug 1497919 we decided to use "glean" as a name for this project. Any chance you could kindly create the library project structure you mentioned during our last meeting?

Okay, the empty "component shell" landed. You can find it in the android components repository in components/service/glean: https://github.com/mozilla-mobile/android-components/tree/master/components/service/glean Just import the repository root into Android Studio and you should be ready to go. I added a "Placeholder" code file and a "PlaceholderTest" test file. For this component we will automatically run all tests and code quality tools for PRs and merges. On release day we automatically release the component with all other ones to maven.mozilla.org. Feel free to look at other components regarding code organization or test structure. Maybe interesting components are "support-base" (with some tools for building components) and "support-test" with helpers for writing tests. Let me know if you need any help. This week I'm in Taipei and not in my regular timezone. :)

(In reply to Sebastian Kaspari (:sebastian) from comment #2) > Okay, the empty "component shell" landed. Thank you so much for the great timing on that!