Flow 1.0 Beta 8

Vaadin Flow 1.0.0.beta8 is a prerelease version for evaluating the enhancements mentioned below. With subsequent beta releases we may change things based on your feedback, and that may lead to API breaking changes.

Vaadin Flow 1.0.0.beta8

Flow is a new Java web framework for creating UIs using Java or HTML. Flow handles everything related to communication between and client and server and makes it possible to create UIs using the desired abstraction level you choose. It has all the capabilities you need to build a modern web app: from high level APIs for structuring your applications and binding data to it, into taking full control over the DOM and communication with HTML templates.

Flow is a part of the Vaadin platform. For information and helpful resources like documentation and examples on Vaadin Flow, please visit the Flow page vaadin.com/flow.

Enhancements in the new Prerelease

• Spring add-on was moved into a separate repository: https://github.com/vaadin/spring

Now this repository's master branch contains Vaadin 10 version of the add-on. Refer to the Readme for details and older versions.

• #2919 Update I18NProvider API

The I18NProvider API reworked to be more convenient for users.

• #3752 Custom PushConnection are now possible to configure

• #3606 Text class now implements HasText interface

• #3944 Gather and report framework usage statistics

• #3675 Added an API for setting Dark Theme

• #3847 ThemableLayout has new api for controlling box-sizing property.

• #3914 MultiSelect API was ported from the Framework 8

Bug Fixes since Previous Prerelease

• #3924 Fix WebLogic support

The WebLogic 12 application deployment issues were fixed.

• #3501 Add a hash to production mode fragments to allow a newer versions to be visible

• #3839 Fix Undertow support

Breaking changes introduced in the newest Prerelease

• #2844 Remove browser-specific style names from the body

Now there are no more v- prefixed styles added to the body, since all modern browsers are able to support the CSS that is used by Flow.

• #3829 Has*Listener interfaces were renamed to the *Notifier ones

• #2594 Deprecated Router API was removed

Documentation added since last Prerelease

• Integrating components in a PolymerTemplate

All documentation can be found

See complete list of changes since previous beta version

Supported Technologies

See the Vaadin platform release notes for browser, server and Java support level.

Known Limitations

• Template-in-Template feature has some limitations
• There is no CDI support #456
• There is no Portal/OSGi support #455

Flow 1.0 Feature Highlights

Using Components to build UIs with only Java

With Flow you to can compose UIs using only Java on the server side. You can use existing components or create your own by creating the DOM from the server side. See the relevant documentation:

• Using Vaadin Components
• Creating New Components and the Element API

Integrating Web Components

Flow allows you to integrate web components and consume them from server side Java. See the web components documentation for more information.

Router

Router is a core concept in Flow, enabling navigation for your website or web app. It is based on HTML5 History API, and makes it possible to for the user to navigate pages back and forward, and keep the page state intact. See the router documentation for more information.

Binding Data to Components

Flow allows you to easily bind your business data to the UI components. You can bind the forms to the business objects by using the Binder, see documentation for more information. For showing a list of data (eg. a database table) on the UI, you can use the DataProvider. See documentation for more information.

Creating UIs Declaratively with Polymer Templates

With Flow you can take full control of building the DOM and the communication by using HTML templates. We recommend using Polymer templates as they bring lots of helpful capabilities on top of the native HTML. See documentation for more information.

Theming Applications

Flow has support for customizing the look and feel of your applications with css, html custom styles or by customizing the ready made Themes provided for Vaadin Components. See the documentation for more information.

Spring Integration

Flow comes with a Spring integration, and you can use it with Spring 5 or Spring Boot 2. Please see the documentation for more information.

Getting Started

For getting started with Vaadin Flow, please see vaadin.com/start where there are three types of examples available:

• Bakery App Starter for Flow and Spring - a full stack example application with Flow and Spring Boot with heavy focus on great UX
• Beverage Buddy App Starter for Flow - a small example app that highlights the basic features of Flow
• Project Base for Flow and Project Base for Flow and Spring
  • A base for your project with some placeholder files available and dependencies available
    All the starters bring the Flow dependency via the Vaadin platform, which is the recommended way for using Flow.

