I threw it on a Windows 8 box (as you can only develop for Windows 8 on Windows 8) and hit F5 to run it. I ended up with a pretty darn good app. I was just about to call it good enough and publish it when I realized that none of the source code on my blog was showing up.
In order to fix that I pulled in a handy library called gist-embedded. This library made us of jQuery which is where I ran into my first problem. I guess that before jQuery 2.0 there were someÂ compatibilityÂ issues between jQuery and the Windows 8 runtime. These have been resolved in jQuery 2.0. However, my application failed validation due to the jQuery file which nuget added. I was confused because I failed in two sections. The first was that the code didnâ€™t run and the second was that the encoding was wrong. The encoding was easy enough to fix. You just resave the jquery file with UTF-8 encoding.But I was totally flumoxed by theÂ compilationÂ errors. I could not manage to duplicate them in the app or in IE10. Eventually I ran the validation again and found everything now worked. I guess the incorrect encoding was causing more than one issue.
Now that I had the application working the way I wanted and passing the validation I signed up for the windows store. I had to give Microsoft $49 of my hard earned dollars for the privilege of giving away a freeÂ application. It is so funny that companies likeÂ MicrosoftÂ and Apple have tricked us into paying for the right to release software on their platform. If he wasnâ€™t a mildly insane toe nail eater I would beÂ interestedÂ to hear what RMS would say about it.
Weirdly Microsoft validate your credit card by charging a small amount then refund it and use it as a method of validating your account. They require that you enter the amount charged to validate your account. This means that if, like me, your bank sucks at posting charges with any rapidity youâ€™ll be stuck waiting.
When setting up the application you have to enter a stunning amount of meta-data about where you want your app advertised, which age groups, what category, whether it contains cryptographyâ€¦ it wasÂ overwhelming and at least half the stuff could have been replaced by setting some reasonable defaults.
At last I got to the point where I could submit my app for publishing.Â Yay! Now I can sit here and wait. And wait.The phase which was suppose to take an hour took a day. Iâ€™m now into hour 20 of the 3 hour security testing. Iâ€™m obviously more excited about getting this app out than I should be. No amount of refreshing seems to speed the process along. It is superÂ unfortunateÂ that this process is so time consuming.
I canâ€™t comment on the rest of the process because Iâ€™m still waiting.
Overall I think that building and distributingÂ Windows 8 apps is more painful than it needs to be. I suppose you do get access to a global distribution channel and a place in the Windows store for your $49 but if uptake on Metro apps has been as bad as reportedÂ then cleaning up app submission should be high on a priority list at Microsoft.
The submission process needs to get faster. I know that the process is far better than Appleâ€™s but it still sucks. Iâ€™m use to hitting publish in my CI system and 5 minutes later everything is up and running on my site. I donâ€™t expect updates to be pushed out to clients with that rapidity but I do expect the app to at least be published in less than a day. App stores are the antithesisÂ of the continuous deployment model.Â
Is it worth making Windows 8 specific apps? Thatâ€™s a firm maybe. I donâ€™t think it should be the default for any company but if there is a customer base asking for it then you might as well. It is no more difficult than building a normal application.