Writing a Big App in Swift

#1

Post by mattiemass » Sat, Mar 12, 2016, 11:03 AM UTC

Writing a Big App in Swift
wooji-juice.com

Re: Writing a Big App in Swift

#2

Post by sdegutis » Sat, Mar 12, 2016, 6:34 PM UTC

> Switching to Auto Layout for almost all layout needs, with a single Storyboard for both iPad and iPhone.

I'm surprised that worked out for him, given what I've heard about Storyboards, which is that they're fine for really trivial UIs but don't scale well at all for any workflow that's even slightly complex. But that was like 2014. Maybe things have changed since then?

Re: Writing a Big App in Swift

#3

Post by jtreanor » Sat, Mar 12, 2016, 7:38 PM UTC

sdegutis wrote: post #2

> Switching to Auto Layout for almost all layout needs, with a single Storyboard for both iPad and iPhone. I'm surprised that worked out for him, given what I've heard about Storyboards, which is that they're fine for really trivial UIs but don't scale well at all for any workflow that's even slightly complex. But that was like 2014. Maybe things have changed since then?

I think it's fair to say storyboards haven't improved much since then, although it's a fairly divisive topic.

Personally I still very much fall on the side of not using storyboards for non-trivial UI.

Re: Writing a Big App in Swift

#4

Post by veidr » Sun, Mar 13, 2016, 1:49 AM UTC

sdegutis wrote: post #2

> Switching to Auto Layout for almost all layout needs, with a single Storyboard for both iPad and iPhone. I'm surprised that worked out for him, given what I've heard about Storyboards, which is that they're fine for really trivial UIs but don't scale well at all for any workflow that's even slightly complex. But that was like 2014. Maybe things have changed since then?

One thing that changed is storyboards became more modular, and you can load them programmatically just like .xib files. So you can break apart UI into multiple storyboards.

Which is good, because some features only work inside storyboards. For example, the Interface Builder component of Xcode cannot lay out a "static" UITableView (one whose content and subviews are set at design time) unless it's inside a storyboard. No idea why.

I used to avoid storyboards as much as possible, but things like that made me decide it's too much trouble to fight The Man, so now I just usually use them like he wants me to.

I think it's fair to say that storyboards have gotten better, but they still suck.