The following decision tree should be used to determine whether to use SwiftUI or UIKit for new and existing components:
The following list shows components that are implemented using SwiftUI and some that have future potential for SwiftUI conversion.
| Component | Type |
|---|---|
| Address Autofill | SwiftUI |
| Credit Card Autofill | SwiftUI |
| Splash Screen Animation | SwiftUI |
| Autofill Bottom Sheet | SwiftUI |
| Fakespot Message CardView | SwiftUI |
| Circular Progress View | SwiftUI |
| iOS 14-based Widgets | SwiftUI |
| Settings Page: Sub components like Dark Reader | SwiftUI Potential Candidate |
| Help and support pages (Licenses) | SwiftUI Potential Candidate |
Ensure SwiftUI views meet all accessibility requirements before replacing UIKit implementations.
SwiftUI components should integrate smoothly using UIHostingController where necessary.
Where applicable, consider using a Redux-like state management approach to ensure predictable and scalable UI state handling.
