7 ms·
WatchKit
- apike 12y agoParticularly interesting are the Human Interface Guidelines for Apple Watch: https://developer.apple.com/library/prerelease/ios/documentation/UserExperience/Conceptual/WatchHumanInterfaceGuidelines/index.html https://developer.apple.com/library/prerelease/ios/documenta... They feature various previously unknown details about the watch, for example that the two sizes have different display resolutions, 340px and 390px respectively.
- thomasfl 12y agoIt's particularly interesting to see which UI elements has made it to the small screen of the apple watch. Not much else than switches, buttons and sliders are featured in the guidelines. Looking forward to see what developers eventually will come up with for these devices.
- deleted 12y ago[deleted]
- deleted 12y ago[deleted]
- deleted 12y ago[deleted]
- sunnynagra 12y agoAnyone have a link to available APIs?
- ryanburk 12y agoyou can start here, but you might need to be a registered dev to get to the content: https://developer.apple.com/library/prerelease/ios/documentation/General/Conceptual/WatchKitProgrammingGuide/index.html https://developer.apple.com/library/prerelease/ios/documenta...
- sunnynagra 12y agoThanks! I am a dev, but was mainly curious if they were opening up the heart rate sensor to apps directly or if we would have to go through HealthKit.
- scald 12y agoIt looks like mostly interface related things, for now. https://developer.apple.com/library/prerelease/ios/documentation/WatchKit/Reference/WatchKit_framework/index.html https://developer.apple.com/library/prerelease/ios/documenta...
- my3681 12y agoIf you log into the developer center, there is an iOS 8.2 beta available with a new version of Xcode and WatchKit.
- yohann305 12y agoI downloaded it, there is no option to create such a project in the xcode 6.2 beta, as of 1pm EST (Nov.18) Edit: You cannot create an Apple Watch project. You create a standard iOS project, then add the Apple Watch storyboard/methods
- pavlov 12y agoBased on the typography guidelines, the DIN-like font used on the Apple Watch is named "San Francisco": https://developer.apple.com/library/prerelease/ios/documentation/UserExperience/Conceptual/WatchHumanInterfaceGuidelines/ColorandTypography.html#//apple_ref/doc/uid/TP40014992-CH9-SW1 https://developer.apple.com/library/prerelease/ios/documenta... Here's hoping it will replace Helvetica on iDevices and Macs as well...
- Osmium 12y agoIt's included in their resource pack if you want to try it out :) along with a punch of .psd templates.
- Someone 12y agoSan Francisco? That font is over 30 years old (http://en.m.wikipedia.org/wiki/San_Francisco_(typeface) http://en.m.wikipedia.org/wiki/San_Francisco_(typeface))
- FreakyT 12y agoIf only they had gone with the "classic" San Francisco font you linked -- the Watch's whimsical level would be off the charts!
- mturmon 12y agoIt's a graphical illustration of the San Francisco of Armistead Maupin vs. that of Jony Ive.
- Someone 12y agoUpdate: wikipedia no longer has http://en.m.wikipedia.org/wiki/San_Francisco_(typeface) http://en.m.wikipedia.org/wiki/San_Francisco_(typeface), but now has http://en.m.wikipedia.org/wiki/San_Francisco_(1984_typeface) http://en.m.wikipedia.org/wiki/San_Francisco_(1984_typeface) and http://en.m.wikipedia.org/wiki/San_Francisco_(2014_typeface) http://en.m.wikipedia.org/wiki/San_Francisco_(2014_typeface)
- 12y ago
- k-mcgrady 12y agoYay! This will keep me busy next weekend I'm sure. Quickly glanced through the catalog of objects available and it doesn't seem to be borrowing UI from iPhone the way iPad did. Some similar UI elements but judging by the names they are different implementations and not just differently scaled/laid out.
- dang 12y agoAlso https://news.ycombinator.com/item?id=8625526 https://news.ycombinator.com/item?id=8625526.
- nawitus 12y ago>Apple Watch represents a new chapter in the relationship people have with technology. Not really.
- jmduke 12y agoAn interesting tidbit from the HIG (https://developer.apple.com/library/prerelease/ios/documentation/UserExperience/Conceptual/WatchHumanInterfaceGuidelines/Animation.html#//apple_ref/doc/uid/TP40014992-CH7-SW1 https://developer.apple.com/library/prerelease/ios/documenta...): Create prerendered animations using a sequence of static images. Store canned animations in your Watch app bundle so that they can be presented quickly to the user. Canned animations also let you deliver high frame rates and smoother animations. Creating animations dynamically from your WatchKit extension and transferring them to Apple Watch adds a delay before playback can begin. This is not a good sign as to the power of the watch, unless I'm drastically misinterpreting things.
- RKearney 12y agoThis is referring to the delay in the transmission between your phone and the watch. By storing the static, pre rendered animations on the watch itself, they're ready to play immediately. By rendering them on your phone (where the WatchKit extension lives) and then transferring the view over bluetooth low energy links to the watch to display them would add a delay.
- fla 12y agoThe main problem is the battery life. All this seems to indicate that the device is deisgned to maximize it. A matter of trade-offs, really.
- c1sc0 12y agoI also found this interesting: "(Dates & Timers) ... Does not need to be updated by your WatchKit extension". Makes me think of timer coalescing in OSX. Now they're just sidestepping the whole issue altogether.
- potatolicious 12y agoNot necessarily timer coalescing and probably more of a radio optimization. All 3rd party code will run on the phone and not the watch, so any updates to the UI made via code will have to necessarily travel over Bluetooth. Apple wants to limit the frequency of these updates, so the most frequently updated UI bits (clocks, timers) will be done on the device itself without the persistent BT use.
- rmcpherson 12y agoAre they allowing access to the sensor data from the watch? I'm particularly interested in heart rate. A brief scan of the documentation didn't show anything obvious.
- Taek 12y agoI'm happy to see new products and a competitive landscape but frustrated to see Apple (and others) using different development processes. It's already painful to write apps that work on all 3 major mobile OSes, but now watch app developers have a huge set of watches they need to develop for too. Frustratating to see products each trying to compete using their own closed ecosystem, because it hurts developers and it hurts innovation.
- jlian 12y agoI understand your frustration, but I don't think products trying to compete with closed ecosystems hurts innovation. The smartphone race ushered a new era for software development. The new development process made it mandatory (in order to stay competitive) to reconsider your software for the specific hardware, which promoted some very good redesigns and innovation that would not have happened otherwise.
- smackfu 12y agoThe only real way that could have happened is if a third party released a great smartwatch that was independent of the phone platform. Something like Pebble but higher-end. Unfortunately with Android Wear existing, I doubt there is still an opportunity for that.
- drewying 12y agoA quick scan makes it look like you don't have direct access to create your own UI elements, you are stuck to the prebuilt stuff. This definitely is designed to maximize battery life
- wiremine 12y agoYeah, and you can't create UX elements on the fly, they have to be contained in the bundle pushed to the phone. So, less to install/push/change over the phone/watch network connection.
- wiremine 12y agoAm 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/documentation/General/Conceptual/WatchKitProgrammingGuide/DesigningaWatchKitApp.html#//apple_ref/doc/uid/TP40014969-CH3-SW1 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."
- pat2man 12y agoYup, still MVC but the view is the only part running on the watch.
- CodeWithCoffee 12y agoWhat'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/documentation/WatchKit/Reference/WKInterfaceObject_class/index.html#//apple_ref/occ/cl/WKInterfaceObject https://developer.apple.com/library/prerelease/ios/documenta....
- Hopka 12y agoFollowing that link consistently makes my Firefox crash. Anybody else experiencing this?
- orand 12y agoThere are actually 4 different types of Apple Watch apps: 1. Glances 2. Actionable notifications 3. Extension WatchKit apps (extension runs on iPhone, view runs on watch) 4. Fully native apps It appears 1, 2, and 3 will be available for the initial launch, while #4 will be available later next year, probably starting with a beta released at WWDC.
- JoseVigil 12y agohey orand, thanks for the summary. You mentioned #4 will be available later next year, probably starting with a beta released at WWDC. Is Apple actually saying this? If so, can you please share the source? I mean from Apple not macrumors.
- orand 12y agoThey actually said this in their September 9th press release, although most people missed it: http://www.apple.com/pr/library/2014/09/09Apple-Unveils-Apple-Watch-Apples-Most-Personal-Device-Ever.html http://www.apple.com/pr/library/2014/09/09Apple-Unveils-Appl... "With Apple Watch, developers can create WatchKit apps with actionable notifications and Glances that provide timely information. Starting later next year, developers will be able to create fully native apps for Apple Watch." Someone from Apple also essentially reconfirmed this earlier today on the WatchKit developer forum. Edit: here's the source that first tipped me off to this detail hidden away in the press release: http://david-smith.org/blog/2014/11/06/expectations-for-watchkit/ http://david-smith.org/blog/2014/11/06/expectations-for-watc...
- JoseVigil 12y agoAppreciate orand. I wonder what fully app for watch means though. I am intrigued on the touch event support. There is something new called Force Touch.
- billyhoffman 12y agoApple mentioned Force Touch during the unveiling demo, and there is a blurb in their documentation as well: "Force Touch. A small screen can only accommodate so many controls. That’s why Apple Watch introduces an entirely new interaction model: Force Touch. As well as sensing touch, the Retina display also senses force. Force Touch interactions display the context menu (if any) associated with the current screen. Apps use this menu to display actions relevant to the current content." [1] I've heard people compare this to a long press, but its subtlety different. Force touch can bring up a context menu faster, because you don't have to wait to determine if a touch is "long" or not [1]- https://developer.apple.com/library/prerelease/ios/documentation/UserExperience/Conceptual/WatchHumanInterfaceGuidelines/WatchOSAppAnatomy.html https://developer.apple.com/library/prerelease/ios/documenta...
- iamandybarnard 12y agoDo you think we will be able to build custom watch faces at some point?
- DonHopkins 12y ago"Watch this spot!"
- ferpect 12y agoDoesn't look like there is any support for drawing on the fly. You could create the watch face as static image, but I don't see a way of drawing the hands and keeping them moving once a minute. Maybe create a series of static images with the hands, and stream them once a minute from the phone? Anybody have any thoughts?
- alexweber 12y agoSeems like this is the type of thing that might be possible once the "fully native watch app" sdk is released.
- deleted 12y ago[deleted]
- deleted 12y ago[deleted]
- gdubs 12y agoThere's a lot of groaning about the constraints of the platform (battery life, available interface components, etc), but I for one am excited by these constraints. It can be a really fun and interesting challenge to design within constraints, and in this respect the watch reminds me of the early days of mobile computing. Those tiny little battery-limited devices forced one to think differently about what a UI is, compared to the gargantuan desktop computers and their nearly cinematic display resolution.
- hrabago 12y ago> It can be a really fun and interesting challenge to design within constraints It'll be fun as a technical exercise and to satisfy one's intellectual curiosity, but not as much fun once you've identified the workarounds for all the constraints and you're just trying to ship.
- arihant 12y agoI would buy this watch, but I'm completely convinced that Android Wear is more spot-on for the watch UX with their card based user interface. It does have all these features, the glaces, the actionable notification, extension apps, but from UI standpoint it is just a card. Also, the UI on Android Wear is prettier. I'm not sure why Apple is using black ugly buttons that remind me on very first Nokia multimedia color phones.
- BinaryIdiot 12y agoI agree; I think for a wearable to be successful it has to be passive and useful. Apple's watch seems too interactive to me but it does look nice and I think it'll have enough passive features to be good.
- Lorenzo45 12y agoThey say the HIG that the black background is to create the illusion of a bezel-less display, which I guess it does pretty well. Not the best solution but it's not a problem for me.
- threeseed 12y agoI was under the impression it was for battery life. It does use an OLED display and we know black uses less power.
- arihant 12y agoI'm not ranting about the black background. I'm ranting about the buttons and the way they look: https://developer.apple.com/library/prerelease/ios/documentation/UserExperience/Conceptual/WatchHumanInterfaceGuidelines/Art/notification_long_look_shot_2x.png https://developer.apple.com/library/prerelease/ios/documenta... Moreover, there is no way this watch is pulling over 24 hours battery life. They said that they expect you to charge it everyday. In that sense, the power should not be much of an issue as big as the comments here presume. LG G Watch easily lasts 24 hours, and Moto 360 easily goes 16-20 hours. So unless this watch lasts 2 days or more, screwing up the UI makes little sense, you'd be charging it every night anyway.
- 12y ago
- gajeam 12y agoLooked like there were a lot of motion detectors on the Apple Watch. Any guesses on whether they'll expose that in the SDK soon?
- seivan 12y agoYou can cache images on the watch using WKInterfaceDevice.currentDevice() but there is no way to check if an image has been cached, lol. Can store up to 20 mb.
- RamaCat 12y agoI think they've gone about this the wrong way, architecturally. I would have streamed draw commands to the watch and received touch events back, with the watch hardware essentially being a display client with no compute power of it's own. That would cut silicon real estate, remove the need for local wifi, etc - and placed the development focus on a super low latency wireless command stream. That way, the watch, as a product, would last much longer between upgrades, and your UI complexity would be bound by the host phone, not the little SoC.
- acqq 12y agoSee wiremine's post here: "The Watch app resides on the user’s Apple Watch and contains only storyboard and resource files; it does not contain any code. "
- RamaCat 12y agoWith regards to the WatchKit apps - I'm sure I read they were static resources - essentially a GUI library that can run on the watch. That's subtly different to being able to render any command in a draw stream, say, from CoreAnimation. The former gives a storyboarded GUI from a resource set (sliders, buttons, etc), with static animated images (!), the latter is more flexible and I think would be less resource intensive watch-side (render display commands vs local GUI library) If you wanted to go super-minimal, you could even probably stream a compressed bitmap to a screen that resolution over a wireless protocol, moving all rendering phone-side. There's also still the issue of the native watch apps coming in 2015.
- archagon 12y agoThis would introduce lag in user interactions, which is unacceptable to Apple and its users.
- comex 12y agoIt would also make it impossible to untether the watch from the phone in future revisions, which seems likely to be the plan for the longer term, once technology improves enough to allow adding cellular connectivity without unacceptable size and battery life compromises. Here's someone's take on it: http://stratechery.com/2014/now-apple-watch/ http://stratechery.com/2014/now-apple-watch/