From Flow getting started documentation you can find a step-by-step tutorial.

Flow 1.0 Beta7

Vaadin Flow 1.0.0.beta7 is a prerelease version for evaluating the enhancements mentioned below. With subsequent beta releases we may change things based on your feedback, and that may lead to API breaking changes.

Vaadin Flow 1.0.0.beta7

Flow is a new Java web framework for creating UIs using Java or HTML. Flow handles everything related to communication between and client and server and makes it possible to create UIs using the desired abstraction level you choose. It has all the capabilities you need to build a modern web app: from high level APIs for structuring your applications and binding data to it, into taking full control over the DOM and communication with HTML templates.

Flow is a part of the Vaadin platform. For information and helpful resources like documentation and examples on Vaadin Flow, please visit the Flow page vaadin.com/flow.

Enhancement in the new Prerelease

• #3538 Make setEnabled(boolean) a server-side security feature.

From now on, components implementing HasEnabled can be completely blocked from interacting with the server-side application. Before this improvement, calling setEnabled(false) would only set the client-side disabled attribute for the component, which can be easily bypassed by the users. Also, disabling a parent component now disables its child components.

Bug Fixes since Previous Prerelease

• #3860 Exceptions thrown by HasUrlParameter correctly redirect to a matching HasErrorParameter view

Documentation updated since last Prerelease

• Component Enabled State

All documentation can be found

See complete list of changes since previous beta version

Supported Technologies

See the Vaadin platform release notes for browser, server and Java support level.

Known Limitations

• Template-in-Template feature has some limitations
• There is no CDI support #456
• There is no Portal/OSGi support #455

Flow 1.0 Feature Highlights

Using Components to build UIs with only Java

With Flow you to can compose UIs using only Java on the server side. You can use existing components or create your own by creating the DOM from the server side. See the relevant documentation:

• Using Vaadin Components
• Creating New Components and the Element API

Integrating Web Components

Flow allows you to integrate web components and consume them from server side Java. See the web components documentation for more information.

Router

Router is a core concept in Flow, enabling navigation for your website or web app. It is based on HTML5 History API, and makes it possible to for the user to navigate pages back and forward, and keep the page state intact. See the router documentation for more information.

Binding Data to Components

Flow allows you to easily bind your business data to the UI components. You can bind the forms to the business objects by using the Binder, see documentation for more information. For showing a list of data (eg. a database table) on the UI, you can use the DataProvider. See documentation for more information.

Creating UIs Declaratively with Polymer Templates

With Flow you can take full control of building the DOM and the communication by using HTML templates. We recommend using Polymer templates as they bring lots of helpful capabilities on top of the native HTML. See documentation for more information.

Theming Applications

Flow has support for customizing the look and feel of your applications with css, html custom styles or by customizing the ready made Themes provided for Vaadin Components. See the documentation for more information.

Spring Integration

Flow comes with a Spring integration, and you can use it with Spring 5 or Spring Boot 2. Please see the documentation for more information.

Getting Started

For getting started with Vaadin Flow, please see vaadin.com/start where there are three types of examples available:

• Bakery App Starter for Flow and Spring - a full stack example application with Flow and Spring Boot with heavy focus on great UX
• Beverage Buddy App Starter for Flow - a small example app that highlights the basic features of Flow
• Project Base for Flow and Project Base for Flow and Spring
  • A base for your project with some placeholder files available and dependencies available
    All the starters bring the Flow dependency via the Vaadin platform, which is the recommended way for using Flow.

From Flow getting started documentation you can find a step-by-step tutorial.

Flow 1.0 Beta6

Vaadin Flow 1.0.0.beta6 is a prerelease version for evaluating the enhancements mentioned below. With subsequent beta releases we may change things based on your feedback, and that may lead to API breaking changes.

Vaadin Flow 1.0.0.beta6

