4 ms·
It's often known as Server-Driven UI. It's basically a generalization of Server-Side rendering. I'm interested in knowing the limitations of that approach bes
by aatd86 4y ago
It's often known as Server-Driven UI.
It's basically a generalization of Server-Side rendering.
I'm interested in knowing the limitations of that approach besides the connectivity requirement.
Are complex data-based interactions easily implementable?
- adamstep 4y agoLocal interactions can be achieved with this approach by building custom components. However, a limitation of Server-driven UI is supporting interactions that update state across the entire app. For example, I wouldn’t use Hyperview or HTMX to implement a spreadsheet, where changing the value in one cell would trigger recalculations across the sheet.
- sibeliuss 4y agoQ: Since this is built on React Native, is it possible to build pages using Hyperview and then supplement them with stateful UI component trees using common RN libraries (eg, Redux)? Like, mix approaches?
- adamstep 4y agoIt is possible. We've built apps this way (integrating Hyperview into an existing RN app). With custom behaviors, you can have actions in Hyperview screens trigger Redux actions: https://hyperview.org/docs/reference_custom_behaviors https://hyperview.org/docs/reference_custom_behaviors
- sibeliuss 4y agoGreat work on this! Seems very commonsensical and futuristic to me.
- JoeyJoJoJr 4y agoI wonder if there is some mechanism that could achieve app wide state updates by performing a “refresh” after a mutation, and hyperview/HTMX handles the integration of the the changeset.