Join Simon Allardice for an in-depth discussion in this video What to expect from this course, part of Developing for Apple Watch First Look.
- View Offline
- we can build Apple Watch applications using either Swift or Objective C, and I'm going to use Swift here. So you should be comfortable with at least the basics of Swift and of iOS development. If that's not true for you, take a look at the iOS App Development with Swift course. And iOS dev skills are essential, but if you make the mistake of thinking that developing for Apple Watch is just like developing for a tiny iPhone that sits on your wrist, you're in for a world of pain. It is different. It's not that you need a new set of skills, you don't.
It's still Xcode, it's still Swift, or Objective C. We use a lot of the familiar classes and functionality we already know. It's more than taking your iOS skills over to Watch development. It's kind of, like, learning to drive, but then going to a country where they drive on the other side of the road. You will use all the same skills, but you need to click over into a different way of thinking. And quicky. Now, we need a different mindset, this is about building super quick interactions, with a minimal interface, and often, minimal code.
Watch apps aren't apps you interact with for minutes, but for seconds, and that takes a different kind of thinking. Now, this course is called Developing for Apple Watch First Look. To be clear, this is no overview, we're going to get hands on into Xcode, up and running, with Watch development as quickly as possible, every major component of it. We've called it a first look course simply because we do know things are going to change. I'm recording this in April 2015, just as the watch is going on sale, and I'm recording with the latest versions of Xcode and Swift that I can get.
Xcode 6.4 and Swift 1.2, but we already know that as we get later into 2015, and into 2016 and beyond, what we can do in Watch development will expand from what we can do right now. But with this first release of Watch kit, we are not being given full access to the device. We have some significant limitations. Many of those limitations exist to make sure we're not writing demanding apps, that drain the battery. But most of the limitations are there to make sure we start thinking about Watch development differently from iPhone.
So understand that when I talk about capabilities, the things we can and can't do in our apps, on the Watch, there is a sentence I could say in this course, that you would get very tired of hearing, which is, that's true today, it may change in the future. One example. Right now, as a third party app developer, there is no code I could write to get access to the heart rate monitor functionality on the Watch. That's true today, it may change in the future.
Okay, I don't want to say that a hundred more times, so imagine a bunch more of those sentences and just scatter them wherever you like throughout this course. This is Apple development, this is a brand new device, things will change. We need to expect that and roll with it. So keep an eye on the FAQ, on the course webpage, we will add any important information there. And we will also update the course and release new content as it becomes available.
- Core concepts and architecture
- Creating a user interface for Apple Watch
- Handling scrollable content
- Creating menus, buttons, and groups
- Using control and lifecycle events
- Creating and populating Apple Watch tables
- Building glances and notifications