Important Notice - Forums is archived

To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Product icon

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.

Vornitologist Oooops...Browsers

Marcio Duran
10 years ago Nov 21, 2012 8:11pm
Thomas Mattsson
10 years ago Nov 22, 2012 8:28am
Marcio Duran
10 years ago Nov 22, 2012 10:52am
Thomas Mattsson
10 years ago Nov 22, 2012 11:23am
Thomas Hoenen
10 years ago Nov 22, 2012 12:21pm
Marcio Duran
10 years ago Nov 22, 2012 5:51pm
Henri Sara
10 years ago Nov 23, 2012 7:25am
Marcio Duran
10 years ago Nov 23, 2012 7:27pm
Henri Sara
10 years ago Nov 24, 2012 8:40am
Marcio Duran
10 years ago Nov 24, 2012 4:11pm
Henri Sara
10 years ago Nov 26, 2012 10:19am

I hope I understand better now, although I don't speak Portuguese... This forum is meant to be in English, so you might ask on some Portuguese Java forum where there are users of Vaadin.

There is a fundamental difference between native applications (written in a phone OS specific way in a specific programming language, running on the phone) and internet applications (both simple page-based applications).

RIA means "rich internet application" and in many cases, like with Vaadin, does not rely on any native code on the phone except the browser. The Vaadin application runs in a Java virtual machine on the server. The browser on the phone just loads and runs some JavaScript and then that client side part communicates with the server to display widgets etc. (There are also other kinds of RIA frameworks that depend on plug-ins on the client, like Flash.)

The general way of programming a Vaadin application is similar to programming an AWT or Swing or SWT application, but Vaadin does not support those technologies. Instead, you use Vaadin components (which are similar to those of Swing), Vaadin listeners etc. on the server. The framework then takes care of displaying them on the browser.

Vaadin uses some "HTML5" features of browsers, but HTML5 is not only one thing - it is a loose collection of separate standards that live independently of each other, and different versions of different browsers support different versions and parts of those standards. It is in many ways misleading that the "5" in HTML5 looks like a version number - it isn't really and never will be.

Vaadin is a framework that supports the browsers that have a major market share and do not excessively complicate the work for developing the framework or limit the framework. There is no guarantee that the favorite browser of user X will ever be supported, nor when. Vaadin is not associated with Apple, Google or the other companies, except in using Google Web Toolkit and being active in developing it.

Google Web Toolkit is developed completely separately from e.g. Chrome and Android and is not in any way related to native apps on phones etc. The browsers Vaadin can support depend on the browsers that GWT supports.

Marcio Duran
10 years ago Nov 27, 2012 12:24am