6 ms·

You 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

by gte910h 16y ago

You 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.

palish 16y ago
What's their phone number?
- icey 16y ago
  Let me google that for you: http://developer.apple.com/contact/phone.html http://developer.apple.com/contact/phone.html Literally the first result when searching for "apple developer support phone number".
  - bittermang 16y ago
    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.
    - gnaritas 16y ago
      > 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 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.
      - panacea 16y ago
        Ack.. I can't fault your reasoning, and I am definitely in the http://lygtfy.com http://lygtfy.com camp, but I have to pause and reflect on this: "Yes, some people prefer to ask a human rather than Google; those people are lazy and need to be educated, not pacified." Doesn't it strike you as somewhat borg-like, subsumed by technology that we should deny people to impulse to ask other people things? I realize that aggregators and comments sections give a sort of false illusion that it's a small number of people in a conversation when the number of actual viewers of a thread (and hence, multiple wasted 'human' cycles spent processing 'noise'), but seriously... we should always defer to the algorithm, the index, the internet rather than asking humans?
        vacri 16y ago
        There is an immense difference between "can someone give me their phone number" and "I'm having troubles with mdadm picking up this array, can someone help out?" Pandering to trivial requests only encourages trivial requests. Hell, in a forum recently I responded to someone saying "you need version -foo- and you can find it here (link)". He said thanks... then three days later asked where he could find it (link was still valid). The next two comments were asking where they could find the exact thing in the link I'd given and described the parameters of. You also see the same thing in countless forums where commentor -foo- comes along, ignores the comments, and demands someone PM them with the solution. I don't have a problem with repeating stuff that's buried in the comments on page 5 or whatnot, but when it's this level of trivial crap, it is just chaff and shouldn't be encouraged.
  - gte910h 16y ago
    The correct number is 1 (408) 996-1010, ask for developer relations, 8am-5pm pacific time. It is not on that page. Be nice to them.
- gte910h 16y ago
  1 (408) 996-1010, ask for developer relations.

by gte910h 16y ago

palish 16y ago

What's their phone number?

icey 16y ago
Let me google that for you: http://developer.apple.com/contact/phone.html http://developer.apple.com/contact/phone.html Literally the first result when searching for "apple developer support phone number".
- bittermang 16y ago
  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.
  - gnaritas 16y ago
    > 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 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.
    - panacea 16y ago
      Ack.. I can't fault your reasoning, and I am definitely in the http://lygtfy.com http://lygtfy.com camp, but I have to pause and reflect on this: "Yes, some people prefer to ask a human rather than Google; those people are lazy and need to be educated, not pacified." Doesn't it strike you as somewhat borg-like, subsumed by technology that we should deny people to impulse to ask other people things? I realize that aggregators and comments sections give a sort of false illusion that it's a small number of people in a conversation when the number of actual viewers of a thread (and hence, multiple wasted 'human' cycles spent processing 'noise'), but seriously... we should always defer to the algorithm, the index, the internet rather than asking humans?
      - vacri 16y ago
        There is an immense difference between "can someone give me their phone number" and "I'm having troubles with mdadm picking up this array, can someone help out?" Pandering to trivial requests only encourages trivial requests. Hell, in a forum recently I responded to someone saying "you need version -foo- and you can find it here (link)". He said thanks... then three days later asked where he could find it (link was still valid). The next two comments were asking where they could find the exact thing in the link I'd given and described the parameters of. You also see the same thing in countless forums where commentor -foo- comes along, ignores the comments, and demands someone PM them with the solution. I don't have a problem with repeating stuff that's buried in the comments on page 5 or whatnot, but when it's this level of trivial crap, it is just chaff and shouldn't be encouraged.
- gte910h 16y ago
  The correct number is 1 (408) 996-1010, ask for developer relations, 8am-5pm pacific time. It is not on that page. Be nice to them.
gte910h 16y ago
1 (408) 996-1010, ask for developer relations.