Michael Long
1 min readJun 7, 2019

--

In our shop our general rule is that we support the current version of iOS minus one.

So when iOS 13 hits this fall we’ll be at 13/12, which means we really can’t use SwiftUI quite yet… unless the client is willing to 13-only. Same time next year, however, we’ll be at 14/13 and we’ll be able to use SwiftUI.

From that perspective, you have one year.

I’ve been building a declarative widget library for iOS that’s similar to Flutter widgets, and I’ve been also been doing some Flutter code. So believe me when I tell you that it’s scary crazy just how fast you can build and iterate UI designs in declarative coding paradigms.

Do a declarative Flutter/Widget/SwiftUI design, and you can probably create that design in 1/20th the amount of code it would take using pure Swift and/or with Storyboards.

And it’s better code, with far fewer places for errors to hide, which means your development/bug cycles are shortened as well.

Bottom line, and from my perspective, we, as developers, do NOT have three years to wait because in three years we’re going to be outperformed and outgunned by shops that learned those paradigms today.

--

--

Michael Long
Michael Long

Written by Michael Long

I write about Apple, Swift, and SwiftUI in particular, and technology in general. I'm also a Lead iOS Engineer at InRhythm, a modern digital consulting firm.

No responses yet