Hey folks,

First of all, thanks for this awesome work. The Android community was claiming this for a long time.
Well, after attend your talk at the AndroidFestBH I would like to suggest these changes/fixes on the roadmap:

• XML ​​is a markup language (not a programming language), I would recommend to move to somewhere else like "File formats" and put it there with JSON standard.
• In accordance with the Android web-site the four App Components are: Activities, Services, Broadcast Receivers and Services (https://developer.android.com/guide/components/fundamentals). My suggestion would be move Fragments to the User Interface section.
• I can't see Notifications Block connected to anywhere. I think it can be moved to User interface section.
• imho ListView and GridView are not layouts, they are ViewGroup's. My suggestion would be add a "Data Views" section (or something) and put ListView, Spinner, RecyclerView there under UIComponents section.
• Spinner is a AdapterView, so it should be under the UI Components> AdapterView section (or to the section I mentioned above).
• Under tests section, would it be "Smoke Tests" instead of "Somke Tests"?
• All architectures under "Architecture> Code Architecture", are standards to organize the presentation layer. My suggestions would be change to "Presentation Architecture", "Presentation Patterns" or something similar.
• I would remove Volley under networking and add the "Data Transfer Format" (or something similar) and put REST, GraphQL, Protocol Buffer and FlatBuffer.
• AndroidX and Jetpack is the same thing, so I would remove AndroidX box.
• It would be nice to have a reference for each jetpack component from its respective topic. Eg: SQLite -> Room, MVVM -> View Model, Services -> WorkManager, Activity / Fragment Lifecycle -> Lifecycle (this is missing). So, I think it's better to spread the components along the graph than centralize them in a single section.
• Under Security, add R8.
• Move (or put a reference to) Animated Vector Drawables to Animation section.

Thanks in advance ;)

To decrease doubts and explain better the objective and how to use the roadmap, will be good if we add at the beginning a section "How to read", to explain...

1. ...that the roadmap is a suggested learning path
2. ...that the correct way to read is from up to bottom
3. ...that you don't need to study and know about everything, but just search about the topics and choose what is better to apply in your scenario (and maybe when we decide about how to apply the suggestion mentioned in #3 add something extra to explain this as well)
4. ...that is a collaborative content, so, if something is missing or incomplete, you must think about how to improve it for the community

As a beginner to Android, it would be good if the user could look at the hierarchy and be able to identify what they should-know vs nice-to-know vs experimental-phase. This could be in the form of design or colour-coding.

I mean, in project we can find that json with entities -> i just wonder if there could be easy way to make anchors for this road image like imagemap in html, that could be so awesome! :)
Give me a hint, i could make further research

Now we have "Roadmap study Content" section that point to a new file that we will fill with reading suggestion, courses, etc, about our roadmap. You can add this section, pointing to the same file, in Dutch language.

I think it's important to know how to use ci for testing, building and publication, especially if you are working in a team.

tools/libs

1. https://fastlane.tools/ - set of cli tools for mobile development automation
2. https://github.com/Triple-T/gradle-play-publisher - publish apk and metadata from gradle tasks
3. https://firebase.google.com/docs/test-lab/android/continuous - cloud testing

ci/cd software

1. https://travis-ci.org/ cloud base
2. https://circleci.com/ cloud base
3. https://docs.gitlab.com/ee/ci/README.html cloud/self-hosted base
4. https://jenkins.io/ - self-hosted
5. https://www.jetbrains.com/teamcity/ - self-hosted/cloud

AsyncTask is now deprecated.

Hi ! Was this Roadmap based on that research posted on AndroidDevBr slack ?
If it is correct, should be included credits to the Android Dev Comunnity too, not only two authors.

Anyway, thanks for the Roadmap, it will be very useful !

Hi,

I think that would be nice to change XML from programming languages, because it's a markup language in the same group as HTML, maybe can group by "interface languages".

Now we have "Roadmap study Content" section that point to a new file that we will fill with reading suggestion, courses, etc, about our roadmap. You can add this section, pointing to the same file, in Spanish language.

Suggest content to our community study and know more about Android! Can be courses, articles, etc, in our new contents file that you can found here:

Contents File

As pointed out in #4 we need to make it clear how to contribute with this project and define a stardard for this.

Hello! Thank you for roadmap, i liked)
I propose to add Clean Architecture.
MVP or MVI or ... - is only presentation layer.
Understanding design for all layers of application is really important for android developer.

We had one suggestion and one fix to the roadmap image:

1. There is a typo in Smoke test that we need to fix
2. In the tests section we can specify which framework or library is used for each type of test in the pyramid or just separate two sections in test (libraries and types of tests) to clarify which purpose each of the boxes has in this tree.

Hi maybe add Jackson

I’ve thought of an idea, why don’t we collect articles and courses that relate to the roadmap just like the Open Source Society University
(https://github.com/ossu/computer-science) to help the developers find quality content and save time.
I am more than willing to contribute in this.

Android support library is deprecated. Use androidx instead