3 ms·
According to this [ http://arstechnica.com/gadgets/2014/09/chrome-os-can-now-run-android-apps-no-porting-required http://arstechnica.com/gadgets/2014/09/chrome-
by georgemcbay 12y ago
According to this [ http://arstechnica.com/gadgets/2014/09/chrome-os-can-now-run-android-apps-no-porting-required http://arstechnica.com/gadgets/2014/09/chrome-os-can-now-run... ] no porting is required.
But with that in mind, it is unclear from the posts I've seen why the list of available apps is currently so small and why working closely with Google is required to get your app up and running right now, perhaps this is just due to the runtime being very much in active development and not supporting the entire set of Android APIs yet.
- pgrote 12y agoThanks. I was wondering why the few number of apps right now if it isn't a rewrite.
- Zigurd 12y agoMy guess is that some app manifests might have to set tighter compatibility restrictions, and would run, but poorly, on this environment. Non-game, non-SDK apps that don't have required accelerated visual transitions are probably the best candidates. But that's not a situation most developers are explicitly coding and testing for.
- dragonwriter 12y ago> perhaps this is just due to the runtime being very much in active development and not supporting the entire set of Android APIs yet. Probably this: its in beta, so they are probably working with individual, high-demand apps to assure that they work (and by doing so validate the runtime itself) to manage the scope of potential consumer-facing bugs.