Time is a valuable resource... That's why I dedicated myself to creating this content with the time I had available. Should there be any discrepancies with the original sources, please consider my main goal: to contribute and help all readers.
This article is part of the series 'Towards Vaadin Developer Certification,' which aims to explain the fundamentals of Vaadin as I study for this certification. The topics covered here are part of the 'Vaadin Developer' Certification curriculum. The content was created based on my personal notes and studies for this certification.
Vaadin: A Democratic Framework
When we expand our definition of "fields" beyond just input components, we discover one of Vaadin's most powerful features - its democratic approach to UI development. This framework allows you to integrate components from outside the Vaadin ecosystem seamlessly.
Despite this openness, it's worth noting that Vaadin already provides dozens of robust components. In fact, it's relatively rare to find situations where you need to look beyond Vaadin's native offerings.
This comprehensive library isn't surprising when you consider that Vaadin has been evolving for over 20 years - making it old enough to be the "father" of Angular and React (or at least their uncle). Throughout these two decades, the Vaadin team has continuously perfected and expanded their component library.
Understanding the Concept of Fields
Up until now, we've extensively discussed fields in Vaadin. However, it's crucial to clarify that we've primarily been referring to "Input Fields." Whenever we mention "fields," we're typically talking about components that hold values and properties.
But let's broaden our perspective. In the Vaadin ecosystem, the term "fields" doesn't necessarily always refer to input fields. The concept extends to various UI components, which opens up fascinating possibilities for interface development.
The Creative Drive of Necessity
Human beings possess a curious tendency to innovate beyond what's already sufficient. This creative impulse is one of our most wonderful attributes. The same principle applies to Vaadin development - sometimes we need to venture beyond the established boundaries and incorporate external components.
This is where concepts like "custom components" and "web components" become relevant. Custom components follow a straightforward concept: they're compound elements that combine either exclusively Vaadin components, or integrate Web Components with Vaadin components, or consist entirely of Web Components working together.
Disclaimer
This content, although based on my studies and notes acquired during the Vaadin 24 certification process, does not intend to be exhaustive. For a deeper understanding of the topic, I recommend consulting the official Vaadin 24 documentation and the materials from the certification courses.
Additionally, I would like to inform you that I used Artificial Intelligence tools to assist in the modeling and structuring of this article. However, the writing and the original content are exclusively authored by me, hence AI was utilized as a helpful tool, not as a replacement for my own authorship.
Authors
Paulo B. A. is an 'Oracle Certified Java Developer' and 'Spring Certified Professional' with a deep passion for Vaadin Flow. He crafts UIs with Vaadin and strives to make it the leading frontend framework for full-stack Java developers worldwide. He loves teaching, sharing knowledge, and creating content. While he enjoys learning theory through certifications, he always advocates for a practical approach.
- Linkedin.com/in/pbalves
- X.com/p_b_alves
- Mastodon.social/@pbalves
Staff Writer: Fábio A. P. is a technology enthusiast, self-taught writer, and scholar of society's relationship with technology. Passionate about sharing insights, he provides reliable perspectives on how technology shapes our lives. With clear and precise writing, Fábio simplifies complex topics, empowering readers to navigate the digital age with confidence.
