News for hackers. Stuff that matters.
Re:WatchKit by wiremine on Tuesday November 18, 2014 @03:19PM (#8626072)
Am I groking this right? The Watchkit app actually runs on the iPhone as an extension, and just the UI component runs on the watch hardware?

Edit: better direct link: https://developer.apple.com/library/prerelease/ios/documenta...

"The Watch app resides on the user’s Apple Watch and contains only storyboard and resource files; it does not contain any code. The WatchKit extension resides on the user’s iPhone (inside your containing iOS app) and contains the code and resource files for managing your Watch app’s interface."

Re:WatchKit by 0x0 on Tuesday November 18, 2014 @03:34PM (#8626163)
It's been said that an updated SDK with support for "native apps" (maybe that also means untethered?) will be released some time in 2015. http://www.macrumors.com/2014/11/18/apple-watchkit-ios-8-2/

This first version is probably just a very early beginning of how the runtime will evolve, to put something out there before launch.

Re:WatchKit by c1sc0 on Tuesday November 18, 2014 @04:34PM (#8626495)
This has been confirmed by Apple
Re:WatchKit by TazeTSchnitzel on Tuesday November 18, 2014 @10:22PM (#8628045)
Reminds me of how the original iPhone only supported web apps, and they later came out with a full SDK.
Re:WatchKit by CodeWithCoffee on Tuesday November 18, 2014 @03:26PM (#8626105)
What's more, you can't get the current properties of the interface objects (e.g. the position on screen, or text content). You can only write to them: https://developer.apple.com/library/prerelease/ios/documenta....
Re:WatchKit by 0942v8653 on Tuesday November 18, 2014 @04:15PM (#8626401)
Wait, then how do you get user input at all? Just buttons? That sounds like a pain.
Re:WatchKit by c1sc0 on Tuesday November 18, 2014 @04:34PM (#8626500)
There seems to be some kind of dictation-based input
Re:WatchKit by mikeash on Tuesday November 18, 2014 @03:57PM (#8626298)
Does that matter? If you need to know those values, you can just store them locally when you set them.
Re:WatchKit by pat2man on Tuesday November 18, 2014 @03:23PM (#8626088)
Yup, still MVC but the view is the only part running on the watch.
Re:WatchKit by sschueller on Tuesday November 18, 2014 @03:29PM (#8626129)
So if the phone is dead the watch won't even show the time?

Does this setup significant improve battery performance?

Re:WatchKit by potatolicious on Tuesday November 18, 2014 @04:00PM (#8626323)
The watch is independently able to show the time.

It also has built-in time-display capabilities in the SDK to limit the amount of traffic going between watch and phone (i.e., you don't have to manually update a timer or clock display from your own code, the watch does so locally).

Seems like all of this is meant to reduce processing on the watch side, and also to minimize the amount of data moving between watch and phone.

Re:WatchKit by wiremine on Tuesday November 18, 2014 @03:31PM (#8626145)
It looks like there are native Apple apps on the watch: they noted in the intro video that clicking on an image of a map opens up the Apple Watch's "Maps App"
Re:WatchKit by dep_b on Tuesday November 18, 2014 @09:09PM (#8627816)
You can add a map to your own app as well
Re:WatchKit by 1234naskjnaf on Wednesday November 19, 2014 @04:21AM (#8629017)
You can add a non-interactive snapshot of a map.
Re:WatchKit by tolmasky on Tuesday November 18, 2014 @04:03PM (#8626341)
> Does this setup significant improve battery performance?

Not for your phone.