Android Apps Now Unofficially Able To Run On Any Major Desktop OS
An anonymous reader writes A developer who goes by the handle Vladikoff has tweaked Google's App Runtime for Chrome (ARC) to allow any Android app to run on any major desktop operating system, not just the handful announced last week which were also limited to Chrome OS. His tweaked version of ARC is re-packaged as ARChon. The install isn't very straightforward, and you have to be in developer mode on Chrome. But there's a support forum on reddit. The extension will work on any OS running the desktop version of Chrome 37 and up as long as the user also installs chromeos-apk, which converts raw Android app packages (APKs) to a Chrome extension. Ars Technica reports that apps run this way are buggy, fast, and crash often but expresses optimism for when Google officially "opens the floodgates on the Play Store, putting 1.3 million Android apps onto nearly every platform."
Why would I want that ad-laden, spyware infested, functionally crippled crap on my desktop?
I'm not sure where Google is going with this stuff, but it's a bad idea.
On one hand, you have the NDK where your standard Android flavoured Java isn't fast enough on handheld hardware. This stuff will not run under ARC, because it's compiled to target the host processor (MIPS/ARM/whatever) architecture. Then you've got the Chrome runtime, which is capable of running Android/Java apps really fast on a modern day computer. Probably fast enough that the NDK isn't required in some cases, but this too is bad because a handheld will most certainly not share the same performance.
So the only thing they've really succeeded in doing here is fragmenting the Android market even more. I'm not sure why they weren't content trying to maintain control over the handheld market, unless they're thinking that the whole tablet craze is already dying out and they need an escape plan for when people inevitably swing back to the laptop/PC side of things.
If this technology matures to the point that it's stable on every desktop OS, then the OS is reduced is reduced to simply being a platform for the chrome browser to run on to run Android Apps. That means
1. Developers gear their software to run on Android since that's where all the software and market is.
2. Microsoft becomes irrelevant as the things consumers want are the Android Apps, not the OS.
I don't think that means Microsoft will die completely, but I do think it means they become just another small player as there is no longer any vendor lock-in to their platform.
This is it; write once run anywhere has finally arrived.
Nononono. As always. "Write Once, Beta Everywhere".
Chas - The one, the only.
THANK GOD!!!
Just run Android for x86 if you don't want the overhead of emulating ARM...
I have been running andy-android-emulator just so I can have clients like instagram in my desktop instead of having to pull up my phone, if they make this stable enough then one can skip the emulator altogether. I can see the drawback for devs as people will expect the apps to function as good with keyboard and mouse in the future and will have to redo their apps/add that functionality.
But why would you want to? The interface is completely different.
It is not designed for mouse so the result is a complete user frustration.
1. I've used Android apps with an external mouse on my Asus transformer, and found the experience reasonably sensible.
2. Don't forget the "nearly every platform" comment from TFA. Apps aren't currently designed for use with a mouse, but it doesn't have to stay that way. The Android app format is coming close to being the fabled "universal binary", finally giving developers the long-promised write once, run anywhere ability.
3. In light of 2. above, it isn't too hard to imagine a future UI toolkit that can sensibly switch between touch and pointer modes.
"I've got more toys than Teruhisa Kitahara."
Something. Something. Year of the Linux desktop.
Don't fight for your country, if your country does not fight for you.
It's worth noting that the Android API already provides methods and identifiers specifically for handling mice and styluses. see http://developer.android.com/r... and http://developer.android.com/r...
http://www.genymotion.com/
"Genymotion, the fastest Android emulator for app testing and presentation."
I used the free version just so I could see acertain app really work (www.flightradar24.com) and was impressed.
You can't be ahead of the curve, if you're stuck in a loop.
Have you actually tried it ? I've got an Android **desktop**, and it's usable. Most apps understand mouse buttons and wheel; the lack of the usual sensors and touchscreen is only a problem in some games.
Things could be better: I miss keyboard shortcuts, right click for Back is silly, and zooming in/out seems to be up to the OEMs. But overall, it's more than usable.
The Cloud - because you don't care if your apps and data are up in the air.
android-x86 is a bit of a dog's breakfast. They only kick out a release image every now and again, everything never works, lots of crashes. The latest 4.4 image is way less stable than the last 4.0 image they put out, and they stopped building nightlies and so did everyone else. It's really quite useless and always has been, because they never actually finish a release. Google kicks out a new version, they say "Ooh, shiny!" and they move on before they actually get the system working reliably or properly. Then you get to deal with all the apps that won't work right on x86 on top of that. It makes far more sense at this point to go ahead and run the emulator.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
So what? Apps are already including modified interfaces for various resolutions.
Why not have one app and trim functionality based on screen size. So your 4" phablet gets one interface, your 7" tablet gets a slightly modified version of that. a 10" tablet and laptop gets another.
Windows 9 is supposedly going to do that. tablets will get metro, but laptops and desktops get the old. There is no reason why you can't push the metro interface all the way down to windows phone resolutions on the same device. attach an external monitor and a bluetooth keyboard and presto you have a standard desktop display.
i thought once I was found, but it was only a dream.
(this sound like the great shareware days of the 90s - and we moved on for a reason (tucows et al.))
Millions of people still flock to "shareware" sites like Tucows and Downloads.com (Now a part of the c|net family). If you mean by moving on Tucows main business is now an ISP wholesaler to resellers who need a web presence but don't want to hire an entire web team and running a wildly popular MVNO (Mobile Virtual Network Operator) Ting as well as domain registration and services to help a business build an online presence then yes they've moved on.
To keep this post on topic how is this different than Bluestacks? I've been using it forever to run Android apps on my PC. I've heard people pan it for being buggy but I've never had any problems with it.
"A person is smart. People are dumb, panicky dangerous animals and you know it." - K
Wasn't Java supposed to do just that?
Ok maybe there is still work to do
Sent from my ASR33 using ASCII
Why are you being modded down for commenting on yet ANOTHER reddit commercial? Don't they know that Slashdot is being absorbed by them?
So I can finally play Candy Crush on my PC ;-)
Kidding aside, I wouldnt mind Angry Birds Epic on my PC, and wouldnt this make loads more money for companies like Gung Ho who were raking it in w/ Puzzle and Dragons and now can code once but have everyone with a PC spending money on their games? Seems like win-win to me, IF IF IF it works properly.
entirely doable with what I have installed on my laptop: Virtualbox. Set up a VM in service mode, release a port to the LAN, log in and the thing automagically sends a window manager in device native resolution (or whatever resolution I have the window set at - it even dynamically adjusts so I can drag corners to resize and not lose anything). Hell, I can run a client from a PII on a VGA screen and have it not only display but interact with an instance of Windows 7 Ultimate with all its bells and whistles going off at once.
Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
You can already do this using Bluestacks. It's alot better than that terrible emulator that comes with the sdk.
It was, but Sun fragmented Java ME (Micro Edition) so they could get millions in licensing fees from all the different variants of the runtime engine since they were pretty closely tied to each phone's hardware for performance reasons.
It's not like today, when we have quad core phones with oodles of ram for under $200, and tablets breaking the $100 barrier, and we can afford to run a generic runtime.
"Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
Hey, Windows 8 wasn't designed with the mouse in mind either, doesn't stop people from using it...
I hope EA sues the hell out of this guy for using the trademarked name "archon"...just because he capitalized it differently that EA did for their game....
Sleep your way to a whiter smile...date a dentist!
What you're looking for is a Chromebook or Chromebox. Stripped-down, does all the basics really well and the new generation of Tegra K1-based Chromebooks have over 10 hours of battery life.
Google has already shown a couple of Android apps running natively on ChromeOS, and the proof of concept of basically all Android apps running as Chrome apps is another step in that direction.
Eat the rich.
Or if you're okay with it being x86 Android, just install it in VirtualBox or VMWare.
How dare they blaspheme the name of the Holy Google. Giver of search results and maps and storage to all of mankind..Blessed be the Stock of the Holy One. Amen.
Really, though. Why do you automatically lash out at this person and accuse them of being an "other"? you sound like a religious zealot. He could very likely be a linux admin, neckbeard and all. Maybe he's an apple fan. Who cares? It's irrelevant to the discussion.
Indeed. Perhaps the OP has not noted that there are a *LOT* of Android TV/streamer devices out there. Most of those work with a keyboard/mouse (or, preferably, an "air mouse"). I've had no issues using the core Google Apps, Netflix, XBMC-android, etc. Perhaps "Angry Birds" might be a little annoying with a mouse but more of the media-centric stuff works very nicely. As it is I've pretty much migrated my former Linux media box to an Android box that runs Play, Netflix, XBMC, and a few other media apps.
Don't forget the "nearly every platform" comment from TFA. Apps aren't currently designed for use with a mouse, but it doesn't have to stay that way. The Android app format is coming close to being the fabled "universal binary", finally giving developers the long-promised write once, run anywhere ability.
Heh. The dream of the 90s is alive on Slashdot.
It wouldn't be the first. Java and HTML/JavaScript long beat Android to the punch. In fact, HTML/JavaScript does it better. OpenGL ES on Android isn't exactly platform neutral (my Mac doesn't have an ES driver for it's Nvidia/Intel hardware so the best it can do is software rendering, while WebGL is abstracted so it can render it perfectly.)
We can use the lessons from it's forebearers to tell why it won't be adopted in the marketplace as a universal app solution. Both Java and HTML/CSS make universal app deployment technically a reality. For the past 20-ish years I've been able to write a Java app and deploy it on any platform. HTML/CSS run well on both desktop mobile devices as well.
The usability problem that is always run into is that by pretending all platforms are the same, the usability strengths of each platform are ignored. A mouse and pointer is a really really basic example that both iOS and Android can handle, but what about security models? The Android security model, OS X security model, iOS security model, and Windows security models are entirely different. Apple platforms like to give capability access capability by capability, at the time they are accessed. Android doesn't work like that at all, it wants everything up front. So an Android app trying to access my Address Book doesn't at all have the API to do so on my Mac.
Or what about contextual menus? I expect those on a Mac but Android doesn't have them. Macs also draw differently. They expect scrollable content to slow under window sidebars and titlebars. Android doesn't expect that. You can't make an Android app act like it's running natively on a Mac without reflowing all the widgets in the window. And Android apps don't have multiple windows. I expect that on a Mac. Mac applications also have toolbars (as do Windows applications) but Android doesn't even have an API for that. All Mac applications have a re-arrangable toolbar, but Windows doesn't. Mac and Windows computers can have multiple GPUs, which means that Android would need an API to handle a window having to shuffle from one GPU context to another, and I don't think it has that... There are also font layout issues. Both Mac and Windows have different default fonts which could dramatically shift around line spacing, and what text fits where. Mac at least also has contextual definitions when you right click on a word. Will Android apps have that? My Mac apps support QuickLook in the Finder, but there isn't anything like QuickLook under Android to abstract into. I also like searching with Spotlight, but Android apps don't have any Spotlight vendors. Do Android apps ask for my user name and password to do secured operations? Again, Android apps don't have any idea of on demand security, and I really don't want to have to enter my admin username/password every time I launch an Android app. Same thing would apply to UAC.
If you hadn't stopped reading by now, you might be starting to get my point. The reason Java failed to take the desktop world by storm is that not all desktops are the same or even have the same capabilities. Yes, as you suggested, you can go down the road of adding a bunch of APIs to handle all these different scenarios. But then you're back to writing a bunch of code to support a bunch of different platforms. It's right back where you started. Java didn't end up saving time for multi-platform because the dream of writing once and running anywhere was unobtainable for desktop GUI applications, and it still is for the same reasons. It's technically possible, but the same user experience everywhere was unacceptable to users and unworkable. Even Microsoft wasn
I could not DISagree with you more. If you have supported hardware (Lenovo x230t here)
My hardware worked okay with their 4.3 release (ASUS EEE 701 4G here) but went into bootloop with 4.4-rc1. The 4.3 release was shit, mind you, but it did boot. You just had to do shit like hit the power button to wake up the lock screen. 4.0.something was the last Android-x86 release I tried which didn't asplode constantly once I got it working.
I'll keep trying every new release, but so far the only usable thing they've kicked out was obsoleted almost immediately.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Now, if it were iOS apps..THEN it would be news. There's a million different options already for running android apps on a desktop.. OK not a million, but plenty. But still not a single one for iOS apps..