There is a spectrum from zero architecture to and over architected application, with upfront costs, vs. technical debt trade offs. It's up to you and your team to find the right fit, but the ultimate goal is to develop as fast as possible, while maintaining that development speed with well designed code. There is also a spectrum of effort from easy to difficult, with a lot of value lining up at the easy portion, but decreasing over time as things become more complex. Working with zero architecture is the most difficult because the code quickly becomes disorganized and bugs and hacks proliferate. The main pieces of MVA (Presenter/ViewModel, Layer Separation, Dependency Injection, Entities, and Coordinator) fall within the easy, high value portion of the spectrum.
- [Instructor] So, we're going to talk about MVA.…What is MVA?…Well, it has all of the same pieces…as the MVP type architectures.…In fact, it is MVP.…We just have some additional things…like vipers entities,…which are really Bob Martin's entities,…the router which follows the coordinator pattern,…and the interactor which is,…in our case,…the model layer.…And you would find this…in any layer separation ideas.…And then I have injection here…because it simplifies…how our classes work…and it makes us follow solid principles.…
I've put reactive programming as being optional, though.…So, is MVA new?…Well, no.…We've just broken MVC,…MVP,…MBVM,…and Viper…to their different components…and then we're applying them…as we need and see fit.…Most of the benefits are found in level one.…As we progress,…we get less return for our efforts.…After level three,…you need to consider if binding an RX…is right for you and your team.…So we have the spectrum…from no architecture heading to over architecture.…
You can see where our MVP type architectures are.…
Author
Jon Bott
Released
6/27/2017- Moving pieces of architecture
- Designing an MVA app
- Walking through a demo application
- Converting to MVP
- Moving non-view logic to a presenter
- Breaking logic into layers
- Using entities
- Setting up dependency injection
- Implementing the coordination pattern
- Adding data binding with RxSwift
Skill Level Intermediate
Duration
Views
-
Introduction
-
Welcome48s
-
-
1. Moving Pieces of Architecture
-
Why architecture?3m 32s
-
Architecture pieces2m 19s
-
Common architectures3m 42s
-
-
2. Demo Application Walkthrough
-
UI overview41s
-
Code overview1m 18s
-
Load data2m 51s
-
-
3. Convert to MVP
-
Create presenter3m 14s
-
Create presenter, part 23m 28s
-
Create presenter, part 32m 36s
-
Create presenter, part 43m 21s
-
-
4. Expand Layers
-
Expand layers5m 59s
-
Expand layers, part 24m 14s
-
Entities2m 49s
-
-
5. Dependency Injection
-
Swinject overview6m 27s
-
Swinject storyboard3m 14s
-
Presenter conversion5m 45s
-
Protocol injection8m 53s
-
-
6. Navigation Coordinators
-
Coordinator walkthrough3m 15s
-
-
7. Data Binding
-
RxSwift – observables11m 15s
-
RxCocoa – data binding6m 46s
-
-
Conclusion
-
Next steps42s
-
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.
Share this video
Embed this video
Video: MVA (mininimum viable architecture)