In previous weeks, I've analyzed several libraries and frameworks that augment the client with AJAX capabilities. Vue.js
Alpine.js
HTMX
Vaadin In this post, I'll compare them across several axes. Analysis Frontend skills:
Remember that I started this series from the point of view of a backend developer. In this section, I grade how much you need to know about client technologies to complete the job.


Team organization:
In the introduction, I hinted that the decoupling of frontend and backend teams profoundly impacted projects. Each team is fast on its own, and they can parallelize their work, but integrating the two can double the initial development time. Here, I grade how easy it is to integrate frontend and backend.


Ease of setup:
How easy it is to set up the tool from the backend.


Ease of styling:
Backend developers are not designers by default. Does the tool offer a default, at least average-looking style? How hard is it to create one? For all intents and purposes, Vue.js and Alpine.js are similar; I'll refer to them as JavaScript frameworks. JavaScript frameworks

HTMX

Vaadin



Frontend skills

Need the full HTML, JavaScript (it's in the name), and CSS tryptic

Only need HTML and CSS, HTMX takes care of the JavaScript burden

No frontend skills needed, Vaadin takes care of everything



Team organization

Depends on each developer's skills:* Either separation between frontend and backend development* Or they can develop their use case from the database to the UI

Depends on each developer's skills:* Either separation between frontend and backend development* Or they can develop their use case from the database to the UI

Each developer can develop their use case from the database to the UI



Ease of setup

* Thanks to WebJars, you can manage dependencies in the POM* WebJars Locator allows not specifying the version number in the HTML* You still need to reference each library in the HTML page

* Thanks to WebJars, you can manage dependencies in the POM* WebJars Locator allows not specifying the version number in the HTML* You still need to reference each library in the HTML page

Everything is in the POM. As Vaadin generates the whole frontend, you don't need additional setup



Ease of styling

No default; one needs to use an existing library, e.g., Bootstrap or create their own

No default; one needs to use an existing library, e.g., Bootstrap or create their own

Vaadin comes bundled with the Lumo theme. Other themes are available in the Vaadin Add-ons Directory, such as the Parity Theme. Applying a theme is as easy as setting it as a dependency and adding an annotation.Creating a custom theme is no small potatoes, though. You can ease the task by starting from an existing one and changing it bit by bit. Vaadin, the company, also provides custom themes for a fee. Time to choose If you are still unsure how to proceed, here are my recommendations. If you're working on a regular business app, e.g., forms, choose Vaadin. Business apps are Vaadin's primary use case and will shine there, immensely increasing productivity. If your app requires good-looking visualization widgets, choose Vaadin as well. For example, its Vaadin Charts component is truly amazing. Note that it's commercially licensed, though. If you want to offer an API from the start, choose Vue or Alpine. While it's possible to use HTMX or Vaadin, it doesn't make sense in this context. I also emphasize "from the start": everybody plans to offer an API at some point, but most never do. The possible productivity potential you plan to have in the future is not worth the guaranteed productivity in the next months. The same goes for distributing your app over several channels - from the start (bis repetita placent). If you're in none of these situations, it's time to go into more detail. Are your developers skilled in frontend technologies? Are they willing to learn to close the gap? Will you need these skills in the near future? These are a couple of questions that can help you decide which way to go. This post concludes my series on AJAX and SSR. I hope you had as much fun reading it as I did writing it. The complete source code for this post can be found on GitHub: https://github.com/ajavageek/compare-frontends?embedable=true In previous weeks, I've analyzed several libraries and frameworks that augment the client with AJAX capabilities. Vue.js Alpine.js HTMX Vaadin Vue.js Vue.js Alpine.js Alpine.js HTMX HTMX Vaadin Vaadin In this post, I'll compare them across several axes. Analysis Frontend skills:
Remember that I started this series from the point of view of a backend developer. In this section, I grade how much you need to know about client technologies to complete the job. Team organization:
In the introduction, I hinted that the decoupling of frontend and backend teams profoundly impacted projects. Each team is fast on its own, and they can parallelize their work, but integrating the two can double the initial development time. Here, I grade how easy it is to integrate frontend and backend. Ease of setup:
How easy it is to set up the tool from the backend. Ease of styling:
Backend developers are not designers by default. Does the tool offer a default, at least average-looking style? How hard is it to create one? Frontend skills: Remember that I started this series from the point of view of a backend developer. In this section, I grade how much you need to know about client technologies to complete the job. Frontend skills: Remember that I started this series from the point of view of a backend developer. In this section, I grade how much you need to know about client technologies to complete the job. Team organization: In the introduction, I hinted that the decoupling of frontend and backend teams profoundly impacted projects. Each team is fast on its own, and they can parallelize their work, but integrating the two can double the initial development time. Here, I grade how easy it is to integrate frontend and backend. Team organization: In the introduction, I hinted that the decoupling of frontend and backend teams profoundly impacted projects. Each team is fast on its own, and they can parallelize their work, but integrating the two can double the initial development time. Here, I grade how easy it is to integrate frontend and backend. Ease of setup: How easy it is to set up the tool from the backend. Ease of setup: How easy it is to set up the tool from the backend. Ease of styling: Backend developers are not designers by default. Does the tool offer a default, at least average-looking style? How hard is it to create one? Ease of styling: Backend developers are not designers by default. Does the tool offer a default, at least average-looking style? How hard is it to create one? For all intents and purposes, Vue.js and Alpine.js are similar; I'll refer to them as JavaScript frameworks. JavaScript frameworks

HTMX

Vaadin



Frontend skills

Need the full HTML, JavaScript (it's in the name), and CSS tryptic

Only need HTML and CSS, HTMX takes care of the JavaScript burden

No frontend skills needed, Vaadin takes care of everything



Team organization

Depends on each developer's skills:* Either separation between frontend and backend development* Or they can develop their use case from the database to the UI

Depends on each developer's skills:* Either separation between frontend and backend development* Or they can develop their use case from the database to the UI

Each developer can develop their use case from the database to the UI



Ease of setup

* Thanks to WebJars, you can manage dependencies in the POM* WebJars Locator allows not specifying the version number in the HTML* You still need to reference each library in the HTML page

* Thanks to WebJars, you can manage dependencies in the POM* WebJars Locator allows not specifying the version number in the HTML* You still need to reference each library in the HTML page

Everything is in the POM. As Vaadin generates the whole frontend, you don't need additional setup



Ease of styling

No default; one needs to use an existing library, e.g., Bootstrap or create their own

No default; one needs to use an existing library, e.g., Bootstrap or create their own

Vaadin comes bundled with the Lumo theme. Other themes are available in the Vaadin Add-ons Directory, such as the Parity Theme. Applying a theme is as easy as setting it as a dependency and adding an annotation.Creating a custom theme is no small potatoes, though. You can ease the task by starting from an existing one and changing it bit by bit. Vaadin, the company, also provides custom themes for a fee. JavaScript frameworks

HTMX

Vaadin Frontend skills

Need the full HTML, JavaScript (it's in the name), and CSS tryptic

Only need HTML and CSS, HTMX takes care of the JavaScript burden

No frontend skills needed, Vaadin takes care of everything Team organization

Depends on each developer's skills:* Either separation between frontend and backend development* Or they can develop their use case from the database to the UI

Depends on each developer's skills:* Either separation between frontend and backend development* Or they can develop their use case from the database to the UI

Each developer can develop their use case from the database to the UI Ease of setup

* Thanks to WebJars, you can manage dependencies in the POM* WebJars Locator allows not specifying the version number in the HTML* You still need to reference each library in the HTML page

* Thanks to WebJars, you can manage dependencies in the POM* WebJars Locator allows not specifying the version number in the HTML* You still need to reference each library in the HTML page

Everything is in the POM. As Vaadin generates the whole frontend, you don't need additional setup Ease of styling

No default; one needs to use an existing library, e.g., Bootstrap or create their own

No default; one needs to use an existing library, e.g., Bootstrap or create their own

Vaadin comes bundled with the Lumo theme. Other themes are available in the Vaadin Add-ons Directory, such as the Parity Theme. Applying a theme is as easy as setting it as a dependency and adding an annotation.Creating a custom theme is no small potatoes, though. You can ease the task by starting from an existing one and changing it bit by bit. Vaadin, the company, also provides custom themes for a fee. JavaScript frameworks HTMX Vaadin JavaScript frameworks JavaScript frameworks HTMX HTMX Vaadin Vaadin Frontend skills Need the full HTML, JavaScript (it's in the name), and CSS tryptic Only need HTML and CSS, HTMX takes care of the JavaScript burden No frontend skills needed, Vaadin takes care of everything Frontend skills Frontend skills Need the full HTML, JavaScript (it's in the name), and CSS tryptic Need the full HTML, JavaScript (it's in the name), and CSS tryptic Only need HTML and CSS, HTMX takes care of the JavaScript burden Only need HTML and CSS, HTMX takes care of the JavaScript burden No frontend skills needed, Vaadin takes care of everything No frontend skills needed, Vaadin takes care of everything Team organization Depends on each developer's skills:* Either separation between frontend and backend development* Or they can develop their use case from the database to the UI Depends on each developer's skills:* Either separation between frontend and backend development* Or they can develop their use case from the database to the UI Each developer can develop their use case from the database to the UI Team organization Team organization Depends on each developer's skills:* Either separation between frontend and backend development* Or they can develop their use case from the database to the UI Depends on each developer's skills: * Either separation between frontend and backend development* Or they can develop their use case from the database to the UI Depends on each developer's skills:* Either separation between frontend and backend development* Or they can develop their use case from the database to the UI Depends on each developer's skills: * Either separation between frontend and backend development* Or they can develop their use case from the database to the UI Each developer can develop their use case from the database to the UI Each developer can develop their use case from the database to the UI Ease of setup * Thanks to WebJars, you can manage dependencies in the POM* WebJars Locator allows not specifying the version number in the HTML* You still need to reference each library in the HTML page * Thanks to WebJars, you can manage dependencies in the POM* WebJars Locator allows not specifying the version number in the HTML* You still need to reference each library in the HTML page Everything is in the POM. As Vaadin generates the whole frontend, you don't need additional setup Ease of setup Ease of setup * Thanks to WebJars, you can manage dependencies in the POM* WebJars Locator allows not specifying the version number in the HTML* You still need to reference each library in the HTML page * Thanks to WebJars, you can manage dependencies in the POM* WebJars Locator allows not specifying the version number in the HTML* You still need to reference each library in the HTML page * Thanks to WebJars, you can manage dependencies in the POM* WebJars Locator allows not specifying the version number in the HTML* You still need to reference each library in the HTML page * Thanks to WebJars, you can manage dependencies in the POM* WebJars Locator allows not specifying the version number in the HTML* You still need to reference each library in the HTML page Everything is in the POM. As Vaadin generates the whole frontend, you don't need additional setup Everything is in the POM. As Vaadin generates the whole frontend, you don't need additional setup Ease of styling No default; one needs to use an existing library, e.g., Bootstrap or create their own No default; one needs to use an existing library, e.g., Bootstrap or create their own Vaadin comes bundled with the Lumo theme. Other themes are available in the Vaadin Add-ons Directory, such as the Parity Theme. Applying a theme is as easy as setting it as a dependency and adding an annotation.Creating a custom theme is no small potatoes, though. You can ease the task by starting from an existing one and changing it bit by bit. Vaadin, the company, also provides custom themes for a fee. Ease of styling Ease of styling No default; one needs to use an existing library, e.g., Bootstrap or create their own No default; one needs to use an existing library, e.g., Bootstrap or create their own No default; one needs to use an existing library, e.g., Bootstrap or create their own No default; one needs to use an existing library, e.g., Bootstrap or create their own Vaadin comes bundled with the Lumo theme. Other themes are available in the Vaadin Add-ons Directory, such as the Parity Theme. Applying a theme is as easy as setting it as a dependency and adding an annotation.Creating a custom theme is no small potatoes, though. You can ease the task by starting from an existing one and changing it bit by bit. Vaadin, the company, also provides custom themes for a fee. Vaadin comes bundled with the Lumo theme. Other themes are available in the Vaadin Add-ons Directory , such as the Parity Theme . Applying a theme is as easy as setting it as a dependency and adding an annotation. Creating a custom theme is no small potatoes, though. You can ease the task by starting from an existing one and changing it bit by bit. Vaadin, the company, also provides custom themes for a fee. Vaadin Add-ons Directory Parity Theme Time to choose If you are still unsure how to proceed, here are my recommendations. If you're working on a regular business app, e.g. , forms, choose Vaadin. Business apps are Vaadin's primary use case and will shine there, immensely increasing productivity. e.g. If your app requires good-looking visualization widgets, choose Vaadin as well. For example, its Vaadin Charts component is truly amazing. Note that it's commercially licensed, though. Vaadin Charts If you want to offer an API from the start , choose Vue or Alpine. While it's possible to use HTMX or Vaadin, it doesn't make sense in this context. I also emphasize "from the start": everybody plans to offer an API at some point, but most never do. The possible productivity potential you plan to have in the future is not worth the guaranteed productivity in the next months. from the start The same goes for distributing your app over several channels - from the start ( bis repetita placent ). from the start bis repetita placent If you're in none of these situations, it's time to go into more detail. Are your developers skilled in frontend technologies? Are they willing to learn to close the gap? Will you need these skills in the near future? These are a couple of questions that can help you decide which way to go. This post concludes my series on AJAX and SSR. I hope you had as much fun reading it as I did writing it. The complete source code for this post can be found on GitHub: https://github.com/ajavageek/compare-frontends?embedable=true https://github.com/ajavageek/compare-frontends?embedable=true

Walkthroughs, tutorials, guides, and tips. This story will teach you how to do something new or how to do something better.

DuckDB in Action: A Review

What You Need to Know About Vaadin - The Battery-Included Server-Side AJAX Framework

Read all my posts!

Comparing Vue.js, Alpine.js, HTMX, and Vaadin: A Backend Developer's Guide to AJAX and SSR

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

16 Best Practices For Securing Your APIs with Apache APISIX - Part 1

AJAX in a nutshell

Ajax Interacting With Security Systems Champion: Type 5 Certification Scheme

An Intro to Data Tables On Rails

Consume REST Services with AJAX and CSRF protection in Django

Eliminating Event Storms With Debouncing in JavaScript

16 Best Practices For Securing Your APIs with Apache APISIX - Part 1

AJAX in a nutshell

Ajax Interacting With Security Systems Champion: Type 5 Certification Scheme

An Intro to Data Tables On Rails

Consume REST Services with AJAX and CSRF protection in Django

Eliminating Event Storms With Debouncing in JavaScript

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps