3 Windows Phone Lessons Learned

As part of the process of publishing our first Windows Phone app in the Windows Store, we spent some time reviewing the guidelines and reading fellow developer blogs trying to get a better understanding of what sort of hangups exist for people publishing to the Windows Store.  Anyone who is familiar with the publishing process for iOS and Android understand that Apple’s testing and publishing is far more difficult than Androids.  Microsoft’s publishing process is very similar to Apple’s process in that an end user tests all aspects of your application to make sure it meets all store guidelines.  Here are three recommendations for anyone looking to publish to the Windows Store.

1. Be very careful when selecting which countries you are publishing to.  Our initial submission failed because our content was deemed inappropriate for certain countries.

2.  The back button after exiting the app should be handled and in my case caused problems with overall application architecture.  The following stack overflow article describes the issue we ran into and how it was resolved.


3.  Windows Phone is a great platform and porting iOS and Android apps over can be done fast if done correctly.  Our apps have relied on service oriented architectures (SOA) with MVC.  The SOA portion of the app did not change at all in the move to Windows Phone and the MVC portion we could reuse the overall architecture.  The end result was a development cycle of about 30% the original development effort.