Hacker News Reader

Comment by gorbypark | Hacker News Reader

Seems interesting and is apparently built on top of React Native. Obviously this is billed as a “server side streaming UI”, but it’s already possible to chunk the React Native bundle and deliver portions on demand (per route/screen, for example). Of course that’s a bit different than generating the XML for the screen on the fly, but more or less gives most of the benefits this would offer in terms of small initial downloads and OTA updates.

View on HN

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?

Local 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.

Q: 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?

It 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

Great work on this! Seems very commonsensical and futuristic to me.

I 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.

Reply on news.ycombinator.com