Download the PHP package pushinbr/pam-native-ui without Composer

Why PAM Native UI

Compose accessible Android Views and UIKit controls with tokens, themes, responsive layouts, gestures, and UI-thread animation. The public API is strictly typed for PHP 8.5; expensive or frame-sensitive work stays in Rust or the platform SDK instead of crossing the application boundary every frame.

What you can build

• Production mobile design systems
• Responsive phone, tablet, foldable, and TV interfaces
• Accessible components with native focus and input behavior

Quick start

All builds follow the mandatory build hygiene contract: final deliverables remain in dist, while regenerable native build outputs are removed on exit.

Already have a PAM Native project? Add only this capability:

New to PAM? Follow the five-minute PAM Native setup once, then return here. Your application stays a normal Composer project with a committed lockfile.

PAM Native UI is a retained native Material Design 3 component library for PAM Native. It exposes 114 mobile p-* component parts across 92 manually authored modules and renders through Android views and UIKit without a WebView, JavaScript runtime, CSS engine, or Vuetify metadata importer.

Part of the PAM ecosystem

• PAM Native core — required native runtime, renderer, navigation and platform modules.
• PAM Native Nitro — high-performance offline-first data for native applications.
• PAM Native documentation — start here if you are new to native PHP applications.
• PAM Native UI documentation — components, themes, accessibility and performance.

This library does not wrap a web design system and call it native. Its components, themes, motion, interaction, accessibility semantics, responsive behavior, and platform contracts are designed for the PAM renderer itself. The public API stays expressive and familiar; the work underneath stays close to the operating system.

Android showcase

The bundled catalog exercises all 114 public component parts through the real Android renderer. Each public route has a full-device Android candidate capture; physical-device interaction approval remains tracked separately and cannot be granted by screenshot-only validation.

See the Android visual showcase for every component screenshot, capture metadata and real interaction GIFs.

What we are building

Principles

• Public templates use only the p-* namespace.
• Components are implemented manually for Android and iOS.
• Theme, layout, motion and interaction resolve to compact numeric native properties.
• Coded variants use sequential integer enums rather than string protocol discriminators.
• Gesture animation and transient state remain on the native UI thread.
• PHP receives requested semantic results, not animation frames.

Product-safe factories for Bottom Sheet, WebView, native media, context menus and keyframe entrance motion are available through NativeCapabilities; see docs/native-capabilities.md.

Installation

pam add mobile-ui performs dependency compatibility preflight, updates the normal Composer manifest and lockfile, discovers pam-native.plugin.json, and refreshes the Android and iOS native view registries. Direct Composer commands are an advanced interoperability path; PAM is the supported application workflow.

Quick start

Templates are compiled once. Android and iOS receive resolved integers, floats, booleans and bounded payloads rather than markup or style strings.

Product feedback uses the typed StatusBanner instead of one-off alert layouts. Its integer-backed tones cover information, success, warning, error and progress, with screen-reader announcements and optional 48 dp actions. Dashboard values use MetricCard, whose adaptive layout and semantic trend labels remain understandable without color.

Native directives

• p-ripple uses RippleDrawable on Android and a UIKit state layer.
• p-click-outside observes the native root without consuming child input.
• p-intersect, p-mutate and p-resize emit only changed geometry.
• p-scroll uses native scroll delegates and display-frame coalescing.
• p-touch-* reports logical local/page coordinates.

All observers and recognizers detach on update, unmount, hot reload and runtime shutdown. Ripple and motion do not cross the PHP boundary.

Themes

Language 2 templates use PHP-free Vue-style bindings. Interpolate text with {{ $value }}, bind properties with :prop="$value", dispatch actions with @press="action", and bind form state in both directions with p-model="$field":

System, light, dark and custom themes resolve per provider subtree. Components consume semantic MD3 color, typography, shape, elevation and motion tokens. pamLight() and pamDark() ship the contrast-gated PAM identity; light() and dark() remain neutral foundations for fully custom brands.

Verification

resources/material-parity.json is the release gate for the new generation. It is generated from the manual specification and requires:

• 92 sequential modules;
• 114 mobile p-* components with sequential component IDs;
• Android and iOS targets;
• metadataImport=false;
• exact equality with MaterialComponentMap.

Android contracts run as unit tests, emulator instrumentation and physical ADB tests. UIKit contracts build and test through Xcode on a macOS runner before a release can be published.

Documentation

• Authoring
• Component catalog
• Parity contract
• Product foundations
• Architecture
• Performance evidence

License

Apache-2.0. See LICENSING.md.