将 iPad 支持添加到 iPhone 项目：通用还是两个独立的应用程序？
我有一个现有的 iPhone 应用程序，而且现在我的用户中似乎有很大一部分在 iPad 上运行它（我可以这么说，因为我从用户那里收到的许多电子邮件都有“从我的 iPad 发送”签名）。
我现在正在实现 iPad 版本，并且是从相同的代码库进行的，这很方便。但当我完成后，我想知道是否应该将其作为通用应用程序发布。我可以将其作为单独的、全新的 iPad 专用应用程序上传。
如果我使其通用：
- ✓ 当我现有的 iPad 用户更新并突然看到 iPad 支持时，他们会很高兴。
- ✓ 我受益于我的应用程序的现有排名/流量，无需从头开始构建。
- ✗ 我的 iPhone 用户将免费看到更新。
- ✗ 用户评级可能会令人困惑，因为这两个版本差异很大
如果我将它们制作为两个独立的应用程序：
- ✓ 我可以为 iPhone 和 iPad 设置不同的定价
- ✗ iPad 上使用我的 iPhone 应用程序的现有用户将不知道有新版本对于他们来说。如果他们发现了这一点，必须迁移数据会让他们烦恼。也将再次为此付出代价。
我是否错过了任何其他可能有助于决定采取哪条路线的权衡？有没有人有走这两条路的经验可以分享？
I have an existing iPhone app and it seems that a significant proportion of my users these days are running it on iPad (I can tell because a lot of the emails I get from users have a "sent from my iPad" signature).
I am now implementing the iPad version and I'm doing it from the same code base, which is convenient to do. But when I'm done, I wonder if I should actually release it as a universal app. I could instead upload it as a separate, brand new iPad-only app.
If I make it universal:
- ✓ My existing iPad users will be delighted when they update and suddenly see iPad support.
- ✓ I benefit from existing ranking/traffic to my app, won't have to build it up from scratch.
- ✗ My iPhone users will see an update for nothing.
- ✗ User ratings might get confusing as the two versions are quite different
If I make them two separate apps:
- ✓ I can set different pricing for iPhone and iPad
- ✗ Existing users of my iPhone app who are on iPad won't know there's a new version for them. And if they discover it, having to migrate their data will annoy them. As will paying once more for it.
Am I missing any other tradeoffs that may help decide which route to take? Does anyone have experience to share from taking either route?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
没有其他办法了。你应该通用。
反对拥有通用应用程序的唯一原因是不同的定价（我认为这可能会激怒客户。尤其是那些在 iPad 上使用该应用程序的现有客户）。
我可以想出很多理由：
客户看到通用支持的应用程序更新警报。制作单独的 iPad 应用程序意味着您必须手动联系 iPad 客户以通知他们
代码更易于管理。如果您正在创建一个为表/视图提供信息的数据处理类怎么办？为什么要在两个不同的项目中拥有相同代码的两个副本？如果您将来修复一个错误并且必须在不同的项目中执行两次相同的修复怎么办？
拥有通用应用程序可以让您作为开发人员看起来更加专业
随着您的项目不断发展，拥有两个不同的应用程序将成为一个问题进行更改、运行更新等方面的开发噩梦。
一些第三方库需要某种形式的应用程序 ID 才能运行。其他应用程序则要求您按应用程序实施付费。当您可以在一个通用应用程序中完成这些操作时，为什么要为不同的应用程序支付两次费用？
客户体验 - 拥有 iPhone 和 iPad 的用户希望使用 iCloud 等在 iPhone 和 iPad 之间实现一定程度的应用程序同步。我认为用户不会太高兴知道他们的数据未在设备之间同步。
必须为另一台设备再次购买一台设备的应用内购买（这不会受到客户的欢迎）。
...我可以继续一整天。总而言之，除非您有充分的理由拥有单独的应用程序（老实说我想不出任何应用程序），否则请通用。通用应用程序给人的印象是干净、构建精良且制作专业。它们给客户留下了良好的印象，并且对于开发人员来说管理起来很容易。
为 iPhone 和 iPad 制作两个独立的应用程序就像将一个网站分成不同的独立版本，并为不同的浏览器提供各自的域名......没有意义:)
There's no other way about it. You should go universal.
The only reason against having a universal app would be different pricing (and I think that may piss off customers quite a bit. Especially the existing ones who are using the app on their iPads).
I can come up with loads of reasons:
Customers see an app update alert for the universal support. Making a separate iPad app means you have to manually reach out to the iPad customers to notify them
Code is more manageable. What if you're creating a data handling class that supplies information for tables/views? Why would you want to have two copies of the same code in two different projects? What if you fix a bug in the future and have to do the same fixes twice in different projects?
Having a universal app makes you look more professional as a developer
As your project continues to grow, having two different apps is going to be a development nightmare in terms of making changes, running updates, etc.
Some third party libraries require some form of app ID to function. Others exist that require you to pay per app implementation. Why pay twice for different apps when you can have it done within a single universal app?
Customer experience - Users who own iPhones and iPads will expect a certain amount of syncing of the app between their iPhone and iPad using iCloud et al. I don't think a user will be too happy to know that their data is not syncing across their devices.
In App Purchases for one device would have to be bought again for the other one (this won't go down well with customers).
... I can go on and on all day. To summarize, unless you have a VERY good reason to have separate apps (and I honestly can't think of any), go universal. Universal apps come across as clean, well built, and professionally made. They make a good impression on the customers, and are a breeze to manage for the developer.
Making two separate apps for iPhones and iPads is like taking a website and splitting it into different standalone versions with their own individual domain names for different browsers... doesn't make sense :)
我看到一篇有趣的博客文章（如下），其中显示如果您有单独的应用程序，您在 iTunes 上的下载排名会降低。
http://www.cocoanetics。 com/2011/05/to-universal-or-not/
I saw an interesting blog post (below) where it shows that you dilute your download rank on iTunes if you have separate apps.
http://www.cocoanetics.com/2011/05/to-universal-or-not/