Flow is a new Java web framework for creating UIs using Java or HTML. Flow handles everything related to communication between and client and server and makes it possible to create UIs using the desired abstraction level you choose. It has all the capabilities you need to build a modern web app: from high level APIs for structuring your applications and binding data to it, into taking full control over the DOM and communication with HTML templates.

Flow is a part of the Vaadin platform. For information and helpful resources like documentation and examples on Vaadin Flow, please visit the Flow page vaadin.com/flow.

Breaking changes introduced in the newest Prerelease

• #3598 Remove CustomElementRegistry
• #3748 Apply Lumo theme by default if it is available on the classpath
• #3749 Set size for body element by default

From now on, Flow applications will use Lumo Theme by default, which means @Theme annotation will only be needed when integrating a customized theme. Same with @BodySize annotation, since flow 1.0-beta6, the size property of the body element will set to height = "100vh", width = "100vw" for flow apps by default, users can use the annotation to customize. Besides, you can configure Java instances to be created for custom elements inside your HTML template file with the @Uses annotation.

• Note that the Lumo theme will be loaded by default if it is present in the classpath, which is true for applications that import vaadin-core as dependecy. Flow project bases have been updated to reflect both annotation changes.
• More information can be found from the documentation update listed below.

Bug Fixes since Previous Prerelease

• #3713 Improve the Element API to handle the existing content that the server doesn't know about
• #3796 fix the wrong value returned from PushConfigurationMap.getFallbackTransport (Thanks to @mcollovati )

Enhancement in the new Prerelease

• #3720 Support query parameters in RouterLink (Thanks to @heruan )

Documentation updated since last Prerelease

• Using sub-template from PolymerTemplate
• Navigation Lifecycle
• Using Component Themes
• Modifying the bootstrap page

All documentation can be found

See complete list of changes since previous beta version

Supported Technologies

See the Vaadin platform release notes for browser, server and Java support level.

Known Limitations

• Template-in-Template feature has some limitations
• There is no CDI support #456
• There is no Portal/OSGi support #455

Flow 1.0 Feature Highlights

Using Components to build UIs with only Java

With Flow you to can compose UIs using only Java on the server side. You can use existing components or create your own by creating the DOM from the server side. See the relevant documentation:

• Using Vaadin Components
• Creating New Components and the Element API

Integrating Web Components

Flow allows you to integrate web components and consume them from server side Java. See the web components documentation for more information.

Router

Router is a core concept in Flow, enabling navigation for your website or web app. It is based on HTML5 History API, and makes it possible to for the user to navigate pages back and forward, and keep the page state intact. See the router documentation for more information.

Binding Data to Components

Flow allows you to easily bind your business data to the UI components. You can bind the forms to the business objects by using the Binder, see documentation for more information. For showing a list of data (eg. a database table) on the UI, you can use the DataProvider. See documentation for more information.

Creating UIs Declaratively with Polymer Templates

With Flow you can take full control of building the DOM and the communication by using HTML templates. We recommend using Polymer templates as they bring lots of helpful capabilities on top of the native HTML. See documentation for more information.

Theming Applications

Flow has support for customizing the look and feel of your applications with css, html custom styles or by customizing the ready made Themes provided for Vaadin Components. See the documentation for more information.

Spring Integration

Flow comes with a Spring integration, and you can use it with Spring 5 or Spring Boot 2. Please see the documentation for more information.

Getting Started

For getting started with Vaadin Flow, please see vaadin.com/start where there are three types of examples available:

• Bakery App Starter for Flow and Spring - a full stack example application with Flow and Spring Boot with heavy focus on great UX
• Beverage Buddy App Starter for Flow - a small example app that highlights the basic features of Flow
• Project Base for Flow and Project Base for Flow and Spring
  • A base for your project with some placeholder files available and dependencies available
    All the starters bring the Flow dependency via the Vaadin platform, which is the recommended way for using Flow.

From Flow getting started documentation you can find a step-by-step tutorial.

Flow 1.0 Beta5

Vaadin Flow 1.0.0.beta5 is a prerelease version for evaluating the enhancements mentioned below. With subsequent beta releases we may change things based on your feedback, and that may lead to API breaking changes.

