Is it more idiomatic to start with the client state (model) or put more effort on the backend ?
Sorry for the extremely vague question btw.
#when developing lustre with ssr, where do you all start ?
sly laurel
dreamy nebula
my unhelpful answer is It Depends ™️
sly laurel
to be honest it is kinda helpful still 😄. the elm architecture is so awesome and incredibly confusing at the same time, i think i just need to start and understand it more as i code.
anyway, thank you!
dreamy nebula
i woudl tend to start on the client state but im a frontendy person so thats the bit i know best. if you can start building out your backend logic with just static rendering then i would start there, but if you need an interactive client for your backend to be useful maybe starting with the client is the best choice?
gloomy widget
A couple of use cases that might prefer one or the other:
-
A photo gallery. You need to dynamically generate a lot of pages and serve a lot of files, and most functionality is CRUD operations and standard HTML forms. You might want client-side interactivity later for search suggestions, toasts, progress bars, etc
-
A photo editor. Almost all of the functionality is driven by client-side interactions, but you might want to add backend functionality later, like login, saving to the cloud, etc
I think the lines get a little blurrier when you start considering things like server components and stuff like that, but when deciding where to start building from, this is how I'd do it