Independent watchOS: principles and practices
For a very long time, Apple Watch was considered to be a device for either people dealing with too many notifications, or a smart remote for the Music app, or a health-centred tracker. Lack of UI components, a terrible way to compose animations, and a strong dependency on an iPhone being present didn't help as well.
However, with the most recent announcements from Apple, everything might finally change. In this talk I will walk you through the best practices and principles behind designing and developing offline-first and independent watchOS apps, as well as briefly touch a few ideas on Watch App Store search optimization and basic approaches to reduce users' pain when dealing with wearable devices.
Similar Talks
Modern devices are way more powerful for users to notice a difference between bubble sort and merge sort. Or not? Should everyone know how to implement Ukkonen's algorithm if they develop a weather app? What's the "Big O" of your average app and how to determine it?
The second part of a thorough introduction into iOS Security, from various pentesting techniques, to possible flaws to use-cases and tools.
Debunked the "iOS is secure by default" myth in 90 minutes. Walked through real pentesting techniques, tools, and war stories from the security trenches.
What teaching iOS at a Russian university taught me about learning. Turns out developers and nomads have more in common than you'd think โ we both carry only what we need.