Swift: VIPER Design Pattern (Architecture, 2023, Xcode 14, Swift 5) - iOS Development

[@xiaoyuguo1370]

Thanks for creating this video! It's pretty easy to understand. But I would like to point out that in your code, there are a few retain cycles with view, presenter, router and interactor. One option you can do is to make those protocols conforms to AnyObject, and mark these references as "weak": 1. router's ref to presenter 2. router's ref to view 3. presenter's ref to view 4. interactor's ref to presenter Eventually your object relationship will look like this in the memory, where -> means a strong reference router ^ | window -> View Controller -> Presenter -> Interactor Correct me if I'm wrong.

[@sexypekk]

Although slightly dangerous, I think `unowned` would be acceptable also so we can assert that our objects that should exist do exist. The alternative would be a completely unresponsive app that people would have to kill and restart themselves anyway so I guess you pick your problems :)

[@iOSInnovator]

I have the same question Interactor has a strong reference of the presenter and the presenter has strong reference of the interactor. It will create retain cycle.

[@pifeeder9027]

That tells a lot about the iOS academy

[@rrahulc]

circular reference can be fixed by replacing one of the strong references with a weak or unowned reference.

[@keenancookson8641]

I started a new job and they use VIPER. I'd never used it before and I struggled to get through some explanations of VIPER (ADHD). This explanation was so concise and easy to understand. Thank you so much, man! ❤

[@coolcodingdad]

Great video! You really explained it well, thank you!

[@lukasz.szarkowicz]

Good video explaining basics. I would like to see some more informations about coordination between modules. I use approach of adding Coordinator pattern into VIPER. Also, Router should be responsible only for routing not building a module - here is good to use some Module builder by using fabric pattern. This way we use SOLID principles. There is also questionable for me conforming to UITableViewDelegate and UITableViewDataSource in UIViewController component. What do you think about using Presenter to conform to that protocol - then we keep responsibility of proper presentation on the side of Presenter (view shouldn't convert DTO to ViewModel). I am also curious about automation for it. I created Xcode template which creates entire module with 1-click, but I am still researching for making it better - that's why I am looking for more opinions :) . Thank you for your work and I am waiting for part 2 with advanced part.

[@AndGordy]

A great intro to VIPER. Actually, go ahead and watch it!

[@iOSAcademy]

Thanks

[@BHFJohnny]

Couldn't manage to *destroy* that like button. It still works.

[@iOSAcademy]

Haha nice

[@Charlot1914]

They all connect by strong reference between each other? Where are the weak references?

[@Bhaukaal-YT-001]

I have been trying to learn this from a long time. Finally i found this hands on tutorial instead of those redundant concepts articles. Thank you

[@abhishekthapliyal7933]

I was trying to learn VIPER but seems confusing, this video is so simple and easy to understand.

[@iOSAcademy]

Thanks!

[@tcleedev]

Whenever I search for Swift/ iOS, I ended up with this channel :) I'll just search in this channel first next time lol

[@sashamakedonskii]

it would be nice if you extend this tutorial for navigation on multiple screens, delegates, callbacks and how to handle this in VIPER appropriate. And yeah, thanks for video. Cleanest explanation of VIPER ever I see 👍

[@iOSAcademy]

Great suggestion!

[@sandipkhedkar]

And finally i understood the VIPER, thanks a lot man

[@iOSAcademy]

Youre welcome

[@FilipeMarques]

