When the scene is fully configured, it is displayed on an Apple Watch. If needed, the Watch app can communicate with the iOS app to retrieve resources and information from remote servers. After choosing the scene, the app launches the WatchKit Extension and creates the objects needed to manage that scene. For example, if you view your Watch app’s glance, it chooses your glance scene.
When you interact with your app on an Apple Watch, the Watch app chooses the appropriate scene from your Watch app's storyboards to handle the interaction. The Watch app and the WatchKit Extension work together to start your app’s interface. The custom logic in the WatchKit Extension is written in Swift. Longer-running tasks should be moved into the paired iOS app that runs on the user's iOS device and communicates with the Watch app via Bluetooth.Įvery Watch app has a WatchKit Extension built into it that contains your app's custom logic. The services a watch app performs should be short tasks that quickly deliver information or require quick, minimal interactions. Watch apps require an iOS app for launching. These three components are illustrated in the following diagram. A Watch app that displays user interface elements and handles navigation.
This is bundled with your Watch app and runs on the Apple Watch. A WatchKit Extension process that executes the watch app's application logic.
0 kommentar(er)
