📬 Issue 125 of our weekly newsletter is out! Join 3,200+ subscribers for community highlights, an Indie App of the Week, and a recap of Apple's "techtober".
https://t.co/PKflx7zsEX
Protecting communication between your iOS app and backend is more important than ever, especially when preventing unauthorized AI API calls.
Artem Mirzabekian (@livsycode) explains how Apple App Attest works under the hood:
https://t.co/HP8UYjiof0
Building adaptive layouts for the new iPhone Duo?
@livsycode breaks down how SwiftUI's new ArrangementView in iOS 27.1 lets you describe view relationships across dual-screen postures:
https://t.co/9k6ZpjfiwD
What happens when a simple transaction history screen becomes a real mobile system design problem?
That’s what @livsycode and I explore in episode 2 of our Mobile System Design Interview series, going live in 30 minutes.
The scenario: design the transaction history of a mobile banking application.
At first, it sounds straightforward:
show a list of transactions, open the details, add search and filters.
But then the real questions start:
- How do you paginate years of financial history?
- How do you model transaction states?
- How fresh does the data need to be?
- Should sensitive banking data be available offline?
- How do you design receipt/download APIs securely?
- Where should pagination cursors live in the mobile architecture?
- How do you explain these trade-offs in an interview?
In this episode, I’m the candidate and Artem is the interviewer.
We focus less on finding the “perfect” architecture and more on the reasoning process behind it: clarifying requirements, challenging assumptions, designing APIs, modeling the domain, and explaining architectural responsibilities clearly.
Because in a senior mobile system design interview, the goal is not to recite a template.
The goal is to think.
Join us live in 30 minutes
https://t.co/4YWUEKwwcX
iOS 27 brings NSTextTable, NSTextTableBlock, and related TextKit APIs to UIKit, making real tables possible inside NSAttributedString. It is meant for rich text—documents, invoices, reports—not as a replacement for UITableView. @livsycode talks about it.
https://t.co/dgRLEhaPIi
The Observation framework remains one I want to explore further, even more so after reading about this new API in @livsycode's article.
https://t.co/dhXKanyWKQ
In this piece from @livsycode, learn about the three ways to bridge callbacks into async/await, and exactly what each trades away.
https://t.co/Mx1sWBGcRs
A Swift 6.4 small and convenient change you don’t want to miss out on. @livsycode shares how anyAppleOS works.
Curated in this week's #swiftleeweekly https://t.co/QMBLyIgwjh
Infinite thanks to the remarkable spirits who so generously placed their hard-won wisdom in our hands: Quinn, @livsycode, @_al_we, @natpanferova, @Codelaby and David Retegan
An innocent piece of code that rotates a SwiftUI view with a glass effect. The result, however, can be disappointing, as @livsycode explains.
Curated in this week's #swiftleeweekly https://t.co/5wW00sbGMp
This new SwiftUI API made people clap during the State of the Union, and for good reasons. @livsycode explains how it works.
Curated in this week's #swiftleeweekly https://t.co/pLcagm6PeK
Endless gratitude to the extraordinary souls who so freely entrusted us with the priceless wisdom they bore: Matt Massicotte, @azamsharp, @iosartem, @livsycode, Lee young-jun, Ugur Toprakdeviren and @leogdion
Posting events, subscribing from other places: it’s a common pattern when writing code. @livsycode shows how to do this in a type-safe manner using Swift.
Curated in this week's #swiftleeweekly https://t.co/ar9LWQ6vYI