Viper is a little bit confusing, but we can isolate the modules, functionalities, I think it was easier to test. Thank you so much for the great lesson! (:

[@iOSAcademy]

Youre welcome

[@nurlanakylbekov7266]

Great content👍, I love when u start project without storyboard. VIPER is one of the design pattern that I want master but always fail. Hope with this tutorial I’ll get proper understanding.

[@flutterswift7278]

Көп қолданылады ма VIPER Қазақстанда?

[@nurlanakylbekov7266]

@@flutterswift7278 Банктерде колданылады

[@mishar4743]

THANK U SO MUCH!!! IT REALY USEFUL!!! FROM RUSSIA WITH LOVE ❤️❤️❤️

[@iOSAcademy]

Youre welcome

[@JoffreyB]

Finally! Was waiting for that

[@iOSAcademy]

Get pumped

[@barche75]

I’m don’t really like VIPER. To much classes. Most of classes knowing about other ones. View layer contacts with models. My preference to Data Driven MVVM + Coordinator (for routing) + Builder (factory to create units) + proxy pattern for fetching data from web or storage. Any way it’s a great video to understand this pattern. Thank you!

[@iOSAcademy]

I agree

[@glennadams7047]

@@iOSAcademy Could you make an app for us demonstrating all of those ? It would be very valuable to see a "best practices" app with them rolled into one, and we could use it as a template for our future apps. Thanks for your great work !!!

[@noodles7240]

Totally agree. Looks like the VIPER is an upgrade for MVP. However, MVP itself is not a perfect architecture due to the dependencies between the presenter and views. In the VIPER, it introduced a new dependency between interactor and presenter, which is a terrible thing. Meanwhile, the too many protocols make it hard to maintain if there's new business logic which requires a new parameter in a protocol, which needs to modify all the implementations of it. MVVM is a perfect architecture since it decouples the dependency of view and view model. The view model no longer needs to hold a reference of view. In Android, we can use live data or data binding to update the view, in iOS we can use RxSwift or things like that.

[@barche75]

@@noodles7240 yes, that’s true. But I’m usually use closures to bind vm and view.

[@bonioctavianus308]

why does the interactor had to have a reference to presenter? doesn't it better if the interactor just return a result? hence it did not know anything about the caller = less coupled

[@tamasballa1]

Thanks, very nice video! My question is, wouldn't it be better to create an AnyEntity protocol, conform the User entity to it, and instead of the update with users method you could write a more generic update with data anyentity function?

[@abdullahumer1683]

What I do is that presenter will have reference to View, Interactor and router but only the View will have reference to the presenter. Interactor and Router does not need to have a reference of the Presenter. With using async and await the presenter will wait for interactor to do the network calls and return the data. Its also a good practice to have a separate helper class for the network calls instead of writing them completely in the interactor.

[@alimehdi4011]

Hi! great learnings in your video and understood VIPER easily because of your video. I have a question that does your code produces retain cycles in router class where interactor, presenter, view contains each other references ?

[@iOSAcademy]

Thanks

[@burakturhan9708]

Hi do you have git for this? It would be better if also inspect on code to learn better

[@marcos6718]

I think maybe the pattern is a bit convoluted... I can’t see myself using it, to be honest. But great video, I learned a lot! Thank you a bunch!!

[@nelsonalva]

I can't thank you enough. Keep the good work!

[@iOSAcademy]

Youre welcome

[@losinsky9356]

You are doing very good content! At this time I'm exploring all your videos. Keep going 😁

[@iOSAcademy]

Thanks!

[@BenjaminAnoh]

Thank you! VIPER has been so overrated. It is so clear now. Can you share the source code for this kind of tutorial?

[@iOSAcademy]

Youre welcome

[@nashtravelandlifestyle]

Thanks for the tutorial. I have question about the code written to create table, label etc. It is a function right, doesnt it get called everytime table or label is accessed and keeps creating new instance of table or label?

[@dhav7634]

Thanks for the great video and explanation. Is there a github link to take a look at this sample project code?

[@iOSAcademy]

Thanks - code available through iosacademy.io/resources

[@programming5523]

Great Explanation helps a lot . 🙌🏻

[@iOSAcademy]

Glad to hear that!

[@maru027]

This is really helpful and clear for me to understand. Thank you!

[@iOSAcademy]

Youre welcome

[@shatadrudatta9405]

Excellent tutorial

[@iOSAcademy]

Thanks!

[@sovrinfo]

Great video! Thank you a lot!

[@iOSAcademy]

You are welcome!

[@АртурКулик-ш3с]

22:38 “let” was pronounced very sensually :)) p.s. Thanks for lesson!

[@rev_kous9275]

Waiting for the Clean architecture implementation. Can be Clean VIPER, Clean MVVM,...

[@Ni7ram]

hey, excellent video! and channel, to be honest. but i have a question: why is the router aware of the view? as i understand it, thats not compatible with the diagram of VIPER at the beginning of the video.. shouldnt it interact with it through the presenter? i think its more tedious, but cleaner.

[@iOSAcademy]

Good call out. Ive seen both approaches

[@antonilin3123]

I think which pattern to use it's depends on project what you are working on. If it's small app then you can use only MVC. But, of course Viper, MVP and so on need to know :)

[@iOSAcademy]

Yep, i completely agree

[@miljanvukicevic8631]

Awesome vid

[@iOSAcademy]

Thanks

[@TheAhmadReza]

Thanks for this great tutorial, however, I still don't understand why entity (users) has to be in view! I think it would be better if it was in the interactor. also why we should have an API call in the router?! it also should be in the Interactor 🤔

[@HarshitKumar-yn8du]

Thanks for video, where can I get the source code?

[@edwardivash8539]

Great example! The only question left is why is the users array inside the view object? View doesn't need to know anything directly about the entity.

[@IBGNW]

have you found the answer yet? I found another viper example also did the same.

[@jawske8233]

Great video as always! Would you mind explaining how to design an app that will run on “small” devices such as iPhone 7 and on “bigger’s” such as iPhone 12 Pro Max? Thanks and keep up the good work

[@asanlidev]

My most favourite part of the video: 02:49

[@iOSAcademy]

Haha thanks

[@FernandoMXoficial]

Great content, very good explanation

[@iOSAcademy]

Thanks!

[@lounge_shows]

I understand that this is just for learning purposes, but I am guess there is a cyclic dependency that gets created here. The view has a reference to presenter and the presenter has a reference to view.

[@rakhipatidar9373]

Please make a video using VIP architecture pattern for Swift 5

[@justinblackvfx]

I want to learn Viper but, I stuck how to implement uitabbarcontroller in viper. Can you show it how next time?

[@quoteu6240]

Can we use viper and combine together ?

[@iOSAcademy]

