I spent the last 7 years thinking of what should be the best Android architecture in terms of simplicity and maintenance, in terms of excellence in the Android programming context. I teach this vision during all those previous years, providing trainings, conferences, books, tutorials, articles, Github projects.
And this year I faced an awesome challenge in terms of architecture for an important project that will impact billions of users in the future. I had a team of 12 full time developers to make it. We spent a year on it. And we make it scalable in term of features, developers’ team and end users.
The project is now used to create the next generation of Android applications for connected car for the biggest car company. It has two faces; an application and a SDK.
This is the perfect time for a feed back, what worked, what didn’t, why you should avoid Rx and focus on testable architecture. Are there different architectures between a SDK and an application? What are the concerns when creating a SDK? If your application can not be a SDK, did you miss something?
Let’s say, we’ll have a discussion, a deep one, about Android architecture.