|
|
|
|
|
by morganvachon
4381 days ago
|
|
For me, it's because Windows Phone is more task-oriented than app-oriented. There's a "flow" to the interface that just jives with my way of working on mobile. To be sure, Android is more powerful in many ways, but with my Windows phone I can do all the same things I did on Android: SSH into my servers, VNC to support clients, etc. I'm missing a few games and novelty apps, but I don't use my phone as a gaming platform or toy, I use it to get work done. And even on a fairly modern Android phone running JB, I've more than once had the same old issue I've always had on Android: If a call comes in when it's low on free RAM, there is simply no way to answer as the screen doesn't respond to taps. This has been the case on every Android phone I've used since 1.5 on a Motorola Cliq. Android is great when you need a mobile computer, but not so much when you need a mission critical device. |
|