Developer UX at Google
Google should do this for regular Android APIs. The frequency you have to look up special-android-things is stunning –&gt; disrupts your flow = very bad<p>There are way too many things you have to keep in your head on Android to get things right (<a href="https:&#x2F;&#x2F;developer.android.com&#x2F;guide&#x2F;components&#x2F;images&#x2F;activity_lifecycle.png" rel="nofollow">https:&#x2F;&#x2F;developer.android.com&#x2F;guide&#x2F;components&#x2F;images&#x2F;activi...</a>). The approach Google took here - do what ever you want, we won&#x27;t tell&#x2F;force you, is pure wrong (I&#x27;m a bit exaggerating, but still).<p>Developers wasted millions of hours of dev-time and therefor money to figuring out how to do basic things, like saving application state when the device is rotated or another app comes to foreground (testing state-changes is also complicated). There were complains about how state-saving is handled, but Google ignored them for many many years. Every platform has good and bad points, acknowledged, but not having a clear-line, a way how things should be done, is to me indecisive leadership and a very big mistake I would not have expected from Google.<p>Last AndroidIO things got better with the introduction of so called &quot;Architecture Components&quot; (among other things a SQLite ORM and guide how basic things should be done, finally). I wonder what took them so long.