Describe. Display. Deploy.
Altia BluePrint helps engineering teams create embedded user interfaces faster by transforming requirements into production-ready GUI software.
Declarative UI for AI-Powered HMI Development
Tell AI the screen you want and it writes the BluePrint. UI developers can do that. So can a product owner who has never opened a GUI editor. Your UI is declarative text, so AI can produce it, revise it and maintain it.
Then watch it run. Changes render on your target hardware as you make them, so there is no gap between describing something and seeing whether it works.
What you end up with is what ships. DeepScreen generates optimized embedded code straight from your BluePrint, so nothing is lost in translation.
What BluePrint Is
Altia BluePrint is a readable description of your entire UI. It is a declarative text format for embedded user interfaces, authored in Visual Studio Code through an Altia plug-in.
Your screens, layout, content and behavior are described in a human readable file, similar in feel to YAML and readable on sight by anyone on your team. The same BluePrint feeds Altia DeepScreen for production code generation.
Change the Text. Watch the Target.
The BluePrint Viewer shows your UI update as you type. When you are ready for the real thing, edit the UI while it runs on your target hardware. No export step, no waiting on a build to find out how it looks. That loop matters most when AI is in the loop, because a fast change is only worth something if you can see what it did.
Fast to Build. Faster to Change.
Describing a screen and letting AI write it beats hand-coding a UI line by line, and the gap widens after the first build. Components are defined once and reused across screens, variants and vehicle programs. Several engineers work in one UI at the same time instead of taking turns on a project file. Every change arrives as a readable diff your team reviews like any other code. The second screen is faster than the first, and the tenth variant is faster still.
How HMI Teams Use Altia BluePrint
- Describe a screen and let AI write the BluePrint
- Iterate in natural language against real files
- Review the diff before anything ships
- Define a component once
- Reuse it across screens, variants and vehicle lines
- Change it in one place
- Multiple engineers in one UI at once
- Branch, review and merge like any other code
- No waiting on a locked project file
- Edit the UI while it runs on target
- Catch performance problems before integration
- Test on the hardware you will ship
- Feed the same BluePrint to Altia DeepScreen
- Generate optimized embedded code
- Ship software with no AI-written code in it
- Commit UI alongside application code
- Run it through existing CI and review gates
- Track every change in version history
See BluePrint in Action
Frequently Asked Questions
Altia BluePrint is AI-powered HMI development. This is a text based, declarative way to define an embedded user interface. Your screens, layout, content and behavior are described in a human readable file rather than drawn in an editor. You author it in Visual Studio Code through an Altia plug-in, changes render live on your target hardware, and the same BluePrint feeds Altia DeepScreen for production code generation.
Because the UI is declarative text, an AI model can read it, write it and change it the way it would change any other source file in your project. You describe the screen you want, the model produces or edits the BluePrint, and you review the result as a readable diff before it goes any further.
A human readable text format, similar in feel to YAML though not YAML itself. It is readable on sight by anyone on your team and works with the text tooling you already use.
In Visual Studio Code, through an Altia plug-in. The plug-in is available now.
No. Altia Design and Altia BluePrint are both first-class ways to define a UI, and both feed Altia DeepScreen for production code generation. Altia Design suits work that is shaped visually and edited in with a WYSIWYG editor. BluePrint is AI-powered HMI development that suits teams who want AI contributing to production UI or work owned by software engineers, programs large enough that parallel development and code review are critical. Choose by how your team works. Plenty of organizations will use both on different programs.
Altia AI is an assistant that works inside the Altia Design editor, helping someone who is already building there. Altia BluePrint is the UI itself, written as declarative text, so AI can build and maintain it directly in files your team reviews like code. Altia AI makes the editor easier to use. BluePrint changes what the UI is made of. Either way, the production code generated by Altia DeepScreen contains no AI output.
Yes. BluePrint is a plain text file format, so it commits, diffs, branches and merges like the rest of your codebase. Changes appear in code review as readable differences rather than as a binary nobody can inspect.
Yes. Because the UI lives in text files, several engineers can work in parallel and merge their work instead of taking turns on a single project file.
BluePrint is the UI definition. Production code comes from Altia DeepScreen, which generates optimized embedded code for your target hardware from that same BluePrint. It is the same code generator behind Altia user interfaces shipping today.
No. DeepScreen-generated code contains no AI output, making performance predictable and easier to validate for safety- and mission-critical applications. AI can help you author the BluePrint. The code that ships is generated by Altia DeepScreen, the same deterministic generator behind Altia UIs in production today.
Yes. While BluePrint is AI-powered HMI development, the code that ships is generated by Altia DeepScreen and contains no AI output, which keeps performance predictable and makes validation easier for safety- and mission-critical applications.