Project Treble: a lifelong technical debt
Sometimes one mistake in developing the architecture of the product can cost you dearly. There was such mistake in Android OS, and to fix it Google had to invent a new language (HIDL), bindarized HALs, VINTF objects and many other interesting things, as a whole called Project Treble. If you want to know what it it, what’s it for, what did it cost Google and how it will influence the developers and end users of Android devices, you should come and listen to the talk.
This talk is a take on Project Treble from people who had to delve into it. It deals with what until recently was a main problem of the Android OS — fragmentation of the ecosystem to different versions — and about all that Google had to change in the Android architecture to solve this problem.
Fyodor will tell about all the main components of what Google calls Project Treble and about what are they for:
what’s the difference between Binderazed and Passthrough HALs;
why Hardware Interface Definition Language had to be invented;
how the partitions on USB flash drive for Android device should look like now;
how Device and Framework use Vendor Interface Object to decide whether they are going to work together.
All of these questions will be laced with personal experience from working with these components. But the main idea of the talk is that from the very first day Android had a problem on the architecture level. Project Treble is a solution for this problem: expensive, bulky and a great illustration of how troublesome the technical debt could be.