This is a fascinating story from McLaren Stanley about a rewrite of the Uber app in the early days of Swift. If you’ve not yet read it, go and give it a look now. I promise it’s worth your time.

It’s easy to forget how rough the first couple of years of Swift development were, and how early adoption had a real cost. That cost might have been manageable in a small app, but this story is a rarely shared insight into what it was like at a big company that decided to go all-in so early.

Rewriting an app when a new technology comes along is so tempting. The idea of being able to remove all those imperfect decisions, and getting a “clean start” is intoxicating. Add the allure of the brand new technology into the mix, and it can be almost impossible to resist. Of course, the path is rarely smooth. New technologies often demo well but also have really spiky edges that hurt when you run into them. You’re also just as likely to make a whole new set of bad decisions as you fix the last set. 😬

We’re fortunate in software development that we’re able to go back and tweak the things we’ve built. We’re able to improve what we already have at the same time as shipping new features. It’s a rare privilege that’s not afforded to many industries. You can’t tweak a novel after it’s been published, or a building after construction is finished.

Yes, it can be hard to make large architectural changes incrementally, but is it harder than making large architectural changes while also adopting a new language like Swift or a UI framework like SwiftUI?

The Swift transition is mostly done by now, and I expect the vast majority of you are now writing most of your new code in Swift. The SwiftUI transition period is still in full swing though, and once that’s done, there’ll surely be another tempting opportunity to rewrite! We’re lucky with technologies like Swift and SwiftUI that Apple pays attention to interoperability, it’s a great deterrent against the lure of the rewrite. 😅

That said, you should also be careful not to fall too far behind. We’re now 18 months into SwiftUI, and if you’ve shipped any part of a real app using it, you’re ahead of the curve. If you’ve not yet had at least a little play with it in a demo/test app, you’re probably on the edge of lagging behind. Like everything in software development, it’s a balance, and there’s no right answer. Just try and avoid being a zealot, or a curmudgeon. Stories like this are also a good reminder that being “pure” anything isn’t something to strive for, in my opinion.

The story McLaren tells worked out in the end, but he also refers to several people burning out. I’m glad they ended up in a good place, but you should treat this as a cautionary tale. It’s not the only time I’ve heard stories like this, and I’ve even participated in one or two over the years, although the scale of mine are much smaller.

Thanks for sharing McLaren!

UPDATE: Several people have messaged/tweeted me since yesterday about this sentence:

If you’ve not yet had at least a little play with it in a demo/test app, you’re probably on the edge of lagging behind.

I should not have said “lagging behind”, and I’m sorry I wrote it. My intention was not to judge or make anyone feel bad, but I did, and I’m sorry. I do think that it’s a good idea to have had a play with SwiftUI in some context, but you’re definitely not lagging behind if you haven’t.

Dave Verwer  




Business and Marketing


iOS Developer @ SpareRoom – Want to work on an app repeatedly featured by Apple? One that’s received tens of thousands of 5-star ratings? Come and join us at SpareRoom, the UK’s best-known flatsharing business. We’re looking for an experienced, passionate developer to lead the development and delivery of our iOS app, at a really exciting time for the team and business. Get in touch! – Manchester UK

iOS Developer @ Doximity – Doximity, the medical network used by over 70% of US clinicians, is hiring passionate iOS engineers (remote friendly!). You'll get to be part of an amazing product team and work on an app that is constantly evolving. Use your skills (Swift, MVVM, FRP) to be an integral part of our newly launched telemedicine feature. Apply today! – Remote within the US, or San Francisco CA

Mid-Level/Senior iOS/tvOS Developer @ Berlin Phil Media GmbH – Join the team working on the Digital Concert Hall of the Berliner Philharmoniker – the leading international video streaming platform for classical music concerts. You will be working on our highly visible iOS and tvOS apps. Development is fully native with fast adoption of the newest Apple technologies. Your contribution will shape a unique global service together with a small but powerful team. – Berlin Germany

iOS Swift & iOS QA Engineer @ Redzone Production Systems – Redzone is looking to hire talented Engineers to join our team. We build a communication and collaboration platform that enables frontline workers to resolve day-to-day production issues themselves before they become problems. (iOS, Swift, Scala, AWS, Kubernetes) – Remote, Miami FL, or Birmingham UK

Senior iOS Engineer @ Branch – Want to build transparent and honest financial services that help working Americans grow? Come join us! – Remote within the US


And finally...

Swipe right if you like the way they indent their code...

I can't let this pass without also linking to Matthew's tweet. I saw so many people tweet about this app during the week, but Matthew made me chuckle the most. In fact, this tweet is much more fun than the app. 😂