As discussed in this post, it should be easy to do. Would this provide a path for Microsoft in the mobile space? Or is there some reason it would be a mistake?
I think under this circumstance a windows phone would still be a device that runs windows, but can also run android apps.
A windows app for such a device would still be preferred, and can deliver continuum.
I must confess I use surface tablet/pc, but not a windows phone. I love having a pen and that has stopped my using a windows mobile so far.
To your points:
As you say, this is not a solutions for every app.
1. Yes there is already google play services, but this is not ready to run out of the box, and I would expect more limited than running on the Linux on android. The more popular the app, the more important that windows has its own app anyway, that can also run on a surface pro etc. This would be more about total number of apps than using the android app for a really core app.
2. Changing direction is painful, but sometimes the old directions are just not sound. Xamarin plays a role in enabling windows as the development platform for everybody. But not one is going to bother with windows apps for the mobile marketplace on current trends and something has to be done.
3. Because it can run continuum, and do many things the android phone cannot. If you want an android phone..then a windows phone will not be an answer. But if you want a windows phone with all your core functions delivered by windows that can also basically run any android app so you will not be left out, then it would be appealing.
4. As you point out this is a real risk. That if you are only a poor clone of an another system it is not enough. But Blackberry did not also have millions of another device type the way windows does. Continuum show real promise...same apps as on your windows tablet on your phone, but there still needs to be a supply of the other less core apps.
Blackberry largely lost that core reason to use the device in the first place. For Microsoft, that reason is there with Microsoft apps being able to run windows 10 everywhere.
All you points are a big part of the debate. But I do feel the answers to these points are there, but there is a lot to consider to get it right.
]We may have each been still missing each others points.
To give perspective, and I am involved in software development. We have teams who develop systems, with server code, browser code and also components that are apps.
Windows recently announced and pre-released Ubuntu on Android. The team I am working with has 9 developers. It was 5 on Apple, 4 on Windows. The announcement of Ubuntu on Android has provided utility that has switched 3 (1/3 of the team) from Apple to Windows so this team is now 7 on Windows, 2 on Apple. Key software utilities like the real rsync etc available on windows.
But the people switched from Apple to Windows not just to run those Ubuntu utilities. The switched for all the touch and pen facilities and the apps on windows. But still having access to those Ubuntu utilities the team members use on servers meant the team members could now switch. Take 'rsync' there have been windows versions before, but as free software maintenance is a hassle and it dies.
Ok, is a small case, but if you want windows to expand in other areas it is the type of success to see repeated over and over.
To go over the points where I think I am missing what you are saying and you are missing what I was trying to say:
1. By 'core apps', i mean the main apps that a person uses all the time. I was never suggesting Android as a way to run these apps. To me, if I am to decide to have a windows phone, then it has to tick all the boxes as an ecosystem that can provide your core apps. I believe windows DOES have all those core apps.
The worry for me is non-core apps. Like my childs sport association launches an app showing when the matches are on, and it is only on android and apps. This s a real example. If only they would use Xamarin maybe they could easily produce a windows app.
Now it could be that some people feel that people who may have 'app anxiety' about possibly needing an app not available on windows mobile should just go buy android or apple and go away, but i think providing a solution for these people will help windows mobile succeed.
All of what I meant by 'core apps' are available on windows. To have the experience of these core apps on windows is why you choose windows. Resorting to an Andoid app is what you do when you need that app at a specific time and the alternative to running such an app from time to time under android on windows is either have two phones or abandon windows.
2. Again, the idea is not that people would buy into the windows in order to run android apps. The idea is to have people who want to run windows apps, get access to other things they may need from time to time.
3. Agree continuum is cool but no winner yet. But I believe we have only seen the start and it could become a winner. Again the idea is not to have programmers writing android apps for use on windows, which would be crazy. The idea is to have the biggest possible market for windows app through having as many as possible users on windows, and if that means addressing 'app anxiety' through android, then it is worth it.
Yes there is a risk that a particular developer will decide. "Hey, I windows mobile users can get my app anyway through android, so i will not bother writing a windows version". But there currently a risk that consumers decide "I will not choose windows phone as the ecosystem is too small, and that leads to developers to deciding, " why write a version for windows mobile, there are not enough people using it".
4. I can certainly suggest that the Microsoft decision to partner with unbuntu to produce Ubuntu on windows is looking like a great decision rather than a liability. I think the same could be done with the most popular 'mobile linux', which is android.
I want windows mobile to succeed. I want the market for windows mobile apps to be great. But i think pathways to address 'app anxiety', given the current state of the windows mobile marketplace, are required.
Be able to run Android apps is not a reason to buy a Windows phone. But if you already have a reason to buy a windows phone, then being able to also run android apps could make that windows phone you already want a practical and more workable choice.
Android may have bought time for the Blackberry 10 and allowed more people to buy a Blackberry 10, but it is not the reason to choose a blackberry 10. Did Blackberry continue to provide the reason to buy one? In the end the Blackberry had an insufficient ecosystem for their own apps. Microsoft has the whole windows ecosystem that funds their app development capability, and the continuum type promise of a consistent environment i feel is compelling.
I want a Surface phone. A windows phone with a pen, that extends the same ecosystem I use on my surface tablet/desktop. But I do need a device that can also occasionally run some of those many apps out there that are currently only available on android and apple.
p.s. Not sure of your point on play services, . as in this online video to get it working on windows 10 mobile. But from my perspective, this is the run the exact type of app needs to be native in windows or use the windows equivalent. Anyway, appreciate the discussion.
All I wanted to say if app developers refuse to produce their apps on a windows platform, will Microsoft hurry up and produce similar apps for the windows platform and give them away just to stick it to them.