1 min read

Issue #26

Hi there,

Every time I sit down to write an intro to an issue, I struggle between staying positive and the desire to address current events in the outside world. And every time I land on the decision to let this newsletter be a small island on the internet dedicated to learning something new in the field we're passionate about.

If you are affected by war, the pandemic, or any of the other struggles in our crazy world - know that I think of you every time I write this 💛

And thanks to all of you for being loyal readers! Seeing the high open rates and receiving your feedback keeps my heart warm(-er) ☺️

So I hope you find something interesting in today's collection. Let's dive in?


Accessible custom tab bars

.tabBar accessibility trait is almost magical when it comes to making a custom tab bar view behave like a system one.

If you want to learn more about this, Bas Broek wrote a detailed article on implementing accessible custom tab bars:

Building an Accessible Custom Tab Bar | Bas’ Blog

Recently, I’ve been working on making a custom tab bar in our app accessible. That is, make it work just like a native, out-of-the-box UITabBarController.

Interactive image preview transition

This is so cool. I didn't even realize that QuickLook framework can be used on iOS! Check out this short thread by Jordan:

Sink

Building safe APIs

The whole Swift language is built upon safety principles, so it only makes sense to apply them to our own APIs:

NSPersistentCloudKitContainer trickiness

A comprehensive write up about the realities of using Core Data with CloudKit syncing. The article is a few months old, and just now it's been updated with new findings. So if you've seen it before - it's worth checking out again.

General Findings About NSPersistentCloudKitContainer

This article contains our findings when converting Streaks to use NSPersistentCloudKitContainer.

🤘☮️

Alright, that’s it for today.

What do you think about me writing the comment above the tweet or link? Does it work? Or do you think it should be after? I'm curious to hear what you think. Let me know by replying to this email :)

Did you enjoy this issue? Let me know by pressing the buttons below, so I can improve the newsletter 🙌