Skip navigation

We will update our Privacy Policy soon. Please see the preview.

Why architecture?

Why architecture?: iOS App Development: Design Patterns for Mobile Architecture
Why architecture?: iOS App Development: Design Patterns for Mobile Architecture

There are several reason for adding architecture into your app. Developers spend 10 times as much time reading code versus writing it. Architecture helps us avoid bugs, isolate complex code, and speeds up development allowing multiple developers to work independently of each other while working in dependent areas. Some good arguments against using architecture include: using architecture because that's just what we do; sometimes speed is more important than perfect architecture. There is a spectrum of architecture that can be implemented, with some pieces providing a lot of value, at little cost. Some misconceptions about using architecture include the idea of not needing architecture, because we need to move fast: there is always a trade off in speed vs. technical debt. And YAGNI (You Aren't Gonna Need It). In large applications, you are going to need some of this, and keeping to simple, consistent patterns keeps your code readable and maintainable.

Resume Transcript Auto-Scroll
Skill Level Intermediate
1h 52m
Show More Show Less
Skills covered in this course
Developer Mobile Apps Mac OS iOS

Continue Assessment

You started this assessment previously and didn't complete it. You can pick up where you left off, or start over.

Start My Free Month

Start your free month on LinkedIn Learning, which now features 100% of courses. Develop in-demand skills with access to thousands of expert-led courses on business, tech and creative topics.

Start My Free Month