Scott Berrevoets

@UIApplicationMain was deprecated a while back and replaced with @main.

In larger teams or companies, most people agree that the mobile platform is the shared infrastructure an app and its features are built upon.

By default, Liquid Glass is enabled for apps that are built with Xcode 26.

Snapshot tests have become an increasingly popular tool for mobile teams to verify UI changes, but one question all teams run into is: where do we store hundreds if not thousands of PNG files?

Software whose author has big ideas they want to implement before committing to a Semantic Versioning (or SemVer) versioning methodology often starts with many 0.x releases before ever reaching a 1.0 version.

While looking at AVAudioSessionErrorCode in Xcode, I noticed something interesting in its definition: typedef CF_ENUM(AVAudioInteger, AVAudioSessionErrorCode) { AVAudioSessionErrorCodeNone = 0, AVAudioSessionErrorCodeMediaServicesFailed = 'msrv',

After the introduction of Optional.toggle() back in 2018, I thought I had learned everything there is to Optional, but today I learned about another method: Optional.take().

Years ago, when we started to have 5+ contributors to our codebase at Lyft, we had to establish a code review process with high enough value to justify the friction it caused.

Typically, markdown files can referenced other files by linking to them: [My File](myfile.md).

Having to type out my password every time in SSH into a machine got a little tedious for me.

Back in 2017, I wrote about how we used Interface Builder as our primary way of building UI at Lyft.

After I started to ramp up on agentic coding, I found my workflow lagging behind how I ended up working.

Today I created a new file at .

They're called numeronyms and they're common terms in tech to refer to long words like "internationalization" (i18n) and accessibility (a11y).

A few weeks ago we got bit by a piece of Apple magic in its localization workflow when combined with Swift PM.

A great manager I once worked with had been at Google for a while and poked fun at an aspect of its engineering culture: any given service was either deprecated or not yet ready for adoption.

Tech debt is often compared to financial debt, in that you're borrowing development time now to pay it off with more development time later.

@State plays a prominent role in any SwiftUI app, and for good reason: app state is what ultimately drives the UI and how the user interacts with your app.

I recently updated my resume, and after a few iterations of tweaking the same Pages file I started more than a decade ago, I decided that I really wanted source control to make it easier to keep track of changes and to have different versions of the same…

I wrote my first app, a map to navigate my college campus, in the winter of 2011, on iOS 4.x and with Xcode 4.x.

When writing code in neovim, I frequently use K to look up documentation, function signatures, variable definitions, etc.

Note This is the third post in a series on shifting our testing culture.

Note This is the second post in a series on shifting our testing culture.

Five years ago I began promoting automated testing heavily within Lyft even though I didn't have any real experience in writing big test suites myself.

Code migrations are a fact of life for large codebases.

I recently saw a thread where someone wanted to introduce a more capable architecture pattern than what most apps start out with in a small team, but received some pushback from teammates and was looking for help in countering their arguments.

What better way to end the week than with a hot take?

June 30, 2014 was my first day at Lyft as the first iOS hire on the ~3 person team.

Update 07-29-2019: The bug described below is fixed in Xcode 11 so this blog post has become irrelevant.

Last week people realized that Xcode 8.3 by default uses storyboards in new projects without a checkbox to turn this off.

Note This article was written by me but originally published on the Lyft Engineering Blog.

When your app has a lot of third-party dependencies, what often happens is that those libraries log a bunch of things to the Xcode console to help their own debugging.

There are a lot of styles out there when it comes to using Interface Builder outlets in Swift.

Back in December I wrote about what I thought was a bug in the Swift compiler that would expose the wrong class name for a Swift class in Objective-C.

I was in the audience for "Implementing UI Designs in Interface Builder" at WWDC, where Apple touted UIStackView as a new, better way to lay out your views that in a lot of cases didn't require Auto Layout.

A few months ago, I decided I'd get started porting SDCAlertView to Swift, but I was only a few minutes in until I ran into a problem I had no idea how to solve: I couldn't get my class names right in both Swift and Objective-C.

With today's release of iOS 8.1, most app developers are looking at 4 significantly different iOS versions they will be supporting: iOS 7.0, iOS 7.1, iOS 8.0, and iOS 8.1.

The responder chain is a very important paradigm in the world of iOS development, and not terribly hard to understand.

Any developer that has worked with Xcode to write a little more than just "Hello, World" knows that Xcode and Objective-C have their quirks.

This past week, there was, again, a lot to do about Objective-C and prefixing.