Apple Watch Concepts
Architecture
Apple Watch
-
Resides on the Apple watch
-
Contains storyboard, resource files and no program code
WatchKit Extension
-
Resides on the user’s iPhone
-
Contains code for managing interface
User Interaction
-
Apple Watch is not functional without a paired iPhone.
-
The Watch OS looks for an appropriate storyboard scene to display.
-
Operating system tells the user’s iPhone to launch the extension and load interface.
-
The interface controller configures the elements and transitions of each scene.
Interface Styles
Hierarchical
-
Select an item displays more information.
-
Always starts with a single root interface controller.
-
Use pushControllerWithName:context to pass data to next controller
Page-Based
-
Fixed number of independent interface controllers.
-
User navigates by swiping left or right on screen.
-
System initializes all interface elements at runtime.
Life Cycle
-
The user’s iPhone automatically launches your WatchKit extension on launch.
-
Messages flow transparently between the app and extension until user interaction stops.
-
The WatchKit framework calls its initWithContext: method.
-
Design your controllers to be lightweight and never perform long-running tasks.
Launch Watch App
Any Questions?