Yes

[@MoAdel92]

Thanks bro

[@iOSAcademy]

Youre welcome

[@SchoolBads]

Can you send a link to the project please?

[@Leopugpiano]

amazing job!

[@minimaster.10]

this UIKit how about SwiftUI ?

[@lucassoares4069]

"Main storyboard file base name" doesnt show in my plist file but when I try to run the app it seems it is still there. Is there a chance it is hidden somehow?

[@gasparfreak]

I don't know, maybe because I'm just a beginner I'm thinking it's a little too much setup, and really I can't get what are the benefits viper brings.

[@iOSAcademy]

It is a lot but with huge projects it is a clean design

[@gasparfreak]

@@iOSAcademy By huge you mean, FANG level of hugeness correct, or am I missing something? Anything less than that I can use MVC or MVVM?

[@iOSAcademy]

Eh, its subjective. Like airbnb isnt fang but uses it. And othrs too

[@PauloSilva252]

@@gasparfreak I work in a smaller company than FANG, ain't that big of an app and we use it too. It's good when you have a lot of business logic inside your app. If an app is heavily based on networking, I don't think Viper would be the best, MVC or MVVM is probably better

[@kumarshastry9177]

protocol is declared as AnyInteractor , AnyPresenter etc, but the methods like getUsers, didfetchusers inside protocols are confusing, i think they should be generic.protocols should not be concrete.

[@cinquain0]

Uuumm... I'll stick to MVVM. Thank you.

[@Lhunath]

FYI- the "Any" prefix is intended to refer to a type erased opaque type that conforms to the protocol.

[@iOSAcademy]

yep!

[@wlugick3326]

What to to next? If I wanna tap the cell to get a network request and push to another Controller? Where and how I should write the codes?

[@PauloSilva252]

You would use the router to move to the next screen

[@roohbear]

Wow, this is so fast! Did you practice this 3 or 4 times before recording this video? I'll have to watch it 2 or 3 times to fully inject it into my head but it seems to make sense. Personally, I think VIPER is overkill. Why take something simple and make it so complicated? I hate when things are over-engineered. It just seems like someone is trying to provide job security for themselves. There are no comments in this code. I would hate to have to try and figure this out. I would be cursing the developer and wondering "why, why, why" so many times. I seriously don't understand the point of it, but my new employer wants it probably because some manager heard it was new. Do you really need the "{ get set }" stuff? Near the end, when you were not getting any data showing up, I thought it might have been because you were missing that annoying "Allow arbitrary loads" setting in your info.plist file but for some reason, you didn't need that. Not sure why.

[@iOSAcademy]

Haha thanks - no, just experience

[@RostyslavKobizsky]

Lots of bad practices detected! But in general good introduction into the pattern itself

[@chimansong8653]

It is got to solve the retain cycle.

[@iOSAcademy]

Yep

[@GrumpyOldTech]

Don’t think it is appropriate to make reference to User in the protocol definitions, should be generic to work across modules. Also an example of routing would be useful.

[@harshitjain7428]

Is the source code for the same is available?

[@iOSAcademy]

Yes, for channel members

[@rajdhakate617]

How you navigate so quickly without using touchpad?

[@iOSAcademy]

Command shift O

[@dev_jeongdaeri]

Oh my god😭👍👍👍

[@iOSAcademy]

Haha thanks

[@GamePlay-sq8lf]

where to put validation code and how to pass data from one viewcontroller to other ?

[@PauloSilva252]

You can use the router for that, since it is the router's responsibility to contain the logic for the flow of screens. This VIPER tutorial is good, but Viper is not really adequate for one screen apps, but rather for large apps with a lot of business logic in it. Validation code in what sense?

[@keepspeed]

If you have such a good pattern, use it yourself. When people understand patterns, they become the ability to make patterns. Do not deprive them of the opportunity to develop the ability to design optimal patterns by themselves trying to understand the patterns you have made. Any pattern is very boring and boring.

[@iOSAcademy]

This isnt my pattern. Its common across industry

[@alifayed5678]

Can we have source code

[@iOSAcademy]

Coming soon

[@bluer5640]

Very fast-paced video and hard to understand. You got to the implementation so fast and confused me about where to put all these protocols and connections

[@iOSAcademy]

Thanks for the feedback

[@ripfrauds]

600 th like

[@iOSAcademy]

Thanks!

[@ziedagoubi7652]

ok i was following until 21:25 then you lost me, you shouldn't be calling an api inside the initialiser

[@abdullahumer1683]

yeah I thought the same. This can cause a race condition.

[@1stplace362]

why don't you ever share the code source ughhh

[@1987alejandroivan]

It would have been cool if the actual View/Interactor/Presenter actually take their references in the initializer, that way we wouldn't need to declare them as { get set } in the actual protocol, just { get }. protocol AnyView { var presenter: AnyPresenter { get } } class ViewController: UIViewController, AnyView { weak var presenter: AnyPresenter? // avoid retain cycle init(presenter: AnyPresenter) { self.presenter = presenter } } // etc.

[@harshit2629]

Thanks for video, where can I get the source code?