Facilitating the spread of knowledge and innovation in professional software development



Choose your language

InfoQ Homepage News What is the future for GWT?

What is the future for GWT?


The newly formed Google Web Toolkit (GWT) steering committee recently published “The Future of GWT Report”, which captures the opinions, usage patterns and hopes of over 1300 Google Web Toolkit users worldwide.

GWT is an open source set of tools that allows developers to create and maintain complex JavaScript applications in Java. Google first released GWT on May 16th, 2006. In June of 2012, Google handed control of the project over to a steering committee which includes members from Vaadin, Google, Sencha and RedHat. The report provides the most comprehensive survey of GWT development ever conducted.

While GWT is often thought of as an enterprise technology, 65% of the survey respondents are working on projects for use outside of their companies. That said, only 1% of the projects are games - the vast majority are business applications.

Half of the respondents are working on projects that contain over a million lines of uncompressed obfuscated Javascript code which suggests that either GWT applications are complex and/or that GWT generates a lot of Javascript code for relatively simple apps. Forty-six percent of the applications have 21+ screens, and a number of the comments in the report suggest that one of the big benefits of GWT is access to static typing and compile time error checking in Java when working with multiple developers. However, the average GWT project team surveyed has less than three front end developers, so most of the projects aren’t working with large numbers of front end engineers.

While the vast majority of the apps (over 98%) target desktop-based users, the number of these apps that also also target tablets (36%) eclipses the 26% of apps that also aim at mobile phones.

The main complaints with GWT are compile time (49%) and the lack of enough good quality UI widgets (34%). The biggest benefit of GWT is not having to deal with browser compatibility issues (60%). Despite the complaints, over 88% of the self selected respondents plan to use GWT on their next project. The report is available online in return for your name and email address.

We need your feedback

How might we improve InfoQ for you

Thank you for being an InfoQ reader.

Each year, we seek feedback from our readers to help us improve InfoQ. Would you mind spending 2 minutes to share your feedback in our short survey? Your feedback will directly help us continually evolve how we support you.

Take the Survey

Rate this Article


Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Links are broken

    by Russell Leggett,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    The links in the article don't work.

  • Need to integrate existing / new JavaScript Frameworks

    by Faisal Waris,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Generating JavaScript is not enough anymore.

    The use of one or more main JavaScript frameworks such as JQuery, JQueryMobile, Dojo, SenchaTouch, etc. is pretty much required for contemporary rich web / mobile web apps.

    These frameworks do a lot of heavy lifting in terms of UI controls, styling, animation & navigation.

    See previous commentary here:

  • Re: Need to integrate existing / new JavaScript Frameworks

    by Mark N,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    For LOB apps GWT might be good enough or even better. Also, notice that the vendor of one of the frameworks you mentioned is on the committee. Als (#2), there is a .NET framework generates JavaScript and it is doing quite well.

    I have had the joy of maintaining other peoples code in everything from QuikJob and COBOL to JavaScript and .NET/Java. My experience is that using a language Java/.NET will make your job tons easier (in the long run). So until that is no longer true, there will always be a place for things like GWT. Granted, GWT is NOT always the right tool for the job. Don't assume all use cases are the same and thus that [native?] JavaScript is always the best tool for the job.

  • Re: Need to integrate existing / new JavaScript Frameworks

    by John L,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    QuickJob?? Holy cow, a blast from the past. :)

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p


Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.