4 ms·
> But it's also not Google's fault if there's no option. I'm still shocked Microsoft couldn't get its act together and stick it out with their mobile platform.
by at-fates-hands 7y ago
> But it's also not Google's fault if there's no option.
I'm still shocked Microsoft couldn't get its act together and stick it out with their mobile platform. One of the main things which absolutely killed their platform was how they handled their app store. Had they managed it better by making it easier to build apps for their platform like Android has, they would've been able to stick around longer.
Shame really and makes other players hesitant to come into an industry when you have a behemoth like Microsoft fail so badly.
December 10th of this year was their sunset date for support.
- HeWhoLurksLate 7y agoIt's been a long time since I did development for Android, and a ling time since I made an app for Windows Mobile, so this is a bit outdated- In my experience, it was actually easier to develop for Windows Mobile than it was for Android, because on Android you had to update constantly just to retain the features that you had. Windows Mobile, especially for someone who's worked with UWP previously, was much easier to work with. I too wish that Microsoft hadn't sunset it so quickly.
- NicoJuicy 7y agoOmg, I so agree on this. I just did a project in flutter to test out out. And some build vs compile bug for androidX kept popping up. Urgh. Untill I removed a package that was added together with 4 others... It did got a lot faster to emulate and hot loading is awesome as well. But MS development ( c#) is a massive pro versus Java/kotlin.
- ggthrowaway12 7y agoIt's unclear any decision they made mattered at all. Building a Windows mobile app made no real sense and even the largest app developers had trouble justifying the investment. Also, I don't think Microsoft stood to gain all that much even if they were able to gain a foothold in the market.