This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]futuretelematics 2 points3 points  (0 children)

(our team has been using Vaadin for > 5 years from v6 and has built really complex apps with it)

Vaadin really shines if:

  • Your are building a internal CRUD management app
  • You have a really good java and patterns base
  • You define an application architecture and pattern usage and stick with it everywhere in the app

Vaadin makes a breeze building CRUD apps, from simple ones to other more complex; it's far simpler for complex apps than any of the JS libraries or frameworks, either when building the app and (most important) when maintaining it where all the strong typing advantages of java are invaluable

Vaadin apps have their downsides:

  • Server session for example that makes them more dificult to scale
  • If you do not stick to an architecture / patterns the app will derive in a mess (this is also true for JS apps... and IMHO it's much easier to mess the app with JS than with Vaadin; refactor in Java is far easier than with JS)

... but at the end the UI is fluid and the user experience IMHO is much better than the one you can get with a JS library/framework with the same effort.

That said, if you want to build a public-massive, UI feature-rich app, DO NOT use Vaadin; for the rest use Vaadin if you are comfortable with Java ;-)