freeman@argosy.UUCP (Jay R. Freeman) (11/20/90)
In article <IbEjOkq00WB8IL4Gdh@andrew.cmu.edu> jg23+@andrew.cmu.edu (John Robert Gray) writes: > What I would like to know is what does it take to become a developer? >What do you have to do as a developer? I suspect someone from Apple will post administrivia on how to apply, so I will not. However, I went through the application process recently (and got accepted), so possibly my experience will be of interest. I had a shareware product for the Mac out -- a Scheme interpreter. (Scheme is a programming language, a dialect of Lisp.) I had heard that officially-sanctioned developers could get lots of useful information, early software releases and other assistance, but I didn't know much about the process. So I called Apple's main switchboard number (in Cupertino, CA -- use directory assistance for the "408" area code), mumbled something about wanting to become a developer, and was immediately transferred to someone who took my name and address and promptly mailed me an application packet. It turns out there are two kinds of developers, depending on whether the product(s) in question are or are not in Apple's primarly line of business (or some such term). Those whose products are, can get to be Apple Partners, at an annual cost of $600, with somewhat more access to instruction and personal assistance than those whose products are not, who can get to be Apple Associates, at an annual cost of $350. Both kinds of developers get gigabytes of information per year (that's the literal truth -- somewhat more than one CD ROM per month), and are allowed to buy modest quantities of Apple equipment at large discounts off list. (I'm not supposed to say exactly how much.) It wasn't quite clear what constituted Apple's primary line of business, but I didn't particularly need a high level of personal support, so I applied to be an Associate. Basically, they wanted a fair amount of forms filled out, plus either (a) a business plan (for those who don't have a product out yet) or (b) some sales literature (for those who do). Hmn, I said to myself, I have a shareware product, what do I do? I decided to send them a couple of distribution discs of the implementation, with a note explaining how come there was no sales literature. About a month later, I got a card saying my application had been approved. Shortly thereafter, I started getting packages of information in the mail. The stuff is useful, timely, great fun to look through, and will be of considerable help in improving my Scheme implementation. When I decide to upgrade my hardware, the discount will be very useful. But even if there were no hardware discount, I am pretty sure the information will be worth the price. (One humorous note -- the beta release of System 7.0 arrived on Hallowe'en, which was pretty frightening ...) So I would say the process is painless. Get a packet and go for it. One question you may have is, what happens to your $350 (or $600) if your application is not accepted. And I do not know. -- Jay "Pixie Scheme" Freeman <canonical disclaimer -- I speak only for myself>