Migrating from UIKit to SwiftUI
Fully updated for Xcode 11.2
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: No SwiftUI equivalentUILabel:TextUITextField:TextFieldUITextFieldwithisSecureTextEntryset to true:SecureFieldUITextView: No SwiftUI equivalentUISwitch:ToggleUISlider:SliderUIButton:ButtonUINavigationController:NavigationViewUIAlertControllerwith style.alert:AlertUIAlertControllerwith style.actionSheet:ActionSheetUIStackViewwith horizontal axis:HStackUIStackViewwith vertical axis:VStackUIImageView:ImageUISegmentedControl:SegmentedControlUIStepper:StepperUIDatePicker:DatePickerNSAttributedString: 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 Instabug helps you identify and resolve severe crashes quickly. You can retrace in-app events and know exactly which line of code caused the crash along with environment details, network logs, repro steps, and the session profiler. Ask more questions or keep users up-to-date with in-app replies straight from your dashboard. Instabug takes data privacy seriously, so no one sees your data but you! See more detailed features comparison and try Instabug's crash reporting SDK for free.
Save 50% on all books and bundles
The biggest ever Hacking with Swift sale is now on, letting you save 50% on all books and bundles. Learn something new with Swift and enjoy great savings while the sale lasts!
Click here to save 50% in our Black Friday sale!
Similar solutions…
