HN 用户提问：为什么 2025 年加入苹果开发者计划会如此困难？
7 分•作者: thomas_witt•9 个月前
我最近尝试为一家只有我一个人的小公司注册 Apple 开发者计划，结果这个过程变成了一段出乎意料的糟糕经历。我原本以为只需快速在线注册并支付 99 美元即可，结果却经历了数周的身份验证，问题接踵而至。
令人沮丧的是，这一切的起因是我想使用“使用 Apple 登录”功能。Apple 强制你加入开发者计划才能启用这项功能，并且每年收取 99 欧元的服务费。而 Google 和 Amazon 提供的类似登录服务都是免费的，并且只需几分钟即可设置完成。我看不出这项政策对 Apple 的生态系统有何益处。
因此，我需要：
* **D-U-N-S 验证：** Apple 要求公司提供 D-U-N-S 编码，这在欧盟非常罕见。申请过程花费了几天时间，甚至需要与外包的邓白氏子公司进行人工电话确认。
* **文件上传：** 随后，Apple 支持要求我上传多份文件：政府身份证明、雇佣证明（当只有我一个人的时候，这很奇怪），以及公司注册文件。我最终通过应用程序和一个特殊链接上传了这三份文件，总共上传了三次。不同的支持代表（总是很友好，但发送的是模板回复）似乎无法看到相同的历史记录。当我给反馈调查打了低分时，我收到的回复是标准化的，根本没有针对我的观点进行回应。
* **网站审查：** 在身份验证之后，Apple 还审查了我的项目网站。他们说网站“内容最少”，并且在发布应用程序之前需要一个适当的支持联系页面。但我确实有问题追踪器和联系信息。如果你甚至还没有发布产品怎么办？
* **地区不匹配：** 系统无法处理我的个人 Apple ID 在一个欧盟国家，而公司在另一个欧盟国家的情况。为了向 Apple 支付 99 欧元，我被告知要将我的 iPad 的地区切换到与开发者帐户匹配的地区——这将破坏我的 Apple One 订阅，等等。我甚至不会用 iPad 进行开发，所以我认为我只需切换到我的 MacBook 即可。
* **设备锁定：** 我尝试在我的 MacBook 上使用开发者 Apple ID 继续操作，但系统强制你必须在开始注册的同一设备上完成注册。在 MacBook 上，我必须从头开始，重新上传所有文件。这不仅仅是糟糕的用户体验，而且令人费解——尤其是对于 Apple 而言。
3 周过去了，我仍然没有注册成功。
我发布这篇文章是因为这次经历感觉完全崩溃了。我没有期望一帆风顺，但这远远超出了正常的摩擦。
问题：
* 其他人是否遇到过 Apple 开发者注册的相同问题，尤其是在跨地区的情况下？
* 你认为这些障碍会劝退独立开发者吗？
* Apple 的员工认为这是一种很棒的体验吗？这仅仅是官僚主义，还是有更深层次的理由？有时我想知道，（通常同样笨拙的）欧盟法规在这里是否实际上是一种有用的良药。
查看原文
I recently attempted to enroll a small 1-person company in the Apple Developer Program, and the process turned into a surprisingly terrible journey. I expected a quick online sign-up and a $99 payment – instead I got weeks of identity checks and problem after problem.<p>Frustratingly, the whole thing started because I wanted to use Sign in with Apple. Apple forces you into the developer program just to enable it, and charges €99/year for the privilege. Google and Amazon both offer their equivalent login services for free, set up in minutes. I can’t see how this policy benefits Apple’s ecosystem.<p>So I needed:<p>- D-U-N-S verification: Apple required a D-U-N-S Number for the company – very uncommon in the EU. Applying took several days and even a manual phone confirmation with an outsourced D&B subsidiary.<p>- Document uploads: Apple support then asked me to upload multiple documents: government ID, employment verification (odd when it’s just me), and business registration papers. I ended up uploading these three separate times, via the app and a special link. Different support reps (always friendly, but sending template replies) didn’t seem to see the same history. When I rated a feedback survey low, I got a standardized response that didn’t engage with my points at all.<p>- Website scrutiny: After identity checks, Apple also reviewed my project website. They said it had “minimal content” and needed a proper support contact page before apps could be distributed. But I do have an issue tracker and contact info. What if you haven’t even launched yet?<p>- Region mismatch: The system couldn’t handle that my personal Apple ID is in one EU country while the company is in another. To pay Apple €99, I was told to switch my iPad’s region to match the developer account — which would break my Apple One subscription amongst other things. I wouldn't even use the iPad for development, so I thought I'll just switch to my MacBook.<p>- Device lock-in: I tried to continue on my MacBook with the developer Apple ID, but the system forces you to finish enrollment on the same device you started with. On the MacBook, I’d have to start from scratch and re-upload all documents. That’s not just bad UX, it’s inexplicable – especially for Apple.<p>3 weeks later, and I am still not enrolled.<p>I’m posting this because the experience felt utterly broken. I didn’t expect smooth sailing, but this was far beyond normal friction.<p>Questions:<p>- Have others run into the same issues with Apple’s developer enrollment, especially cross-region?<p>- Do you think these hurdles discourage indie developers?<p>- Do people at Apple consider this a great experience? Is this just bureaucracy, or is there a deeper rationale? Sometimes I wonder if the (often equally clumsy) EU regulations are actually a useful medicine here.