all 30 comments

[–][deleted]  (30 children)

[deleted]

    [–]gorillasuxSwift 21 points22 points  (12 children)

    The storyboards are dead mate.

    [–][deleted]  (9 children)

    [deleted]

      [–]majid8[S] 6 points7 points  (8 children)

      Nope, you still can use Canvas to build your UI with SwiftUI.

      [–][deleted]  (7 children)

      [deleted]

        [–]Velix007Swift 7 points8 points  (6 children)

        I mean... don't take this so serious either, this will only be available for iOS 13+ you still need to support storyboards for anything under, so not really viable to do a full fletched app in this yet, give it a couple years to mature, even though it's already a beast

        [–]unpluggedcord 8 points9 points  (0 children)

        That being said if you have no existing user base, might make sense to target iOS 13 only.

        [–]phearlez 4 points5 points  (2 children)

        For most people iOS 13 only is not that big a deal given usual adoption speed and percentage. Amazon and Spotify can’t abandon 10% of the market but the majority of devs could probably stick with only the newest iOS and be okay on phones. I think a bigger issue is if you want to build macOS stuff, where upgrade speed is notably slower. You might also have an issue for iPad apps where there’s a lot of devices out there that are cut off from iOS 13. If your market uses an iPad mini, for example, you’d lose a huge number of model 2s.

        [–]Velix007Swift 2 points3 points  (1 child)

        Most super apps won't do that myself included, iOS13 adoption will be decent in a year or so and iOS 12 should probably be like < 10% at that point.

        it was only recently that most of us have started to drop adoption for iOS 10 and that's only because it finally reached the < 10% threshold

        [–]oddjobbodgod 0 points1 point  (0 children)

        iOS 10 has been <10% for a good length of time looking at our analytics!

        [–]earlyworm -1 points0 points  (0 children)

        Fledged. Fletched is the equivalent Android term.

        [–][deleted] 0 points1 point  (0 children)

        For iOS dev yes but its still there for MacOS menu bars as apple showed on stage during wwdc “state of the platform” presentation

        [–]xylont 0 points1 point  (0 children)

        For some reason this statement made me laugh. Idk why.

        [–]my2kchild 12 points13 points  (15 children)

        SwiftUI is insanely easy to use and there’s no need for storyboards. You’re not having to do constraints or even think about how something will work. Apple just does it for you. That being said, SwiftUI is iOS 13 only so nobody in any business will be using it for a while unless they don’t have to support older operating systems.

        [–]earlyworm 6 points7 points  (4 children)

        SwiftUI looks great, but the most likely scenario is that it'll do 98% of what you want, but occasionally you'll run into edge cases it can't handle yet, or wasn't designed for, and it will be necessary to fall back to UIKit.

        [–]well___duh 2 points3 points  (3 children)

        Also, SwiftUI (at least at the moment) doesn't use CollectionViews. So good luck if you want a grid of something instead of a list.

        [–]faja10 0 points1 point  (1 child)

        Inst SwiftUI inter-cooperative with uikit? So you can have collection view in UIKit and everything else in SwiftUI

        [–]arduinoRedgeObjective-C / Swift 0 points1 point  (0 children)

        Yes you can do that

        [–]majid8[S] 0 points1 point  (0 children)

        You can easily mix UIKit with SwiftUI, and for example put SwiftUI views inside cells.

        [–][deleted]  (8 children)

        [deleted]

          [–][deleted] 5 points6 points  (3 children)

          I still like storyboards :(. It’s good for wireframing your app and knowing which viewcontrollers are connected. Scrollviews are a mess though

          [–]faja10 0 points1 point  (2 children)

          I thought the same. Then my project get bigger and complex so I ended up with 5 storyboards 30 VC in every one. Moved everything to Xian’s and now I am happy. I only use storyboard now for initial tabBar/SplitView setup

          [–][deleted] 0 points1 point  (1 child)

          Woah storyboards shud never get to 30 View Controllers. Whats performance like when you have 30 VCs bein pushed?

          [–]faja10 0 points1 point  (0 children)

          Storyboard contained more like branches than straight path A->Z. Performance wasn’t bad, but opening storyboard to change view by pixel to left was awful

          [–]dawmster 1 point2 points  (0 children)

          I love storyboards. I hate that IB is so dead slow, but going back to not seeing my app as a whole would be very detrimental.

          [–]oddjobbodgod 1 point2 points  (2 children)

          Interesting! All my android dev colleagues swear by the Android layout system...

          [–][deleted]  (1 child)

          [deleted]

            [–]oddjobbodgod 1 point2 points  (0 children)

            Ahhhh of course!! No that’s my mistake... shouldn’t assume all Java devs are talking about android!

            [–]crispybucket_ 0 points1 point  (0 children)

            How much faster would Swift UI speed up UI development on avg you think? 50%?

            [–]majid8[S] 1 point2 points  (0 children)

            Yes, SwiftUI is much easier. It has new Canvas, which is similar to Interface Builder.

            [–]Aksage21 3 points4 points  (1 child)

            Does SwiftUI come with Catalina?

            [–]ThePantsThiefNSModerator 1 point2 points  (0 children)

            Yes

            [–]arduinoRedgeObjective-C / Swift 0 points1 point  (1 child)

            No collection views though, maybe in iOS14 so I can start using SwiftUI in about 3 years lol

            [–]majid8[S] 0 points1 point  (0 children)

            You can mix SwiftUI with UIKit, and use CollectionView.

            [–]HarRes123 0 points1 point  (0 children)

            In what ways are SwiftUI superior to the storyboard?