Form — PAM Native UI
PAM Native UI · Android evidence
p-form rendered by the production retained-native pipeline. The specimen below is a real Physical Samsung SM-G973F Android 12 (API 31) capture at 420 dpi, not an HTML recreation.
Physical Samsung layout, route and native interaction verified
- Family
- Forms and editing
- Module
form- PHP facade
PForm- Native targets
- Android · UIKit
Forms and editing component rendered through the retained-native Android and UIKit pipeline.
Android specimen

Interaction recording
The touch trace was captured from the Android application while exercising the native component.

Showcase profiles
Every profile below is rendered by the Android catalog route shown above.
- Default
- Focused
- Required
- Disabled
- Read Only
- Error
- Success
PHP usage
use Pam\MobileUi\Material\PForm;
use Pam\Native\UI\Text;
PForm::make(
[
'accessibilityLabel' => "PForm preview",
'disabled' => true,
'error' => true,
],
Text::make('Form'),
);The equivalent PAM template entry point is <p-form>…</p-form>.
See the PAM Native UI guide for event, state and styling conventions, and the quality contractfor native behavior requirements.
Component properties
| Property | Observed type | Showcase values |
|---|---|---|
accessibilityLabel | string | "PForm preview" |
disabled | bool | true |
error | bool | true |
errorMessage | string | "Invalid value" |
focused | bool | true |
messages | string | "Looks good" |
readonly | bool | true |
required | bool | true |
success | bool | true |