iPhone 应用程序本地化，针对不同市场发布单独的应用程序
我在瑞典应用商店中有一个应用程序，我打算将其适应其他一些市场。在这种情况下，本地化最重要的部分是改变应用程序针对不同市场（国家）的工作方式的某些方面，因此这主要不是语言适应。
也许，我不会使用正常的内置机制进行本地化。相反，我考虑为不同的市场构建单独的版本，并将它们作为单独的应用程序在 App Store 上发布（具有相同的图标和相似的名称），并且每个版本仅在一个国家/地区提供。
我的主要论点是：
1）由于App Store支持的语言少于iOS，因此有几个国家Apple将App Store语言定义为英国英语（例如丹麦、挪威）。那么我就无法用他们自己的语言创建良好的销售宣传，除非我为这些国家发布完全独立的应用程序。
2) 我认为在这种特殊情况下，通过在源代码中插入编译器指令并为不同的市场制作不同的 Xcode 目标，我认为实现本地化会更快。 （这可能是由于我的应用程序的第一个版本的架构不太智能造成的，尽管如此，这就是当前的状态。）
现在，我的问题：
除了明显的缺点之外，为不同的市场发布单独的应用程序是否有任何缺点将会有更多的行政管理？ （例如不太利于在 App Store 上获得良好排名、被拒绝的风险等......）
I have an app on the Swedish App Store which I intend to adapt to some other markets. In this case, the most important part of the localization is to change some aspects of how the app works for different markets (countries), so this is not primarily about language adaptations.
Probably, I will not use the normal built-in mechanisms for localization. Instead I consider to build separate versions for different markets and release them as separate apps on App Store (with the same icon and similar names), with each one of them only available in one country.
My main arguments are,:
1) Since App Store supports fewer languages than iOS, there are several countries where Apple has defined the App Store language to be UK English (e.g. Denmark, Norway). Then I cannot create a good sales pitch in their own language, unless I release completely separate apps for these countries.
2) I think it will be faster for me to implement the localization, in this particular case, by inserting compiler directives in the source code and make different Xcode targets for different markets. (This may be caused by a not so smart architecture of the first version of my app, by nevertheless, this is the current state.)
NOW, MY QUESTION:
Are there any drawbacks of releasing separate apps for different markets, except the obvious one that there will be more administration? (e.g. less favourable for achieving good ranking on App Store, risk of rejection, etc...)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
App Store 审核指南，其中之一是
App Store Review Guidelines, one of them is that
苹果公司总体上不太喜欢这种方法。我听说出于本地化原因，同一应用程序有三个副本的非官方限制，但我不知道具体情况如何。
难道不能将此逻辑构建到应用程序中吗？您可以使用 NSLocale 在运行时获取设备区域设置（不仅是语言，还包括国家/地区），然后使用运行时逻辑来切换视图控制器、nib 文件等。如果您的应用程序结构不佳，您可以在如果需要，MainWindow.nib 级别，然后在加载时可以完全控制更改应用程序的任何方面。
我认为，由于您提到的原因，这是比发布多个应用程序版本更好的方法，并且可以避免让您的应用程序获得批准的麻烦。它不能解决应用程序商店注释问题，但也许您可以通过另一种方式解决这个问题，将营销策略集中在网站或应用程序商店外部的东西上。
Apple are not a big fan of this approach generally. I heard somewhere that there was an unofficial limit of three copies of the same app for localisation reasons, but I don't know how concrete that is.
Would it not be possible to build this logic into the app? You can use the NSLocale to get the device locale (not just language, also country) at runtime, and then use runtime logic to switch out view controllers, nib files etc. If your app is not well structured, you could just branch at the MainWindow.nib level if necessary, and then have complete control to change any aspect of the app when it loads.
I think this is a better approach than releasing multiple app versions for the reasons you mention, as well as avoiding hassles getting your app approved. It doesn't solve the app store notes problem, but perhaps you can work around that another way, by focussing your marketing strategy on a web site or something external to the app store.