NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #5265 most downloaded on Packagist
Build fast native Android and iOS applications with PHP and PAM.
Latest stable
v1.54.3
Last release 3 days ago
19 Nov 2026
Ships on a steady schedule
a new release about every 2 weeks
Nearly every release is documented
notes for 58 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
3 months old
386 releases · first in 2026
Drag across the ruler to compare, or tap a release to open it.
Added: the #[Transient] property attribute keeps bookkeeping fields (caches, counters, handles, timestamps) out of the render snapshot, so writing the
#[Transient] property attribute keeps bookkeeping fieldsYour coding agent can read these notes before it upgrades. Set up the MCP server →
One column per month.
Fixed: Android — while a panning KeyboardAvoidingView is translated by the keyboard, a gesture enters through the highest ancestor whose hit test stil
App::reload() mounts the relaunched request's tree from scratch onpam_native_runtime_reload_fresh_prepared.Full Changelog: v1.54.1...v1.54.2
Fixed: App::reload() relaunches PHP like a cold start in the same window: the old request no longer records hot reload state, so no #[State] from the
App::reload() relaunches PHP like a cold start in the same window:#[State] fromsetup() and mount() (releasepam dev hot reload and the errorPamRuntime.reload() gains fresh; iOS addspam_native_runtime_reload_fresh.android.orientations also declares the portrait andFull Changelog: v1.54.0...v1.54.1
Fixed: Android uses no deprecated Window bar colour setters (Play edge-to-edge warning); modal bar colours are painted by the host.
App-declared Android capabilities (queries, orientation, picture-in-picture, URL schemes), media and notification-permission fixes, link navigation that stacks, and localized formatting.
android.queries (packages, intents); the host manifest no longer queries Instagram, WhatsApp or smsto.android.orientations locks PamActivity's screenOrientation (same values as ios.orientations).android.pictureInPicture declares supportsPictureInPicture; in PiP the host keeps media playing and PHP active.MediaPlayer keeps the screen on; with sound it holds audio focus (pauses on loss or unplugged headphones).Notifications permission follows areNotificationsEnabled() below Android 13 (Blocked when off).DeviceStatus::watch() accepts DeviceStatusField filters; useNetwork() watches only the network.Window bar colour setters (Play edge-to-edge warning); modal bar colours are painted by the host.PamTextProcessors lets a plugin rewrite text spans before measure and draw (e.g. EmojiCompat).fadingEdgeLength on VirtualizedList, FlatList and SectionList (Android).Route::open()/Route::openInitial() accept a mode; 'push' opens the link over the current screen and reuses the focused screen only for the same route with the same path params. Default stays navigate.OfflineMutationQueue::online(true) after online(false) makes every waiting retry due now before draining.pam-native.json linking.openSchemes (e.g. ["otpauth"]): extra schemes for Linking::open()/canOpen(), with Android <queries> and iOS LSApplicationQueriesSchemes generated; file/content/intent/javascript/data-like schemes are rejected.Linking::open()/canOpen() match URL schemes case-insensitively; Linking::open() hands the URL to the system directly on Android and iOS.MovedToPlugin aliases due in 1.47 (location, contacts, sensors, audio, media, media editor, auth, notifications, share extension); import the plugin classes. Drawer, Toast and UI\WebView aliases remain.packages/native/benchmarks or the SDK build-time audits.Files::delete() accepts an optional failure closure and treats a missing file as deleted (Android, iOS).Files::cachePath() / Files::CACHE_DIRECTORY (a sandbox cache folder Caches::clear() empties) and CacheUsage::$importBytes; Caches::clear(imports: true) removes picker/import copies.useSafeAreaInsets()->cutoutTop/Right/Bottom/Left and WindowMetrics::$cutout*: the display cutout alone, for immersive screens.App::reload() relaunches PHP on the active entry (e.g. after a language change); older hosts report to failure.Support\Format formats Spanish and French, and without useLocale() follows the active I18n locale when catalogs are registered (pt-BR otherwise).No published PAM Native plugin or pam init template uses these names. Replace each import and require the plugin:
| Removed name | Use | Package |
|---|---|---|
Pam\Native\AudioRecording |
Pam\Native\Audio\AudioRecording |
pushinbr/pam-native-audio |
Pam\Native\AudioRecordingProgress |
Pam\Native\Audio\AudioRecordingProgress |
pushinbr/pam-native-audio |
Pam\Native\BiometricError |
Pam\Native\Auth\BiometricError |
pushinbr/pam-native-auth |
Pam\Native\BiometricKind |
Pam\Native\Auth\BiometricKind |
pushinbr/pam-native-auth |
Pam\Native\CapturedImage |
Pam\Native\Media\CapturedImage |
pushinbr/pam-native-media |
Pam\Native\CaptureType |
Pam\Native\Media\CaptureType |
pushinbr/pam-native-media |
Pam\Native\Contact |
Pam\Native\Contacts\Contact |
pushinbr/pam-native-contacts |
Pam\Native\ImageCaptureFormat |
Pam\Native\Media\ImageCaptureFormat |
pushinbr/pam-native-media |
Pam\Native\ImageCropRatio |
Pam\Native\MediaEditor\ImageCropRatio |
pushinbr/pam-native-media-editor |
Pam\Native\ImageFilterType |
Pam\Native\MediaEditor\ImageFilterType |
pushinbr/pam-native-media-editor |
Pam\Native\ImageTextLayerStyle |
Pam\Native\MediaEditor\ImageTextLayerStyle |
pushinbr/pam-native-media-editor |
Pam\Native\IncomingShare |
Pam\Native\ShareExtension\IncomingShare |
pushinbr/pam-native-share-extension |
Pam\Native\LocationError |
Pam\Native\Location\LocationError |
pushinbr/pam-native-location |
Pam\Native\LocationPosition |
Pam\Native\Location\LocationPosition |
pushinbr/pam-native-location |
Pam\Native\LocationServicesResult |
Pam\Native\Location\LocationServicesResult |
pushinbr/pam-native-location |
Pam\Native\MediaAlbum |
Pam\Native\Media\MediaAlbum |
pushinbr/pam-native-media |
Pam\Native\MediaAssetPage |
Pam\Native\Media\MediaAssetPage |
pushinbr/pam-native-media |
Pam\Native\MediaAsset |
Pam\Native\Media\MediaAsset |
pushinbr/pam-native-media |
Pam\Native\NotificationImportance |
Pam\Native\Notifications\NotificationImportance |
pushinbr/pam-native-notifications |
Pam\Native\Notifications\ActionEndpoint |
Pam\Native\Notifications\Contracts\ActionEndpoint |
pushinbr/pam-native-notifications |
Pam\Native\Notifications\ConversationNotification |
Pam\Native\Notifications\Contracts\ConversationNotification |
pushinbr/pam-native-notifications |
Pam\Native\Notifications\NotificationAction |
Pam\Native\Notifications\Contracts\NotificationAction |
pushinbr/pam-native-notifications |
Pam\Native\Notifications\NotificationActionType |
Pam\Native\Notifications\Contracts\NotificationActionType |
pushinbr/pam-native-notifications |
Pam\Native\Notifications\NotificationCredentials |
Pam\Native\Notifications\Contracts\NotificationCredentials |
pushinbr/pam-native-notifications |
Pam\Native\Notifications\Person |
Pam\Native\Notifications\Contracts\Person |
pushinbr/pam-native-notifications |
Pam\Native\Notifications\PushRendering |
Pam\Native\Notifications\Contracts\PushRendering |
pushinbr/pam-native-notifications |
Pam\Native\Notifications\PushRenderingRule |
Pam\Native\Notifications\Contracts\PushRenderingRule |
pushinbr/pam-native-notifications |
Pam\Native\Notifications\ReplyFailures |
Pam\Native\Notifications\Contracts\ReplyFailures |
pushinbr/pam-native-notifications |
Pam\Native\PushEventType |
Pam\Native\Notifications\PushEventType |
pushinbr/pam-native-notifications |
Pam\Native\PushMessage |
Pam\Native\Notifications\PushMessage |
pushinbr/pam-native-notifications |
Pam\Native\PushProvider |
Pam\Native\Notifications\PushProvider |
pushinbr/pam-native-notifications |
Pam\Native\PushToken |
Pam\Native\Notifications\PushToken |
pushinbr/pam-native-notifications |
Pam\Native\SensorReading |
Pam\Native\Sensors\SensorReading |
pushinbr/pam-native-sensors |
Pam\Native\SensorType |
Pam\Native\Sensors\SensorType |
pushinbr/pam-native-sensors |
Pam\Native\System\AudioRecorder |
Pam\Native\Audio\AudioRecorder |
pushinbr/pam-native-audio |
Pam\Native\System\Biometrics |
Pam\Native\Auth\LegacyBiometrics |
pushinbr/pam-native-auth |
Pam\Native\System\Contacts |
Pam\Native\Contacts\Contacts |
pushinbr/pam-native-contacts |
Pam\Native\System\ImageEditor |
Pam\Native\MediaEditor\ImageEditor |
pushinbr/pam-native-media-editor |
Pam\Native\System\IncomingShares |
Pam\Native\ShareExtension\IncomingShares |
pushinbr/pam-native-share-extension |
Pam\Native\System\Location |
Pam\Native\Location\Location |
pushinbr/pam-native-location |
Pam\Native\System\MediaCapture |
Pam\Native\Media\MediaCapture |
pushinbr/pam-native-media |
Pam\Native\System\MediaLibrary |
Pam\Native\Media\MediaLibrary |
pushinbr/pam-native-media |
Pam\Native\System\Notifications |
Pam\Native\Notifications\Notifications |
pushinbr/pam-native-notifications |
Pam\Native\System\PushNotifications |
Pam\Native\Notifications\PushNotifications |
pushinbr/pam-native-notifications |
Pam\Native\System\Sensors |
Pam\Native\Sensors\Sensors |
pushinbr/pam-native-sensors |
Pam\Native\System\Sms |
Pam\Native\Contacts\Sms |
pushinbr/pam-native-contacts |
Pam\Native\System\ViewCapture |
Pam\Native\Media\ViewCapture |
pushinbr/pam-native-media |
Full Changelog: v1.53.9...v1.54.0
feat: app theme tokens resolved at compile time (pam-native.json theme.tokens) by @DavidWilliamBalbino in #279
Full Changelog: v1.53.8...v1.53.9
pam-native.json "theme": {"tokens": "src/theme.css"} names a file of :root { --token: value; }
declarations that the compiler appends after every component library's own
src/app.css (and to the app's components): a library such as PAM Native
UI takes the app's palette, radii and sizes at compile time, in light and
dark. The file may only declare custom properties (64 KiB), is validated by
the CLI and the JSON schema, and is part of every compiled component's
cache key, so editing it recompiles and hot reloads. Apps without it are
untouched (one cached lookup per directory).pam dev on Android can no longer take the adb server down. When
a session ended, the device client could still connect to a mapping that
was gone; adb 37 aborts the whole server on that ("handle_packet
disallowed connect to tcp:39100"), which dropped every device, and a
Galaxy S10 on wireless debugging stayed off adb until debugging was
toggled by hand. Now every adb call names the device (-s, from
ANDROID_SERIAL or the only connected device; several devices without it
is an error), the mapping is added with --no-rebind and a device port
mapped by another session is never taken over, and a watcher process that
survives Ctrl+C, SIGTERM, crashes and SIGKILL stops the app before it
removes only this session's own mapping. Tests drive the real watcher
against a fake adb and check the order of the calls.Font size and language changes keep the reader's place.
Font size and language changes keep the reader's place.
onBlur/onEndEditing/onFocusFull Changelog: v1.53.7...v1.53.8
release: 1.53.7 no PHP restart when pam dev serves the installed bundle; prompts close on reload; per-app dev port by @DavidWilliamBalbino in #276
Full Changelog: v1.53.6...v1.53.7
pam dev no longer restarts the PHP request
when the installed bundle already is the served version. It switched to
the live directory (a full PHP restart) even with "0 files changed",
right after the first mount, dropping every pending native callback: a
biometric prompt opened in onMounted then answered nobody (Galaxy S10,
pam-native-auth). The client hashes the installed bundle once against the
manifest; any difference still reloads as before.ReloadAwareModule.prepareReload().pam dev device port
(39100-39899 from its package name; the CLI computes the same). Every app
used device port 39100, so a second pam dev on the same phone pushed its
bundle into another app. The host port follows the device port unless
PAM_NATIVE_ANDROID_DEV_PORT is set, and a busy host port says so.Android keeps the running app and its plugins alive through font, display size and language changes.
Android keeps the running app and its plugins alive through font, display
size and language changes.
density|fontScale|layoutDirection|locale|mcc|mnc|navigationdocs/android-activity-lifecycle.md.pam_native_engine_invalidate_text_measurements FFI drops cached hostlocale; useLocale()pam dev and pam run only require the connected device's ABIlongPress after press, pressOut is always emitted and the controlrelease: 1.53.5 explicit IME show, Maven Central mirror in CI by @DavidWilliamBalbino in #272
Full Changelog: v1.53.4...v1.53.5
1.53.4, released: its tag was not published because the release hit Maven Central rate limits and a lost macOS runner.
WindowInsetsController.show(ime()) next to SHOW_IMPLICIT, as autofocus
already did: an implicit request made before the field's input connection
is served is dropped. The keyboard instrumented tests request it the same
way (each CI run had one keyboard test time out waiting for the IME).scripts/ci-gradle-mirror.sh, an init script). A release starts dozens of
Gradle jobs at once and repo.maven.apache.org answered 429 for longer than
three retries; the mirror serves the same artifacts.A fresh Mac runs pam mobile ios:* with no manual step.
A fresh Mac runs pam mobile ios:* with no manual step.
ios:prepare downloads the verified iOS PHP runtime
(PamPhp.xcframework, device arm64 + simulator arm64/x86_64) when PAM's
slot is empty, as PAM's macOS release ships it. The runtime is built once
per PHP version and revision by PAM's iOS PHP runtime workflow and
published as the immutable runtime-ios-<id> release; the CLI verifies
the SHA-256 pinned in PAM's runtime/ios-runtimes.json (PAM 2.2.22+) or
the .sha256 beside the asset, accepts only PamPhp.xcframework/ and a
matching runtime.json, and caches it in <engine cache>/ios-runtime.
Building PHP locally stays an explicit opt-in (runtime-builder/ios/build.sh)
named in the error. ios:doctor reports a downloadable runtime as ready.pam dev, pam mobile build, bundles) retry up to
three times on transient repository errors (Maven Central 429, 5xx,
timeouts) and return build failures at once.WindowInsetsController.show(ime()) while they wait:
after an earlier test hid the keyboard, SHOW_IMPLICIT alone was ignored
on CI (28 keyboard tests pass locally, idle and under CPU load).scripts/ci-ime-ready.sh waits for the default IME, binds it and lets
the soft keyboard show next to the emulator's hardware keyboard before the
instrumented contracts; a different keyboard test timed out waiting for
the IME on each API 36 run.The 1.53.2 fixes, released: that tag was not published because the release gate failed on the two items below.
The 1.53.2 fixes, released: that tag was not published because the release gate failed on the two items below.
PHP_INI_SCAN_DIR. pam starts package
executables with it blanked (so its ini reaches no other PHP), which left a
distribution PHP (Ubuntu, setup-php) without its conf.d extensions:
"Call to undefined function token_get_all()" during pam dev. Reproduced
with PHP_INI_SCAN_DIR= php; a unit test covers the environment.The fixes below plus the 1.53.0 and 1.53.1 changes; neither of those tags was published (the release community gate failed; see "Fixed (release)").
The fixes below plus the 1.53.0 and 1.53.1 changes; neither of those tags was published (the release community gate failed; see "Fixed (release)").
Http::upload streamed a file threw an IllegalStateException from
the request body, which OkHttp rethrows on its dispatcher thread: the app
crashed. The upload now fails with an IOException and its call reports
the failure to PHP. A JVM test closes the module mid-upload and asserts
that no thread dies.Modal presentation="dialog")
was re-measured from its children and lost its padding: PAM Native UI's
320 dp confirm dialog came out 272 dp wide with "Cancel" and "Delete"
ellipsized to "C..." and "...". The card keeps the engine's size and is
centred; an instrumented test checks the width and the labels.scrollTo and dragged the viewport
back to the field. Reproduced with a loaded emulator (2 of 3 runs of
PamKeyboardAwareScrollInstrumentedTest failed, the CI flake); 4 of 4
pass loaded and all 55 keyboard and scroll instrumented tests pass.pam init --template native-ui run.ellipsized for text that
PamTextView truncated by replacing it (React Native tail truncation),
which has no ellipsis in its own layout. The geometry check missed the
dialog's "C..." because of this.Appearance::set) after
the keyboard had been shown left a blank screen in the background colour.
The new opaque background was also given to UIKit's transparent
UITextEffectsWindow, which sits above the app. Only the app's own
opaque windows are repainted now; every window still gets the style.pam mobile could not fetch the Native
CLI ("cannot download"): the assets are public, but PAM's macOS PHP looks
for CA certificates in its build directory, so TLS verification failed.
The launcher now verifies against the system bundle (/etc/ssl/cert.pem
and the usual Linux and Homebrew paths) when PHP has none, and falls back
to the system curl (HTTPS only), still checking the SHA-256.Fixed: apps above minSdk 24 (including the default 26) no longer fail lintDebug with ObsoleteSdkInt on the host's Android 7.0 version checks; the fram
:app:lintDebug with ObsoleteSdkInt on the host's Android 7.0 version
checks; the framework still lints the host at minSdk 24. 1.53.0 was tagged
but never published because the ecosystem Android certification caught
this.Android apps reach the same devices as a typical React Native app: 32-bit ARM and x86 phones and Android 7.0/7.1.
Android apps reach the same devices as a typical React Native app: 32-bit ARM and x86 phones and Android 7.0/7.1.
armeabi-v7a and x86 builds. pam-native build android
now packages arm64-v8a, armeabi-v7a, x86 and x86_64 by default, linked
against the 32-bit PHP 8.5 runtimes from PAM v2.2.21 (64-bit integers on
every ABI). The bridge refuses a runtime without 64-bit zend_long.android.minSdk accepts 24 (the default
stays 26) and plugins default to minSdk 24. Below API 26 the host links a
small bionic shim (mblen, nl_langinfo) for the prebuilt PHP runtime,
and android.icon adds a square pre-adaptive launcher icon.NoSuchFieldError,
Typeface.Builder, java.nio.file, java.util.Base64, java.time,
autofill, tooltip, justification, autosize, focus highlight, light
navigation bar, vibration, network callback, MediaPlayer seek, animator
scale, dev-tools receiver); lint runs at minSdk 24.HTTP that survives broken IPv6, input that never loses its last keystrokes, pixel-exact centring and the evidence tools behind PAM Native UI 2.1.
HTTP that survives broken IPv6, input that never loses its last keystrokes, pixel-exact centring and the evidence tools behind PAM Native UI 2.1.
Files::download), sharing one connection pool. Happy Eyeballs (RFC 8305)
races IPv6 and IPv4 250 ms apart: on a network whose IPv6 is broken a
request to a dual-stack host took 15-21 s (the connect timeout per AAAA
address) and now takes the normal round trip. HTTP/2 is used when the
server offers it.PendingResponse::cancel() (and Http::cancelRequest($id) for the
callback API) aborts the native request, so a screen that unmounts can
stop its downloads: $this->onUnmounted(fn () => $pending->cancel()).submit, blur and any press (Android and iOS): the submit handler and a
button tapped right after typing see the text on screen, not the value from
before the last keystrokes.VirtualizedList mounted inside deferred content (a long list in
a BottomSheet) is built through its adapter instead of receiving its rows
as children (#262).Input with a CSS box (background, border, radius) and
underlineColorAndroid="transparent" lost its whole box on Android: the
underline tint was applied to PAM's own background drawable. The tint now
colours only the platform underline.sheetDismiss, like a swipe down (Android and iOS). PHP's bound
state stayed open, so the next open request changed nothing and the sheet
never reopened.Modal with presentation="dialog" keeps its card at the
size the layout gave it; the card stretched with the window (a 300pt
dialog drew window-sized). An explicit backdropColor dims behind a
transparent modal, as on Android.testID (React Native's spelling) sets the native test identifier
like testId; it was dropped silently, so test ids written that way never
reached Android or iOS.pam dev hot-reloads Composer path packages linked into vendor/
(a component library or plugin developed next to the app).PamNativeEngine.xcframework
(iOS arm64 device, arm64 and x86_64 simulator) as
pam-native-ios-engine-<version>-<protocol>-<engine>.zip with its SHA-256.
pam mobile ios:* downloads it once, verifies it and caches it per
version and fingerprint (~/Library/Caches/pam-native/engines,
PAM_NATIVE_ENGINE_CACHE overrides), so projects on different pam-native
versions no longer depend on, or overwrite, the single engine slot of the
shared PHP runtime. A matching locally rebuilt engine in that slot is still
used first.am broadcast -a dev.pam.nativeapp.action.CAPTURE_LAYOUT and the iOS UI
driver's {"layout": "name"} step write every view's frame, visible part,
real touch target and text metrics. The iOS driver also gains
{"expectText": id, "contains": [...]}.Two-way binding for components, plugin component libraries and the fixes found while rebuilding PAM Native UI 2.0 and porting PushinPay.
Two-way binding for components, plugin component libraries and the fixes found while rebuilding PAM Native UI 2.0 and porting PushinPay.
p-model on component tags. <my-field p-model="$email" /> passes
the bound value as the modelValue prop and writes back what the component
emits as model ($this->emit('model', $value)), cast to the bound
property's scalar type. p-model="$form->email" writes one level into an
object; a NativeForm field is set through set() (dirty, touched, error
cleared). Before, p-model on any component threw "The model attribute is
only valid on Input"..pam components. "php": {"components": "dir"} in
pam-native.plugin.json registers every component of that package
directory at boot, and the component prebuild packs them, so release builds
compile none on the device.#[Event('change', 'string')]: component events accept scalar
payload types (mixed, string, int, float, bool, array, null).on:change on a component that declares a change event is that
component event, like @change (native elements already accepted both).
It no longer fails with "PAM2401 unknown prop".label="2.0" stayed 2), numeric props accept integral values, and key
is no longer reported as an unknown prop of a typed component.VirtualizedList whose p-for is empty on the first render
(data still loading) stays a virtualized list; it used to become a legacy
string list, and the rows that arrived later never appeared ("Node … cannot
contain children"). An empty ScrollView renders instead of throwing.flex-wrap: wrap with percentage widths (a 3x4 keypad of
width: 33.333% keys) measures every wrapped line; the container was one
line tall and the lines overlapped what followed.->statusBar('light') on a route rendered an empty screen; the
status bar wrapper now fills the scene.Icon finds assets/fonts/<Font>.ttf and its glyph map from the
project root, not the working directory, so icon fonts work during Android
hot reload.pam dev runs loads on the next
Android reload (packaged asset:// paths resolve from the synced tree
first) instead of after restarting pam dev.android section) defaults to minSdk 26
instead of 0, which the CLI rejected.maxResponseBytes for HTTP: per client
(Http::create(maxResponseBytes: 2 * 1024 * 1024), withMaxResponseBytes())
and per request (Request::withMaxResponseBytes(), Http::request(..., maxResponseBytes:)). The default stays 1 MiB; the hard limit is 16 MiB.
Responses were capped at 900 KiB by the native module bridge ("HTTP response
exceeds one MiB"); bodies over 900 KiB now reach PHP through a private cache
file on Android and iOS (a 1.17 MB store page loads with a 2 MiB limit).require-dev
packages: a fresh pam init --template native-ui printed 34 warnings for
PHPUnit files that never run on the device.@media/@container block of a component stylesheet
carried a full copy of the sheet-level IR, bytecode, source map and the
20 KB compatibility table (~75 KB per block). Query blocks keep only their
rules now: a themed component with light, dark and platform blocks compiles
~4x smaller and loads with less memory.Fixed: Android reads pam-native.properties and pam-plugins.properties as UTF-8, so an app name with accents ("Zé Chat") reaches the launcher label int
pam-native.properties and pam-plugins.properties as
UTF-8, so an app name with accents ("Zé Chat") reaches the launcher label
intact instead of "Zé Chat".Crash-safe release extraction. No API change.
Crash-safe release extraction. No API change.
.pam-release completion marker (file sizes) is written last..pam-release
marker matches and every listed file has its recorded size (parallel stat,
no hashing); otherwise it is discarded and extracted again. The first launch
after installing or updating takes ~190 ms longer (fsync, 16 threads); later
launches are unchanged.Navigation: a held prewarm (releaseAfterMs: null) now survives switches between kept-alive screens (tabs) while the screen that warmed it stays kept a
releaseAfterMs: null) now survives switches
between kept-alive screens (tabs) while the screen that warmed it stays kept
alive; returning to it no longer remounts the warm screen (Galaxy S10: a
17-20 ms commit ~1 s after returning to the inbox is gone). Navigating to a
screen that is not kept alive, a reset, another prewarm, cancelPrewarm()
and trimMemory() still release it.trimMemory() on every live navigator, releasing
preloaded and warm screens before App::onMemoryPressure().Tab switches in one cheap frame (Galaxy S10: Chats → Feed worst frame 16 → 8.7 ms, display-list recording 7.9 → 0.5 ms, no missed deadline). No API ch
Tab switches in one cheap frame (Galaxy S10: Chats → Feed worst frame 16 → 8.7 ms, display-list recording 7.9 → 0.5 ms, no missed deadline). No API change.
PamMount.remove.<KIND> / PamMount.move.<KIND> trace sections
name the node kind while tracing.Navigator::preload() of a route already mounted in the stack no longer
builds a second, unused instance.Frame-cost and media-loading fixes measured on a Galaxy S10 after 1.50.0. No API change.
Frame-cost and media-loading fixes measured on a Galaxy S10 after 1.50.0. No API change.
PamTextView): in a long fling a row binds ~30% faster and creates ~6x
fewer text views. A recycled cell releases the layout, resize/mutate,
click-outside, span-press and keyboard-progress bindings its nodes
installed, so a reused view never reports events under the previous row's
id. A Pressable is configured once per mount. A list's first layout binds
only the rows in its viewport; a hidden list (a pushed screen's first
layout) mounts its on-screen rows while binding them, removing a
window-wide second layout pass.blurRadius to the heap and blurs them
on the image loader's workers, never on the UI thread, and never reads a
GPU bitmap back (15.5 ms per image on the S10). Blurred bitmaps are cached
per sigma and size, so recycled rows paint them in the bind frame. A
blurred image (spoiler) never shows a sharp frame; changing blurRadius or
resizing re-blurs off the UI thread. iOS runs blur and color-matrix filters
off the main thread, cached on the shared decoded image.Retry-After (capped at 30 s); other 4xx fail
at once. A 429/503 pauses its host for every image, prefetch and video, so
queued media waits instead of spending the rate limit. Android downloads
(5 threads) and decodes (3) run on separate priority lanes: visible images
first, a recycled cell's queued work is dropped, one download is shared
across sizes. First-byte timeout 7 s, up to 15 s on retries (iOS: was
60 s). A failed image or video loads again when shown or attached again;
failures no longer stick. Cache-Control: no-store keeps image bytes off
disk unless cacheKey is set.ClockFormat::format().mountSliceObserver); whole-frame budgets apply only on
hardware GL (SwiftShader CI emulators skip them).Native-level interaction release: the UI thread never waits for PHP to answer a touch, never builds more than the screen shows in one frame, and PHP r
Native-level interaction release: the UI thread never waits for PHP to answer a touch, never builds more than the screen shows in one frame, and PHP re-renders only what changed — state and logic stay in PHP.
component.patch Profiler spans;
GranularRender::enabled(false) turns it off. (Typing in a comment field
inside a sheet of a large screen: 45 component renders → 15.)PamCommit.mutations while a trace records.Pressable::prewarm(), <Link prewarm>,
<Pressable prewarm :prewarmParams prewarmMode prewarmTransition> mount the
destination on press-in (validated, middleware); the press reuses it; a
press-out without a press releases it after 300 ms. navigatesTo(),
Route::prewarm(), Navigator::intentKey(). Android: a press whose
declared destination is the warm route starts the push on the tap and the
commit adopts the running animation. prewarm()/cancelPrewarm() mark the
navigator for render.blocksNavigationGesture attribute.gestureDirection /
fullScreenGestureEnabled change, so a route pushed over a full-screen-back
route (stories over a chat) went back from anywhere. Android: the back
gesture works over scrollable vertical lists again.Text::clock(), countdown(), countdownTo(), ClockFormat
(clockStartedAt, clockEndsAt, clockDurationMs, clockOffsetMs,
clockRunning, clockFormat), Element::timeProgress()
(progressStartedAt, progressDurationMs, progressOffsetMs,
progressRunning) and Text::reveal()/revealOver() (revealCharMs,
revealDurationMs, revealKey). They tick only on screen and catch up
from the wall clock; reduced motion steps fills each second and shows
reveals at once.BottomSheet/Modal unmounted while presented (p-if) plays the same exit
as visible = false over a snapshot of its content before the window goes;
it takes no touches, notifies nothing, and a sheet reopened meanwhile
presents above it. Android: closing a sheet no longer drops its backdrop to
a third of its opacity on the first frame.blocksNavigationGesture), 1022–1034
(time primitives), 1035–1038 (press navigation intent and warm launch).Templates: an event handler written as one call of a #[PureHandler] method (on:press="open($post['id'])", a relay with an argument) no longer marks it
#[PureHandler]
method (on:press="open($post['id'])", a relay with an argument) no longer
marks its component before it runs: like a method-name handler, the
component re-renders only when its own state changed. Inside list rows
each such press re-rendered the row, the list and every ancestor screen.
Any other expression (relay('a') || bump()) keeps marking its component.cache with streamingCache/downloadWhilePlaying): a remote
video not in the cache streams alone first; the copy for the cache starts
4 s later. Both downloads started together and split the bandwidth, so the
first frame took about twice as long on a mobile network. iOS also plays a
fresh cached copy from disk (it streamed it from the network again).Navigation: the host's transition-end and gesture callbacks and a system Back that pops a route re-render the navigator they changed (child navigators
interceptSystemBack()) still re-renders everything, and so does
a handler set with App::onBack().pagingEnabled with estimatedRowHeight/rowHeight)
plans its first frame by pages instead of the 900 pt fallback screen:
windowSize="3" opens with the page at initialScrollIndex and one on
each side (it built 5 and released 2 once the host reported).PamPhpCompiler::prebuild() streams the component pack to disk instead of holding every compiled class and template twice (once per entry, once in the
PamPhpCompiler::prebuild() streams the component pack to disk instead of
holding every compiled class and template twice (once per entry, once in
the packed string): a 444-component app peaked at 124 MB and a release
build ran out of the CLI's 128 MB memory_limit; it now peaks at 68 MB.
The pack is byte-identical.Route::openInitial($uri) opens a link without a transition, settled before the next frame (React Navigation's initial state from a deep link), the sta
Route::openInitial($uri) opens a link without a transition, settled
before the next frame (React Navigation's initial state from a deep link),
the stack under it kept for Back. It matches routes.php links itself, so it
works with Route::linking(false), runs middleware like Route::open()
and builds no screen while resolving the link (Navigator::openInitial()
only knew the native stack's own deep links and mounted the current screen
looking for a nested handler).translationX/Y are in the detector's own space, as iOS
translation(in: view): under a scaled or rotated ancestor (or detector)
the screen delta is mapped through the inverse of their scale and rotation,
so x - translationX stays the touch-down point, velocityX/Y (already
local) agree with it, and a native Drag (atTouch, bounds) follows the
finger. Pan and swipe distance/direction use the same space; tap slop and
the pager hand-back stay in screen pixels. Without scale or rotation the
values are unchanged.gestureNativeTransform) on a rotated or
scaled detector, or inside a scaled canvas, follows the finger again. The
renderer handed it the detector-space translation, which
parentSpaceVector then mapped through the same transforms a second time
(a story layer inside a 0.69 canvas moved about 1.45x the finger, a rotated
one off its axis); it now gets translation(in: nil). PHP's
translationX/Y stay in the detector's space. Android's native transform
likewise maps the screen delta (not the payload's detector-space
translation) once into the target's parent, now also for the pan a focal
pinch owns.PushEventHandler gains didLaunch(response:) and
didLaunch(remoteNotification:), with empty default implementations. The
host forwards UIScene connectionOptions.notificationResponse (the
notification tap that launched the app, which reaches no other callback)
from scene(_:willConnectTo:options:), and
launchOptions[.remoteNotification] from didFinishLaunching once the
plugins are built, both before PHP boots, so a plugin can hand PHP the
launching notification.iOS: a Pressable/GestureDetector with accessibilityLabel (or any other accessibility prop) stays a VoiceOver element, as on Android and in RN; role ge
accessibilityLabel (or any other
accessibility prop) stays a VoiceOver element, as on Android and in RN;
role generic reads as a button. Before, the first accessibility prop turned
it into an unreachable node. accessible="false" still exposes its
children.accessibilityContainerType
(list/semanticGroup) and keep their children reachable instead of
becoming one silent element; a header/text/listitem/summary container
without a label does the same. A label-less View element with an
interactive role reads its content (RN RCTRecursiveAccessibilityLabel).accessibilityLiveRegion polite/assertive posts a VoiceOver
announcement (queued/interrupting) of the region's label or visible text
when it appears with content or that content changes, as TalkBack reads
Android live regions. Nothing runs while VoiceOver is off, and what
changed meanwhile is not read when it turns back on.accessibilityRole="adjustable" with on:accessibilityAction receives
increment/decrement from VoiceOver's swipe up/down and TalkBack's
slider scroll forward/backward, without declaring them in
accessibilityActions.AccessibilityCheckedState::None (0, template none) documents "no
checked state"; Android treats it like the absent property.accessibilityElementsHidden, accessibilityState, aria-*,
typos) as PAM2302: a development warning, an error in strict/release
builds.Android images that arrive within 120 ms (disk cache, fast network) replace the placeholder at once instead of cross-fading 300 ms over a frame alread
MediaPlayer with preloadSeconds and no startBufferMs
starts after 1 s of buffered media (2 s after a stall) instead of
ExoPlayer's 2.5 s / 5 s, like AVPlayer: feeds and viewers no longer hold
the poster for seconds.Gestures inside pagers and lists keep the drag. A pan with gestureMinDistance="0" that is not simultaneous (a seek bar, a slider, a trim handle) owns
gestureMinDistance="0" that is not simultaneous (a seek bar, a slider,
a trim handle) owns the touch from the first point on Android, and an
off-axis drag hands it back to the ancestors; any recognized
exclusive/race pan now keeps the rest of the touch instead of being
intercepted midway by an ancestor scroll. iOS: ancestor pans wait for an
immediate pan to fail. Dragging a video seek bar inside a horizontal
gallery no longer pages to the next video.CADisableMinimumFrameDurationOnPhone, so
ProMotion iPhones run PAM animations and display links above 60 Hz. On
Android the engine sizes each frame's work for the display's peak rate
at its resolution (adaptive panels report 60 Hz while idle), as iOS does
with maximumFramesPerSecond.Keyboard::dismiss() hides the keyboard through the window when
no view holds focus (the field already blurred with the keyboard up).Release, benchmark and update bundles precompile components in strict mode, the mode those devices run since 1.49.1. The prebuilt cache was compiled l
android/, ios/, tests/, docs/ and scripts/, Markdown, licences,
composer.lock, Kotlin/Swift/Gradle/Python sources and the web/TV
compiler (packages/web, not autoloaded on Android or iOS). Apps no longer
list them in .pamignore (Zé Chat: 2 MB of plain assets -> 278 KB).Handler purity analysis no longer spikes the PHP heap on the device: it reads only the analyzed method's lines (not the whole file once per method) an
use header, not the wholememory_limit mid-flush ("Allowed memory size ...usememory_limit; 128 MB stays for smaller devices.Vertical scroll content measures each stacked child inside its own width (content width minus its side margins, or its width, clamped by min/max), lik
Vertical scroll content measures a row's children at the widths the final layout gives them (icon, flex text, chevron), like intrinsic layout does. Te
DeviceModule registers its battery/power receiver and networkAndroid release builds keep PamRuntime.onNativeRemount from R8. The JNI lookup failed in minified builds, so the retained tree was never replayed onto
PamRuntime.onNativeRemount from R8. The JNIscripts/check-jni-keep-rules.py now fails when aAndroid and iOS export PAM_NATIVE_MODE before PHP starts: production for release builds, development for debug builds and benchmark for the Android be
PAM_NATIVE_MODE before PHP starts:production for release builds, development for debug builds andbenchmark for the Android benchmark build type. Release builds used to runBuildConfiguration::mode() could not tell them apartApple TV (tvOS): the UIKit renderer and the PHP runtime run on tvOS. See docs/tv.md .
Apple TV (tvOS): the UIKit renderer and the PHP runtime run on tvOS. See
docs/tv.md.
tvos:prepare, tvos:build and tvos:run build the iOS host forruntime/tvos/<runtime> (runtime-builder/ios/ build.sh tvos in pam); simulator builds link only the architectures theautoFocus, focusGroup, captureKeys,@keyDown, @focus / @blur, :focus styles, the default focus ring);Switch and pull to refresh.key, expect, expectNot, expectFocus and waittests/e2e.json runs on the tvOS Simulator.examples/tv passes its end-to-end script on the Apple TV Simulator.PamNativePlugins package declares tvOS 15.Samsung (Tizen) and LG (webOS) TVs, without a server: the PHP app is compiled ahead of time to static HTML/JS. See docs/tv.md .
Samsung (Tizen) and LG (webOS) TVs, without a server: the PHP app is compiled
ahead of time to static HTML/JS. See
docs/tv.md.
pushinbr/pam-native-web (packages/web): PHP to JavaScript compilertizen and webos targets and web (icon, tv.overscan).tizen:build, tizen:package, tizen:run, webos:build,webos:package, webos:run and web:build.scripts/web-e2e.py: the end-to-end scripts on a web build, with Tizen andvendor/composer (classmap, PSR-4, PSR-0, files) from src/ and theinstanceof and constants, preg_*armeabi-v7a): apps with the android-tv target andpushinbr/pam-native-web ship the web build in the APK; on 32-bit devicesPamActivity hands off to PamWebActivity (WebView), with the remote'sscripts/web-e2e.py --adb sends the keys through adb for the Android WebView.TV apps: Android TV, Google TV and Fire TV from the same code as the phone app. See docs/tv.md .
TV apps: Android TV, Google TV and Fire TV from the same code as the phone app.
See docs/tv.md.
targets (android, ios, android-tv) and android.tvbanner, overscan). The android-tv target adds the TV launcher entry,armeabi-v7a is refused with a clear message, because the PHP SDKon:keyDown with a typed KeyEvent (W3C names:Enter, GoBack, ContextMenu, media and colour keys) andcaptureKeys, like PAM Desktop.focusable, autoFocus on any element, focusGroup (rails and menusnextFocusUp/Down/Left/Right and afocusRing="none" or a :focus style replace it). on:focus/on:bluruseFormFactor() (type, tv, phone, tablet, remote, touch), anddeviceClass is Television on a TV. The pointer of a remote is none.Name.tv.pam.php (and .phone/.tablet) variants: another template forandroid.tv.overscan).android-tv.scripts/android-e2e.py: end-to-end scripts that drive an app with theexamples/tv (PAM TV) runs oneKeyDown) and properties 1012-1020.Platform media queries and a lighter component precompile on top of 1.46.33.
Platform media queries and a lighter component precompile on top of 1.46.33.
@media (platform: ios) / @media (platform: android) select rulesPlatform.OS / Platform.selectios:prepareAndroid list rows on the React Native pixel grid for any list origin, and empty list rows that take no space, on top of 1.46.32.
Android list rows on the React Native pixel grid for any list origin, and
empty list rows that take no space, on top of 1.46.32.
round(origin + height) - round(origin) fromiOS pixel grid like React Native and a keyboard fix for end-anchored lists on top of 1.46.31.
iOS pixel grid like React Native and a keyboard fix for end-anchored lists on
top of 1.46.31.
roundLayoutResultsToPixelGrid): the position is rounded relative to thestackFromEnd list whose rows rested against the end and stopPamFrameTrace logs every applied frame (engine floats and thePAM_FRAME_TRACE=1 or the PamFrameTraceAndroid list pixel grid like FlashList and an empty-container fix in the layout engine on top of 1.46.30.
Android list pixel grid like FlashList and an empty-container fix in the
layout engine on top of 1.46.30.
fullSpan rows are the list's header (ListHeaderComponent):Android list-cell pixel grid and component-root text styles on top of 1.46.29.
Android list-cell pixel grid and component-root text styles on top of
1.46.29.
Templates: a text style a component's call site only inherited from an
ancestor (a color on a dark container) no longer decorates the component's
root over its own attributes; it reaches the component as an inherited
style. A component whose root is a Text (an icon glyph) was drawn in the
container's text colour instead of its own.
Android: list cells sum the rounded origin of every layout-only ancestor up
to the slot, a layout-only cell root included, as React Native's cell view
flattens it. A child 2 + 2 dp below such a root rounded its whole 4 dp
offset at once (11 px instead of 5 + 5 at 2.625), one pixel low.
Android: a list cell's children subtract their scroll host's content insets
like the non-cell layout does. A horizontal ScrollView with
paddingHorizontal inside a list row drew its items one padding further in.
Layout engine aspect-ratio measurement on top of 1.46.28.
Layout engine aspect-ratio measurement on top of 1.46.28.
aspectRatio box with a definite width (points or a percentagewidth: 100%; aspect-ratio map was measured atadb shell setprop log.tag.PamFrameTrace DEBUGAndroid pixel grid like React Native's Yoga rounding on top of 1.46.27.
Android pixel grid like React Native's Yoga rounding on top of 1.46.27.
roundLayoutResultsToPixelGrid, as React Native mounts them: positions areiOS video audio session like expo-video ( #223 ) and a lighter Android debug commit path on top of 1.46.26.
iOS video audio session like expo-video (#223) and a lighter Android debug
commit path on top of 1.46.26.
PamNativePerf line (frame kind,setprop log.tag.PamNativePerf DEBUG set before the app starts. The lineAVAudioSession like React NativeaudioMixingMode: 'auto'): .playback/.moviePlayback while a.mixWithOthersshouldResume;on:error, likeon:error.Android list scrolling (first scroll after opening a list), lighter debug tooling, and the list stackFromEnd property ( #220 ) on top of 1.46.25.
Android list scrolling (first scroll after opening a list), lighter debug
tooling, and the list stackFromEnd property (#220) on top of 1.46.25.
PamListTrace motion log batches its lines andPamList.slice andPamList.mountShown.stackFromEnd rests rows that do not fill the viewport against itsAndroid list scrolling fix and iOS Switch parity on top of 1.46.24.
Android list scrolling fix and iOS Switch parity on top of 1.46.24.
Switch is the system UISwitch (React Native parity) instead of aSwitch withoutpam_native_engine_set_switch_size; Android keeps 46.5 × 27), andtrackColorTrue/trackColorFalse/thumbColor map toonTintColor/tintColor/thumbTintColor only when set; removing oneAndroid: an autoFocus input mounted in a pushed route focuses and opens the keyboard once the route is shown (the hidden attempt was dropped). iOS ( #
Android: an autoFocus input mounted in a pushed route focuses and opens the keyboard once the route is shown (the hidden attempt was dropped). iOS (#214): route change releases the input of routes left behind; StatusBar backgroundColor paints no band by default (Info.plist opt-in); UI driver bundle target. macOS CLIs follow.
Android autoFocus fix and iOS parity on top of 1.46.23.
autoFocus input mounted in a pushed route focuses and opens
the keyboard once the route is shown. A pushed route mounts hidden until its
transition starts, and the focus attempt for a hidden input was dropped
without a retry, so the keyboard never opened on screens whose only input
auto-focuses (React Native focuses it on mount, the keyboard rising with the
push). Inputs of retained routes still never focus while hidden.StatusBar backgroundColor paints no band by default, as in React
Native where it is Android-only; PamStatusBarPaintsBackground in
Info.plist opts back in. UI driver bundle target for host UI tests.Android: a KeyboardAvoidingView with behavior height/padding outside a modal is laid out above the keyboard by the engine (absolutely positioned child
Android: a KeyboardAvoidingView with behavior height/padding outside a modal is laid out above the keyboard by the engine (absolutely positioned children dock on the keyboard, onLayout reports the avoided frame); a focused route change blurs the input of the route left behind and hides its keyboard. macOS CLIs follow.
Android keyboard layout and navigation fixes on top of 1.46.22.
KeyboardAvoidingView with behavior height or padding
outside a modal is laid out above the keyboard by the engine (as on iOS and
inside modals) from the root IME inset, every frame. The native viewport
reduction was invisible to layout: absolutely positioned children docked
against the unreduced frame (a button meant 8 dp above the keyboard rested
48 dp above it) and onLayout reported the full height. Android 8-10 keeps
the native reduction.Android: a KeyboardAvoidingView with behavior height/padding outside a modal measures its keyboard overlap from the bottom it had before giving the vi
Android: a KeyboardAvoidingView with behavior height/padding outside a modal measures its keyboard overlap from the bottom it had before giving the viewport up (it relaid out every frame while the keyboard was up). macOS CLIs follow.
Android keyboard avoidance fix on top of 1.46.21.
KeyboardAvoidingView with behavior height or padding
outside a modal measures its keyboard overlap from the bottom it had before
giving the viewport up. Measured from the reduced bottom the overlap read 0,
so the viewport was restored and reduced again on the next layout: the
screen relaid out every frame while the keyboard was up (about 60 frames/s
of idle work) and a button docked above the keyboard flickered behind it.Engine wrap measurement fix and iOS transparent modal presentation on top of 1.46.20 (includes #212 ).
Engine wrap measurement fix and iOS transparent modal presentation on top of 1.46.20 (includes #212).
flex-wrap) measures its height at itsScrollView holding the wrap ended one label short:Dialog modal layout like React Native and lower background memory on Android, on top of 1.46.19 (includes the iOS fixes of #209 and #210 ).
Dialog modal layout like React Native and lower background memory on Android, on top of 1.46.19 (includes the iOS fixes of #209 and #210).
Modal's growing child (flex: 1 / flex-grow), ReactKeyboardAvoidingView, fills the window (width stretched, height grown)width: 100% on it. Compact cards keep the centered contract.onStop (cancelled on resume), because some devices never sendTRIM_MEMORY_UI_HIDDEN, and on the UI_HIDDEN/background trim levels.KeyboardAvoidingView resting on the keyboard follows it natively.Android modal keyboard fix on top of 1.46.18.
Android modal keyboard fix on top of 1.46.18.
Android: a panning KeyboardAvoidingView (chat composer) follows every IME animation frame natively; a bottom sheet's entrance keeps its offscreen star
Android: a panning KeyboardAvoidingView (chat composer) follows every IME animation frame natively; a bottom sheet's entrance keeps its offscreen start through early relayouts (no open first frame); a video reports ready once its first frame is on the surface (400 ms fallback). Responsive (#206): per-property window/insets/font-scale signals, Material height class, font-scale clamp, Android lint clean on minSdk 26 (crash fix on Android 8-10).
Android keyboard, sheet and video follow-ups plus responsive signals, on top of 1.46.17.
onProgress and again when the trailing engine frame lands. It used to
hide under the rising keyboard until the animation ended.useFontScale()
clamp/scaled, AdaptiveLayout::clamp(), docs/responsive.md; Android lint
clean on minSdk 26 (the root insets animation callback is set only on
Android 11+, a crash on Android 8-10).Touch follow-ups, on top of 1.46.16.
Touch follow-ups, on top of 1.46.16.
Android text and sheet follow-ups, on top of 1.46.15.
Android text and sheet follow-ups, on top of 1.46.15.
onTextLayout measures the full text of a tail-truncated text
view. It measured the copy shown on screen (already cut with the
ellipsis), so a caption limited to two lines never reported truncated
and its "more" affordance disappeared.Android: overflow:hidden clips to the container box only (descendants overflowing a smaller child are no longer cut); long animated scrolls jump to on
Android: overflow:hidden clips to the container box only (descendants overflowing a smaller child are no longer cut); long animated scrolls jump to one viewport from the target and glide that screen.
Android rendering and scrolling follow-ups, on top of 1.46.14.
overflow: hidden clips the subtree to the container's box only
(React Native semantics). The container no longer sets clipChildren,
which also clipped every child to its own bounds and cut a descendant
that overflows a smaller child (an animated tap effect past its
Pressable was cut off mid-shape).PAM Native 1.46.14 (on top of 1.46.13).
PAM Native 1.46.14 (on top of 1.46.13).
Android sheet keyboard, zoom and camera follow-ups.
interactive); aAndroid sheet keyboard, zoom and camera follow-ups, on top of 1.46.13.
interactive);
a KeyboardAvoidingView that is the sheet's root no longer resets that lift.PAM Native 1.46.13 (on top of 1.46.12).
PAM Native 1.46.13 (on top of 1.46.12).
Android glide, modal and press follow-ups.
contentOffsetAnimationMs no longer cuts a page glidenavigationBarColor (extension property 1010) paints the modalAndroid glide, modal and press follow-ups, on top of 1.46.12.
contentOffsetAnimationMs no longer cuts a page glide
that is already running; re-requesting the glide target keeps it (the
Android twin of the 1.46.12 iOS fix).navigationBarColor (extension property 1010) paints the modal
window's navigation bar with that colour, no system scrim, buttons by
contrast. Android only; iOS has no navigation bar.