Hey folks!

I’d like to introduce AshSDUI, a new library for generating complex interfaces and dynamic layouts directly from declarative Ash resource metadata, powered by Ash and Phoenix LiveView.

I know excellent tools like AshAdmin, Backpex, and Aurora UIX already exist. However, in my experience, they often lack architectural flexibility and clear escape hatches and sometimes excessive boilerplate and low-level handling. I wanted the ability to generate nested forms easily and dynamically alter layouts straight from the database or resource code, based on the actor, tenant, or user role without cluttering templates with conditional logic, and to do so with minimal boilerplate.

With AshSDUI, I’ve focused on creating a highly compact public interface that relies on your existing resource Ash metadata and ready-to-use receipts, but remains fully extensible at any level. It’s designed as an authoring ladder: you can start with fully generated screens and step down to custom recipes or raw LiveView only when needed, all without rewriting the whole stack.

AshSDUI is useful when you want more than scaffolded CRUD, but you still want a declarative path that stays close to your Ash resource model.

• It separates metadata, view resolution, recipes, and render trees into clear layers.
• It gives humans and llm agents a smaller authoring surface through standalone UI modules.
• It keeps generated screens, custom layouts, and live runtime components on one contract.
• It can grow from generated pages into product UI without forcing a rewrite of the whole stack.

Key highlights:

• Server-Driven UI (SDUI): Dynamically resolve layouts and component compositions based on context (actor, tenant, audience, etc.) without touching the frontend templates.
• Metadata-Driven Generation: Seamlessly generate complex UI, handle deep model relationships, and build nested forms right from Ash resource descriptions (ui_field, ui_intent, etc.).
• Architectural Flexibility: Build ephemeral, code-authored, or database-persisted layout trees with clear escape hatches at every layer.
• Shared Runtime Contract: Both generated screens and custom SDUI layouts share the exact same underlying contract (view, bindings, state, and context), keeping your data loading and rendering completely consistent.

You can find all the details, tutorials, and deep dives into the runtime/authoring models in the documentation here:

AshSDUI Repository and Readme

AshSDUI Tutorial

I would love to hear your feedback, thoughts, and suggestions! Thanks for your time.