Although we've been impressed so far with Microsoft's execution of Windows Phone 7, not all are happy and we're starting to see why.
While some 3,000+ developer devices are out in the wild, that is a drop in the bucket of those who want/need a device to actually test their applications on in time for an October release. Of course, we get it: logistically its hard to make thousands of pre-production devices and make them available to developers and ship them out--it's no trivial problem for Microsoft. Nor is deciding who gets priority for the phones.
Still, at least one enthusiast Silverlight programmer has taken to his Twitter stream to vent some and we kind of see his point too. After all, we have maybe 10 weeks till release (!) and developers are still missing programming tools and hardware to work on. Justin Angel believes this is a recipe for disaster, where there will be a clash between what developers have worked on via an incomplete emulator versus how it actually performs.
Other have noted that this is just run-of-the-mill for any new software platform, as we've seen these type of issues on WebOS, Android and even the iPhone when they were being rolled out. On the other hand, Microsoft may have to do better to get this right, despite keeping on track for a holiday release.
We're not developers, but we do see both sides here. Hopefully Justin and others will be able to get a device soon, Microsoft can deliver some of those features for the emulator and we'll have some solid software come October. We should finally note that "big" developers (Netflix, Foursquare, New York Times, Seesmic, etc.) have long had all the tools and hardware, so this seems more about independent developers at this point.
Comments
Dear Microsoft,
Please remember, you have one shot at reviving the platform. You miss this boat and it's game over, no matter what clever new UI you concoct in the future. Remember Google is ahead and Android 3 is coming AFTER WP7.
A concerned user.
As a .NET developer, we have it easy, maybe too easy. Microsoft has provided such a rich framework *some* programmers get lazy and expect to be handed every component they might need to build any app. I have been learning Silverlight and developing a WP7 GPS tracking app over the last 6 weeks by mocking the GeoLocator in code. I'm confident I'll be able to sell a quality app in the marketplace when the phone hits retail outlets and make money.
I agree that this development platform isn't perfect yet but its a heck of a lot better and more consistent than WM6, in my opinion. And from what I've heard, easier to use than the IPhone or Andriod platforms.
I'm really excited about the WP7 platform and how it will be improved in the coming months. I already have two more apps in the design phase.
@Robb Schiefer
Thanks for the alternate perspective on the matter. Shoot us an email when your app is finished and best of luck.
Let them get lazy if they want... They will be in for a rude awakening. MS has indicated that the app approval process is going to be a lot more strict, apple strict is the impression I'm getting and more so in some ways. Thousand fart apps, nope, not here! So they can bitch and moan and then submit crappy apps only to get a big fat rejection. This aint windows mobile.
"developers, Developers, DEVELOPERS!!"
MSFT is not going to be accorded the same time period as apple or google to ramp up quality WP7 apps.
So, the team in charge of providing appdev tools needs to step up their game. WP7 success will be defined by:
- Slick, tightly engineered, highly capable and efficient hardware;
- Excellent, consistent user interface, without glitches, freezes or hiccups;
- High-quality, useful, bug free applications; and
- Visible, relevant-to-consumers-needs-and-aspirations advertising and market education.
Crappy, inconsistent, buggy applications will not help.
I have a friend who's working directly with Microsoft on his app. They all have builds well in advance of the public beta - it includes things like panorama, pivot, etc. He has a phone, as do the others he's talking to. It's too bad that Twitter allows for the frustrated venting of one guy on the outside to be taken as a news story.
There will be a lot of apps at launch that Microsoft has been pretty involved in shepherding through the process...
Exactly, they're not called "BETA" dev tools for no reason. MS has said more stuff is coming soon, srsly, I find it lame/idiotic that people have no ability to wait for something and just want everything here and now.
Software dev/building doesn't work that way, and new platforms don't spring up full complete from day one. A little common sense and logic seems to be missing from lots of people in todays world.
I personally have no doubt that Microsoft wants great apps when WP7 launches. They have significant investment to make sure all is successful. I can imagine they do not want another Windows Vista fiasco on their hands.
What Vista fiasco? They sold 200 million copies of it and posted their best quarter *ever* doing so. In fact Apple, Linux and the rest of the industry never ever came anywhere close to that "fiasco"...
The fiasco was not in the sales numbers but the damage on Microsofts reputation.
Such is the nature of working with a work in progress. A work in progress is not complete, thus one may find features that are not yet complete. If some one doesn't want to deal with the challenges of an incomplete SDK he or she should wait for the final SDK. However some of us believe there is a competitive advantage to working with what is available now.
But lack of completion aside given any mobile platform (or desktop platform) I can identify features or functionality that the platform doesn't support or functionality that cannot be easily emulated. But focusing on what one cannot yet do doesn't tend to move one closer to accomplishing something. Instead focusing on what one can do with what's available may better contribute to accomplishing something.
I've got a developer device beside me now. Before I had the developer device I acquired a computer with a multitouch screen so the emulator would have access to multitouch. Others used a solution that allowed one to use multiple mice connected to a computer to emulate multitouch. The emulator doesn't support the accelerometer, but as a work around one person used a wii controller. His solution had some lag, but it's a step up from where one would be if he or she concentrated on the lack of built in support.
I could name other examples of developers working around the lack of support for some functionality, but I think I've said enough to illustrate my main points. A developer can choose to wait for the complete SDK or be creative with what's available. It's a personal decision and either pathway has its merits, but embracing what's available now will result in more accomplishments.