VIP, not a VIPER, Clean Swift Architecture - iOS Conf SG 2022
Переглядів 14,182
День томуSpeaker: Danijela Vrzan
VIP and VIPER, while having the same basic components, are quite different in their implementation. They both follow Uncle Bob's Clean Architecture principles and often tend to be mixed up due to their name similarities. This talk will introduce you to the VIP architecture and it’s principles. While specifically made for UIKit apps to fix the MVC problem (Massive View Controllers), we'll take a look at how we could implement it in SwiftUI apps.
About the Speaker:
Danijela is an iOS Developer and an article author for raywenderlich.com. In her free time, you can find her hiking or lifting heavy weights at the gym. When not working out, she's playing video-games, cooking, and trying to keep up with Swift updates!
Event URL: iosconf.sg
@draganmarkovic7221 2 роки тому
Great video Danijela! Throurghly explained with great examples, keep up the good work!
@renymustika6347 2 роки тому
Thanks for sharing. It's like more simple than VIPER
@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 6 місяців тому
читаю и думаю чем-то напоминаю т**ю :)
@abhigna.amarraju Рік тому
Can we please have this code link,?
@CanaldoJabinho Рік тому
the example could be in viewcode but ok Great job
@paulikhane 2 роки тому
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 2 роки тому
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 4 місяці тому
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
iOS Conf SG
Переглядів 939
ЮМОР ICTV - Официальный канал
Переглядів 111 тис.
Mobile Developer
Переглядів 8 тис.