VIP, not a VIPER, Clean Swift Architecture - iOS Conf SG 2022

[@alenayoutube1574]

wow , helpful @2024

[@dmitrykhotyanovich5035]

Could you explain the concept of Clean Architecture in the VIP scope? Please try to understand and build the enterprise application based on VIPER and develop the backend using the Clean Architecture concept. Thank you for the example of the Scene code built from XCode templates.

[@renymustika6347]

Thanks for sharing. It's like more simple than VIPER

[@draganmarkovic7221]

Great video Danijela! Throurghly explained with great examples, keep up the good work!

[@abhigna.amarraju]

Can we please have this code link,?

[@kanstantsin-bucha]

We do similar design pattern for UI, only based on ViewModel and Interactors, where the view is subscribed to the ViewModel state and has some callbacks that ViewModel provides to handle User actions. ViewModel talks to Interactor, validate data and prepare presentation data from models.

[@AG-ym6iw]

читаю и думаю чем-то напоминаю т**ю :)

[@CanaldoJabinho]

the example could be in viewcode but ok Great job

[@paulikhane]

I think this great and I really appreciate the insight. I just one small contribution. Interactor should not be talking to network layer, that breaks Single Responsibility Principle. I know you can use Protocol to define a contract between this layers but in general business logic (functions or methods) should only accept parameters(values) and return values, matter fact they should be pure functions(taking a clue from functional programming). There should be a repository layer between the interactor and the network workers.

[@eahmedshendy]

Can we just make the Interactor takes the role of repository?

[@SwiftWithWalid]

Thank you for sharing but for me vip or viper aren’t architecture. Architecture define correctly the relation between modules which is not defined at all in this “architectures” and in the end we will end with a spaghetti code :)

[@kanstantsin-bucha]

It is a UI design pattern. The naming needs to be corrected, agreed. Still we should have one to deal with UI =)

[@sarojraut7634]

It will end with well defined code with less bugs if you are using it in long term large projects.

[@JHEVR]

The Hogwarts project was VIPER not VIP 🤔 right? VIP pattern works well with SwiftUI, VIPER doesn't because of the Routing, I think that's what you wanted to say