Michael Long
1 min readJun 7, 2019

--

As Apple pointed out in the SwiftUI demos, the goal is to handle more of the grunt work and to free the developer to focus more on what adds value to the app.

Not to mention the not-so-minor goal of eliminating a ton of potential error conditions, race conditions, and invalid UI states that come from each and every developer rolling their own solutions to the same exact problem.

We have a Swift Meetup here and a few weeks ago someone gave a mini-presentation on solving form field tabbing and keyboard management! Why are new developers still forced to solve these problems?

As I mentioned to someone else, I’ve used (and written) declarative widget systems in Flutter and iOS and it’s scary just how fast you can iterate designs when you’re not sweating out each and every minor detail.

And SwiftUI isn’t going to save me writng ten lines, twenty, fifty lines of code… it’s going to save me from writing thousands of lines of code.

--

--

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