TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Why iOS 8 Represents a New Kind of Challenge for Developers

5 点作者 stax012超过 10 年前

2 条评论

rizwan超过 10 年前
iOS 8 added many useful APIs, but I find many are hard to use while maintaining support for iOS 7.<p>For example: - To share code between your app and your iOS 8 extensions, you want to put them in a shared framework, something which was just added in Xcode 6, and compatible only with iOS 8. So using shared code from iOS 7 means you&#x27;d have to keep copies of your source in the main app framework.<p>- Photos.framework is really great, but is completely different from Assets.framework, so building a photo app means writing your code twice. Yes, you can use Assets framework from iOS 8, but it&#x27;s unclear how iCloud Photo Library will work with it (iOS 8.0 inadvertently removed &quot;Camera Roll&quot; from Assets framework, for example)<p>- Can&#x27;t clean up your UIActionSheet, UIAlertView, UIPopoverController code with UIAlertController until you go iOS 8+<p>So iOS 8 moves a lot of things forward really nicely, and building an iOS 8-only app has been really great, but I feel, more so than before, that it&#x27;s harder to maintain support for older iOS versions.<p>I was hoping iOS 8&#x27;s adoption numbers would be rising faster than it did for iOS 7, so it&#x27;d be easier to justify dropping iOS 7 support sooner, but anecdotally it seems the large installation binary has made it hard to update 16GB devices.
mvelie超过 10 年前
This is the same as the jump from iOS 6 to iOS 7, except that was more UI code. It was difficult to support both and keep the correct look and feel between the apps without a lot of extra work, even more if you weren&#x27;t using auto layout. The basic controls changed a lot and the change with the status bar still affects apps today.