# Nexamas UI Customer Guide

This guide is for a customer, buyer, or non-implementation stakeholder who wants to understand what Nexamas UI is before making a commercial decision.

## What Nexamas UI is

Nexamas UI is documented as a proprietary Windows desktop UI SDK for .NET Framework 4.8 Windows Forms applications. This statement is backed by the project file, package specification, buildTransitive target file, commercial documentation inventory, and package evidence pages.

Naming model: `Nexamas UI` / `Nexamas.UI` is the product and package identity. `MAS*` names such as `MASApplication`, `MASButton`, and `MASDataGrid` are the stable API/control family inside Nexamas UI.

Start with:

- [Commercial product brief](commercial/product-brief.md)
- [What is included](commercial/what-is-included.md)
- [Platform overview](product/platform-overview.md)

## What the customer receives conceptually

The verified documentation describes these product pillars:

- Application/window composition through public application facade entry points.
- Component system through Application-owned control factories and component descriptors.
- Layout, size, and responsive infrastructure through public layout/sizing surfaces and internal proof infrastructure.
- Theme, surface, and visual material infrastructure with clear public/internal boundaries.
- Localization and RTL product foundation, including a public page attachment gateway and internal readiness evidence.
- Data presentation through DataGrid/DataView and internal virtualization infrastructure.
- Output facade for manifests and visual capture; release-evidence bundles are kept outside the beginner SDK facade.
- Quality and verification infrastructure including Render Verification public gateway and internal quality proof systems.

## What is not included as a runtime feature in this snapshot

Do not treat the following as verified runtime features unless a later source-reviewed phase proves otherwise:

- runtime subscription billing;
- online activation server;
- customer portal;
- cloud/SaaS backend;
- production PDF export;
- operating-system printer integration;
- public Theme Studio API;
- public Surface Designer API;
- public Quality Orchestrator API;
- public virtualization SDK;
- public translation/resource-engine API.

See [Stability and roadmap boundary](commercial/stability-and-roadmap-boundary.md) and [Subscription readiness](commercial/subscription-readiness.md).

## How to read the documentation

Read the commercial pages first. Then read the quality proof guide and public surface references only if a technical evaluation is needed.

- [Quality proof guide](quality-proof-guide.md)
- [Reference guide](reference-guide.md)
- [Release documentation pack inventory](./_inventory/release-documentation-pack.md)