What’s New In watch OS
Download as PPTX, PDF0 likes234 views
The document outlines new features in watchOS 2, including additional watch faces, time travel capabilities, and public transit support in Siri and maps. It discusses the SDK that allows for native apps and complications, as well as various frameworks for communication and interaction with the Apple Watch hardware. Additionally, it highlights resources for developers regarding watchOS and WatchKit, emphasizing performance and accessibility.
What’s New In watch OS
- 2. • 1
- 3. • 1
- 4. • 1
- 5. • 1
- 6. • 1
- 7. • 1
- 8. • 1
- 9. • 1
- 10. watchOS 2 and watchOS 1 architectures
- 11. Complications on the clock face
- 12. watchOS 2 • new watch faces (photo, album, time lapse) • time travel feature - shows events and predicted status of various things (e.g. weather) in the future or in the past if you've missed something • night stand mode - landscape display, buttons act as "snooze" and "off" • public transit support in maps and siri • siri can show glances • watch is protected by Activation Lock on startup
- 13. watchOS SDK (1) • native apps - still supplied as an iOS extension, no completely custom views, but the code runs on the watch • "complications" - tiny widgets that can be displayed inside various watch faces (ClockKit) • you create a timeline up front - what to show at what time, and watchOS uses this to show up to date data immediately when the screen turns on (also used for time travel - forward and backward) • scheduled updates - lets you update the data in the timelines at scheduled intervals • push updates - via push notifications • apps can access the Internet through known WiFi networks w/o an iPhone
- 14. Watch OS SDK (2) • apps can access microphone, HealthKit including heart rate, HomeKit, accelerometer, taptic engine, crown, play audio and video, record audio, make phone calls • a lot of well known frameworks are available like CoreGraphics, CoreLocation, CoreMotion, CoreData etc. • WatchConnectivity framework for communication between the extension and the iPhone app • NSURLSession can be used directly on the watch even if the iPhone is out of range • WKInterfacePicker control for scrolling through elements with the crown
- 15. • 1
- 16. • 1
- 17. • 1
- 18. • 1
- 19. • 1
- 20. • 1
- 21. • 1
- 22. • 1
- 23. • 1
- 24. • 1
- 25. Reference • GitHubGist - mackuba / wwdc15.md New stuff from WWDC 2015 https://gist.github.com/mackuba/15994186a4f9d7da3137 • WatchKit - Apple Developer https://developer.apple.com/watchkit/ • watchOS for Developers - Apple Developer https://developer.apple.com/watchos/pre-release/ • watchOS 2 Transition Guide https://developer.apple.com/library/prerelease/watchos/docume ntation/General/Conceptual/AppleWatch2TransitionGuide/index. html
- 26. Reference • WWDC 2015 • Introducing WatchKit for watchOS 2 • Layout and Animation Techniques for WatchKit • Building Watch Apps • Designing for Apple Watch • WatchKit Tips and • Apple Watch Design Tips and Tricks • Apple Watch Accessibility • Performance on iOS and watchOS • WatchKit In-Depth, Part 1 • WatchKit In-Depth, Part 2 • Introducing Watch Connectivity • Networking with NSURLSession
Editor's Notes
- #11: A Watch app for watchOS 2 consists of two separate bundles that work together to deliver your content to the user. The Watch app itself contains the storyboards and resource files needed to display your interface, and the WatchKit extension contains the code and resources needed to update that interface. In watchOS 2, the extension runs on the user’s Apple Watch instead of on the user’s iPhone, as was the case in watchOS 1. Moving the extension to Apple Watch makes communication between the Watch app and extension much faster and makes it possible for your app to run when the user’s iPhone is not present. Figure 1-1 shows the architecture for apps running on watchOS 2 and watchOS 1. In watchOS 2, not only does the WatchKit extension run on the user’s Apple Watch, it is delivered inside the user’s Watch app. This arrangement makes it easier for the Watch app to access resources stored in the WatchKit extension’s bundle. Apart from the architectural changes, the division of labor between your Watch app and WatchKit extension remains unchanged in watchOS 2. You use storyboards to define your app’s interface controllers and defineWKInterfaceController subclasses to configure and manage each of your screens. When the user interacts with controls in your interface, WatchKit calls the action methods of your interface controller object to give you an opportunity to respond. Most of your existing WatchKit extension code should continue to work in watchOS 2, but moving the WatchKit extension to the user’s Apple Watch has implications for how you design your app: You must implement your extension using the frameworks in the watchOS SDK instead of the iOS SDK. For any features not available in the provided frameworks, you must rely on your iPhone app to perform the corresponding task. For a list of frameworks available in the watchOS SDK, see Available System Technologies. Your extension now stores files and data on Apple Watch. Any data that is not part of your Watch app or WatchKit extension bundle must be fetched the network or from the companion iOS app running on the user’s iPhone. You cannot rely on a shared group container to exchange files with your iOS app. Fetching files involves transferring them wirelessly to Apple Watch.
- #12: In addition to updating your WatchKit extension code, apps can now provide custom complications. Acomplication is a small UI element that displays custom information on the clock face of Apple Watch. Like your app’s glance, complications are a way to display your app’s most important information to the user quickly. Your complications can be displayed alongside system complications for displaying the current date, moon phases, sunrise times, user activity, and many other types of information.