Apple App Approval Tips Nobody Told Me About
buzzwordcompliant.net
Apple App Approval Tips Nobody Told Me About
1–10 of 40 posts
Re: Apple App Approval Tips Nobody Told Me About
#2Summary: Be proactive and do as much work as you can to provide evidence on your own behalf, don't expect them to do the work for you.
Re: Apple App Approval Tips Nobody Told Me About
#3Summary: Be proactive and do as much work as you can to provide evidence on your own behalf, don't expect them to do the work for you.
Sounds like tips for getting hired :)
Re: Apple App Approval Tips Nobody Told Me About
#4Summary: Be proactive and do as much work as you can to provide evidence on your own behalf, don't expect them to do the work for you.
That's a reasonable summary. From looking at my server logs I can tell that they only spend a few minutes using the application during the approval process, so it is vitally important that you tee up as much information as possible for them.
Re: Apple App Approval Tips Nobody Told Me About
#5Summary: Be proactive and do as much work as you can to provide evidence on your own behalf, don't expect them to do the work for you.
That is how it is for everything when you are submitting something for approval. Always provide everything you can to make their job easy.
Re: Apple App Approval Tips Nobody Told Me About
#6You can actually call up the developer relations people and find out if anything is particularly troubling they can think of before you go through an expensive dev phase.
Their comments aren't binding (or even something I'd reference), and the approval criteria is constantly evolving, but they're pretty good at pointing out concerns from a 30 second description of the app.
This is good to do if you're doing something you think may get you in trouble, but think it won't necessarily do so. They've been very helpful in the past about their criteria for the different GPS APIs etc.
Re: Apple App Approval Tips Nobody Told Me About
#7You can actually call up the developer relations people and find out if anything is particularly troubling they can think of before you go through an expensive dev phase. Their comments aren't binding (or even something I'd reference), and the approval criteria is constantly evolving, but they're pretty good at pointing out concerns from a 30 second description of the app. This is good to do if you're doing something…
What's their phone number?
Re: Apple App Approval Tips Nobody Told Me About
#8You can actually call up the developer relations people and find out if anything is particularly troubling they can think of before you go through an expensive dev phase. Their comments aren't binding (or even something I'd reference), and the approval criteria is constantly evolving, but they're pretty good at pointing out concerns from a 30 second description of the app. This is good to do if you're doing something…
What's their phone number?
Let me google that for you:
http://developer.apple.com/contact/phone.html
Literally the first result when searching for "apple developer support phone number".
Re: Apple App Approval Tips Nobody Told Me About
#9Earlier quoted context omitted.
What's their phone number?
Let me google that for you: http://developer.apple.com/contact/phone.html Literally the first result when searching for "apple developer support phone number".
And herin lies the problem of this attitude.
The original commentator posed a solution, "Call them" but no phone number.
The second commentator realized this gap, and asked, "What is the phone number?" One could reasonably expand upon this, it certainty hasn't occurred to me that you could call them and talk to them either. Do you need to be enrolled? Is the number secret? Where is the number. Clearly the first commentator must know this and more, as he is posing it as a solution. At the very least, he must have the number, or know where to get the number.
You, the third commentator, come in with the Google Result. Obvious to some, just Google it. Not obvious to others. If it wasn't obvious that you could call them, it would be less obvious that the number is simply publicly available. Further, search results can sometimes be inconclusive, and while this one was the first result and directly on Apple.com, other queries are not so obvious. Again, the first source clearly had the information, and he was directly asked when he did not provide it.
That is why communities, question and answer sites, forums, Stack Overflow, and everything else exist. Direct knowledge from people who are verified or profess to having the information that you seek. Some people feel better about direct conversations or direct answers from people vs. casting their fishing hook out in to the giant open Internet and hoping they catch their answer. Some people aren't any good at searching. Sometimes just asking someone who knows can be quicker.
Re: Apple App Approval Tips Nobody Told Me About
#10Earlier quoted context omitted.
Let me google that for you: http://developer.apple.com/contact/phone.html Literally the first result when searching for "apple developer support phone number".
And herin lies the problem of this attitude. The original commentator posed a solution, "Call them" but no phone number. The second commentator realized this gap, and asked, "What is the phone number?" One could reasonably expand upon this, it certainty hasn't occurred to me that you could call them and talk to them either. Do you need to be enrolled? Is the number secret? Where is the number. Clearly the first comme…
> Some people aren't any good at searching.
You don't need to be good to Google most things.
> Sometimes just asking someone who knows can be quicker.
Google knows the answer to most simple queries like this.
You shouldn't ask a question where the answer is trivially Googled; Google first, then ask when you can't find the answer. The previous poster had the right attitude by saying let me Google that for you, it's such a pervasive problem that sites like http://lmgtfy.com have to exist to help educate lazy people.
Yes, some people prefer to ask a human rather than Google; those people are lazy and need to be educated, not pacified.