Oh sorry I just meant, from a developer's perspective, Apple's site is very "hands on". An 80s and 90s way of looking at software development that requires mor

Oh sorry I just meant, from a developer's perspective, Apple's site is very "hands on". An 80s and 90s way of looking at software development that requires more setup and boilerplate than today. To me, they are passing the buck to developers to just "work it out". I realize that Android is even worse (I wouldn't be able to test on the hundreds of devices it runs on). I'm hard on Apple because they have billions of dollars. Two policies that would fix their site for me: * Throw provisioning in the wastebasket. They forgot the first rule of security: if you leave it up to the user to learn it, it's insecure. Imagine how easy it would be to steal the private keys from a developer's machine, or from the email they used to send the key to someone on their team. It's fine to let devs sign their binaries. But don't impose that as a requirement. Xcode should automagically jump through whatever hoops are necessary to sign a binary to run on the device you are building for, and also sign it when you upload it to the app store (with credentials it receives from iTunes Connect using your username and password). To me, there is no excuse for the way it runs now. I understand that they rushed it through to get the iPhone released to the public, and that they perceive their current policy as more secure. But they are wrong. It's just more work. * If they are going to deprecate something, don't get rid of the original page. This is web design 101 and I just don't understand how it keeps happening.