Best practices for structuring Vaadin Flow code?

Most (if not all) Vaadin enterprise grade applications are built in non-accessible private repositories of companies… so it’s pretty hard to get you an example.

Some good examples publicly available are from:

In the end most of your questions can be answered with “it depends” and “how you like it”. Even building views in the constructor vs. life circle is a big topic by its own. Probably the only easy answer I can give you: put your css in your theme and don’t (overuse) the getStyle()-API - this can quickly get really messy.

1 Like