Slashdot Mirror


Microsoft Rumored To Integrate Android Apps

phmadore writes "Windows Phone has been struggling for market share, largely due to a serious lack of developers willing to invest their time in what one might consider a niche market. Statistically speaking, Android has more than 1.1M apps to Windows Phone's 200,000+. Well, according to unnamed sources informing the Verge, Microsoft may soon integrate/allow Android applications into both Windows and Windows Phone." This follows the recent debate over whether Microsoft should try to fork Android. Peter Bright made the point that doing so would be extremely difficult, and probably not worth Microsoft's time. Ben Thompson has an insightful post about how Microsoft's real decision is whether to focus on devices or services.

2 of 189 comments (clear)

  1. Slippery slope by mlg98 · · Score: 5, Interesting

    As a Windows Phone user I think this is a terrible idea. Didn't BlackBerry already try this? Did it help them? I don't think so. It is a slippery slope that only leads to irrelevance.

    The beauty of Windows Phone is that it is not like Android and iOS. Well written WP apps, which follow the Metro (I know they don't call it that anymore) design philosophy integrate beautifully into the environment. Slapping Android apps, which follow very different conventions would diminish the user experience.

    --
    Code to live, live to code.
  2. Re:right, by fuzzyfuzzyfungus · · Score: 5, Insightful

    The trick with 'Android compatibility' is that it's really two different problems. One is merely engineering ('merely' in the 'may actually be quite difficult; but there are engineers that are quite smart, trying giving them money' sense) and one is strategic:

    'Android' as in the ASOP is a mixture of GPL and Apache. Exactly how many man-hours it takes to get ASOP running on your platform, or Dalvik and friends running on your non-Linux kernel is an open question, and may end up being quite a few if you want it to work well; but there is nobody to stop you, and you just need suitably skilled software people.

    Trouble is, much of the good stuff in 'Android' (and stuff that Google doesn't exactly discourage developers from using) isn't ASOP, it's Google Play Services, a set of proprietary applications, libraries, and Google-backed web servcies that can be bestowed or denied to your device at the power and mere pleasure of Team Mountain View. They tend to ignore indie ROM-cookers and two-bit pacific RIM clonemongers who quietly pirate GPS; but if a company large enough to target, or ambitious enough to try to cut deals with major carriers in markets Google cares about, tries to distribute GPS without Google's blessing, it's world-of-hurt time.

    At a greater or lesser cost in software engineers, you could get an ASOP-compatible Android compatibility layer running on QNX, NT, OSX, whatever. However, how much that helps you is increasingly limited.