UIScrollView与Vimeo的最新播放器屏幕

On Vimeo’s Mobile team, one of our goals is to empower our users with the latest technologies from iOS and Android as well as with an intuitive, easy-to-use user interface. One of many examples that demonstrate this commitment is the latest player screen that we shipped with version 8.6.0 of the Vimeo flagship app. In planning and designing the new screen, we not only parted ways with the user interface that had been serving us well for many years, but we also decided to refactor a major base of legacy code that no longer served Vimeo’s needs moving forward. In other words, the new player in Figure 1 below wasn’t merely re-skinned but rebuilt from the ground up:

在维密欧的移动团队中，我们的目标之一是通过iOS和安卓的最新技术以及直观、易用的用户界面来增强用户的能力。我们在Vimeo旗舰应用8.6.0版本中推出了最新的播放器屏幕，这是体现这一承诺的众多例子之一。在规划和设计新的屏幕时，我们不仅与多年来一直为我们服务的用户界面分道扬镳，而且我们还决定重构一个主要的遗留代码库，这些代码不再满足Vimeo前进的需要。换句话说，下面图1中的新播放器不仅仅是重新换了皮肤，而是从头开始重建的。

Notice in the figure how smooth the transition from one tab to another is compared to the legacy screen. In order to achieve such a smooth user experience, we agreed that the new screen must be architected around UIScrollView. During development, our team had to deal with many technical challenges related to UIScrollView, and at the same time we gained a number of insights in adopting it. In the following sections, we walk you through how we were able to overcome these challenges as well as share some pro tips for incorporating UIScrollView into your apps.

请注意图中，与传统的屏幕相比，从一个标签到另一个标签的过渡是多么的平滑。为了实现如此流畅的用户体验，我们同意新屏幕必须围绕UIScrollView 。在开发过程中，我们的团队不得不处理许多与UIScrollView 有关的技术挑战，同时我们也在采用它的过程中获得了许多启示。在下面的章节中，我们将向你介绍我们是如何克服这些挑战的，并分享一些将UIScrollView 纳入你的应用程序的专业技巧。

Why UIScrollView?

为什么是UIScrollView？

Before diving into our implementation, we want to stress that if you can architect your solution without using UIScrollView, you should definitely consider it. From our experience with UIScrollView in the past as well as with the new player screen, its reputation of being one of the most complicated while powerful UIView subclasses in UIKit is very true. A good p...