I’ve been programming in Java for a long, long time. I’ve learned what it takes to write and maintain big (as in million-lines of code) software in Java and I’ve witnessed industry-wide struggle to avoid and contain the dreaded NullPointerException (NPE) that seemed to plague any reasonably-sized Java codebase. This realization of the danger of the null reference had dawned on the industry way before its inventor, Tony Hoare, had admitted in 2009 that null reference was his “Billion Dollar Mistake”.
Not so long ago we have realized that a mobile application is not just thin-client but it’s a huge diverse logic which we need to organize. That’s why we have been inspired by the ideas of Clean architecture, we understood DI and we learned how to use Dagger 2 correctly, and now we can split any feature into layers with closed eyes.
You have a fantastic feature in your application that requires your users to swipe a view up to open it. But your users do NOT use it. WHY?! Of course, because they are not aware of that awesome feature. Let’s help them discover that feature.
Over the past year, Google has worked closely with partners to create consumer products powered by Android Things with the Google Assistant built-in. Given the successes we have seen with our partners in smart speakers and smart displays, we are refocusing Android Things as a platform for OEM partners to build devices in those categories moving forward. Therefore, support for production System on Modules (SoMs) based on NXP, Qualcomm, and MediaTek hardware will not be made available through the public developer platform at this time.