As asked
You are starting a major iOS feature that has complex navigation, custom animations and a long support window. How do you choose between SwiftUI, UIKit or a hybrid?
Sample answer outline
A strong answer starts with product and platform constraints rather than preference. SwiftUI is productive for state-driven screens and modern OS targets, but UIKit still gives mature control over complex navigation, collection views and custom transitions. A hybrid can work well if ownership boundaries are clear, for example SwiftUI feature screens hosted inside a UIKit shell. The candidate should mention minimum iOS version, team skill, testability, accessibility and long-term maintainability. Weak answers treat SwiftUI as automatically newer and better without naming the actual risks.
Expect these follow-ups
- Where do SwiftUI and UIKit lifecycle models clash?
- How do you test a hybrid screen?
- What would make you reverse the decision after a prototype?