Vaadin Flow 1.0.0.beta5

Flow is a new Java web framework for creating UIs using Java or HTML. Flow handles everything related to communication between and client and server and makes it possible to create UIs using the desired abstraction level you choose. It has all the capabilities you need to build a modern web app: from high level APIs for structuring your applications and binding data to it, into taking full control over the DOM and communication with HTML templates.

Flow is a part of the Vaadin platform. For information and helpful resources like documentation and examples on Vaadin Flow, please visit the Flow page vaadin.com/flow.

Breaking changes introduced in the newest Prerelease

• #2492 Remove AngularTemplate from flow
• #3382 Rename the model converter concept to avoid confusion with Binder converters. ModelConverter was changed to ModelEncoder Change commit

Bug Fixes since Previous Prerelease

• #3649 Adjust cases each of the navigation observers are notified
• #3767 RadioButtonGroup is enabled when I setEnabled(false) in a grid
• #3713 Improve how the Element API deals with existing content that the server doesn't know about
• #43 Calling setText for Button appends the text to an existing caption
• #3758 Add support for @id without value
• #3628 Application run with Spring Boot Maven plugin does not discover all routes
• #3714 Mention semantic mismatch in @id javadocs
• #3741 Support JSR-356 websockets with Spring Boot
• #3648 Remove code duplication between NavigationStateRenderer and ErrorStateRenderer
• #3729 StateNode.runWhenAttached should accept SerializableConsumer
• #3042 Styling documentation is misleading

Documentation fixes

• #3042 Reword styling for getting started docs
• #3382 Update docs for ModelEncoders instead of ModelConverts
• #3347, #3042 Introduce a proper theming chapter
• #3628 Mention @route package scanning option in the docs
• #41 Extend doc for @id semantic
• #3435 Note on docs that two-way binding doesn't work for array properties

See complete list of changes since previous beta version

Supported Technologies

See the Vaadin platform release notes for browser, server and Java support level.

Known Limitations

• Template-in-Template feature has some limitations
• There is no CDI support #456
• There is no Portal/OSGi support #455

Flow 1.0 Feature Highlights

Using Components to build UIs with only Java

With Flow you to can compose UIs using only Java on the server side. You can use existing components or create your own by creating the DOM from the server side. See the relevant documentation:

• Using Vaadin Components
• Creating New Components and the Element API

Integrating Web Components

Flow allows you to integrate web components and consume them from server side Java. See the web components documentation for more information.

Router

Router is a core concept in Flow, enabling navigation for your website or web app. It is based on HTML5 History API, and makes it possible to for the user to navigate pages back and forward, and keep the page state intact. See the router documentation for more information.

Binding Data to Components

Flow allows you to easily bind your business data to the UI components. You can bind the forms to the business objects by using the Binder, see documentation for more information. For showing a list of data (eg. a database table) on the UI, you can use the DataProvider. See documentation for more information.

Creating UIs Declaratively with Polymer Templates

With Flow you can take full control of building the DOM and the communication by using HTML templates. We recommend using Polymer templates as they bring lots of helpful capabilities on top of the native HTML. See documentation for more information.

Theming Applications

Flow has support for customizing the look and feel of your applications with css, html custom styles or by customizing the ready made Themes provided for Vaadin Components. See the documentation for more information.

Spring Integration

Flow comes with a Spring integration, and you can use it with Spring 5 or Spring Boot 2. Please see the documentation for more information.

Getting Started

For getting started with Vaadin Flow, please see vaadin.com/start where there are three types of examples available:

• Bakery App Starter for Flow and Spring - a full stack example application with Flow and Spring Boot with heavy focus on great UX
• Beverage Buddy App Starter for Flow - a small example app that highlights the basic features of Flow
• Project Base for Flow and Project Base for Flow and Spring
  • A base for your project with some placeholder files available and dependencies available
    All the starters bring the Flow dependency via the Vaadin platform, which is the recommended way for using Flow.

From Flow getting started documentation you can find a step-by-step tutorial.

Flow 1.0 Beta4

