I finished the SwiftUI Animations Mastery chapter on the Matched Geometry Effect. 🎉
Whew! It was a long 3-month journey through many problems, bug reports, much testing, and a lot of experimentation, blood, sweat, and tears. If you have even tried to use matchedGeometryEffect to any extent you will know exactly what I'm talking about.
This new chapter doesn't just teach ideal circumstances, it will show you all the pitfalls, traps, and potential mistakes you're going to make along the way with all of the solutions for them as well.
The book is now uploaded to my site. If you already own the book, go download the update and take a look. It's available now!
143 New Pages
That's more than a 25% increase in the book. Man, what a journey.
The amount of work for this one chapter was almost equal to the rest of the book.
The matched geometry effect is pretty cool. It's powerful. But it can be incredibly confusing so I hope I can help you out and clear up how it works.
I'm going to walk you through the basics. You can actually use this modifier with no animation at all.
In order to do that I included many common scenarios as possible.
I'll show you how to use matched geometry effect on:
But I know many devs will want to know how to apply the matched geometry effect from some kind of list/stack/grid. So I included these scenarios as well:
- Opening a view from a List
- Opening a view from a LazyVStack
- Opening a view from a LazyHStack
- Opening a view from a LazyVGrid
- Opening a view from a VStack
- Opening a view from an HStack
Common and Not-So-Common Problems
I also included all the problems one might run into when using the matched geometry effect and as many solutions as I could find. Some problems with matched geometry effect include:
- Corner radius
- Clip shape
- Animation race conditions
- With the NavigationView
Exercise & Challenge
And like all my chapters, there's a fun exercise at the end where you build out a couple of views with multiple matched geometry effects.
Don't forget the challenge!(Don't worry, if you get stuck then you can find the code in the companion Xcode project that comes with the book.)
This chapter has more writing than I normally do because there is so much to explain.
So when you go through this chapter, I recommend going through it linearly, from start to finish
. If you skip around, you might miss some vital information.
I wish you the best of luck with your animations.
Need a little incentive? Well, here's 20% OFF
if you buy it this week.
Your SwiftUI friend,
Mark MoeykensBig Mountain Studio
PS: I'm ALWAYS interested in your creations, large or small. Post your creations on Twitter and tag me with @BigMtnStudio