Choosing to develop for the Apple Watch

, ,
Productivity is never an accident. It is always the result of a commitment to excellence, intelligent planning, and focused effort.
Productivity is never an accident. It is always the result of a commitment to excellence, intelligent planning, and focused effort.

I’m a recent convert to developing in Swift for the iOS devices.

I got my Apple Watch when it was still mirroring Apps on the iPhone. The Watch basically being a display with the WatchKit Extension running on the iPhone and sending over it’s data to the WatchKit App on the wearable.

watchOS 3 changed a lot of things on the device and it was about that time that I started to renew my interest in trying to develop for the iPhone.

I came across a course on Udemy which was an introduction to developing for the Apple Watch. It was a great course and really opened up my thinking around the device. However, the more I tried to develop the ideas into my own Apps the more I started to realise that I really did need a stronger understanding of the whole developing for iOS way of thinking.

That’s when I came across the Devslopes iOS course. From Beginner to Paid Developer.

This course was great. Mark is a very infectious teacher. You definitely get enthused by his way of teaching.

I had a bit of an issue really getting my teeth into development further as things has started to change from iOS 9 to iOS 10 and from Swift 2 to 3.0. Little did I know that as a budding Swift developer I would find the changes between to the two versions of the language such a stumbling block. Often when I piece of code wasn’t behaving as I expected I would google for an answer to presented with answers for a differing version of Swift.

It is great being able to make this wearable mini computer on my wrist react to my instructions.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.