I used to have this weird thought experiment: what if a front-end is just additional "views" (think of SQL views) of application data, but scoped by say a user

I used to have this weird thought experiment: what if a front-end is just additional "views" (think of SQL views) of application data, but scoped by say a user or org. UI event handlers are just a way of mutating application data and/or the "views" of application data. Renderers should consume this "view" and render to their platform (browser, android, desktop, etc) and just proxy back UI events. #1 Such system will mandate a data mutation contract to be defined. Both "back-end" as well as "view" related code will use the same contracts to change application data. #2 Such a tech will be batteries included, where one language/framework will take care of business logic both in front-end as well as back-end. #3 There won't be ten different layers to touch, when a change happens. #4 Development teams will be all full-stack, i.e no distinction between front-end & back-end teams. It's all just business logic at the core. Will facilitate more work with smaller teams. Of course I haven't thought through this fully, for example what are animations in such a system? But it sure is interesting to think about.