Day 1:
One thing you can do to make your iOS app better today 📱

1️⃣ Activate Voice Over
2️⃣ Now, turn on screen curtain (3 finger triple tap)
3️⃣ Try to navigate your app and look for places to improve VoiceOver navigation 🍻Day 2🍻

1️⃣ Hitting performance issues and not sure where to start?
2️⃣ Use os_signpost and .pointsOfInterest category to help benchmark your code
3️⃣ Then, use instruments to dial in on what the problems might be or where to start tuning your code

💡Tip 11 💡

Many users invert iOS' colors to help with light & color sensitivities. But, ensure you aren't degrading rich media in your app, which users likely expect to remain at their true fidelity.

For images & media, you'll likely want them to forgo this setting. 💡Tip 11 Continued 💡

This requires almost zero effort to support - simply set accessibilityIgnoresInvertColors to false (which also will do the same thing for subviews of that view):

🎨 iOS Design and UX Tips 🎨

I’ll be extrapolating out things I’ve learned, read from the HIG and have seen that make an iOS app look and feel good.

Tip 1) Make a table view row animate its selection state as it’s popping and pushing on the nav Stack. Tip 1 Continued:

UITableViewControllers get this behavior for free. If you roll your own table view you’ll need to do it yourself. You can do so by grabbing the controller’s transition coordinator as seen in this (gasp!) Objective-C code here called in viewWillAppear 💫

For the past 2+ years I’ve been building my side project using #CloudKit and I’d love to share what I’ve learned.

There isn’t a ton of info out there on it, and I’ve got some tips that I’m not sure I’ll get around to blogging about so I’ll add them here in a thread 👇 First off - subscriptions. There are three main types:
CKDatabaseSubscription
CKRecordZoneSubscription
CKQuerySubscription

Unless you’re *only* using the default zone, you should start with CKDatabaseSubscription.

A fun bit of #macOS development history I stumbled upon today, Apple Tech Note 2034.

Essentially it included a bunch of guidelines and tips on macOS development but contained such inflammatory assertions that Apple straight up *pulled* it down (2033/5 are still there)! Among some of the the things that didn't sit very well with devs in the note:

- Positing Objective-C as being a more portable cross-platform language than C++
- Promoting hard-coded pathname APIs for accessing files over traditional Mac APIs