Live data from Hacker News

Windows 8 Doesn’t Want Your App. Try Again Later

themissingbit.blogspot.be

21–30 of 73 posts

Re: Windows 8 Doesn’t Want Your App. Try Again Later

#21
post #13

I can relate a bit about this article and the Windows Store submission process - I have been using it since the end of July. The requirements mentioned in the post (1.2, 3.2, 3.8, etc.) are part of a big document that tries to clearly outline what an app should and shouldn't do. They are defined rather well, but sometimes will leave you wandering what the hell is going on. I submitted an HTML app that was accepted, t…

"Requirement 3.2: The app crashes"

Really? They've listed a 'requirement' as 'app crashes'?

Re: Windows 8 Doesn’t Want Your App. Try Again Later

#22
post #13

I can relate a bit about this article and the Windows Store submission process - I have been using it since the end of July. The requirements mentioned in the post (1.2, 3.2, 3.8, etc.) are part of a big document that tries to clearly outline what an app should and shouldn't do. They are defined rather well, but sometimes will leave you wandering what the hell is going on. I submitted an HTML app that was accepted, t…

"Requirement 3.2: The app crashes" Really? They've listed a 'requirement' as 'app crashes'?

No. "The app crashes" is the reason that it has failed on Requirement 3.2.

A bit of googling gives this which contains the full text of Requirement 3.2:-

http://msdn.microsoft.com/en-us/library/windows/apps/Hh92158...

Re: Windows 8 Doesn’t Want Your App. Try Again Later

#23
post #13

I can relate a bit about this article and the Windows Store submission process - I have been using it since the end of July. The requirements mentioned in the post (1.2, 3.2, 3.8, etc.) are part of a big document that tries to clearly outline what an app should and shouldn't do. They are defined rather well, but sometimes will leave you wandering what the hell is going on. I submitted an HTML app that was accepted, t…

"Requirement 3.2: The app crashes" Really? They've listed a 'requirement' as 'app crashes'?

FYI, the first requirement for the Apple App Store is the same:

2.1 Apps that crash will be rejected

Re: Windows 8 Doesn’t Want Your App. Try Again Later

#24

Earlier quoted context omitted.

>MS has had years to learn about what went wrong with the Apple process, and design around those issues. All that time spent learning about what and why Apple does what they do might have brought them to the conclusion that they ought to be doing the same thing. Or maybe they're "backed up" while they take it all in, figure out what's crap and what's not crap, create a good initial sorting of non-crap -> crap, and th…

"All that time spent learning about what and why Apple does what they do might have brought them to the conclusion that they ought to be doing the same thing." I fear that conclusion. But, really... concluding that courting developers pissed off with an arbitrary opaque process by giving them the same arbitrary opaque process makes sense to ... who? "You have to imagine that they've just suddenly become inundated by…

Not to mention, this guy released to the app store early.

Re: Windows 8 Doesn’t Want Your App. Try Again Later

#26
Look, if Apple can't manage to do a curated app store in a way that "works" for developers, if Microsoft can't manage to do it... maybe a curated app store isn't a good idea. I mean, it's obviously a good idea for whoever curates the app store (they can leverage their power in all kinds of ways), but perhaps the problems for developers is not because these companies are doing it poorly, but just that injecting a review process by a third party between the developer and their customers is NATURALLY bad for developers.

Re: Windows 8 Doesn’t Want Your App. Try Again Later

#27
post #22

Earlier quoted context omitted.

"Requirement 3.2: The app crashes" Really? They've listed a 'requirement' as 'app crashes'?

No. "The app crashes" is the reason that it has failed on Requirement 3.2. A bit of googling gives this which contains the full text of Requirement 3.2:- http://msdn.microsoft.com/en-us/library/windows/apps/Hh92158...

Also note that one of the common reasons for failing Requirement 3.2 now includes a reference to using CurrentAppSimulator that wasn't in the one linked in the original article.

I guess the OP just got stung by being an early adopter and the FAQ/requirement pages not being anywhere near complete as not enough people had gone through the certification process for MSFT to find all of the common reasons for rejection.

Re: Windows 8 Doesn’t Want Your App. Try Again Later

#28
post #23

Earlier quoted context omitted.

"Requirement 3.2: The app crashes" Really? They've listed a 'requirement' as 'app crashes'?

FYI, the first requirement for the Apple App Store is the same: 2.1 Apps that crash will be rejected

The way it was written was as a requirement:

"Requirement 3.2: the app crashes"

3.2 as a reason something is rejected ("app crashes") makes more sense. I wasn't sure if they're written it that casually, as it was quoted as such.

Re: Windows 8 Doesn’t Want Your App. Try Again Later

#29
I've submitted multiple apps to the Windows Store.

They're not desperate and they don't want crap, which is why they have a high bar. The problem is the testing procedures aren't always consistent, so something may pass once and get rejected when you do your next update for a bug that existed in a previous version. But, that's the nature of testing - the same thing has happened for us on Apple's app store.

Android appears to be the only store that lets you ship anything you want.

Re: Windows 8 Doesn’t Want Your App. Try Again Later

#30
As a developer (albeit not of Appstore Apps) I can understand the frustration of being told "It crashes" without being told why.

However, there was a very interesting comment on the actual blog itself suggesting something along the line of "re-submit the app under a different name". I actually think that may not be that bad of an idea. If you have done as much verification as possible as to the stability and performance of your product, sometimes you have to do some sideways thinking to get it approved by the powers that be.

I would like to see (just as an experiment) what would happen if the original developer would try this, and see what happens. The worst thing that could happen is that he could get told no (again).

Post reply on HN