BlogsHybrid UI App: How Vibe-Coded UIs Co-Exist with Existing UIs

Hybrid UI App: How Vibe-Coded UIs Co-Exist with Existing UIs

Tony Chen
Reading Time: 2 min
Hybrid UI App: How Vibe-Coded UIs Co-Exist with Existing UIs

Hybrid UI: where stable existing UIs meet fast UIC-built pages — no compromise.

UIC works great for greenfield UIs, but we also have many existing UI apps in production. We believe the two can co-exist and give clients the best of both worlds. We call this the hybrid UI app.

Take the EasyPA UI as an example. A hybrid UI app combines three things:

  • The existing RainbowUI app keeps running. It represents the stable functionality the project has already delivered. Changes to it still require professional front-end developers and follow the standard SDLC process.
  • The same backend APIs for this app — the EasyPA APIs — are exposed through Playbooks. Nothing new needs to be built on the backend; the APIs are simply made discoverable and reusable.
  • New UIC pages can be built on top of those Playbooks using a full vibe coding experience, then added to the RainbowUI app as a new menu item.

The picture below shows the hybrid EasyPA UI. The menus in the red box come from the existing UI app; the green box highlights pages built with UIC. The main area shows the Training Policy Insights page, which is a UIC-built page.

Hybrid EasyPA UI showing existing RainbowUI menus (red box) and the UIC-built Training Policy Insights page (green box)

With the hybrid model, clients do not have to choose between stability and speed. The existing UI continues to deliver proven, reliable functionality and keeps improving over time. Meanwhile, innovative ideas and purpose-built UIs can iterate very fast on UIC — and they can be built by people who are not front-end specialists.

Embrace the future of agentic engineering with insureMO.

Build faster, innovate smarter, and stay in control in the age of AI coding.

Talk to an Expert