3 ms·
"Jobs at first quashed the discussion," Isaacson writes, "partly because he felt his team did not have the bandwidth to figure out all the complexities tha
by sambeau 15y ago
"Jobs at first quashed the discussion," Isaacson writes,
"partly because he felt his team did not have the bandwidth
to figure out all the complexities that would be involved
in policing third-party app developers.
Looking at all the policy difficulties the iPhone App Store initially had, I think we can safely say he was right about that.
- tadfisher 15y agoThey still have serious policy issues. Case in point: a friend of mine needed to transfer ownership of an app from a third party to himself. Apple dragged this on for months, and it has been a constant stream of emails and 3-way phone calls. In the end, their Final Solution was this: he had to create a second LLC, add the third party as a "member" of this new company, get state documents certifying the existence of this LLC and the membership status of this third party, and a notarized letter from the third party authorizing the transfer. The most recent issue was that Apple kept deleting the transfer request form because the name of his second LLC was too similar to the name of his first (seriously, Apple?). Absolutely none of this is a technical problem; the whole reason he decided to go through this fiasco was to avoid breaking the upgrade path and losing all his reviews and stats (not to mention forcing his customers to lose data). Obviously, there is some switch that an Apple employee can tick that transfers apps from one developer account to another. Contrast this to the Android Market's transfer process, which boils down to both developers sending an email to Google to authorize a transfer.