Vaadin Flow 1.0.0.beta4 is a prerelease version for evaluating the enhancements mentioned below. With subsequent beta releases we may change things based on your feedback, and that may lead to API breaking changes.

Vaadin Flow 1.0.0.beta4

Flow is a new Java web framework for creating UIs using Java or HTML. Flow handles everything related to communication between and client and server and makes it possible to create UIs using the desired abstraction level you choose. It has all the capabilities you need to build a modern web app: from high level APIs for structuring your applications and binding data to it, into taking full control over the DOM and communication with HTML templates.

Flow is a part of the Vaadin platform. For information and helpful resources like documentation and examples on Vaadin Flow, please visit the Flow page vaadin.com/flow.

Breaking changes introduced in the newest Prerelease

• #3678 Remove confusing leftovers from the experiment with fluent component APIs (ComponentSupplier was removed)

Bug Fixes since Previous Prerelease

• #3701 Don’t add scroll=auto to body

• #3732 Exception after application startup with beta3

• #3647 Prevention of reentrant renavigation is broken in multiple related ways

• #3707 Add isFromClient to SelectionEvent

• #3404 SelectionEvent has no source

• #3265 Error message about missing element for id mapping should mention the name of the template

• #3676 If no custom I18NProvider is configured the log is polluted by INFO messages.

Documentation fixes

• #3671 Explicitly document that multiple children can be assigned to the same slot

See complete list of changes since previous beta version

Supported Technologies

See the Vaadin platform release notes for browser, server and Java support level.

Known Limitations

• Websockets as the push channel is not working for Spring Boot #3251
• Template-in-Template feature has some limitations
• There is no CDI support #456
• There is no Portal/OSGi support #455

Flow 1.0 Feature Highlights

Using Components to build UIs with only Java

With Flow you to can compose UIs using only Java on the server side. You can use existing components or create your own by creating the DOM from the server side. See the relevant documentation:

• Using Vaadin Components
• Creating New Components and the Element API

Integrating Web Components

Flow allows you to integrate web components and consume them from server side Java. See the web components documentation for more information.

Router

Router is a core concept in Flow, enabling navigation for your website or web app. It is based on HTML5 History API, and makes it possible to for the user to navigate pages back and forward, and keep the page state intact. See the router documentation for more information.

Binding Data to Components

Flow allows you to easily bind your business data to the UI components. You can bind the forms to the business objects by using the Binder, see documentation for more information. For showing a list of data (eg. a database table) on the UI, you can use the DataProvider. See documentation for more information.

Creating UIs Declaratively with Polymer Templates

With Flow you can take full control of building the DOM and the communication by using HTML templates. We recommend using Polymer templates as they bring lots of helpful capabilities on top of the native HTML. See documentation for more information.

Theming Applications

Flow has support for customizing the look and feel of your applications with css, html custom styles or by customizing the ready made Themes provided for Vaadin Components. See the documentation for more information.

Spring Integration

Flow comes with a Spring integration, and you can use it with Spring 5 or Spring Boot 2. Please see the documentation for more information.

Getting Started

For getting started with Vaadin Flow, please see vaadin.com/start where there are three types of examples available:

• Bakery App Starter for Flow and Spring - a full stack example application with Flow and Spring Boot with heavy focus on great UX
• Beverage Buddy App Starter for Flow - a small example app that highlights the basic features of Flow
• Project Base for Flow and Project Base for Flow and Spring
  • A base for your project with some placeholder files available and dependencies available
    All the starters bring the Flow dependency via the Vaadin platform, which is the recommended way for using Flow.

From Flow getting started documentation you can find a step-by-step tutorial.

Flow 1.0 Beta3

Vaadin Flow 1.0.0.beta3 is a prerelease version for evaluating the enhancements mentioned below. With subsequent beta releases we may change things based on your feedback, and that may lead to API breaking changes.

Vaadin Flow 1.0.0.beta3

Flow is a new Java web framework for creating UIs using Java or HTML. Flow handles everything related to communication between and client and server and makes it possible to create UIs using the desired abstraction level you choose. It has all the capabilities you need to build a modern web app: from high level APIs for structuring your applications and binding data to it, into taking full control over the DOM and communication with HTML templates.

