Nice to see something like CABasicAnimation. Very well explained, and very interesting to work with. There is so much stuff out there hidden somewhere in the huge amount of available classes and objects, that you often forget or just don't know where to begin and what to use in certain situations.

I used a `CAAnimationGroup`. It allows me to set stuff like duration in one place. my code: ``` let groupAnimation: CAAnimationGroup = { let groupAnim = CAAnimationGroup() groupAnim.duration = 0.3 ``` ... ``` groupAnim.animations = [rotAnim, posnAnim, opacityAnim] return groupAnim }() ```

Hi Brain, hope all is well. Can you show us how to slide between pages like how the actual Tinder app does?

great stuff!

Hi Brain , i hope you do well . after playing with the code i have notice when i fetch more data, even i remove the card view and the user, the memory increase badly going to 500 MB , how i can fix such a problem ? .

Hi guys. Very nice animation with CABasicAnim, butter smooth. My question here is do I allow this to happen in the app if it was a real app? the user to tap away maybe without looking at the cards? maybe increasing data fetches and rising firestore costs? Prior to this lesson I've implemented a temporary disable of "like button" only for the 1s duration of animation and I showed that to the user by fading the alpha of the button. Is this a acceptable solution in a real app situation?

Found one more small bug, if tapping 2 times consecutively on "refreshButton" the stack of cards gets loaded twice and the top card wont move, can't be liked or disliked. only the cards underneath the top card will react to like/dislike. I found a solution where handleRegresh works only when topCardView is empty, at the end of the stack, or in my case at the end of paggination which i kept as a feature. @objc fileprivate func handleRefresh() { if topCardView == nil { fetchUsersFromFirestore() } }

Hey Brian! Why do we need to commit() from CATransaction?

Hey, Brian. For some reason my animations go in reverse order - the bottom card from the stack gets of the screen first and so on. Can't figure out why, hope you can help me. Thanks.