Automatic application improvement

DeplAI works with the running application, not only the source.

After a preview starts, DeplAI can exercise important workflows, inspect how the application renders on different screen sizes, identify material issues, and make additional improvements.

When DeplAI repairs an issue, it saves the updated application as a new version and evaluates the result again.

This is a self-healing build process: generate, run, review, improve, and re-check within the same build.

What DeplAI can evaluate

Once the application runs, DeplAI can look at the actual product, including whether:

• important workflows work
• pages load correctly
• forms and actions behave correctly
• navigation works
• required product features are present
• the application works on desktop and mobile
• obvious layout problems appear
• images fail to load
• usability or visual-quality issues are serious enough to block a trustworthy preview

What happens when an issue is found

If DeplAI identifies a material problem, it can update the application, save a new version, start the preview from that version, and check again.

Improvement is bounded. If an issue cannot be repaired within that process, the build ends in Needs attention with checks and activity you can inspect. You can then Retry, Ask DeplAI to fix, or change the request.

Be precise about quality

DeplAI automatically checks important workflows and can repair issues it detects. It does not guarantee a bug-free application, and it does not replace all quality review.

You should still walk through the journeys that matter for launch, including edge cases DeplAI may not have treated as required checks.

Related: Application quality | Checks | Preview