When does a GWT to Angular migration make sense?
GWT is still maintained: version 2.13.1 shipped on 19 June 2026. So a GWT to Angular migration makes sense when the problem is people and stack, such as hiring front-end developers who don’t write Java, not when the worry is a dead framework.
GWT 2.13.1 was released on 19 June 2026. The 2.13 notes say it is likely the last release where the compiler and dev tools run on Java 11.
What GWT is doing in your app today
GWT lets a team write the browser UI in Java, then compiles that Java into optimized JavaScript. So the front end is Java code, often sitting in the same codebase as the server, and sharing classes with it. That is convenient right up to the day you want the two apart, and it is the main thing a migration has to undo.
What breaks in a GWT to Angular migration
- GWT RPC. Client and server share a Java interface that extends RemoteService, the server extends RemoteServiceServlet, and GWT handles serialization. Angular needs a plain HTTP API instead, usually REST or JSON, so the server side changes too.
- Shared Java classes. Validation and domain objects used on both sides have to be rewritten in TypeScript or generated from an API spec. Generate them if you can. Two hand-written copies of one rule agree for about a week.
- Widgets and UiBinder layouts. Each becomes an Angular component.
- Java version pressure. The 2.13 release notes warn that Java 11 support for the tools is likely ending, and 2.13 also removed more old IE workarounds. Staying put has its own upgrade work.
Steps
- Put an HTTP API in front of the existing GWT RPC services, so both clients can use the same backend.
- Write an OpenAPI spec for that API and generate TypeScript types from it.
- Build the Angular shell and move screens one at a time behind the same domain.
- Retire each RPC service once no GWT screen calls it. Check the access logs first. Memory is a poor source for this.
When not to
If your team is all Java developers and the app is internal, a supported GWT release may serve you for years, and I would not talk you out of it. Moving to Angular means a TypeScript front end and a second skill set to hire for. Weigh that before you weigh the code.
Getting a plan
The 14-day Trial is $995, one time. In the first 5 business days you get a map of the RPC services and shared classes and the order to move them in. I then make the first fixes that fit in the 14 days, and it ends with a written plan for the rest. The migration itself runs as tasks on a monthly plan, the Limited plan at $1,995 a month or the Full plan at $4,995 a month, with the number of months agreed on the kickoff call.
Read next
Sources
- GWT Project, release notes, read 17 Nov 2026
- GWT Project, overview, read 17 Nov 2026
- GWT Project, communicating with a server, read 17 Nov 2026