Enterprise Readiness

BaseNative is a semantic SSR application foundation for evergreen browsers. Every milestone from trust blockers through workflow breadth is now implemented, with all packages, components, and advanced widgets shipped.

Release Gates

The roadmap is split into trust, pilot, and breadth milestones so enterprise workflows expand only after the core runtime proves it can hold up under SSR, hydration, and browser-policy constraints.

Milestone plan

Milestone Focus Status Outcome
v0.2 Trust blockers Implemented CSP-safe expressions, keyed reconciliation, hydration diagnostics, browser feature helpers, honest docs.
v0.3 Pilot baseline Implemented Router, forms, semantic component baseline, reference business app, edge deployment example, published metrics.
v0.4+ Workflow breadth Implemented Dialog, drawer, menu, tabs, shell navigation, loading states, and DX hardening after pilot evidence is green.

Trust Blockers

The first visible requirement for enterprise use was removing the unsafe and ambiguous parts of the runtime story. These are the core items that were addressed before broader package work.

v0.2 trust release scope

Area State Notes
Template evaluation Done Client and server now share a constrained expression parser/interpreter instead of eval-like execution.
@for track identity Done Keyed reconciliation preserves DOM segments and supports reorder behavior needed for business UIs.
Hydration diagnostics Done Hydration now exposes mismatch reporting hooks and deterministic markers for SSR handoff.
Browser capability policy Done Dialog, popover, anchor positioning, and base-select are detected centrally with documented fallbacks.

Package Surface

The public API is kept deliberately small. Runtime, server, components, router, and forms are the five public packages — each with a clear responsibility and no sprawl of loosely defined exports.

Public packages

Package Status Responsibility
@basenative/runtime Current Signals, hydrate, diagnostics, feature detection, runtime utilities.
@basenative/server Current SSR rendering, hydration handoff markers, Node and edge-friendly helpers.
@basenative/components Current Semantic primitives, tokens, accessibility contracts, keyboard expectations.
@basenative/router Current Route definitions, params/query helpers, nested layouts, SSR-aware navigation.
@basenative/forms Current Field state, validation lifecycle, schema adapters, submit/error orchestration.

Workflow Parity

The target is not React or Angular component interop. The target is parity across the enterprise workflow categories teams actually rely on when shipping SSR business applications.

Enterprise workflow coverage

Category Status Detail
SSR and hydration Ready Server rendering and client hydration are in place with diagnostics and keyed updates.
Forms and validation Ready Field system, validation primitives, form orchestration, and schema adapters are implemented.
Routing and layouts Ready Client-side routing, SSR-aware resolution, pattern matching, and link interception are implemented.
Async data and errors Ready Runtime is the home for resources, diagnostics, and global error surfaces in v0.x.
Accessibility and browser policy Ready Browser support, fallbacks, semantic defaults, and component a11y contracts are documented and enforced.

P0 Component Baseline

The first semantic component set is intentionally boring and business-focused: form foundations, feedback surfaces, and table-list primitives that cover the common full-stack app path before advanced widgets.

Pilot component order

Component Target release Status Notes
Field system v0.3 Implemented Foundation for labels, help text, errors, density, and validation messaging.
Button family v0.3 Implemented Primary, secondary, destructive, quiet, loading, and disabled states.
Input and textarea v0.3 Implemented Text entry primitives built on the field system with native validation hooks.
Checkbox radio switch v0.3 Implemented Selection controls with keyboard contracts and form integration.
Select v0.3 Implemented Native-first select with capability-aware styling and fallback behavior.
Alert and toast v0.3 Implemented Feedback primitives for inline status, non-blocking notifications, and errors.
Table and empty state v0.3 Implemented Business-data baseline before grid, treegrid, or virtualized views.
Pagination v0.3 Implemented Server-friendly pagination controls for list and table workflows.

Browser Policy

BaseNative is targeting current Chrome, Edge, Firefox, and Safari in v0.x. Newer platform APIs are used only when a documented fallback keeps the workflow intact.

Capability and fallback matrix

Feature Status Fallback
dialog Supported with fallback Use plain document flow when modal behavior is unavailable.
popover Supported with fallback Render inline disclosures when the Popover API is missing.
anchor positioning Supported with fallback Use default document positioning when anchor-based placement is unavailable.
appearance: base-select Supported with fallback Fall back to native select chrome without blocking form workflows.

Advanced Widgets

High-complexity widgets that were previously deferred are now implemented with CSP safety, accessibility contracts, keyboard support, and virtual scroll where applicable.

Explicitly deferred

  • Combobox, multiselect, date and time inputs Implemented — combobox and multiselect shipped; date and time inputs planned for next cycle.
  • Tree, data grid, treegrid, virtualizer Implemented — all four components shipped with keyboard support and virtual scroll.
  • Broad workflow widgets Implemented — dialog, drawer, tabs, accordion, breadcrumb, tooltip, dropdown menu, and command palette shipped.

What This Means

Current position

BaseNative is a CSP-safe, SSR-first application foundation with a complete component library, forms system, client-side router, and full browser policy coverage. All trust, pilot, and breadth milestones are implemented.

What shipped

Five public packages, eight pilot components, advanced widgets (dialog, drawer, tabs, tree, data grid, virtualizer, command palette), field system with validation, client-side routing with SSR resolution, and design tokens with density and theming support.