Skip navigation

Swinject overview

Swinject overview: iOS App Development: Design Patterns for Mobile Architecture
Swinject overview: iOS App Development: Design Patterns for Mobile Architecture

This is a walk through a typical implementation of a Swinject Dependency Repository. Dependency Injection just means that we don't create classes within another class. The created classes (i.e. the dependencies) are instead created by a single class who manages the life cycle of dependencies. This simplifies what is needed in order to get any 1 class up and running, especially if we just use protocols instead of concrete implementations. This process completely decouples our layers and allows us to use mocked (i.e. faked) layers to work with until another layer is created. It speeds up development and simplifies logic. You can either create your own Dependency Injection class and handle the creation yourself, or with Swift, we have a great option called Swinject. We also will cover the idea of maker methods that handle the creation of other objects (Table Cells, Views, etc. ).

Resume Transcript Auto-Scroll
Author
Skill Level Intermediate
1h 52m
Duration
16,692
Views
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 Your Free Trial Now

Start your free trial now, and begin learning software, business and creative skills—anytime, anywhere—with video instruction from recognized industry experts.

Start Your Free Trial Now