PAM Mobile UI

PAM Mobile UI is the first-party component layer for PAM Native. It provides typed PHP APIs, declarative tags, theme tokens, utility classes, composed components, and a machine-readable parity contract.

pam init my-app --template mobile-ui

The preset installs pushinbr/pam-mobile-ui, enables its system theme, and generates a starter screen.

What “parity” means

The project records 61 component entries. Each entry identifies:

• a sequential integer component ID;
• category and maturity enums;
• implementation kind;
• public exports and component parts;
• supported variant axes;
• example count; and
• ten verification gates.

This lets the project say that a component exists without pretending that every detail is equally verified.

Rendering policy

Simple presentational components may compose lower-level PAM Native nodes in PHP. Interaction-heavy or platform-sensitive behavior stays in the native renderer. Large data lists remain native and recycled.

The library does not add a second render tree, React Native, or a JavaScript bridge.

Accessibility baseline

Components preserve native semantics and state where the Android platform provides them. Accessibility is part of the parity contract, but each component’s evidence must be checked individually.

Current limitation

PAM Mobile UI inherits PAM Native’s Android-only platform contract. An iOS component appearance and behavior contract does not exist yet.