Migrating from UIKit to SwiftUI
Updated for Xcode 14.1
If you’ve used UIKit before, many of the classes you know and love map pretty much directly to their SwiftUI equivalents just by dropping the UI prefix. That doesn’t mean they are the same thing underneath, just that they have the same or similar functionality.
Here’s a list to get you started, with UIKit class names followed by SwiftUI names:
UITableView:ListUICollectionView:LazyVGridandLazyHGridUILabel:TextUITextField:TextFieldUITextFieldwithisSecureTextEntryset to true:SecureFieldUITextView:TextEditor(plain strings only)UISwitch:ToggleUISlider:SliderUIButton:ButtonUINavigationController:NavigationStackorNavigationSplitViewUIAlertControllerwith style.alert:AlertUIAlertControllerwith style.actionSheet:ActionSheetUIStackViewwith horizontal axis:HStackUIStackViewwith vertical axis:VStackUIImageView:ImageUISegmentedControl:PickerUIStepper:StepperUIDatePicker:DatePickerUIProgressView:ProgressViewwith a valueUIActivityIndicatorView:ProgressViewwithout a valueNSAttributedString: Incompatible with SwiftUI; useTextinstead.
There are many other components that are exclusive to SwiftUI, such as a stack view that lets us build things by depth rather than horizontally or vertically.
SPONSORED In-app subscriptions are a pain to implement, hard to test, and full of edge cases. RevenueCat makes it straightforward and reliable so you can get back to building your app. Oh, and it's free if your app makes less than $10k/mo.
Sponsor Hacking with Swift and reach the world's largest Swift community!
Similar solutions…
