SwiftUI launched in 2019 with a demonstration that made experienced iOS developers simultaneously excited and nervous. Excited because the declarative paradigm promised to eliminate the impedance mismatch between interface builder storyboards and code. Nervous because Apple’s track record with new frameworks included several that were replaced, deprecated, or quietly ignored within a few development cycles.

Five years later, SwiftUI is neither the complete replacement for UIKit that Apple’s marketing implied nor the abandoned experiment that skeptics predicted. It is a mature but still-evolving framework that handles a large majority of common iOS UI requirements elegantly, struggles with a specific set of advanced requirements, and has permanently changed how iOS UI code is written even when developers reach for UIKit to solve problems SwiftUI cannot.

Apple’s App Store commission structure has been the subject of regulatory scrutiny, antitrust litigation, developer revolt, and congressional testimony for five years. The outcome of all this attention is a commission structure that has changed at the margins while remaining fundamentally intact at its core. The 30 percent standard rate — reduced to 15 percent for developers earning under a million dollars annually and for certain subscription renewals — continues to apply to the overwhelming majority of App Store revenue.