My current company, Apperian, is the industry leader in a technology called &quot;App Wrapping&quot;, for which we have several patents pending (I&#x27;m only there for another week, I&#x27;m leaving after nearly 6 years for a new adventure). Read more here: <a href="https:&#x2F;&#x2F;www.apperian.com&#x2F;mobile-application-management&#x2F;mobile-app-wrapping&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.apperian.com&#x2F;mobile-application-management&#x2F;mobil...</a><p>iOS is different, but on Android we run the decompiled binaries through software making heavy use of finite state machines to alter the Dalvik VM code. These alterations allow us to automatically add features like SSO, analytics, security, self-updating apps, etc. to native apps without the customers making any code changes.<p>Because the binaries are provided to us by customers, and distributed 100% outside of the official App Stores, the risk of app-breaking updates is much reduced.<p>Over the years the technology has matured a great amount, and most apps &quot;just work&quot;, but we still get apps that have some edge case we didn&#x27;t think of, that requires manual intervention by engineering to update the wrapping software.<p>Now, the use-case that MS has is different from Apperian&#x27;s, but similar enough that I can imagine what they are going through, especially trying to re-map the UI elements to native MS widgets. This is a hard problem that is difficult to nail seamlessly, and it is infeasible for them to tweak their code for every app. Even worse, the apps people want most (FB &#x2F; Messenger, Google Maps, etc.) are the most complex of all, so their tech needs to be super advanced to get value out of it.