I’m happy to announce that Developing for Apple Watch, Second Edition is now out of beta! You can order the eBook version and receive it nearly-instantly, order a paper edition, or order both and get the eBook now and the paper edition in the mail. And of course, it’s available on Amazon if you prefer to buy it there (but if you want to support me and the Pragmatic Bookshelf, buy it direct!).
One of the more interesting things I did for this book was to create a promotional video for it. With some guidance by Chris Adamson, I used Motion to stitch together some music, the cover image of the book, and some screen captures to bring the book to life in a more visual format. It’s on YouTube, so I guess this is where I say, “Be sure to like and subscribe!”
After a long time of writing, my second book has been published! Developing for Apple Watch is now available from the Pragmatic Bookshelf in both paper and eBook formats! This is a “Pragmatic exPress” book, meaning it’s a shorter look at a specific technology. It’s also available on Amazon if you’d prefer it that way.
The book introduces WatchKit, Apple’s technology for making Apple Watch apps. With 100% of its code in Swift, you’ll be ready to go with the latest Apple technology. Get it now and get a head start on making watch apps before WWDC!
Today was MobiDevDay in Detroit, and it was a heck of a good conference (and I’m not just saying that because Detroit Labs helped put it on). The slides from my presentation are on Speaker Deck, and you can see AmazeKit on GitHub or view its documentation. Enjoy!
Yesterday I gave a talk on concurrency in OS X and iOS at CocoaConf Columbus. As promised, here are the slides and code:
Take Me Home is an ancient, buggy iPhone app that was my “Hello, World!” in the App Store. Its sale rate has plummeted to only a couple of buyers a week and, with the prevalence of real, honest-to-God GPS apps in the store these days, its usefulness is questionable. So from here on out, it’s free. I can’t promise to continue supporting it—especially for new devices and APIs—so the best I can do may be to remove it from the store in the event that some update breaks it.