Skip to content
This repository has been archived by the owner on May 6, 2024. It is now read-only.

Get rid of storyboards #26

Open
konnork opened this issue Apr 11, 2017 · 2 comments
Open

Get rid of storyboards #26

konnork opened this issue Apr 11, 2017 · 2 comments

Comments

@konnork
Copy link
Member

konnork commented Apr 11, 2017

Goals:

  • Allow for custom view controller initializers (for dependency injection)
  • Prevent difficult merge conflicts
  • Easier view reuse
@manavgabhawala
Copy link
Member

I just want to say, I actually like having storyboards, it makes it convenient and easy to add layout attributes and visualize the app hierarchy. Storyboards are also a great place for new comers to start looking at rather than jumping into some code.
Finally, I always question big changes by asking is the effort and restructuring work required worth it? I think adding new and better features is a far more prudent use of time than trying to get rid of the storyboard.
I know in theory having no storyboards is ideal, but this is just my 2¢.

@konnork
Copy link
Member Author

konnork commented Apr 14, 2017

Yeah it is definitely easier for newcomers, especially since most of them (and more as we go) will not know how to /not/ have storyboards.

That said, I find it much cleaner to not use storyboards, and the limitations (like compile time checking) can get annoying. I don't really see tooooo much of a time issue getting rid of it as quite a few view controllers are independent already.

At the very least I'd like to refactor each tab to its own storyboard. I'll ask the iOS peeps at the meeting on Monday what they think

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants