You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really like what this (and other similar) architecture offers but I’m wondering about the reusability of the views and the role of the view controllers.
In the majority of the occasions I create custom views and then compose them all in the viewController creating the screen that I want.
I would like to see how this is approached in this architecture since I see that the VC/Views are really tied and only can represent one screen.
For example how you would handle if we want to use the “Add” view in another place? For example if we want to use the add as a view on top of the table.
Thank you!
The text was updated successfully, but these errors were encountered:
I really like what this (and other similar) architecture offers but I’m wondering about the reusability of the views and the role of the view controllers.
In the majority of the occasions I create custom views and then compose them all in the viewController creating the screen that I want.
I would like to see how this is approached in this architecture since I see that the VC/Views are really tied and only can represent one screen.
For example how you would handle if we want to use the “Add” view in another place? For example if we want to use the add as a view on top of the table.
Thank you!
The text was updated successfully, but these errors were encountered: