iOS App Architecture: When and how to create a shared UI module | Live Dev Mentoring
/This video was publicly available only until August 22nd, 2022. Now, it's only available to students of the iOS Lead Essentials program.
"Should I extract my code into reusable components to avoid duplication?" 👇
Well, it depends...
Usually, yes. We don't want to duplicate UI code because every time we need to make a change, we'd have to remember to update it in EVERY duplicate component. And this is inefficient and error-prone.
But in large modular apps, we also don't want to couple all feature modules with a shared UI module. Otherwise, changing the shared module because of "Feature A" will also impact "Feature B" directly. This would also be inefficient because it would increase build times and require synchronization between feature teams.
Is there a solution to this problem?
Yes! There's a specific way of creating shared UI modules without increasing coupling between modules.
To become a complete senior iOS developer, you need to know when it's the right time to extract duplicate code into a shared module and how to do it efficiently without increasing coupling between feature teams.
So watch this mentoring session now to learn when and how to create a shared UI module.
But hurry up because this video is publicly available only until August 22nd, 2022. After that, it'll only be available to students of the iOS Lead Essentials program.