Flow is a part of the Vaadin platform. For information and helpful resources like documentation and examples on Vaadin Flow, please visit the Flow page vaadin.com/flow.

Bug Fixes since Previous Prerelease

• #3677 Loading frontend dependencies with different loading strategies causes an exception
• #3640 Can't find resources via servlet context when those use frontend:// protocol
• #2820 Remove broken Shady DOM forcing feature

This release also includes major improvements to IE11 performance, mainly related to the Grid component. The improvements are included as part of the beta6 release of the vaadin-grid webcomponent. See the component release notes for details.

See complete list of changes since previous beta version

Supported Technologies

See the Vaadin platform release notes for browser, server and Java support level.

Known Limitations

• Websockets as the push channel is not working for Spring Boot #3251
• Template-in-Template feature has some limitations
• There is no CDI support #456
• There is no Portal/OSGi support #455

Flow 1.0 Feature Highlights

Using Components to build UIs with only Java

With Flow you to can compose UIs using only Java on the server side. You can use existing components or create your own by creating the DOM from the server side. See the relevant documentation:

• Using Vaadin Components
• Creating New Components and the Element API

Integrating Web Components

Flow allows you to integrate web components and consume them from server side Java. See the web components documentation for more information.

Router

Router is a core concept in Flow, enabling navigation for your website or web app. It is based on HTML5 History API, and makes it possible to for the user to navigate pages back and forward, and keep the page state intact. See the router documentation for more information.

Binding Data to Components

Flow allows you to easily bind your business data to the UI components. You can bind the forms to the business objects by using the Binder, see documentation for more information. For showing a list of data (eg. a database table) on the UI, you can use the DataProvider. See documentation for more information.

Creating UIs Declaratively with Polymer Templates

With Flow you can take full control of building the DOM and the communication by using HTML templates. We recommend using Polymer templates as they bring lots of helpful capabilities on top of the native HTML. See documentation for more information.

Theming Applications

Flow has support for customizing the look and feel of your applications with css, html custom styles or by customizing the ready made Themes provided for Vaadin Components. See the documentation for more information.

Spring Integration

Flow comes with a Spring integration, and you can use it with Spring 5 or Spring Boot 2. Please see the documentation for more information.

Getting Started

For getting started with Vaadin Flow, please see vaadin.com/start where there are three types of examples available:

• Bakery App Starter for Flow and Spring - a full stack example application with Flow and Spring Boot with heavy focus on great UX
• Beverage Buddy App Starter for Flow - a small example app that highlights the basic features of Flow
• Project Base for Flow and Project Base for Flow and Spring
  • A base for your project with some placeholder files available and dependencies available
    All the starters bring the Flow dependency via the Vaadin platform, which is the recommended way for using Flow.

From Flow getting started documentation you can find a step-by-step tutorial.

Flow 1.0 Beta2

Vaadin Flow 1.0.0.beta2 is a prerelease version for evaluating the enhancements mentioned below. With subsequent beta releases we may change things based on your feedback, and that may lead to API breaking changes.

Vaadin Flow 1.0.0.beta2

Flow is a new Java web framework for creating UIs using Java or HTML. Flow handles everything related to communication between and client and server and makes it possible to create UIs using the desired abstraction level you choose. It has all the capabilities you need to build a modern web app: from high level APIs for structuring your applications and binding data to it, into taking full control over the DOM and communication with HTML templates.

Flow is a part of the Vaadin platform. For information and helpful resources like documentation and examples on Vaadin Flow, please visit the Flow page vaadin.com/flow.

Bug Fixes since Previous Prerelease

• #3605 afterNavigation on the view is fired twice if there is a layout

See complete list of changes since previous beta version

Supported Technologies

See the Vaadin platform release notes for browser, server and Java support level.

Known Limitations

