Whats the catch with vaadin hilla instead of flow

Question

I develop webapps with vaadin and flow for some time now (together with spring boot) and just stumbled across hilla, a new vaadin 'addon' or project... (www.hilla.dev).

I know that flow and vaadin use typescript for some things but I never needed to dig deeper into this meta-layer between my java backend and the generated html/js/css things...

So I ask myself what's the use of hilla to make my life easier? Or is hilla better suited for people coming from javascript & typescript to vaadin instead of the other way around?

Answer 1

Hilla is the new name of vaadin-fusion.

In short:

Flow= Java in Backend and Frontend JS generated at runtime

Hilla = Java in the Backend + Typescript Frontend

So if you love typescript and css Hilla is good for you. If you are a java Fan (as myself) Vaadin Flow is the way to go (Or stay)

https://vaadin.com/blog/renaming-fusion

Answer 2

In hilla you use vaadin as a bridge. That means you can annotate endpoints and vaadin generate a ts class that give you a easy way to access the backend. It also generate for any type that are used at the endpoints a ts object, including constraints. With the Binder object you have a comfortable solution to validate the input data.

Customizing existing webcomponentsor write a new one is with hilla way more easy than with pure vaadin.

Another benefit is, that hilla don't need for every user interaction a request to the backend.

Hilla also allows you to build a PWA with offline support.