Skip to content

Banner Actions — PAM Native UI

PAM Native UI · Android evidence

p-banner-actions 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
Overlays and feedback
Module
banner
PHP facade
PBannerActions
Native targets
Android · UIKit

Overlays and feedback component rendered through the retained-native Android and UIKit pipeline.

Android specimen

p-banner-actions running in the PAM Native UI Android catalog

Interaction recording

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

p-banner-actions native Android interaction

Showcase profiles

Every profile below is rendered by the Android catalog route shown above.

  • Default
  • Single Action
  • Disabled Action
  • Long Labels
  • Independent Pair

PHP usage

use Pam\MobileUi\Material\PBannerActions;
use Pam\Native\UI\Text;

PBannerActions::make(
    [
        'accessibilityLabel' => "PBannerActions preview",
    ],
    Text::make('Banner Actions'),
);

The equivalent PAM template entry point is <p-banner-actions>…</p-banner-actions>.

See the PAM Native UI guide for event, state and styling conventions, and the quality contractfor native behavior requirements.

Component properties

PropertyObserved typeShowcase values
accessibilityLabelstring"PBannerActions preview"