Slashdot Mirror


Microsoft's Plan To Port Android Apps To Windows Proves Too Complex (networkworld.com)

An anonymous reader writes: The Astoria project at Microsoft has failed because a breakthrough was needed to overcome the complexity of the software development challenge. Microsoft tried to automate mapping the Android UI into the Windows 10 UI and to map Google services within the app such as maps, payments and notifications into Microsoft equivalents. Automated conversion of a UI from one platform to another has never been successfully demonstrated. When I first saw Microsoft's Android bridge at Build 15, I thought it was achievable. But project Astoria, as it is called, is much too complex. Drawing on my architectural knowledge of the underlying Microsoft/Lumia hardware that is very similar to Android phones.I concluded that in the context of partitioning the device or running a VM Microsoft would succeed. But Microsoft tried something much more ambitious. Rather than "failed," The Next Web reports that for now the project may have only been delayed.

131 comments

  1. TFS is oversensational? Say it ain't so! by halivar · · Score: 3, Funny

    But kudos for pointing it out.

    1. Re:TFS is oversensational? Say it ain't so! by Richard_at_work · · Score: 2

      Considering pretty much all other news sites are covering the story from the aspect that providing an Android compatibility layer has more legal issues than not (considering the unsure outcome of the Oracle vs Google API case - if MS went ahead with a compat layer and Oracle won then both Oracle and Google could take issue with it) and that providing a compatibility layer cheapens the Universal Windows Platform MS has been touting for WP10, Im not entirely sure where the angle taken in TFS has come from - seems its more sensational anti-MS stuff than anything else really...

    2. Re:TFS is oversensational? Say it ain't so! by Anonymous Coward · · Score: 0

      I would love if there were a compat layer in Windows Phone that let it run Android apps and that the same compat layer was usable on a Win 10 desktop!

    3. Re:TFS is oversensational? Say it ain't so! by Anonymous Coward · · Score: 0

      You already can do it on a Windows 10 desktop through Chrome.

      https://www.reddit.com/r/chromeapks

    4. Re:TFS is oversensational? Say it ain't so! by Penguinisto · · Score: 1

      Geez - it's not that hard - just license the Android OS from Google and give it a Windows UI skin!

      ( /me ducks and runs like hell...)

      --
      Quo usque tandem abutere, Nimbus, patientia nostra?
    5. Re:TFS is oversensational? Say it ain't so! by Anonymous Coward · · Score: 0

      "Only apps modified to run with ARChon will work."

      Good start, but I was hoping for it just being another device hooked up to the play store.

    6. Re:TFS is oversensational? Say it ain't so! by Z00L00K · · Score: 1

      At least last time I was looking into the Windows for mobile devices it had severe shortcomings but maybe they have filled in the grand canyon-sized holes in their platform, otherwise they don't have any hope of succeeding.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    7. Re:TFS is oversensational? Say it ain't so! by Junta · · Score: 1

      To be fair, a company like MS will 'delay' a project a lot before admitting publicly that it's a lost cause...

      --
      XML is like violence. If it doesn't solve the problem, use more.
    8. Re: TFS is oversensational? Say it ain't so! by Anonymous Coward · · Score: 0

      Want to buy my zune?

    9. Re:TFS is oversensational? Say it ain't so! by Anonymous Coward · · Score: 0

      > Geez - it's not that hard - just license the Android OS from Google and give it a Windows UI skin!

      http://www.microsoft.com/en/mobile/phone/nokia-x/

    10. Re:TFS is oversensational? Say it ain't so! by KingRatMass · · Score: 0
      No license need to pull from the AOSP repo... Any licensing with Google is for the Google Mobile Services apps, the suite of application that are the "googly" parts of most android phones. Play Store, Gmail, Maps, etc... The agreement is called MADA, Mobile Applications Device Agrrement. It's a two year contract between a handset OEM and Google that licenses the suite and requires that it be installed on the OEM's handsets. The downside of the MADA is that it disallows the OEM from forking Android and creating their own distribution. Company pairings of OPPO/Cyanogenmod and Amazon/Foxconn are examples of devices that do not have GMS because no MADA was signed. Alibaba and Acer attempted to fork Android and Acer was smacked down by Google's legal team because of their MADA.

      Microsoft could push out their own fork of Android easily... They may already have such a creature in the works, judging by the apps coming out of Microsoft's Garage. They have the Arrow Launcher, Next Lockscreen, Bing, Cortana and MS Office for Android... The only three major parts missing are the app store, mapping software and payment app. But if they enter into a MADA with Google, they are locked out of creating a fork for two years.

      This would not be a terribly bad move for MS, they would essential be taking a play from Tom Sawyer and they could leverage all the development being done by the hardware makers, OEM's and other source code contributors.

    11. Re:TFS is oversensational? Say it ain't so! by KingRatMass · · Score: 0
      I can add that I have a working prototype of what it would be like in it's present state. I took my Nexus 4 and installed the Mako Lollipop AOSP ROM, no GMS apps are installed with a pure AOSP build. I then installed the pico version of Google Apps, which is JUST the Play Store. From there I installed nearly every useful app that MS has published to the Play Store. All the apps I listed above and a few others like Skype. Incredibly, the phone actually runs well, very fast and stable. The Arrow Launcher and Next Lock Screen are actually quite innovative and have some unique feature not found in most builds.

      It's a damn sight better than the last ROM I was running on my Nexus 4: Ubuntu Phone. What a piece of dogshit that is! This is coming from someone that ditched MS on the desktop and server many years ago and has not seen a reason to go back. What I've seen from even a half baked pseudo build of a MS Android phone is almost enough to make me a believer in MS again.

    12. Re:TFS is oversensational? Say it ain't so! by exomondo · · Score: 2

      I would love if there were a compat layer in Windows Phone that let it run Android apps and that the same compat layer was usable on a Win 10 desktop!

      The general consensus on Windows 8 was that people did not want phone-style apps on desktops.

    13. Re:TFS is oversensational? Say it ain't so! by Anonymous Coward · · Score: 0

      I would love if there were a compat layer in Windows Phone that let it run Android apps and that the same compat layer was usable on a Win 10 desktop!

      The general consensus on Windows 8 was that people did not want phone-style apps on desktops.

      Android apps are what people are used to on tablets. Being able to run those Android apps on a Microsoft Suface Pro under Windows 10 when using it as a tablet would give MS a huge advantage.

    14. Re:TFS is oversensational? Say it ain't so! by Bert64 · · Score: 1

      And that's the effect of competition...
      They actually have to compete in the mobile market, while on desktops they take their customer base for granted.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    15. Re:TFS is oversensational? Say it ain't so! by Anonymous Coward · · Score: 0

      Unfortunately, the legal concern will overshadow any technical concern.

      Most Android software that is written against the "java" dalvik cruft will be a monster to create compatibility with. Think of the Wine project, now add the additional complexity of 50 different vocabularies (compared to Windows which has Win16, Win32, Win64, and the rare WinARM and rarer WinRISC/WinMIPS/WinIA-64(Itanium) which the API only adds features between versions, doesn't break them except in the different vocabulary versions), An Android program might be written against 1.x or 2.x or 3.x or 4.x or 5.x versions of Android, and may be on ARM, MIPS, RISC, X86/X86-64, or anything else that Linux can be compiled for.

      Like ignoring for the moment the different CPU architecture, the point of "bridge" is to take your project from Android (or iOS), and recompile it straight on windows without having to go through the quandry of the HTML5 webview route. With iOS, this is fairly simple because Swift/OBJC compiles into machine code, so MS can write their own compiler, and we're done. With Android, it compiles to a "Virtual machine" intermediate representation which means Android software still needs VM/interpreter to run an Android program, and since the vast majority of developers who write anything cross-platform and port to Android hate dalvik, they actually write the minimum amount of code for it, and then just run the rest of their application in C/C++, which means Microsoft must ALSO emulate how GCC/LLVM creates linux binaries.

      Like from Microsoft's point of view, it's not really worth it. Even if they somehow jump through all the hoops necessary to create such a monster, it's going to have the god-awful performance of an Android device, not native performance. It's better for Microsoft to focus on iOS bridges, because that allows developers to bring their best version of a cross-platform project to Windows instead of bringing the mangled android dalvik version.

  2. Honestly ... by gstoddart · · Score: 4, Insightful

    Honestly now ... did anybody believe this could be achieved? I'm pretty sure lots of people looked at this and thought "yeah, right, never gonna happen".

    This is why people have been maintaining cross-platform libraries to solve this problem -- because it's a huge and difficult problem.

    Automagically converting apps from Android to use all the Windows stuff? That always sounded like a pipe dream. They'd be better off writing something like a reverse Mime to allow native Android apps to run on Windows.

    I am not in the least shocked Microsoft isn't going to create the magic path to putting Android apps on Windows phones. And, honestly, I'm not sure the Android users ever expected to care about this, this was all about trying to lure people to Microsoft's platform.

    As usual, Microsoft can only see the world through their own lens, and have yet to demonstrate they know what people are actually looking for.

    --
    Lost at C:>. Found at C.
    1. Re:Honestly ... by Anonymous Coward · · Score: 0

      >Honestly now ... did anybody believe this could be achieved?

      I did. BB has been running Android apps on their non-Android products since 2011 (playbook). The support is now good enough it is rare to find one that doesn't work. Of course, that extra support didn't get backported to the PB, and you need a BB10 device for it.

    2. Re:Honestly ... by Anonymous Coward · · Score: 4, Interesting

      Of course it can be achieved!

      Ever heard of Jolla? They are a small Smartphone manufacturer created by former Nokia employees who were let go when Microsoft bought up the phone activities of Nokia.
      => jolla.com

      Ever heard of sailfish? It is an operating system based on Linux and Qt, with its origins in the next Linux OS developed by Nokia. It was suppose to replace the OS running on the N900 (which used GTK for the UI). That was before that smart guy Stephen Elop became CEO, if you know what I mean...
      => sailfishos.org

      So what, you ask? Jolla runs sailfish and sailfish contains an Android runtime (VM + glue code + libraries).

      In a sense, I just love the irony of the situation!

    3. Re:Honestly ... by gstoddart · · Score: 1

      So what, you ask? Jolla runs sailfish and sailfish contains an Android runtime (VM + glue code + libraries).

      In a sense, I just love the irony of the situation!

      Which is essentially what I said: instead of trying to write something which re-maps all of the Android stuff to Windows to try to create a native app ... implement an Android runtime, or a layer like Mime which allows the Android calls to run without caring it's Windows underneath.

      The problem is Microsoft was trying to map it to their own native calls and toolkits.

      What I'm saying is unlikely to be achieved is something which automatically takes and piece of software and maps it to Microsoft's stuff as if it was a native app.

      My bet is Microsoft was so invested in trying to make native apps they failed to make working apps, because they chose the solution with the highest complexity.

      --
      Lost at C:>. Found at C.
    4. Re:Honestly ... by ripvlan · · Score: 1

      I'm pretty sure they put it on a shelf for now - and that developers can still take a look at it. I don't think open source - but it is still available for people to play with and take a look at it. Gosh - can't remember my source, maybe a recent Dotnetrocks episode?

      Apparently there were parts that they couldn't figure out - and the implementation was becoming ugly.

      Sounds like the approach was never going to work out - so they are taking time to rethink it.

    5. Re:Honestly ... by Anonymous Coward · · Score: 0

      Honestly now ... did anybody believe this could be achieved? I'm pretty sure lots of people looked at this and thought "yeah, right, never gonna happen".

      I see no technical reason they couldn't achieve it. The user land of Android is fairly minimal, most apps are running in a VM anyway and even those that reach out to native code are talking through well defined interfaces. On top of that, all the source code is there. On top of that, it's already been done and there are people advertising Android on Windows already.

      If Microsoft dropped the project its probably for strategic reasons. One of the main reasons OS/2 flopped was it offered Windows 3.1 compatibility. Few companies bothered porting apps from Windows to OS/2 when they already ran over there. Fast forward a few years and RIP OS/2. And Blackberry tried Android compatibility and it didn't work out too well for them either.

    6. Re:Honestly ... by Anonymous Coward · · Score: 0

      Automagically converting apps from Android to use all the Windows stuff? That always sounded like a pipe dream.

      Converting users from Android to the Windows stuff? That always sounded like a pipe

    7. Re:Honestly ... by unrtst · · Score: 1

      The problem with what you're saying is that you're blaming the complexity/difficulty and saying it's not possible. That's just plain wrong. It's certainly possible. Is it feasible? Even if it was feasible, if they did it, would it be a good thing?

      I suspect this is pretty much a bait and switch type of situation - lure people along thinking they'll have the entire android ecosystem available, and then just give up on that project as they slowly get the top NNN apps to move over to native apps. They don't want really want this to work, and there would be a lot of work in keeping it functional and secure and updated... it's just not worth it to them.

    8. Re:Honestly ... by narcc · · Score: 1

      Honestly now ... did anybody believe this could be achieved?

      Pretty much everyone believed that. Blackberry users have been running Android apps for ages. They even have Amazon's app store. If a much smaller company can do it, and do it well, there's no reason to believe that Microsoft couldn't.

    9. Re:Honestly ... by UnknowingFool · · Score: 1

      Microsoft's current problem with Windows 10 Phone is that there are few applications. And it doesn't look like there will be many in the future unless Microsoft does something. One reason is the classic chicken-and-egg problem of customers and application: There aren't that many customers so few developers are interested in building applications; there are few applications so few customers are interested. The other is cost. By making it easier to port from Android, Microsoft would like to reduce the cost. It does cost money to develop/maintain multiple platforms; if Android developers could easily port to Windows 10, at least some of them might be willing to create apps.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    10. Re:Honestly ... by Anonymous Coward · · Score: 0

      > if Android developers could easily port to Windows 10, at least some of them might be willing to create apps.

      If Android developers could easily port to Windows 10 ... then WindowsPhone developers would not bother with changing to 'Universal' apps but would change to Android apps in the expectation that they would run on Win10 and have 50 times that market to sell to.

      If Android developers could easily port to Windows 10 ... then cross platform developers would drop their WinPhone and Universal ports and rely on having their Android apps run on Win10x.

      Then Google would make changes that made running Android apps on Win10 somewhat more difficult*.

      * Just like Microsoft made OS/2 only get Win3.1 when 3.11 was ready to be released and changed Win32s.dll so that it no longer worked on OS/2.

    11. Re:Honestly ... by unixisc · · Score: 1

      At a binary level, there are plenty of applications for Windows 10 - both native Windows 8/10 apps as well as previous 64-bit Windows 7 apps. So for Windows 10, it's not an issue

      For Mobile, Microsoft needs to come up w/ a strategy so that the killer mobile apps are there. Some are - Fandango, Yelp! and so on. However, a lot of them ain't - Uber, Lyft, Vonage are some apps that could be a make/break decision of whether a phone gets used or not. Microsoft should identify the indispensable apps and do all it can to get them to Windows 10 Mobile.

    12. Re:Honestly ... by gl4ss · · Score: 1

      some things that might be achievable would be things like the google play services location services and such.

      the payment api services however.. they would need the dev to do so much work they might just as well switch to ms apis anyways for those. they need to set the iap options on ms's servers anyways and switch the server side to do confirmations from ms. this is a task that I cannot see being automated.

      as to mapping the ui libraries? why the fuck. nothing good can come out of that, and with that I mean it would just break most ui's totally. just use the ui as it is already.

      note that they will have to provide a filesystem as well etc. might just as well run android in a vm and provide a limited compatibility library for google play services..

      --
      world was created 5 seconds before this post as it is.
    13. Re:Honestly ... by Anonymous Coward · · Score: 0

      "Android on windows already"

      You mean the really godawful "android emulators" that run at about 1/10th the speed of an actual device, and the Intel VM which gives you an x86-native Android VM but nearly none of the software on Google Play is X86

  3. Port? Really? by Anonymous Coward · · Score: 3, Funny

    I thought all Android apps were just written in Java, you know, that language that is supposed to compile and run on any platform?

    1. Re:Port? Really? by oakgrove · · Score: 4, Funny

      Your knowledge and experience is truly a credit to the Slashdot community and part of what makes this site so great.

      --
      The soylentnews experiment has been a dismal failure.
    2. Re:Port? Really? by abies · · Score: 4, Informative

      I think that you are confused about java-the-language, java-the-standard-library and java-the-platform. Android is java only as far as first one is concerned. And I don't think that this is giving any troubles with possible porting.

      Basic subset of C is quite portable, isn't it? Then according to your logic, game written for Xwindows+opengl should work against MSWindows+DirectX without any issues...

    3. Re: Port? Really? by WarJolt · · Score: 1

      Android runs portable byte code unless you're using the NDK. It's not java bytecode. For example one big difference is that it's register based instead of stack based. Arm had a ton of registers. X86 only has a few general purpose ones.

      To get the integration that Microsoft seeks they would have to reimplement a good portion of the runtime, which heavily depends on Linux. For example android has a rather sophisticated IPC mechanism.

      It's unlikely this will get done without QEMU.

      In summary most android apps are usually architecturally portable, but the runtime is not.

    4. Re:Port? Really? by pseudorand · · Score: 1

      I think that you are confused about a earnest question vs a rhetorical question.

      Seriously though, we software developers should never miss an opportunity to ask "how's that platform-independent Java working out for ya?" so that the business guys remember why they need us.

      It's also not true that platform independence hasn't been achieved. It's just that we call it "open standards". There are many examples, but in terms of a full application stack, HTTP/HTML is probably the best. Sure, it took the w3c and browser makers a (very long) while to get down to business, but we all stopped testing every change in 5 different browsers about 5 years ago and a year or two ago we got vector graphics and 3D when HTML5 became broadly supported.

      The only remaining question is why Apple, Google and Microsoft all insisted on making smart phones and tablets entirely new beasts, incompatible with each other and with the modular, cohesive, loosely coupled web-based application stack that is obviously the clear winner for just about everything else (sorry embedded device guys).

      And yes, I know your smart phone browser can display HTML and the newer ones with more RAM than your laptop had 5 years ago do 3D and overly-busy pages just fine. But if a dev needs access to all those mobile-devices specific features like GPS, notifications, access to contacts and other such info, raw IP/Sockets, IPC, etc. (s)he has to learn a whole new programming paradigm (make that 3 whole new programming paradigms) rather than just reading the docs for some new Javascript API calls.

      And No, I'm not suggesting mobile browsers throw out the security boundary and let untrusted code do anything it wants. But a mobile device OS could have been just a web browser on steroids and an "app" could have been a single-archive-file website that did have access to the filesystem, the network, etc. after appropriate signed-code checking, user notification/acceptance and maybe even OS-vendor approval.

      To be fair, it's no mystery why it didn't go that way. That slimy goo you find oozing out of your phone isn't a defective battery -- it's Steve Jobs', Larry Page's and Steve Balmer's drool which flows more freely when they hear the word "lockin" than if you gave pavlov's dog a real T-Bone. So thanks guys. Thanks for learning nothing at all from the PC marketplace. Thanks for saddling us with yet another set of crappy technology stacks. Thanks for laughing at us from your expensive yachts where you have your personal secretary do all the things that need to get done while we sit here cursing our "smart" phones because they simply don't do enough, don't do it right, don't talk to each other and are generally designed for you to collect data about us rather than to help make our lives easier.

      I hope all of your yachts sink and you're eaten by sharks (lava-sharks in Jobs's case).

      </rant>

    5. Re:Port? Really? by Anonymous Coward · · Score: 0

      > But if a dev needs access to all those mobile-devices specific features like GPS, notifications, access to contacts and other such info, raw IP/Sockets, IPC, etc. (s)he has to learn a whole new programming paradigm (make that 3 whole new programming paradigms) rather than just reading the docs for some new Javascript API calls.

      You've not heard of Phonegap/Cordova then ?

    6. Re:Port? Really? by bondsbw · · Score: 1

      The only remaining question is why Apple, Google and Microsoft all insisted on making smart phones and tablets entirely new beasts, incompatible with each other and with the modular, cohesive, loosely coupled web-based application stack that is obviously the clear winner for just about everything else (sorry embedded device guys).

      But, Microsoft didn't. UWP/WinRT apps can be built using HTML/JS/CSS. (Or C#/XAML, VB/XAML, C++/XAML, or C++/DirectX if that's what you prefer.) Additional APIs can be accessed for platform and device capabilities like notifications, live tiles, persistence, 3D printing, etc. And you get the same security sandbox guarantees.

      --
      All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
    7. Re:Port? Really? by david_thornley · · Score: 1

      The only remaining question is why Apple, Google and Microsoft all insisted on making smart phones and tablets entirely new beasts, incompatible with each other and with the modular, cohesive, loosely coupled web-based application stack that is obviously the clear winner for just about everything else (sorry embedded device guys).

      Originally, only Apple could write actual apps for iPhone. The Apple line then was to write web apps that will run on Mobile Safari. After they made such programming available, there were plenty of apps that were thin skins over websites. In short, Apple initially required iPhone developers to use the web platform, and people complained loudly. Then they made it easy to implement web apps, and everybody started writing actual iOS apps again.

      Apple didn't insist on iPhones and iPads not working with web apps. They just didn't insist that iPhone and iPad should use web apps, and the developers and users went out and did what they want. I don't see how it could be Apple's fault.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  4. Not surprised by Tyrannosaur · · Score: 1

    Running android on my phone, I notice that there are a lot of very buggy apps. Even assuming the apps all worked perfectly, I imagine it'd be way hard, but with buggy ones...

  5. wine? by Anonymous Coward · · Score: 0

    Microsoft attempting to implement a Wine-like solution for its phone OS?
    How ironic.

    1. Re:wine? by SpectreBlofeld · · Score: 1

      Not really. From what I understand, the plan was to make it easy for developers to port over apps they wrote for Android without having to re-write it for Windows (an automated conversion), not to provide a compatibility layer. Basically to re-compile the code in such a way that it becomes a native Windows app.

    2. Re:wine? by Anonymous Coward · · Score: 0

      Not really. From what I understand, the plan was to make it easy for developers to port over apps they wrote for Android without having to re-write it for Windows (an automated conversion), not to provide a compatibility layer. Basically to re-compile the code in such a way that it becomes a native Windows app.

      Nope, the plan was to make APK's run untouched on Win (and many did (!), on the leak that came out a few months ago). Microsoft presented lot's of java stuff to devs so that they could interface to different microsoft API's in existing code in their favorite IDE. Just look at the keynote...

  6. GenyMotion by jtara · · Score: 1

    All they have to do is license GenyMotion.

    It's meant for Android developers, but could work for this with a new skin. It runs X86 Android in VirtualBox So, you build your project for X86. I build for dual X86/ARM and use the same executable on physical devices and GenyMotion.

    I run it on OSX. It really is the only practical solution for Android simulation on desktop. The Google-supplied emulator is dog-slow to the point of total uselessness, and Intel Haxm isn't much better. GenyMotion is a joy.

    Don't work for them, just a happy user!

    It is pricy, but they have a $99/year option for Indie developers. (I think individual or company with 3 or fewer developers.)

    I'm sure Microsoft could cut a deal.

    1. Re:GenyMotion by jtara · · Score: 0

      OK, /. is totally wacky now. I guess it was /. that made the subject "Score:?" That's what happens when the "professionals" take over!

    2. Re:GenyMotion by fhage · · Score: 4, Insightful

      All they have to do is license GenyMotion.

      It's meant for Android developers, but could work for this with a new skin. It runs X86 Android in VirtualBox So, you build your project for X86.

      Microsoft would never do this because It's not in their interest to build something which connects a customer to Google's services.

      They want to replace the entire Google cloud services infrastructure with Microsoft services.

    3. Re:GenyMotion by idontgno · · Score: 0

      You're blaming slashcode for your double post?

      Ok, fine, that's actually quite credible. But still, a craftsman doesn't blame his tools.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    4. Re:GenyMotion by Anonymous Coward · · Score: 0

      You're blaming slashcode for your double post?

      Ok, fine, that's actually quite credible. But still, a craftsman doesn't blame his tools.

      If your chisels are all blunt, or your screwdrivers have all snapped in half, if your tape measure is metric, or if you're on /. then you do.

    5. Re:GenyMotion by LordWabbit2 · · Score: 1

      They want to replace the entire Google cloud services infrastructure with Microsoft services.
      You hit the nail on the head there, and I think that is one of the main reasons for the delay/abandonment of this project. Even if they could get an approximation of Googles services up and running they would probably run into a wall of lawyers, so even if it was technically feasible (albeit extremely complicated) would it be legally feasible?

      --
      There are three kinds of falsehood: the first is a 'fib,' the second is a downright lie, and the third is statistics.
  7. GenyMotion by jtara · · Score: 1

    All they have to do is license GenyMotion.

    It's meant for Android developers, but could work for this with a new skin. It runs X86 Android in VirtualBox So, you build your project for X86. I build for dual X86/ARM and use the same executable on physical devices and GenyMotion.

    I run it on OSX. It really is the only practical solution for Android simulation on desktop. The Google-supplied emulator is dog-slow to the point of total uselessness, and Intel Haxm isn't much better. GenyMotion is a joy.

    Don't work for them, just a happy user!

    It is pricy, but they have a $99/year option for Indie developers. (I think individual or company with 3 or fewer developers.)

    I'm sure Microsoft could cut a deal.

    (Sorry for dupe, posted first as a response to existing with irrelevant subject. Slashdot, do we still have to party like it's 1999? How about ability to edit posts?)

  8. SUICIDE IS NEVER THE ANSWER!! by Anonymous Coward · · Score: 0

    But always a question looking for one!!

  9. I wouldn't count on failure yet by Actually,+I+do+RTFA · · Score: 1

    Microsoft has an amazing history of backwards compatibility. I mean, the SimCity hack is just my favorite, but they go on and on. If anyone can overcome the delays (not failure) in porting over Android programs, it's Microsoft.

    And that's without taking into account their EEE mehtodology. Excel took off the same way, being 100% compatible with 1-2-3.

    I don't understand why the GUI would even be difficult. There are a finite number of calls. All they have to do is be slavishly followed. If you want to make the GUI feel more MS'y, that'd be difficult. But first they embrace, then add a few MS only options, then boom.

    --
    Your ad here. Ask me how!
    1. Re:I wouldn't count on failure yet by Anonymous Coward · · Score: 0

      This puts it better than I can

      http://www.joelonsoftware.com/...

      MS is 'done'. They are slowly eating themselves. Balmer did a real trick on that company. Maybe the new dude can pull it out. But it will be exceedingly harder to do.

      People do not upgrade hardware like they used to. It used to be if you bought a new computer 1 year later it *was* in every way better. Now it is only marginally better. I know people who still use every day Vista. They have no real reason to upgrade at all. What does that mean? It means if MS wants to push a new tech they can no longer rely on people upgrading the OS which typically happened at 'buy a new computer time'. Hence windows 10 and its rolling release. For them to survive they *must* push windows forward. There other software platforms will depend on it. The telemetry being sent back is to figure out how much backwards compatibility they need to spend time on. If 3 people in the world are playing some game dont bother. But if 50 million people are playing it then it may be worth the time to reverse engineer it and write the shims. The dev market basically dried up so they are as quickly as they can open sourcing the whole dev stack.

    2. Re:I wouldn't count on failure yet by art123 · · Score: 1

      You reference an article from 2004. In 2004 Microsoft had $36.8 billion in revenue. In 2015 it was $93.5 billion.
      Is Microsoft really "done"?

    3. Re:I wouldn't count on failure yet by whoever57 · · Score: 1

      You reference an article from 2004. In 2004 Microsoft had $36.8 billion in revenue. In 2015 it was $93.5 billion. Is Microsoft really "done"?

      I don't know about Microsoft, but Windows phone is "done". Market share never reached anything like critical mass and is now dropping. App developers are actively pulling their apps from Microsoft's app store. He's dead Jim.

      --
      The real "Libtards" are the Libertarians!
    4. Re:I wouldn't count on failure yet by UnknownSoldier · · Score: 0

      > Microsoft has an amazing history of backwards compatibility. I mean, the SimCity hack is just my favorite,

      Ah, you're referring to How Microsoft Lost the API War

      I first heard about this from one of the developers of the hit game SimCity, who told me that there was a critical bug in his application: it used memory right after freeing it, a major no-no that happened to work OK on DOS but would not work under Windows where memory that is freed is likely to be snatched up by another running application right away. The testers on the Windows team were going through various popular applications, testing them to make sure they worked OK, but SimCity kept crashing. They reported this to the Windows developers, who disassembled SimCity, stepped through it in a debugger, found the bug, and added special code that checked if SimCity was running, and if it did, ran the memory allocator in a special mode in which you could still use memory after freeing it.

      No wonders Windows is so buggy. They keep enabling other people's crap.

    5. Re:I wouldn't count on failure yet by Jerry+Atrick · · Score: 1

      I don't understand why the GUI would even be difficult. There are a finite number of calls. All they have to do is be slavishly followed

      There may be a finite number of them (vast but still finite), they're sitting in a sea of asynchronous execution while maintaining internal state. If MS don't just clone Android source, manually reproducing all the subtle interactions adds a huge level of complexity to the task.

      Get that all working and you still have to replace the rendering layer or accept the graphics won't render identically, shim the hardware drivers and fake up an interface to hide lots of timing and formatting issues with the hardware.

      Then remember, Microsoft has spent years telling people how much more efficiently Windows uses hardware than Android. That's suddenly not true.

      It's not easy.

    6. Re:I wouldn't count on failure yet by Actually,+I+do+RTFA · · Score: 1

      This gen is done. Next gen will come out again.

      MS has the money to try again and again til it gets traction. They will have a Windows phone that succeeds, even if it's just a fork of Android.

      I mean, hell, didn't they buy Cyanogenmod?

      --
      Your ad here. Ask me how!
    7. Re:I wouldn't count on failure yet by Anonymous Coward · · Score: 0

      Fair enough. Name one company creating brand new windows software that is not a video game or some utility that there is already 50 of? All the new companies are creating web platforms or are connected to creating that environment. MS has 3 bits in that environment. ASP.NET, Windows Mobile, and Azure. MS as a desktop platform will at this point forward only aim you buy into those 3 platforms.

      MS will not go down without a fight. But from a developer perspective it is not exactly 'oooo want to learn how to do that and make a living'. It is more 'oh my company I work for is making software on that so you know its a job...'

  10. ARC Welder by JigJag · · Score: 2

    Yes with ARC welder from Google, I can run Android apps on my Linux machine and possibly others.

    --
    "The hallmark of humanity is the ability to move beyond sensory inputs" - Mary Helen Immordino-Yang
    1. Re:ARC Welder by Anonymous Coward · · Score: 0

      They are merging Android and ChromeOS anyway so ARC Welder will end up depreciated I imagine.

  11. Phonegap by Anonymous Coward · · Score: 0

    Why dont they use PhoneGap?

    Cross platform frameworks do consume more power if youre app is device hardware heavy (I have a research paper on that confirming it).

    1. Re:Phonegap by jtara · · Score: 1

      Phonegap would be great for apps written with PhoneGap! If they can get the authors to publish for Windows.

      PhoneGap apps use a combination of Javascript and native plugins.

      PhoneGap won't "convert" some arbitrary app that is written with Java and/or the NDK.

    2. Re:Phonegap by art123 · · Score: 1

      Microsoft did include decent Cordova (Phonegap) integration into Visual Studio 2015 including native Windows and Android build process with connected device deployment, and remote build on networked Mac for iOS builds and deployment.

    3. Re:Phonegap by tkrotchko · · Score: 1

      Can you post a link to your research?

      --
      You were mistaken. Which is odd, since memory shouldn't be a problem for you
  12. "just" an implementation of what Android/Google by raymorris · · Score: 3, Insightful

    The Android API is some thousands of functions. Android and Google already implemented that API on top of Linux . I don't see any fundamental reason that a company with Microsoft's resources -couldn't- implement the same API as follows:

    Android.textbox.Draw(blah, x, y) {
            Winforms.textbox.Draw(x, y, blah);
    }

    Sure there are thousands of functions, but Microsoft can put hundreds or thousands of programmers to it. It's not an easy task, but mostly it seems -big-, lots of functions, not necessarily anything all -that- complicated.

    Looking at it another way, not only did Android and Google implement the Android API, Google also re-implemented the Java API from scratch, while the Mono project and Wine have re-implemented the Microsoft APIs. Given that they've done that, I don't see how it would be impossible for Microsoft re-implement the Android API, mostly with simple stub functions which call the corresponding Windows function.

    1. Re:"just" an implementation of what Android/Google by TheRaven64 · · Score: 3, Insightful

      It's really easy to reimplement it in that way if you want to - you can reuse all of the AOSP code directly and just plug in your own back ends for OpenGL, Skia, and so on. The problem is that you'll now have an Android app running on a Windows phone, looking and behaving like an Android app. If you've ever tried to use WINE for anything other than games (which try not to use the platform-native UI, as it breaks immersion) on OS X then you'll know how badly that sucks. You won't have an app that integrates nicely with the underlying system services (even things like copy and paste won't work correctly) and you'll have UI patterns that don't quite fit and feel weird and wrong, and a load of frustrated users. Even UI ports where a human is involved are very hard. Automated ones suck - remember Java's AWT?

      --
      I am TheRaven on Soylent News
    2. Re:"just" an implementation of what Android/Google by beelsebob · · Score: 4, Informative

      The Android API is some thousands of functions. Android and Google already implemented that API on top of Linux . I don't see any fundamental reason that a company with Microsoft's resources -couldn't- implement the same API as follows:

      Android.textbox.Draw(blah, x, y) {
                      Winforms.textbox.Draw(x, y, blah);
      }

      Simple... Android.textbox.Draw, and Winforms.textbox.Draw usually don't have the exact same semantics. In fact, usually the APIs are structurally different. Often there simply isn't analagous functionality on one or other platform.

      Furthermore, even if you somehow magically managed to make all of that work out properly, you'd still be stuck with a bunch of functionality that's subtly different. The behaviour of the controls is subtly different, and that can make or break the functionality of an application.

    3. Re:"just" an implementation of what Android/Google by Bearhouse · · Score: 1

      Except they are trying to implement, emulate whatever the entire damn ecosystem, sounds like, rather than just port an app, or provide a limited technical environment in which it will run...sort of...
      Sounds like just the spot of mega-project that will fail hard.

      Given the amount of cash they're sitting on, would it not be easier to get the "thousands of programmers" the easy way?
      Just contact the dudes that wrote the top 100 (or 200, 300 whatever your budget) apps on android and iOS and given free free dev tools and support plus a slug of cash to port their apps.

      Ironically, Google "killer" app (as far as I am concerned) for mobile devices - Waze - is already available on Windows phone....

    4. Re:"just" an implementation of what Android/Google by RoverDaddy · · Score: 1

      I don't want to write a thesis on this, but it's really not that easy. APIs have all sorts of implicit rules that are not obvious at first glance (and undocumented, hence 'implicit'), so even if you write what appears to be a valid drop-in replacement for every individual API function, you may end up with a garbage result. Throw in multi-threaded programming and event-driven GUI programming, and it becomes exponentially more complicated. It's not unusual for a GUI program to rely on a specific order of events received from the OS in order to calculate things like layout, positioning, font sizes, etc., or to make desired features like animation work properly. The events might -always- occur in the expected order on one OS and give all the right answers, but come in differently on another OS or a new release of the same OS. An emulation of one OS by another has to replicate a ton of behavior that you can't predict in advance just by reading the API specifications.

      --
      RETURN without GOSUB in line 1050
    5. Re:"just" an implementation of what Android/Google by squiggleslash · · Score: 1

      The problem is that you'll now have an Android app running on a Windows phone, looking and behaving like an Android app

      True, but is this really a problem? The apps will usually run full screen, and so you're not going to have users forced to see a jumble of different UI types as you do with, say, Wine.

      Going back to my old Amiga, where apps either ran in windows on the Workbench screen, or on their own screens, there was never really a problem with "different UIs" when apps ran on their own screens - which many developers took advantage of.

      To a certain extent, I see that in regular Android apps to. Most (non-games) seem to try to make themselves look as much like GMail as possible, but every now and again you come across something that doesn't resemble any other Android app, and it really doesn't matter as long as the UI is well designed and the implementation isn't clunky. Of course, many of the custom UIs are neither well designed or clunky, but that's not relevent here ;-)

      --
      You are not alone. This is not normal. None of this is normal.
    6. Re:"just" an implementation of what Android/Google by Anonymous Coward · · Score: 0

      That would be:
      Android.textbox.Draw(blah, x, y)
      {
              PAINTSTRUCT ps;
              HDC hdc = BeginPaint(blah, &ps);
              insert code here to actually paint the window...
              EndPaint(blah, &ps);
              return 0;
      }

      (relevant MSDN docs: here)

      And you'd better only do it in response to a WM_PAINT message, or it's going to absolutely peg one of your processor cores.

      What you're describing is what Java tried to do with the AWT. It didn't work then, and it won't work now, for exactly the same reason: ain't nobody got time for that. There are just too many better things to spend time on than to wrangle a hamstrung version of your platform's UI into a shim library to fit a generic, overengineered-yet-underengineered spec that is only going to undercut your platform's competitive advantages.

    7. Re:"just" an implementation of what Android/Google by DrXym · · Score: 2

      Simple... Android.textbox.Draw, and Winforms.textbox.Draw usually don't have the exact same semantics. In fact, usually the APIs are structurally different. Often there simply isn't analagous functionality on one or other platform.

      The same could be said of lot of emulation / compatibility layers yet they still exist. Apparently the Xbox One supports certain 360 games because they recompiled and linked the executables using a compatibility library - they run natively but think they're running on the 360.

      Likewise wine / winelib allows Windows software to run on Linux or OS X (through commercial forks of Wine). And Wine didn't even have the benefit of being able to look at the Windows source. I actually looked at a Wine implementation of the comctl32 tooltip today because MSDN's documentation is so bad I couldn't figure out what I was supposed to pass in.

      A closer example might be Blackberry porting Android to run over QNX on the Playbook and BB10. Somehow Blackberry can manage it but Microsoft can't? I see no reason to believe that. More likely they know it would be commercial suicide to support Android apps and killed the project.

    8. Re:"just" an implementation of what Android/Google by Junta · · Score: 1

      Problem is there's a lot of awkwardness to reconcile. Off the top of my head:
      -Background execution managed by a notification icon
      -Things like accelerometer, magnet, gps, and other sensor data inputs
      -Low level data from the cellular radio

      Now for something like an angry birds, the bar is probably pretty low. If you want to claim support for 'everything', well that's a whole world of possible hurt.

      However supporting the common pieces that a lot stick to because they are already trying to have consistent experience between Apple and Google may not be too unreasonable, with developer cooperation...

      --
      XML is like violence. If it doesn't solve the problem, use more.
    9. Re:"just" an implementation of what Android/Google by exomondo · · Score: 1

      It's fine for AOSP where you can see what everything does and wrap that behavior, it's a lot harder when you have programs relying on proprietary libraries like Google Play Services.

    10. Re:"just" an implementation of what Android/Google by Anonymous Coward · · Score: 1

      Which is why you dealt with those problems when making the conversion wrappers that handled said calls.
      All they had to do was write something similar to WINE that took every Android call and did it natively.

      It seems they tried to over-analyse things and make it way more complicated than it need be.
      WINE is complex, but it is only complex because there are loads of different calls and specs they need to basically recreate manually.
      It is heavily TIME-based, not complexity based. That is the issue. Microsoft just don't seem to want to put the time in to it, even though it would give them access to a whole ecosystem.
      If things aren't 100% exactly the same, it isn't a massive issue, as long as it isn't app-breaking. (such as things that require pixel-perfect UIs)
      Look at web-development. Practically every major browser still has various layout and interpretation issues with CSS and JavaScript. It isn't a huge issue because there are LIBRARIES that people use to deal with those minor annoyances for them. (whether hand-written or some bog-standard pre-written thing like jQuery or angular)

      WINE team were able to do it and without even having Windows source, just a spec sheet (and sometimes NO specsheet!) and a lot of patience.
      Microsoft have BILLIONS of dollars and a lot of developers, and both the Windows AND Android source code.
      They have literally zero excuses in any world that exists across any dimensions.

    11. Re:"just" an implementation of what Android/Google by BitZtream · · Score: 1

      Android is OSS under a fairly liberal license. You don't need to emulate it completely, you just need to emulate the relatively small number of syscalls/kernel interfaces so that the existing OSS code could run on a Windows kernel and get a graphics context to draw on ... Pretty trivial with OpenGL or DirectX since Microsoft will try to shoe horn that in instead of using the more directly compatible OpenGL layer.

      That's the first month. Now you spend a couple years integrating with your own services instead of the competition only to find out it's really hard to do anything useful after that awesome first month.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    12. Re:"just" an implementation of what Android/Google by Anonymous Coward · · Score: 0

      Well actually you'd do a InvalidateRect in Android.textbox.Draw and then plug your code there into the WM_PAINT handler...except that's how to do it in Win32, and this plan was for it to run on phones, so it needs to be using the WinRT API.

    13. Re:"just" an implementation of what Android/Google by TheRaven64 · · Score: 1

      To give a simple example: If you want to share a document between two apps on Windows Phone, then one passes it directly to the other. To do the same on Android, one writes it to the (typically emulated) SD card and now that you've completely bypassed the security model, everything else can open it. It would be easy to designate a directory on Windows Phone that would act as the SD card, but only Android apps would be allowed to use it, you wouldn't have the same user model for document sharing between Android and Windows apps as you do between Windows apps. There are lots of other issues with differences in standard widget implementations and so on. Even moving between iOS and Android (whose UIs are a lot more similar to each other than either is to Windows Phone), the difference in behaviour of the back button is confusing.

      --
      I am TheRaven on Soylent News
    14. Re:"just" an implementation of what Android/Google by beelsebob · · Score: 1

      All they had to do was write something similar to WINE that took every Android call and did it natively.

      You realise that Wine is 1.4 million lines of code, and *still* doesn't accurately implement all the windows SDKs, right?

      That's not an "all" you have to do.

  13. Automated conversation has been done before by noldrin · · Score: 1

    Actually, the original poster is wrong, automated conversation from one platform to another has been done at least one time in the past, check out Project Odin which could on the fly automatically convert a Win32 binary into a native OS/2 binary.

    1. Re:Automated conversation has been done before by Anonymous Coward · · Score: 0

      Automatic conversion is perfectly easy IF and only IF you architect it well with good abstraction then you can just convert the appropriate abstraction layers.

  14. Much More Simple Idea by Anonymous Coward · · Score: 0

    How about throwing the 'windows' operating system into a trash, and creating own Android port?
    It's 100% compatible!

    It also has great market share and just works. Contrary to the windows toy.

    1. Re:Much More Simple Idea by Anonymous Coward · · Score: 0

      > How about throwing the 'windows' operating system into a trash, and creating own Android port?

      Already done, and dumped.

      https://www.microsoft.com/en/mobile/phone/nokia-x/

    2. Re:Much More Simple Idea by Anonymous Coward · · Score: 0

      How about throwing the 'windows' operating system into a trash, and creating own Android port?

      How about no? One mobile OS is connected to uber-expensive phones and another is spyware masquerading as an OS. So we do need a cheap, reliable, non-spyware mobile OS.

    3. Re:Much More Simple Idea by art123 · · Score: 1

      Maybe Microsoft should flip things and make an Android phone (with 100% Android compatibility) but possibly with Windows style tiled home screen (optional for users) but also have a Windows 10 Mobile native programming interface (to give Windows 10 developers easy access).

      The development model of Windows 10 Universal Windows Platform is pretty cool (phone to tablet to laptop to desktop to tv). The ui tools are there to make this not too difficult to take advantage of.

    4. Re:Much More Simple Idea by Yunzil · · Score: 1

      It also has great market share and just works.

      For small values of "works".

    5. Re:Much More Simple Idea by Anonymous Coward · · Score: 0

      Oh look, the idiot wants a cheap, reliable non-spyware OS from a company that makes a spyware ridden OS that connects to hundreds of telemetry servers and sends back keystrokes to those shit stains in Redmond. Idiot.

  15. copyright by anwyn · · Score: 1
    Is this not a plan to create a derived work without permission of the copyright holder? Android apps are proprietary, not free software. How did Microsoft think it would get by with this legally?

    Google would enjoy suing MS for a gazillion dollars! It could not happen to a nicer company.

    1. Re:copyright by bananaquackmoo · · Score: 1

      Microsoft isn't doing anything automatically. It's providing tools so publishers can port things quickly and easily.

  16. NDK = Native Development Kit by jtara · · Score: 1

    The good stuff uses native code. There is an NDK = "native development kit"

    I write hybrid apps, using the Rhodes cross-device platform. So, UI is a webview. The platform uses some Java on Android, but mostly C and C++, because it can use the same code used on iOS and Windows CE/Mobile.

    So, Rhodes uses Java on Android where it uses Objective-C on iOS - to interface to native APIs.

  17. Separation of Presentation Over-Hyped by Tablizer · · Score: 0

    This partly demonstrates why "separation of content from presentation" is an overrated concept that often complicates designs by making unnecessary "busy work" layers.

    How features are presented and grouped are largely interrelated to the function of the application itself. On different devices or gizmos one may design or group features entirely different. The UI is not just a "skin", it's an integral part of the overall product. It's what the users and customers see and largely what they judge you on, fair or not.

    You can bend over backward to keep them separated, but then you create a bureaucratic bloated middle-man layer that you have to support and wade through even if you never change UI methods. It's expensive meteor insurance.

    That being said, I'd like to see IDE's or similar that make it easy to change (virtual) groupings and filters of UI related code to fit the viewpoint of a given task.

    I've kicked around the idea of a "table oriented GUI" where the code is stored, or at least managed, in a database. That way you can sort and group widget code by widget type, screen, title, change-date, property values, method names, etc. etc. -- all the powerful virtual grouping and filtering that database queries offer. For big projects, multiple viewing, searching, and grouping angles becomes more useful. It's what databases are for.

    The traditional approach hard-wires one grouping aspect into linear code, making tasks not aligned to that grouping aspect more difficult.

    Note the UI-related code doesn't necessarily have to "run" in the table, for compiled languages could have the IDE generate file-based code from the tables. The database would be a code management tool.

    Some IDE's kind of do this, but they are essentially reinventing databases. Why reinvent something that already exists?

    (One difficult part of this is that "dynamic relational" doesn't exist yet, and each widget kind has different attributes. Making a custom table for each widget gets unruly. Dynamic relational would allow columns to be dynamic. Name/value attribute-tables have to be used instead for traditional RDBMS.)

  18. How is this a different from Rosetta (Apple)? by NMBob · · Score: 1

    Or something like VMWare? Or did they really want the apps to look like native apps? That I'd get. I wish I could run many of my iPad apps on my MacBook...there already is a simulator, so it must be close.

    1. Re:How is this a different from Rosetta (Apple)? by SpectreBlofeld · · Score: 1

      It's not a virtual machine, it's a tool that would hypothetically allow developers to compile their native Android code to a Windows app and keep all functionality intact. Basically a super easy way to port their apps to Windows phone.

    2. Re:How is this a different from Rosetta (Apple)? by gstoddart · · Score: 2

      The reality is, they were trying to do FAR more than port apps:

      Microsoft complicated the project by orders of magnitude when it linked the porting of Android apps to Windows 10 with replacing Google's cloud services. Microsoft wrote an app interoperability library that traps and converts Google cloud APIs for things like payments and advertising to Microsoft's APIs. Microsoft's anemic smartphone market share, 2.6% according to IDC, gave the company no choice but to do all the heavy lifting to acquire Android apps, because a developer-intensive port from Android to Windows wouldn't be justified by its tiny market share.

      They have no interest in making these things simply run, they want to replace the underlying APIs with Microsoft stuff so they can horn in on the revenue.

      They wanted more than just native apps. They wanted to alter how those things worked so they'd get the money.

      --
      Lost at C:>. Found at C.
    3. Re:How is this a different from Rosetta (Apple)? by NMBob · · Score: 1

      Got it, thanks. It's like Slime vs Slime. :) I'm not sure who to root for.

  19. This reminds me by tkrotchko · · Score: 2

    This reminds me of when IBM had the mistaken notion that if they added Windows 3.x compatibility to OS/2 they'd be the platform of choice.

    You'd think Microsoft of all companies would remember that logical fallacy of that plan.

    --
    You were mistaken. Which is odd, since memory shouldn't be a problem for you
    1. Re:This reminds me by PRMan · · Score: 1

      They were all babies then. They don't know anything about that.

      --
      Peter predicted that you would "deliberately forget" creation 2000 years ago...
  20. Focus on Universal apps by unixisc · · Score: 1

    Very simply, Microsoft has to work on the Universal apps - making as many apps available on Windows 10 Mobile as there are in the mainstream Windows 10 platform.

    Also, Microsoft should identify and work on helping vendors port some major apps in the market - like Uber, Lyft, Vonage, et al to their platform. Do a drive so that most apps that are already there for both iOS and Android are also ported to Windows 10 Mobile. It doesn't have to be most, or even a majority of apps, just the ones that are already indispensable.

  21. Happens time and time again... by Anonymous Coward · · Score: 0

    This business happens time and time again. People forget all the past failures, like say the OSI Scientific 3-CPU machines, The Zenith Z-100 dual-CPU system, Apple's various stillborn OS's of the 1990's, and Taligent, and mine, all mine, a CP/M emulator for the Convergent Techologies systems. Remember all of those? All fell flat. Everybody thinks it's a great idea but when they run it they soon notice all the loose ends and rough edges and the slowness and they pretty soon go back to native.

  22. The one supporting the competitor system... by DrTJ · · Score: 1

    ...is the one loosing.

    1. Re:The one supporting the competitor system... by cbhacking · · Score: 1

      Loosing... an arrow? Loosing the dogs of war? "Loosing" as in releasing, a reference to the way Windows 10 Mobile is being released imminently?

      --
      There's no place I could be, since I've found Serenity...
  23. Clarifications (Re:Separation of Presentation Over by Tablizer · · Score: 1

    Clarifications and further details:

    Re: "to support and wade through even if you never change UI methods"

    Change: "to support and wade through even if you never change UI frameworks or platforms"

    Re: "For big projects, multiple viewing, searching, and grouping angles becomes more useful."

    Change: "For big projects, multiple viewing, searching, and grouping angles becomes more valuable to help deal with the volume of (UI) code."

    Re: "UI-related code doesn't necessarily have to "run" in the table, for compiled languages could have the IDE generate file-based code..."

    Note that interpreted languages could optionally do an "eval()" function on code in tables. Or they can use the same technique mentioned for compiled languages, but it's an extra code preparation step. Or just store attributes in tables, not methods. But one may be able convert common method behavior into "action" attributes, such as opening a given screen in an "on-click" event.

    A lot of GUI activity has reoccurring patterns that can be parameter-ized rather than rely on lots of explicit app code. That way more of the GUI activity is attributes instead of direct code, reducing the tricky issue of how to execute UI-related app code. I'd say at least 3/4 of GUI activity can be readily parameterized in such a way. It's just not the habit of GUI engine/API designers to think that way because they are writing for coders, not attribute "programmers".

    (And added advantage of such a system is that it's less language-dependent. You do most GUI "coding" by setting attributes and action-lists having parameters, not using a specific app language.)

    Regarding dynamic relational, generally each widget will have a fixed or common set of attributes, such as an ID, container ID/ref, title, default value, sequence or coordinates, widget type, etc., but also have a widget-type-specific set of attributes. Traditional RDMBS don't deal with these widget-specific attributes very well, and this may be why the idea hasn't really been tried. (Visual FoxPro did it to some extent, but mostly didn't expose it to the coder. OODBMS may use sub-classing for widget-specific stuff, but that creates other problems, especially if the differences are not clean "type" hierarchies.)

  24. Two words by Anonymous Coward · · Score: 0

    Virtual Box.

    or one, $50.00 word:

    Parallels.

    or I will put it another way...
    Not news.

  25. Wait, what? by Anonymous Coward · · Score: 0

    The 10 people who bought windows phones because of this are going to want their money back.

    1. Re: Wait, what? by Anonymous Coward · · Score: 0

      I got one for $30. It's not bad, but it's not great either.

  26. Blackberry did it by edtice1559 · · Score: 2, Insightful

    BB10 QNX phones run Android apps just about as well as they run natively from what I can tell.

    1. Re:Blackberry did it by Anonymous Coward · · Score: 0

      Which is to say, pretty crap.

    2. Re:Blackberry did it by Anonymous Coward · · Score: 0

      Ya, but if Microsoft is trying to replace Google maps with their own, yhey'll be violating the terms of use. They probably forgot to read about what they could do then realized they went to far.

    3. Re:Blackberry did it by Anonymous Coward · · Score: 0

      Yeah. But then you'd be using a BB.

      And nobody in 2015 wants that.

    4. Re:Blackberry did it by sysrammer · · Score: 1

      Yeah. Good phone. Poor marketing. Few will listen. One must have the Correct Brand(tm) else one will not be deemed a valid hipster.

      --
      His ignorance covered the whole earth like a blanket, and there was hardly a hole in it anywhere. - Mark Twain
    5. Re:Blackberry did it by Anonymous Coward · · Score: 0

      Reminds me when those idiots tried to reverse engineer the YouTube API's and create a YouTube app. They thought they could just use Google's AP without being smacked down.

    6. Re:Blackberry did it by edtice1559 · · Score: 1

      Forget being deemed a hipster, companies like Mobile Iron have sold their crap to large organizations. And now if you don't have iOS or Android, the mail server won't let you sync!

  27. Also Ran by Anonymous Coward · · Score: 0

    -- Never Mistake a Clear Vision, for a Short Path --

  28. Bluestacks? by Anonymous Coward · · Score: 0

    Not sure why MS couldn't just purchase Bluestacks or similar and expand it with hiding the UI to give it the "integrated" look similar to Parallels for OSX. While a VM is not the same as native, most modern W10 hardware can handle the overhead.

  29. Truth is opposite by Anonymous Coward · · Score: 0

    Microsoft had a private beta with the bridge and the problem was it worked flawlessly. The bridge allowed anyone to run any Android app on WM. The problem was that it would have resulted in the destruction of universal apps. Why write to Windows if Android apps can run natively?

  30. Good point by kervin · · Score: 1

    Why not port the Java Virtual Machine, then using the MS widget set/chrome? E.g. RoboVM uses this to run Android Apps on IOS.

  31. You don't kid around, do you? by Anonymous Coward · · Score: 0

    I could not even get MS's Android emulator to run! They overengineered it to the max. Installing it cripples your PC by taking over your ethernet card, without warning. After trashing my development machine with this junkware, I uninstalled their crap and went back to Google's slow-mulator, which at least doesn't trash your computer. I'm not surprised anything MS does with Android has fail written all over it.

  32. Bullshit by kbg · · Score: 1

    There is no such thing as too complex especially when you have the resources of Microsoft. All you have to do is to emulate the Android API at a high level. The only problems are those application that have native Linux binary code.

  33. BlackBerry BB10 devices run Android by Anonymous Coward · · Score: 0

    They could even run Google Play and Google Services internally. The issue is Google wouldn't certify their Android Player to run those programs officially.

    Anti-competitive behavior, imho.

    1. Re:BlackBerry BB10 devices run Android by Anonymous Coward · · Score: 0

      No, the issue was Google would never licence a non Android OEM to use Google Play Services and Apps. Those hacks you saw on BB were just that - hacks that broke constantly.

  34. I'd heard it wasn't just complexity by rsilvergun · · Score: 1

    Their existing developers were none too happy about all the time they spent on native apps being made worthless under a deluge of quick and dirty ports.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  35. Port the Dalvik VM to windows by Anonymous Coward · · Score: 0

    Port the Dalvik VM to windows would be a good start, which would run 90% of the apps - then get sued by Goo$le and Ora$le.

    Seriously if WINE can be written and maintained, then with MS's resource they cannot achieve something similar they are just approaching the problem wrong. All they need to do is rethink their approach.

  36. Never been accomplished? by Tony+Isaac · · Score: 1

    Automated conversion of a UI from one platform to another has never been successfully demonstrated.

    Isn't this the definition of an emulator?

    1. Re:Never been accomplished? by cbhacking · · Score: 1

      Emulators are run-time, this is compile-time. The closest thing I'm aware of it WineLib, which lets people compile Win32 code for Linux or OS X, and takes care of stuff like translating DirectX calls to OpenGL ones. It's reasonably "successful" in terms of usage, but far from complete or bug-free. A lot of apps just won't work through it, and many others will exhibit new and exciting bugs.

      --
      There's no place I could be, since I've found Serenity...
    2. Re:Never been accomplished? by Tony+Isaac · · Score: 1

      These days, all libraries are bound at run-time. That's true for .NET, Android SDK, even Win32. You can write your own version of Shell32.dll, drop it in place, and as long as you implemented all of the entry points, your application would never know what happens on the back end.

      Maybe an emulator is "thicker" than a bridge, a little less seamlessly part of the host OS, but it certainly does convert (or implement) the entire UI of the client to the host platform. The emulator has to implement every single API entry point that the client application expects.

  37. WP8.1 has Uber by cbhacking · · Score: 1

    Not to contradict your point in any way, but Uber has been available on Windows Phone for months, possibly years. Lyft is not, though. It's a WP8 app, but will run fine on W10M.

    --
    There's no place I could be, since I've found Serenity...
    1. Re:WP8.1 has Uber by unixisc · · Score: 1

      I actually meant Uber Partner, not Uber. The app for drivers

  38. Delay of spyware by Anonymous Coward · · Score: 0

    Microsoft. The spyware.

    http://arstechnica.com/information-technology/2015/08/microsoft-has-no-plans-to-tell-us-whats-in-windows-patches/
    http://arstechnica.com/information-technology/2015/09/leaks-show-that-microsoft-writes-release-notes-so-why-cant-it-publish-them/

    https://www.gnu.org/proprietary/malware-microsoft.html
    http://www.computerworlduk.com/blogs/open-enterprise/how-can-any-company-ever-trust-microsoft-again-3569376/
    http://www.networkworld.com/article/2956574/microsoft-subnet/windows-10-privacy-spyware-settings-user-agreement.html

    http://www.technobuffalo.com/2013/08/22/nsa-windows-8-exploit/
    http://www.technobuffalo.com/2013/07/11/microsoft-gave-the-nsa-direct-backdoor-access-to-outlook-skype/
    http://winsupersite.com/windows-10/how-stop-windows-10-upgrade-downloading-your-system
    http://www.extremetech.com/computing/195592-with-windows-10-microsoft-could-move-to-a-subscription-based-model
    http://www.extremetech.com/computing/205320-microsoft-windows-10-will-be-the-last-version-of-windows
    https://www.youtube.com/watch?v=5GU5uv28a3I
    http://techrights.org/2015/07/31/vista-10-anticompetitive/
    https://www.youtube.com/watch?v=wwRYyWn7BEo
    https://www.youtube.com/watch?v=Gghj03J_ri0
    http://localghost.org/posts/a-traffic-analysis-of-windows-10
    http://www.ghacks.net/2015/08/28/microsoft-intensifies-data-collection-on-windows-7-and-8-systems/

    THESE
    https://gitlab.com/windowslies/blockwindows
    ^(have to uncomment the #'s on two url's in the hosts file per latest change)
    https://senk9.wordpress.com/checklists/windows-10-privacy-checklist/
    ^Applies to 7/8/8.1 too.

  39. Oh the lulz, it's too much by Anonymous Coward · · Score: 0

    MS tried to make it so difficult for Windows apps and services to work on other platforms, now the tables are turned and they're sad... Oh boo hoo MS

  40. Jolla and Sailfish too by Anonymous Coward · · Score: 0

    I just got my new Jolla phone, and it runs Android apps through a layer on the Sailfish O/S just fine, thanks !!!