October 31, 2026. The App SDK goes dark. Every custom app built on Rally's old framework stops loading for your users. Not "please upgrade" stops. Just gone.
Broadcom's official guidance is to rebuild those apps as Custom HTML Widgets. That's technically correct. It's also the entire guidance.
The App SDK was a framework. It handled the WSAPI calls, managed workspace and project scope, rendered components, and papered over about ten years of Rally API quirks. A Custom HTML Widget gives you a text editor, a WSAPI endpoint, and a deadline. The gap between those two things is the migration. We've been filling that gap for a while, and we finally built a tool to do it.
The problem with building this kind of tool
Training an AI to migrate Rally apps sounds like a weekend project until you hit the obvious question: trained on what?
Generic React knowledge doesn't help. An AI that has read the React docs and the Custom HTML Widget documentation will produce code that compiles and runs. It won't know that Rally's WSAPI has opinions about how you query hierarchical data. You need an AI that has seen real Rally apps. Not documentation. Actual source code, in all its ExtJS glory.
We had those.
The CustomAgile GitHub organization has 474+ repositories accumulated over more than a decade. Simple query tiles, full PI planning dashboards, everything in between. Add every open-source Rally app we could track down, and you have the largest combined catalog of Rally apps in the world. We pointed WidgetAI at all of it.
Drag in the old app. Here's what comes out.
You drag your legacy Rally HTML file onto the tool. The file tree starts filling in immediately. Not after a five-minute wait. Right now. You watch it read your ExtJS source and figure out what the app actually does. It maps your xtype calls to the components that replace them. It traces your WSAPI stores to build typed interfaces. It finds your getSetting() calls so the settings panel comes back correctly.
When it's done, you have a complete React widget project: typed models, a WSAPI hook, assembled components, a main entry point that works in both Rally and a local dev environment, and a MIGRATION_REPORT.md that explains in plain English what was migrated, what choices were made, and what still needs a human eye.
That last part matters. The AI does a self-review pass. It audits its own output for consistency and type errors before you see the result.
What's under the hood
WidgetAI's output runs on the WidgetAI SDK, a React and TypeScript component library built specifically for Rally Custom Views. Every component the generated code uses is typed, tested, and aware of Rally's scope system. The output uses the same foundation we rely on for our own widget development.
Where it is now
WidgetAI is in beta. We're running it with pilot customers: organizations that have App SDK apps, an October deadline, and not enough developer hours to handle both.
If that's you, we'd like to talk before the calendar does.