Skip to content
Menu

Procedural UI

Shape your Unity UI without a texture for every variation.

A focused standalone tool for authoring responsive uGUI shapes and visual styles, with reusable pieces for your game's interfaces.

Is it a fit?

A starting point for your project.

For Unity developers working with uGUI who want to vary interface shapes and styling without maintaining a separate texture for each variation. The planned product can be adopted independently of a full Aether Solution.

In development

Before you plan around it
In development for Unity uGUI. This is not a UI Toolkit product. Supported Unity versions and render pipelines remain subject to release validation.

A design-to-Unity workflow

From concept to Unity.

Give your agent a design and a prompt. Our Agent Usage guide explains how to build it in Unity with Procedural UI.

Built almost entirely with Procedural UI. Panels, meters, borders, gradients and effects in our Unity examples are procedural. Most icons and portraits use sprite artwork. These Unity examples are included as Samples in the Procedural UI package.

Explore the building blocks.

Shapes, color and effects for your interface. Captured directly in Unity.

Select a preview to view its full-size source.

Know the boundaries

Scope & compatibility.

Review the intended installation and the evidence still needed before release.

Unity versions, rendering & UI systems

The customer-facing tool targets Unity uGUI. Editor inspection helpers do not make it a UI Toolkit runtime product. Unity-version and render-pipeline claims require clean-project, rendering and build evidence before publication.

Standalone packaging & dependencies

The planned release separates shared inspection tooling from Core's application lifecycle infrastructure. Procedural UI, the required Aether Inspection dependency and Unity uGUI define the intended installation boundary. The package migration and final submission format remain release work; required Aether dependencies are not intended as separate purchases.

Current limitations & release gates

The final 1.0 feature boundary, clean installs and upgrades, sample imports, serialization, rendering and performance must be verified against one release artifact. Documentation, third-party content clearance and support procedures also remain launch gates.

Availability & working together

The product. Help when you need it.

The product and its release scope are in development. Software licensing and project services are separate offers.

Software · In development

A standalone Unity asset

Procedural UI is the first planned Aether Unity Asset Store product. Its required Aether dependencies are intended to be included in one product. No store listing, price or release date is published here yet.

Ask about the product

Separately scoped services

Need custom UI work?

Project-specific UI implementation can be scoped as custom engineering. It is a separate engagement and is not required to adopt the planned Procedural UI asset.

Discuss custom UI work
Compare service options & how we work together

Software licensing and project implementation are separate offers. Product-based setup and integration depend on a verified release and supported configuration; a concept page does not establish availability.

Assisted Setup

Your project fits a supported configuration and you need help getting started.

What you receive

Project preflight, installation, supported provider configuration, a checked reference flow and handoff notes.

Scope & engagement

Custom UI, data migration, unsupported providers and major architecture changes need a separate scope.

Fixed scope once the setup checklist confirms the fit.

Discuss setup

Production Integration

You need a supported product adapted to your existing game and its systems.

What you receive

Discovery, an integration plan, agreed project changes, provider and data integration, testing and handoff.

Scope & engagement

New provider adapters, broad redesigns and unrelated features are scoped separately.

Fixed scope for verified configurations. Uncertain work starts with paid discovery, then agreed milestones or time and materials.

Discuss integration

Custom Engineering

You need custom Unity UI, a new adapter, a migration or behavior beyond an existing product's scope.

What you receive

Agreed project-specific implementation, documentation and tests, with architectural work where needed.

Scope & engagement

The written scope defines what is included. New requirements are agreed before adding work.

Milestones or time and materials, with written change control.

Discuss custom work

How working together works.

  1. Start with a conversation

    Describe the outcome you need. A short free fit call establishes whether the work is a fit; detailed investigation belongs in discovery.

  2. Define the work

    Where the requirements are uncertain, paid discovery produces findings, risks and a recommended path. Before delivery, we agree on inputs, deliverables, exclusions and acceptance checks.

  3. Build, test and hand over

    I deliver against the agreed scope and hand over documentation, test results and known limitations. Ongoing support is a separate agreement.

A direct line to the developer

Tell me what you're building.

Ask about Procedural UI, or describe where your project needs a hand.

Inquiry delivery is loading. See the privacy notice for how submissions are handled.

Inquiry details
Use the name you would like us to use when replying.
We use this only to reply to your inquiry.
A short description of your project and the support you need is enough.