Base44's Base Code turns designers' Figma-style edits into pull requests engineers must still review

A designer using Base Code sees a canvas laid out like Figma. Base44 chief product officer Yoav Orlev said many designers already use that kind of interface to build web applications ^[5]. Underneath is a sandbox built from the company's GitHub codebase, with the services the app needs already running ^[2][4]. The work leaves the canvas as a pull request, and an engineer reviews it ^[6].

The pitch is collaboration across software engineers, application developers, designers and product teams ^[1]. What the product actually does is narrower. Base Code gives designers a sandbox built on the real code and a way to send changes into the pull request queue ^[2][6]. Production changes only when an engineer merges. Product managers are on the audience list ^[1], but when Orlev describes who works in the canvas, he names designers and application developers ^[5].

Teams tend to tell themselves a story about tools like this: designers will send small, finished changes, and engineers will approve them in minutes. So far the only account of what users do comes from Orlev, in one launch article. Base44 has not published pricing or usage figures, such as how fast designer changes get merged.

Review is the constraint. The devops.com article that reported the launch says many DevOps teams already cannot review all the code being created, and that more unvetted code runs in production than anyone cares to admit ^[9]. The article hopes AI agents will one day do more of that reviewing ^[10].

I think Base Code is worth piloting for teams whose engineers already keep up with their review queue, and a poor fit for teams that do not. The cost of a bad fit falls on the designer. In a slow-review shop, a finished change waits in line with everything else, and the designer now owns code they cannot ship themselves.

Two axes sort the decision. One is review speed: whether the team merges pull requests within a day or two or lets them age. The other is reach: whether the changes designers want stay in the interface or touch the data and services the sandbox has to stand up ^[4]. Fast review with interface-only changes is the pilot case. If the changes go deeper, the same team needs a named engineer to review every designer pull request. Where review is slow, interface work should wait until review is fixed, and deeper work should wait longer. The count of pull requests opened will go up in every quadrant, and it says little about value. The figure to track is the number of days from a design decision to a merged change.