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).
我有一个现有的iPhone应用程序，似乎我的用户中有很大一部分用户在iPad上运行它（我可以说，因为我从用户那里获得的很多电子邮件都有“从我的iPad发送”签名）。
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.
我现在正在实现iPad版本，我正在使用相同的代码库来完成它，这很方便。但是当我完成后，我想知道我是否应该将其作为通用应用程序发布。我可以将其作为一个单独的，全新的iPad专用应用程序上传。
If I make it universal:
如果我把它变成普遍的：
- ✓ My existing iPad users will be delighted when they update and suddenly see iPad support.
- ✓我的现有iPad用户在更新时会很高兴并突然看到iPad支持。
- ✓ 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.
- ✗我的iPhone用户将看到无更新的更新。
- ✗ 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
- ✓我可以为iPhone和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.
- ✗我的iPhone应用程序的现有用户在iPad上不会知道他们有新版本。如果他们发现它，不得不迁移他们的数据会使他们烦恼。将再次支付它。
Am I missing any other tradeoffs that may help decide which route to take? Does anyone have experience to share from taking either route?
我是否缺少任何可能有助于决定采取哪条路线的权衡？有没有人有经验可以分享任何一条路线？
2 个解决方案
#1
7
I saw an interesting blog post (below) where it shows that you dilute your download rank on iTunes if you have separate apps.
我看到一篇有趣的博客文章（如下），如果您有单独的应用程序，它会显示您在iTunes上淡化了您的下载排名。
http://www.cocoanetics.com/2011/05/to-universal-or-not/
http://www.cocoanetics.com/2011/05/to-universal-or-not/
#2
12
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).
反对使用通用应用程序的唯一原因是价格不同（我认为这可能会让客户受到很大的压力。特别是那些在iPad上使用该应用程序的现有用户）。
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
客户会看到针对通用支持的应用更新提醒。制作单独的iPad应用程序意味着您必须手动联系iPad客户以通知他们
-
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?
某些第三方库需要某种形式的应用程序ID才能运行。存在其他需要您按应用实施付费的其他内容。如果您可以在一个通用应用程序中完成它，为什么要为不同的应用程序支付两倍？
-
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.
客户体验 - 拥有iPhone和iPad的用户希望使用iCloud等人在iPhone和iPad之间进行一定数量的应用程序同步。我认为用户不会太高兴知道他们的数据没有在他们的设备上同步。
-
In App Purchases for one device would have to be bought again for the other one (this won't go down well with customers).
在App购买中，一个设备必须再次购买另一个设备（这对客户来说不会很好）。
... 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 :)
为iPhone和iPad制作两个独立的应用程序就像是将一个网站分成不同的独立版本，并为不同的浏览器分别拥有自己的域名......没有意义:)
#1
7
I saw an interesting blog post (below) where it shows that you dilute your download rank on iTunes if you have separate apps.
我看到一篇有趣的博客文章（如下），如果您有单独的应用程序，它会显示您在iTunes上淡化了您的下载排名。
http://www.cocoanetics.com/2011/05/to-universal-or-not/
http://www.cocoanetics.com/2011/05/to-universal-or-not/
#2
12
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).
反对使用通用应用程序的唯一原因是价格不同（我认为这可能会让客户受到很大的压力。特别是那些在iPad上使用该应用程序的现有用户）。
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
客户会看到针对通用支持的应用更新提醒。制作单独的iPad应用程序意味着您必须手动联系iPad客户以通知他们
-
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?
某些第三方库需要某种形式的应用程序ID才能运行。存在其他需要您按应用实施付费的其他内容。如果您可以在一个通用应用程序中完成它，为什么要为不同的应用程序支付两倍？
-
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.
客户体验 - 拥有iPhone和iPad的用户希望使用iCloud等人在iPhone和iPad之间进行一定数量的应用程序同步。我认为用户不会太高兴知道他们的数据没有在他们的设备上同步。
-
In App Purchases for one device would have to be bought again for the other one (this won't go down well with customers).
在App购买中，一个设备必须再次购买另一个设备（这对客户来说不会很好）。
... 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 :)
为iPhone和iPad制作两个独立的应用程序就像是将一个网站分成不同的独立版本，并为不同的浏览器分别拥有自己的域名......没有意义:)