测试 iOS 应用程序通常会追溯到多少个版本？
测试应用程序与更旧的 iOS 版本的兼容性是否很常见（在我的例子中，iOS 4.3 应用程序与 iOS 2.x）？或者大多数应用程序只是测试了一个版本左右。如果我的应用程序无法在旧版本上运行，你知道我会失去多少比例的 iOS 市场吗？我猜数量很小，但这似乎足以让我的雇主要求我提供远程向后兼容性 -_-
Is it common to test apps for compatibility with much older iOS versions (in my case, iOS 4.3 apps with iOS 2.x)? Or are most apps just tested one version back or so. Any idea what percentage of the iOS market will be lost to me if my app doesn't work on much older versions? I'm guessing a miniscule amount, but that seems to be enough for my employer to ask me for distant backwards compatibility -_-
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
每个应用程序之间的差异很大，具体取决于所使用的功能和市场的广泛性/利基性。您应该瞄准的最广泛的目标是：当前版本、之前的“点”版本、之前主要版本的最后一个版本。 （现在，5.0 尚未发布，那就是 4.3、4.2、3.2（仅限 iPad，因此 iPhone/iPod 为 3.1.3）。
我的建议是，您永远不需要支持比这更多的内容。如果您的产品不支持在 3.0 上不起作用，用户可以免费更新当然，旧的硬件并不总是更新，并且如果您的市场是“人们被抛在后面”（通常与“人们在应用程序中花钱”不重叠）。商店”）你可以支持旧版本。
有些只支持新版本，因为新版本中使用了强大的功能。4.0 有很多很棒的附加功能（其中包括块/GCD/多任务）。尽快将 3.x 抛在后面如果
您的受众是前沿人群，您可以只支持最新版本（现在是 4.3、4.2 - 实际上，那里没有巨大的 API 差异），
我有一个针对 5.0 的应用程序，但不会。支持任何较旧的、较新的 API 是核心，
就测试而言，如果您拥有您认为目标是最小的 RAM 的最旧的硬件，这将有助于测试。 CPU和内存确实可以压在这些上面。
This varies quite a bit app-to-app, depending on features being used and broadness/niche-ness of market. The broadest you should target is: current release, previous "dot" release, last version of previous major release. (Now, with 5.0 not yet released, that would be 4.3, 4.2, 3.2 (which was iPad only, so 3.1.3 for iPhone/iPod).
My suggestion is that you never need to support more than this. If your product doesn't work on 3.0, the user can update for free. Of course older hardware doesn't always update, and if your market is "people getting left behind" (which usually doesn't overlap with "people spending money in the app store") you can support older.
Some will only support newer because of powerful features being used in newer releases. 4.0 had a lot of great additions (blocks/GCD/multitasking among them). Leave 3.x behind as soon as you can.
If your audience is a push-the-edge crowd, you can just support the latest (4.3, 4.2 right now - realistically, there's not huge API differences there).
I have an app targeted at 5.0 that will not support anything older, newer APIs are central.
As far as testing, if you have the oldest hardware with the smallest RAM you think you are targeting, that will help test. CPU and memory can really be pushed on those.