It’s Been Real, Android: Why I’m Retiring from Android
A while back, Dianne Hackborn famously said:<p>&quot;We often see questions from developers that are asking from the Android platform engineers about the kinds of design patterns and architectures they use in their apps. But the answer, maybe surprisingly, is we often don&#x27;t have a strong opinion or really an opinion at all.&quot; (1)<p>While that may have been a lofty ideal, in practice Android has many strict requirements on how you partition your code between Activity, Fragment, ContentProvider, and Service classes. Never mind testability and all the new semi-opaque &#x2F; intelligent battery optimizations Android applies to your app.<p>After all these years, I still find the most difficult and un-natural thing is mixing concurrency &#x2F; background tasks that must outlive the UI with complex UI component lifecycles. This is a frequent and necessary thing to do, and also quite awkward. The result is unnecessary complexity that often and easily permeates the code. Dianne says they have no opinions on architecture, but where I disagree is <i>concurrency is  an architectural concern</i> and there are definitely many corner cases &amp; snafus mixing that with Android APIs.<p>(1) <a href="https:&#x2F;&#x2F;plus.google.com&#x2F;+DianneHackborn&#x2F;posts&#x2F;FXCCYxepsDU" rel="nofollow">https:&#x2F;&#x2F;plus.google.com&#x2F;+DianneHackborn&#x2F;posts&#x2F;FXCCYxepsDU</a>