Wave is indeed developed in GWT, and the Adwords management interface was rewritten in GWT in the recent years (as mason55 mentioned). They talked a lot about i

Wave is indeed developed in GWT, and the Adwords management interface was rewritten in GWT in the recent years (as mason55 mentioned). They talked a lot about it during Google I/O 2009 (the session videos are still available online: http://code.google.com/intl/fr/events/io/2009/sessions.html#gwt http://code.google.com/intl/fr/events/io/2009/sessions.html#... ). While not a "web app", SpeedTracer ( http://code.google.com/intl/fr/webtoolkit/speedtracer/ http://code.google.com/intl/fr/webtoolkit/speedtracer/ ) was also made using GWT. What's interesting, is that with the Adwords UI, Google started using GWT on an enterprise app, and thought about ways of writing such an app. This project lead them to introduce many best practices for large GWT enterprise apps: - MVP (Model View Presenter) and testable UIs: MVP is good for SoC, but it's also very important if you want to unit test your UI logic in pure java (which is a lot faster than GWTTestCases) - EventBus - Command Pattern - UIBinder (declarative UI in XML) Ray Ryan's talk ( http://code.google.com/intl/fr/events/io/2009/sessions/GoogleWebToolkitBestPractices.html http://code.google.com/intl/fr/events/io/2009/sessions/Googl... ) at Google I/O 2009 created a lot of interest around these concepts, and many GWT developers around the world started discussing / following them. Google I/O 2010's sessions also have a lot of talks about these subjects, and while the best way of writing GWT apps is not yet known, we are getting there.