Daniel Gauthier

You’re telling me this person has written several books, hosts 3 podcasts, organizes community meet-ups, regularly speaks at conferences, has sold two companies, has won an Apple Design Award, is politically active, volunteers at a shelter twice a week, is an ultra distance runner, has 4 kids and is really into sourdough, while I…play a lot of video games, I guess?

If I’m building a simple presentation that slides in from the bottom, I certainly don’t want every view controller that uses it to be locked to one specific size — the size should depend on the content! — and I also don’t want to have to think too hard about setting the size appropriately every time I use my custom transition with a new view controller.

Making interactions feel "natural" is a bit of a subjective thing, but for me, there were a few details I knew I wanted to get right when it came to dismissing my view controllers interactively.

Let’s be real: all technical debt seeps into the user experience eventually! So, let’s figure out how to make sure our custom transitions are easy to use and reuse.

Well, in the name of lofty design ideals, I decided that custom view controller transitions ARE the “fun stuff”, damn it, and I hunkered down and endeavoured to truly, totally, finally wrap my head around this whole clustercuss of classes and protocols.

If you google “core interaction loop”, you’ll see…nothing, really, because it turns out I may have accidentally made it up. Let’s talk about it anyways!