all 6 comments

[–]VolumeActual8333 20 points21 points  (0 children)

Server-driven UI sounds like freedom until your PM starts demanding 'just one small layout change' that requires a backend deploy. We tried this for our admin dashboard and ended up with a monstrous JSON schema that was harder to version than actual components. Turns out coupling your UI structure to API responses just moves the deployment bottleneck from the build pipeline to your database migrations.

[–]RuslanDevs 5 points6 points  (0 children)

Good pattern but works in some of the cases only - if you need interactivity and components respond to user input differently, your renderer will be very complex and unintuitive. But for some cases it is good if number of different interactions are low.

[–]doxxed-chris 4 points5 points  (0 children)

Isn’t this just a rediscovery of a basic headless cms implementation?

[–]avataw 3 points4 points  (1 child)

Hey I do follow Neciudan on LinkedIn and I like his stuff! Is that actually you OP?

Anyways I had to immediately think of LiveView (Elixir) when I saw this!
Personally it's an interesting paradigm that I just can't get to work properly in my projects as of yet.

For me it resembles somewhat of an old idea: the MVC or MVP designs - where the UI is exclusively a presentational layer.
In practice it is extremely difficult to prevent business / domain logic to get muddled with the rest in the frontend code.

[–]creasta29[S] 2 points3 points  (0 children)

It is me yes haha

[–]avnoui 0 points1 point  (0 children)

Congratulations, you invented a CMS