Under the Radar

322: Requiring iOS 26?

9 snips
Jul 3, 2025
The discussion delves into the headaches of maintaining compatibility with outdated iOS versions while trying to embrace the latest innovations. A clever strategy to require iOS 26 is explored, weighing the benefits against user accessibility. Insights on the complexities of app development using SwiftUI versus UIKit reveal the challenges developers face. Strategies for reusability and effective communication with users are highlighted, emphasizing how to balance technological progress with a stable user base.
Ask episode
AI Snips
Chapters
Transcript
Episode notes
INSIGHT

Complexity of Supporting Old iOS Versions

  • Supporting old iOS versions complicates development and slows productivity, especially in SwiftUI due to modifier chaining complexity.
  • Dropping old versions eases development but risks locking out users from future updates and bug fixes.
INSIGHT

Tradeoffs in Requiring iOS 26

  • Cutting off support for old iOS versions impacts potential new users who cannot download the app at all.
  • Losing a small percentage of new users by requiring iOS 26 may not justify the technical savings for some apps.
INSIGHT

Timing iOS 26 Launch Wisely

  • Releasing on day one of iOS 26 means fewer customers have updated, limiting reach.
  • Waiting until later months increases user adoption of iOS 26, simplifying testing and allowing more aggressive redesigns.
Get the Snipd Podcast app to discover more snips from this episode
Get the app