Please log in to watch this conference skillscast.
Storyboards are a powerful yet sometimes maligned tool for controlling the flow of your iOS app through configuration instead of code. The storyboard approach in theory allows a clean separation of flow and presentation that provides greater flexibility to change. The reality though is that view controller code typically ends up becoming deeply entwined with the storyboard itself, leading to inflexible, oft duplicated code.
This approach can leave many an experienced developer wondering "is it worth it?" and becoming wary of its use. In this session we take a fresh cut - we pick up the story where other 'Architecture' approaches end and learn about a powerful approach to maintaining the separation of storyboard and view controller that delivers the promise of flexibility and less configuration in our code.
This talk will share a technique that makes powerful use one of the oldest but least understood design patterns in the book coupled with the modern language features of Swift for a story with an ending you don't want to miss!
Learn how to make Storyboards an even more compelling tool that instead of consigning to the trash can be instead at the heart of a flexible architecture for a modern app.
YOU MAY ALSO LIKE:
- Track Lead: Brainstorms are Dead! - How 'Design Sprints' are Revolutionising 'Design Thinking' and Helping Companies Solve Big Problems and Test New Ideas Quickly (SkillsCast recorded in November 2018)
- Espresso Patronum: The Magic Of The Robot Pattern (SkillsCast recorded in October 2019)
- Effective Reactive Architecture (SkillsCast recorded in October 2019)
Paul is an iOS expert combining skills in mobile product design with extensive software engineering experience. An influencer and leader having worked with development teams, key stakeholders and corporate clients incl. Apple and Sky. After years masquerading as a professional developer, Paul discovered 'Clean Code' and began a journey to a new understanding of what being a software professional meant. That journey continues through working with best practices such as TDD, Acceptance Testing and Pair Programming "as standard" in the pursuit of building the best possible software; Paul believes in the principle of getting software right early, and then keeping it working as intended.