Tag: dependencies

Software Dev

Scaling up: how AirBnB ships a quality, gigantic app

patmcgLeave a comment

AirBnB’s iPhone app has a gigantic code base (1.5 million lines of first-party code), a giant mobile team (75 iOS engineers), and a long history (first commit: 2010).

Over time, their app got so big and complex that the project began to take minutes to open (not build) in Xcode. Developers had to use the USB port on the right side of their MacBooks to avoid thermal throttling. 🤦🏻‍♂️

Given all this sheer complexity, the team there made some clever adjustments to develop, test, and ship their app pretty efficiently. Check it out.

👉 Designing for Productivity in a Large-Scale iOS Application

Among the highlights are independent modules called Dev Apps.

A Dev App allows a product developer to iterate on their feature’s UI and much of its business logic while building a fraction of the overall Airbnb application.

Dev App for an existing Airbnb module

For dependencies across modules, module types allow for “visibility rules” to minimize and document dependencies.

Also, AirBnB uses the Buck build system to keep Xcode projects out of source control (bye bye, Xcode project merge conflicts).

via iOS Dev Weekly.

Software Dev

What Adding Dependencies Will Do To Your App in 2020

patmcg1 Comment

I like the title of this article because it recognizes that pulling third-party dependencies into your app has a cost.

👉 What Adding Dependencies Will Do To Your App in 2020

And yet we all do it because it also has its benefits. 🤦🏻‍♂️😂

That article is a realistic and practical look how the dependencies affect your app in terms of app launch times, app size, and build times. It compares Swift Package Manager 🤓, Carthage 🤷🏻‍♂️, CocoaPods 😬, manual dependency management 🥺, and Git Submodules 🤮.

I still have a dream of zero dependencies 🤩, but I know it’s not realistic in a complex app. 😑

Via iOS Dev Weekly.

Software Dev

Playbook

patmcgLeave a comment

Developing features for a large, established app, I often run get slowed down trying to throw together a new screen. You have to find the right spot in the code to update, build the whole app (not just what you changed), log in, and drill down to the right spot to try out your creation. Something’s off? Do it all over again.

Which is why I love the idea of the Playbook library, which is “a library that provides a sandbox for building UI components without having to worry about application-specific dependencies.” Yass! 🤟

👉 Playbook on GitHub

Supports both SwiftUI and UIKit.

playbook

Via iOS Dev Weekly.