Developer Experience at Vaadin

Sami Ekblad
Sami Ekblad
On Mar 12, 2020 5:20:22 PM

Have you felt frustrated about something lately and think that the problem is with Vaadin? Ok, we’d like to help you with that. Before we can make things better, we first need to know what you think. As a developer, what is your experience with Vaadin? We invite you to tell us, either through or, and hope that you do.

Because Vaadin is a web user interface tool, we actually have two distinct groups of users. First, the end users, people who use web applications and sites built with Vaadin. Second, developers, people who build these applications. Since you ended up here, you are most likely a developer.

But why are developers considered secondary? As a developer am I not important? Yes, you are, but primarily from the perspective of the value you build for end users. You also consider your end users to be your most important target group, right? And this is why we do too.

However, without your contribution, we cannot reach the end user. You build the applications, make them work properly, and hopefully also enjoy doing it. This is why, today, we focus on you and your developer experience (DX).

A framework to understand/measure how developers feel about Vaadin

The way we see Vaadin is different to the way you do. To understand and address the plethora of needs and requirement developers have for a framework, we have split the product experience along the adaptation journey. DX-at-Vaadin

As you can see, we use time, or rather time investment, as the critical factor. The time periods are not exact, but rather an approximation of how much time you can expect to spend doing something with Vaadin. If you only have a certain amount of time, what can you expect to achieve in that time?

During the initial minutes, we hope you can get an idea of where and when to use Vaadin. In the second stage, we expect you to be able to test it yourself and see how well it works for you, and so on, until the full developer journey of application development with Vaadin is addressed.

Collect feedback, measure and improve

As we said before, the most important thing is for us to know how we are doing. This we can’t do without you. The time has come for you to make some noise and let your load voices be heard.

In addition to collecting feedback, we also measure key areas in Vaadin. These are the things that we think should be awesome (or at least not suck) for a tool to qualify as a good tool for developers. To determine this, we created a survey that we use when conducting Vaadin user tests. Our aim is to understand the developer experience in important Vaadin areas. Currently, the “happiness” of Vaadin-14 users for the “first 90 minutes of use”, according to the survey, is 70.2%. This was the aggregated response of developers trying Vaadin 14 for the first time for different key experience areas. We want to increase this number, by working on the product itself and all related things, like our start page.

So, if you recently tried out Vaadin, please help us by taking the survey here

If you haven’t tried Vaadin yet, today is a good day to do that. Head over to, choose a project template, and build your first Vaadin application in 90 minutes or less.

Sami Ekblad
Sami Ekblad
Sami Ekblad is one of the original members of the Vaadin team. As a DX lead he is now working as a developer advocate, to help people the most out of Vaadin tools. You can find many add-ons and code samples to help you get started with Vaadin. Follow at – @samiekblad
Other posts by Sami Ekblad