According to the docs and some tests I just ran, interface objects in watchOS 2.0 are still write-only. I'm wondering what the reasoning behind this is now the code excutes on the watch, and therefore there's no longer a round trip to the phone. WatchKit developers have traditionally had to keep track of UI state manually due to this restriction imposed by the old architecture, but now the architecture has changed it seems a little strange to keep those restrictions in place. Could someone from Apple please comment on this?
Also, it also seems a little strange that new watch app projects in Xcode still have seperate groups and targets for the interface and the code. Is this likely to change in a future beta?