Apple's newly released WatchKit documentation offers us an insight into how the new class of device will look, feel, and work. I've been digging through the documentation looking for clues as to what the new device has to offer and what new features it will bring to the Apple ecosystem.
We get the screen sizes and pixel densities for both sizes of Apple Watch. App designers will have to design the app to work on both screen sizes. Both displays fall into the "retina" display category.
Apple is introducing a lot of new concepts when it comes to interacting with the Apple Watch (and how the Apple Watch interacts with the owner).
Apps won't run native on the Apple Watch, at least not initially. Instead, when the user taps on an app on their Apple Watch, it launches a WatchKit extension on their iPhone and connects to each other that way. This allows messages to be sent from the app on the iPhone to the app on the Apple Watch until the user stops interacting with the app.
Not only does this transfer the bulk of the work to the iPhone, it means less of a battery drain on the Apple Watch (although how much additional battery drain this will put on the iPhone remains to be seen).
Apple is offering two layout styles for apps:
Apps will support simple menus, which allows developers to make better use of the limited screen real estate. Users will be able to bring up menus using the Force Touch gesture.
However, they are not scrollable so they can't be used too heavily.
See also: