在大规模的iOS应用中为生产力而设计

How innovation in technology and people processes have enabled iOS developers to remain productive in a large codebase.

技术和人员流程的创新如何使iOS开发人员在大型代码库中保持生产力。

Every iOS engineer remembers the joy of seeing their first application running on an iOS device. The human-centric interface of the iPhone brings the program to life. When you choose iOS development as a career, that joy grows as your application touches more people’s lives.

每个iOS工程师都记得看到自己的第一个应用程序在iOS设备上运行时的喜悦。iPhone以人为本的界面将程序带入生活。当你选择iOS开发作为职业时，这种喜悦会随着你的应用程序接触到更多人的生活而增长。

Affecting more users often involves new iOS features, flows, and functionality. But as an application grows to serve more users, new features and functionality can introduce additional weight and complexity, which slows product iteration and precludes atomic refactors.

影响更多的用户往往涉及新的iOS特性、流程和功能。但是，随着应用程序的发展，为更多的用户提供服务，新的特性和功能会带来额外的重量和复杂性，这将减缓产品的迭代，并排除原子重构的可能性。

We have undergone this journey as an iOS team at Airbnb. There is a profound joy knowing that the code we ship every week enables unforgettable vacations for guests and new revenue streams for host entrepreneurs. A focus on design is in our DNA and we take immense pride in perfecting every detail of what we show to our users. At the same time we have not been immune to the challenges of developing at scale.

作为Airbnb的一个iOS团队，我们经历了这个旅程。知道我们每周发送的代码为客人带来了难忘的假期，为房东企业家带来了新的收入来源，这是一种深深的喜悦。注重设计是我们的DNA，我们为完善我们展示给用户的每一个细节而感到无比自豪。同时，我们也不能幸免于大规模开发的挑战。

In this article, we will walk through difficulties that we have encountered in accommodating the growing business needs of Airbnb. We will outline how investments in technology, ownership, and processes have allowed the Airbnb iOS team to have the best of both worlds: working in a globally impactful codebase without feeling its weight.

在这篇文章中，我们将走访我们在适应Airbnb不断增长的业务需求中遇到的困难。我们将概述在技术、所有权和流程方面的投资如何使Airbnb的iOS团队获得两全其美的效果：在一个具有全球影响力的代码库中工作而不感到它的重量。

Challenges of developing a large-scale iOS app

开发大规模iOS应用的挑战

An Airbnb intern made the first commit to our iOS application on June 16th, 2010. Since then, that sam...