• There are known performance issues for rendering on Internet Explorer 11 when using the Grid component with multiple columns. After using more than five columns, the application is not usable anymore. This is due to be fixed in a later beta.
• Websockets as the push channel is not working for Spring Boot #3251
• Template-in-Template feature has some limitations
• There is no CDI support #456
• There is no Portal/OSGi support #455

Flow 1.0 Feature Highlights

Using Components to build UIs with only Java

With Flow you to can compose UIs using only Java on the server side. You can use existing components or create your own by creating the DOM from the server side. See the relevant documentation:

• Using Vaadin Components
• Creating New Components and the Element API

Integrating Web Components

Flow allows you to integrate web components and consume them from server side Java. See the web components documentation for more information.

Router

Router is a core concept in Flow, enabling navigation for your website or web app. It is based on HTML5 History API, and makes it possible to for the user to navigate pages back and forward, and keep the page state intact. See the router documentation for more information.

Binding Data to Components

Flow allows you to easily bind your business data to the UI components. You can bind the forms to the business objects by using the Binder, see documentation for more information. For showing a list of data (eg. a database table) on the UI, you can use the DataProvider. See documentation for more information.

Creating UIs Declaratively with Polymer Templates

With Flow you can take full control of building the DOM and the communication by using HTML templates. We recommend using Polymer templates as they bring lots of helpful capabilities on top of the native HTML. See documentation for more information.

Theming Applications

Flow has support for customizing the look and feel of your applications with css, html custom styles or by customizing the ready made Themes provided for Vaadin Components. See the documentation for more information.

Spring Integration

Flow comes with a Spring integration, and you can use it with Spring 5 or Spring Boot 2. Please see the documentation for more information.

Getting Started

For getting started with Vaadin Flow, please see vaadin.com/start where there are three types of examples available:

• Bakery App Starter for Flow and Spring - a full stack example application with Flow and Spring Boot with heavy focus on great UX
• Beverage Buddy App Starter for Flow - a small example app that highlights the basic features of Flow
• Project Base for Flow and Project Base for Flow and Spring
  • A base for your project with some placeholder files available and dependencies available
    All the starters bring the Flow dependency via the Vaadin platform, which is the recommended way for using Flow.

From Flow getting started documentation you can find a step-by-step tutorial.

Flow 1.0 Beta 1

Vaadin Flow 1.0.0.beta1 is a pre-release version for evaluating the enhancements mentioned below. With subsequent beta releases we may change things based on your feedback, and that may lead to API breaking changes.

Vaadin Flow 1.0.0.beta1

For information and helpful resources like documentation and examples on Vaadin Flow, please visit the Flow page in vaadin.com/flow.

Bug Fixes since previous prerelease

• #3614 BeforeEnter is called for wrong view if views have common parent layout

See complete list of changes since previous alpha version

Alpha23: Easier Configuration of Push and Migration Guide

Bug Fixes

• #3577 Theme resolving doesn't work in dev mode when having a servlet path.
• #3612 Asynchronous work on generated property change listeners

Enhancements

• #480 Configuring @Push when there are only views and no UI

Breaking Changes

• #3610 UI::navigateTo method has been renamed to UI::navigate
• #3617 Add context object to beforeClientResponse calls
• #3621 Making ContinueNavigationAction class to be an inner class

Documentation Updates

• About Server Push
  • Server Push Configuration
  • Asynchronous Updates
  • Creating Collaborative Views
• Migration Guide from Vaadin 8 to Vaadin 10

All Changes

https://github.com/vaadin/flow/milestone/73?closed=1

Alpha 22: Bugfixes

Bug Fixes

• #3587 Bakery storefront view can't be shown in production mode
• #3574 Theme defined in RouterLayout doesn't work in production mode
• #3573 PolymerTemplate parsing is not thread safe in production mode
• #3562 vaadin-flow-bundle-manifest.json is not found when its context path has double slash
• #3513 Element methods do not work in some cases inside vaadin-dialog

Enhancements

• #3526 Add highlight capabilities to RouterLink
• #3560 Prevent DOM nodes serialization
• #3563 Support setting and using custom CSS properties through Element.getStyle()
• #3479 Designer templates and @theme should work together