Separate Views from Apps
O
Oleg Kuzmenkov
The View is a place where all work happens.
Problem:
Now views are hidden inside of the hierarchy Solutions/App/Views/ViewABC. A view can contain data from different Apps. A view can represent a pipeline process that involves different people and uses data from different Apps.
- There is no way to switch between views in one click
- There is no way to see all views in the solution
- It is not easy to figure out in which app view is located
Proposed solution:
- Separate views from apps
a. App is just a DB with data
b. View is a representation of data from different Apps
c. While Apps just store data, Views help us to get work done
- Make all views 1-click accessible on the Solution level (Like Apps)
I believe that view should be under Solution in the hierarchy. Apps should not contain views and should be renamed in DB or Tables
I like how fibery.io do that
Cheyenne at MassiveReach
I definitely think there is some merit to this level of thinking. I do find myself "losing" multi-app views. In an MVC framework you definitely have the Model (or App in SS case) separated from but informing the View. I imagine Automations in a well-oiled SS implementation would e the Controller part.