The worst part for me is when I start every freelancing project by making a list with the features I can’t include in the Windows Phone app, and it’s making me unhappy. If you’re a Windows Phone freelancer, how many times did you have to say this?

“I’m sorry, this feature cannot be implemented on Windows Phone”.

I really hate saying that I can’t do something. I AM A DEVELOPER, I got into programming because I love making computers do what I want, and now I can’t do it because you don’t support it? WHY? If you’re so willing to copy things from Android, why don’t you give us more APIs and access to the OS? Android does this and look at their market share. Do you think they care about the malware they have? Do you think they care about the crappy apps that slowdown the OS? No, and you know why? Because they’re the 1^st mobile OS in the world, that’s why.

Solution

People complained about Windows being unsecure for decades, but it’s still the number 1 OS for desktops. Now I’m not saying that Microsoft should make Windows Phone unsecure, far from that, but if you have a good certification process, this won’t be an issue. I don’t care that it will take 1-2 weeks for my app to get into the Store as long as it can do anything I want, and I think I’m not the only one who thinks like this. If people will sideload malware on their phone, it’s their fault, as long as you keep the Store clean I don’t have a problem with it. Trust me, instead of allowing fake apps and duplicates just to increase the number of apps, give us more access and you will gain more developers which will develop more apps, with higher quality.

Lack of Official SDKs

This was an issue all the way since Windows Phone 7, but don’t get me wrong, I don’t just complain about this, I actually wrote small libraries and made them available through Nuget, so I’m trying to help as much as I can to fix this problem, but the problem is not with the 3^rd party libraries. I know that every company who creates an app first starts with iOS and Android, but this is also the case with SDKs. Look at Facebook, Google, Twitter, and many others who have SDKs available for iOS and Android, but nothing official for Windows Phone. 3^rd party libraries are good for authentication and basic stuff like sharing content, but if you need more advanced features, then you need a native app and a SDK. Microsoft is improving the Facebook app but you still can’t do many things with it, and although Twitter and LinkedIn have native apps, they don’t offer any APIs, not even for authentication.

Last year, I was working on an app which shared content through LinkedIn, Facebook, Twitter and Google+. I managed to get the sharing to work on the first 3, but there is no Windows Phone library available for Google+(or at least there weren’t any last year), so I had to tell the client that we have to remove that functionality from Windows Phone. Fortunately, this wasn’t very important for the client, but I still don’t like that I had to do it.

Solution

Maybe get Microsoft to build them? I don’t really know a perfect solution, but if Windows Phone had a bigger market share, I’m sure they would build them themselves, unfortunately this is not the case right now.

Microsoft needs to understand that companies will not create apps for Windows Phone if they can’t have the same functionality like the other operating systems, so they should work hard on improving this part. Don’t just give us a limited SDK of a closed system, make it accessible and let us create great apps for it.

Let me know in the comments section if you have something to add or you disagree. Soon, I will publish a post about the good parts when developing for this platform.

The post Why it’s sad to be a Windows Phone developer appeared first on Bogdan Bujdea.