Throwdown With Windows Phone 7 App Submission
UPDATE: After flying off the handle in this post, I wrote another post that will hopefully help. It boils down the submission guidelines and categorizes them into a handy checklist.
I really hate complaining about things. If you read through my posts, you’ll see I write almost entirely constructive information and tutorials. My goal with this blog is to build up, not to tear down. But I’ve had it with the Windows Phone 7 app submission process. It is severely broken. And Windows Phone 7 will be a failure as long as it is broken.
If I may submit into evidence the following non-fictional story:
A short time ago, I made an app submission for an app that uses GPS. I got a rejection notice under section 2.10.7 of the Windows Phone 7 Application Certification Requirements, which reads:
But then I looked on the Marketplace and Microsoft doesn’t publish our Legal URL in the app page. “OK,” I said to myself, “it seems kind of stupid to ask for it if you’re not going to pass the information along, but whatever. Maybe what they mean is that the user should be able to find that information through the actual application itself.”
So I added that information to the application. 2 hours of work. Resubmit. 2 days of waiting. Rejected. This time, the rejection was because of section 5.6, which reads:
An application must include the application name, version information, and technical support contact information that are easily discoverable.
Um… OK. The version that is in the Marketplace doesn’t have that. Neither, for that matter, did the last version I submitted previous to this one. It’s not that adding that information is hard… it took 30-45 minutes. But my last error report didn’t mention that at all. I would have been happy to add it when I put the terms of service in. Is it really too much to ask that they mention both of those things at the same time so that, instead of 2 hours of work, 2 days of waiting, 30 minutes of work, 2 days of waiting I could just go ahead and do 3 hours of work at one time?
Fine. You guys suck. But this is a really important update so I put in the new information and submitted it.
Microsoft… what the fuck? That shit is in there. I put it in 2 error reports ago. What kind of fucking monkeys are testing my app that they don’t read my “terms of service” when my “terms of service” are both required and accessible. Do they get paid on a per/rejection basis? I only ask because I pay you $20 on a per/rejection basis (free apps have a limited number of free submissions). And when I’ve paid you and met your dumb ass requirements and get rejected based on something that makes it obvious to me that your tester didn’t actually look at my application, I get pretty pissed.
Perhaps I need to write a 150 page report, walking the tester through my application as if they were 5 years old, with screenshots of the application, pointing to different parts of the app, and explaining in vivid detail how I am abiding by each and every one of the guidelines. It’s not a huge deal, the guideline document is only 27 fucking pages long (over 2 times longer than Apple’s App Store Review Guidelines) with well over 100 rules that I need to follow, written in the finest legalese.
Do I sound ticked off? I’m pretty ticked off. Does this blog post sound unprofessional? This joke of an app submission process is unprofessional. I’ve always supported Microsoft as a business-friendly company. I love business software, in part because many of my friends work in environments where they use crappy software and I love to try to build good software for businesses that are too small for a major piece of software. Microsoft has always supplied the go-to technology to make that happen. But businesses don’t like waiting 2 days to fix a 30 minute problem. And they like it even less when it takes 2 additional days just to tell the tester that they screwed up, not us. And then pay for the privilege.
Let me be as clear as possible: Windows Phone 7 is the single best development platform for mobile that I’ve seen. Very fast, very easy, excellent tools. Simply amazing. But no one gives a crap if they can’t get their apps out. It’s all bullshit if no one can get to the end product the tools allow me to create. On that count, Microsoft, you aren’t just bad. You are the worst. By a large margin.
0 Responses to Throwdown With Windows Phone 7 App Submission
Did you file a support request on the app hub? I know the team is really helpful and lots of times they can get things past certification when they made a mistake.
Good post, Matthias. I agree that this is just unacceptable and Microsoft should definitely fix it (and reimburse you these payed submissions).
Personally I bailed at registering for the Marketplace, because I’m not a US citizen and I was not going to go through all the IRS hoops to get a reasonable amount of money for my payed apps. It would have seriously taken me at least three months to get signed up.
Pingback: Tweets that mention Designer Silverlight » Blog Archive » Throwdown With Windows Phone 7 App Submission -- Topsy.com
Well said sir and I agree with you. It is not unprofessional at all (but some may say it is). I think it is the response to the issue.
I had a similar experience with one of my apps. On the second update it was rejected because I have an email function that allows users to email the data in the app. It failed because if the user did not have email setup correctly it would not exit gracefully. Okay, no problem. My only question is why was this functionality not tested in 1.0 and only failed in 1.1. It has been there since 1.0 and has not changed.
It is a good plaform and hopefull with blogs like this people will pay attention and things might level out and eventually change. Well, one can hope.