- ARKit gives iOS developers a native augmented reality layer without custom ML pipelines or third-party SDKs.
- iOS 11’s drag-and-drop API and improved filesystem access open new interaction patterns for iPad app engineering.
- Apple’s hardware refresh, from Kaby Lake Macs to the iMac Pro, raises the performance baseline that teams can target.
Apple’s WWDC17 keynote in San Jose delivered six announcements that shift what iOS and macOS development teams can build right now. Two of the most consequential ARKit and iOS 11 require developers to make concrete architecture decisions before shipping their next update.
AR Capability Gap in Mobile Apps: How ARKit Closes It Without Custom Infrastructure
ARKit solves the hardest part of mobile AR development: scene understanding without proprietary hardware or a custom vision pipeline. Before this release, teams building augmented reality features on iOS had to rely on third-party SDKs that added complexity, licensing overhead, and unpredictable update cycles. ARKit integrates directly with the iOS camera and motion sensors, giving developers a stable, Apple-maintained foundation for placing virtual objects in real-world scenes.
The live demo at WWDC17 showed a lamp and coffee cup placed precisely on a real table surface, with the app maintaining correct perspective as the camera moved. That kind of positional stability previously required purpose-built depth sensors. Now it runs on a standard iPhone or iPad, which means the addressable device base for AR-enabled apps expands significantly on day one.
For iOS app development teams, the engineering decision is not whether to evaluate ARKit; it is which existing app features benefit from an AR layer and what session management patterns to apply. Healthcare apps, retail configurators, and field service tools all have use cases where ARKit can replace a screen-based workflow with a spatial one.
Fragmented iPad Multitasking: The Engineering Decision Behind iOS 11’s New Interaction Model
iOS 11’s drag-and-drop API for iPad is not a UI feature; it is a cross-app data transfer architecture that requires deliberate adoption. Apps that do not implement the new drag-and-drop delegates will not receive items dropped from other apps, creating a visible gap in the user experience as the platform shifts. The engineering decision is whether to treat this as a compatibility patch or use it as a forcing function to rework how the app handles external data input.
The handwriting recognition improvement tied to Apple Pencil adds a second layer of complexity. Notes made with the Pencil are now indexed and searchable through deep learning running on-device. For teams building productivity, documentation, or clinical note-taking apps, this means the search infrastructure needs to account for handwritten content as a first-class input type, not an edge case.
According to Apple’s developer documentation, the new cross-platform app development patterns introduced in iOS 11 align closely with how modern multi-platform frameworks handle shared state. Teams already working with reactive architectures will find the transition more straightforward than teams running view-controller-heavy codebases.
What San Diego Mobile Teams Are Prioritizing After WWDC17
The San Diego development community tends to move quickly on Apple platform updates because several local industries, such as healthcare, defense technology, and consumer mobile, ship iOS apps on tight release cycles. After WWDC17, the immediate priority we see across projects is ARKit evaluation: not full AR rewrites, but targeted feature additions where spatial context adds genuine user value.
The hardware announcements matter too. The iMac Pro, with 8-to-18-core Xeon processors and 22 teraflops of graphics compute, raises what development and CI/CD environments can handle locally. Teams doing compute-heavy work, such as ML model training, video rendering, or large Xcode build pipelines, will see measurable build time reductions on the new hardware. That is an infrastructure decision worth timing with the December release.
Conclusion
WWDC17 moved the iOS development baseline on two fronts: a native AR framework that removes the biggest barrier to spatial app features, and an iPad interaction model that requires deliberate engineering adoption to execute well. Review which of your current app features have a clear ARKit use case, and audit your iPad app’s drag-and-drop readiness before iOS 11 ships to production users. Working with a team that stays current on Apple’s platform changes makes both transitions faster.
Frequently Asked Questions
What is ARKit and why does it matter for iOS developers?
ARKit is Apple’s augmented reality development framework, introduced at WWDC17, that lets iOS apps place virtual objects in real-world scenes using the device camera and motion sensors. It removes the need for third-party AR SDKs and runs on standard iPhones and iPads, which makes it practical to ship AR features without additional hardware dependencies.
What changed in iOS 11 for iPad app development?
iOS 11 introduced a cross-app drag-and-drop API for iPad that requires apps to implement specific delegates to send and receive data between applications. It also added on-device deep learning search for Apple Pencil handwriting, which changes how productivity and note-taking apps need to index and retrieve user input.
ARKit vs. third-party AR SDKs: which should iOS teams use?
ARKit is the stronger default choice for teams building on iOS because it is Apple-maintained, has no licensing overhead, and integrates directly with the device’s native sensor stack. Third-party SDKs may still be appropriate when cross-platform AR support is required, but for iOS-only or iOS-primary apps, ARKit reduces integration complexity significantly.
How does WWDC17 affect iOS app development teams in San Diego?
San Diego iOS teams working in healthcare, consumer mobile, and field service have the most immediate opportunities from ARKit and iOS 11’s interaction updates. The spatial features in ARKit map directly to clinical, retail, and inspection workflows, where screen-only interfaces create friction.
Is the iMac Pro worth the upgrade for iOS development teams?
The iMac Pro’s multi-core Xeon processors and high-bandwidth memory make it a meaningful upgrade for teams with heavy Xcode build pipelines, ML training tasks, or video rendering in their development workflow. For teams with lighter build requirements, the updated standard iMac with Kaby Lake and 4K Retina covers most development needs at a lower entry point.
What is HomePod and does it create any developer opportunities?
HomePod is Apple’s home speaker with Siri integration, designed to compete with Amazon Echo and Google Home. For developers, the primary opportunity is in SiriKit extensions apps that already support Siri commands can surface through HomePod, making voice interaction design a more relevant engineering consideration for utility, productivity, and smart home apps.
