It is really an interesting aspect of the whole Android versus iOS &quot;war&quot;, that indeed Google did not up-front plan to make the OS actually useful for realtime Audio&#x2F;synthesis&#x2F;processing; but instead, Android has had more of a &#x27;data-center&#x27;-like design, wherein the kernel and its onboard assets is more of a &#x27;managed host&#x27; than it is &#x27;realtime embedded&#x27; sort of system ..<p>That the Android designers are having to play catchup with this speaks a lot, I think, of how significant design-decisions were influenced by the territory from which the originated - the web, managed systems - and the realm which they hoped to capture - the embedded system in your pocket. Android was not designed up-front to be an amazing media system; iOS, was.  Thus, iOS has more synth-plugins and a vibrant, thriving Audio-Application eco-system (seriously, its million-dollar) whereas Android has a lot of new players, but so far: not such a great playground, really, for &quot;Musicians&quot;.<p>In fact, while iOS has really impinged upon the Music-Instrument (Digital) industry, Android has yet to make a dent.<p>So it is an interesting time to be having new solutions to what have been, relatively, frustrating and troublesome aspects of Android realtime Audio, as a developer.