Clips, developed by Clean Shaven Apps, is an app I use on a daily basis to copy multiple bits of text and move them between apps using a widget, an action extension, and a fantastic custom keyboard – one of the few keyboards I keep on my devices, in fact. I reviewed the app when it came out last September, and I’ve been using it since.

Today, Clips 1.2 has been released with a refreshed design, Apple Watch support, and a faster keyboard. While I’m not sure why I’d want to use Clips on my Watch, I believe it can be useful to those who use the app to store text they access frequently and not as a temporary holding place for clipped items. I’m a fan of the new dark design and the increased contrast between URLs and plain text, and I continue to appreciate the time the app saves me when composing articles, researching topics, and collecting a bunch of notes from different apps with just a few taps. Clips is the epitome of iOS 8’s extensibility features for productivity apps, and it’s one of my must-have utilities.

Clips 1.2 is available on the App Store.

July Clover, reporting for MacRumors on Apple’s Jeff Williams’ appearance at the Code conference earlier today:

On the topic of Apple Watch apps, Williams says third-party apps will get better when developers are able to release native apps and when access to native sensors is permitted. He gave an example of what a native Apple Watch app might do, suggesting an app like Strava will be more full featured as it would have direct access to sensors.

The native Apple Watch app SDK will be previewed at WWDC, according to Williams, suggesting full featured Apple Watch apps that can access health sensors, the Digital Crown, and more, will be available when iOS 9 is released to the public in the fall.

As assumed by many, the Watch SDK will give developers access to sensors. After trying the Watch for the past two weeks, it’s obvious that the only useful fitness app for me is Apple’s Workout because it’s the only one to use the heart rate sensor.

Eight years from now, I wonder if we’ll remember WatchKit as a very sweet solution, too.

(I love Steve’s comment on the “really complex update process”. It didn’t turn out to be that complex after all.)

Watch mode is where you take quick glances at information and notifications; app mode is where you go to “do something”. Watch mode is where most people will spend the majority — perhaps the overwhelming majority — of their time using Apple Watch. App mode is a simple one-level hierarchy for “everything else”.

John Gruber has a good analysis of the Apple Watch interaction model and the differences between the watch face and the app screen.

I’ve been reading a lot of comments on the Watch OS hierarchy and I’ve (obviously) been using my Apple Watch as much as possible for a variety of tasks and scenarios.

The more I read and try, the more I don’t understand the criticism of those who claim Apple Watch should work like an iPhone. Yes, the multiple functions of the Digital Crown can be confusing initially, and I imagine that eventually there will be settings to customize what the side button does. But to argue that clicking the Digital Crown should always go back to the watch face seems shortsighted to me. There’s a benefit in having an easy way to open/go back to the app screen to quickly do stuff with apps, and it will be even more obvious once a native SDK and faster apps become available.

Ben Thompson, writing about Apple Watch and Siri:

Moreover, the Watch may even help Apple to rival Google when it comes to Siri and the cloud: the best way to improve a service like Siri is to have millions of customers using it constantly, and I for one have used Siri more in the last two weeks than I have the last two years. Multiply that by millions of Watch users and you have the ingredients for a rapidly improving service. Perhaps more importantly, the fact that Siri is critical to the Watch’s success in a way it isn’t to the iPhone’s may finally properly align Apple’s incentives around improving its cloud services.

Apple has been improving Siri both in terms of speech recognition and load times considerably over the past two years (they’re now at the third generation of Siri). I’m finding the wrist to be a better activation point for Siri – raising your wrist to talk to a watch like a spy somewhat feels more natural than staring at a phone and speaking into it (although that may come down to cultural heritage and personal taste).

As I wrote in my iOS 9 wishes, faster interactions with all Watch apps (Apple and third-party ones) could be possible with a Siri API. I’m curious to see how Apple Watch will shape Siri’s future.