Hey Brian, the pan gesture bug that you mostly eliminated is still present when the app launches.

If one uses Refactor / Extract Method, Xcode tries to put in the correct argument list, e.g., fileprivate func handlePanGestureEnded(_ translation: CGPoint, _ velocity: CGPoint). Very handy.

Hi Brian - another great video. Regarding debugging the layout constraints, do you ever use the console suggestion to 'Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger'? Useful or not for this type of situation?

Hey Brian, Thanks for the videos, I have a question, how would you go about refactoring the Player out of the View file? Could we create a separate file for the Player and then use it, the problem for me is understanding how to setup those observables for the timing features once we refractor the player out.

Hey Brian, I found and fixed a minor visual bug. You can cause the bug by dragging the miniPlayerView up past "200" pixels. Doing so will cause the miniPlayerView to briefly flicker back into sight. Based on my fix, I believe it has to do with a very large translation assigning a negative alpha value. Anyways, here's the code that should be changed: replace: self.miniPlayerView.alpha = 1 + (translation.y / 200) with: let newAlpha = 1 + translation.y / 200 self.miniPlayerView.alpha = newAlpha < 0 ? 0 : newAlpha

Hi Brian In 04:23 Why you put the code of "maximize player" in the animation code of "minimize player"? And it still works perfectly?