The VIPER Architecture – Daniela Jovanoska Petrenko

VIPER is an iOS application architecture that aims to tame the Massive View Controller syndrom by constructing layers with very defined responsibilities. In this talk, Daniela Jovanoska Petrenko explains the different components in VIPER and share some experiences from applying the architectural pattern.

Recorded at CocoaHeads Stockholm meeting 68 hosted by Blocket on 2016-03-07.

[bluechess]

I work in a startup where we were using VIPER architecture. It has its merits but the biggest demerit is that it is time consuming and complex. And the on-boarding time is also huge. This is why I think VIPER may not be the best architecture for startups where time is the most valuable thing. So a startup should start with MVVM architecture. And once it grows and it can afford more resources, it can gradually move to the VIPER architecture.
I would love to hear some opinions on this. Thanks.

[daniadelbani]

Thanks for the nice explanation, would you please add the final links in the description so that we can check more. thanks

[guptaayush]

it's a great talk. Really helpful. Thank You!

[armenk]

thanks for introduce)
you are amazing