Download the PHP package nativephp/native-ui without Composer
On this page you can find all versions of the php package nativephp/native-ui. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download nativephp/native-ui
More information about nativephp/native-ui
Files in nativephp/native-ui
Package native-ui
Short Description Native SwiftUI and Jetpack Composer components for NativePHP
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package native-ui
NativeUI Plugin for NativePHP Mobile
A NativePHP Mobile plugin
Installation
Usage
Listening for Events
Theming & Colors
Theme tokens live in config/native-ui.php (publish with
php artisan vendor:publish --tag=native-ui-config). Every authored color —
theme tokens, element color props, and arbitrary-value classes — accepts the
same grammar:
Alpha hex is authored in CSS #RRGGBBAA order; the framework converts to the
native wire format. Dark mode is auto-derived from light (alpha preserved)
unless a dark block overrides specific tokens.
Disabled controls draw from the surface-variant (fill) and
on-surface-variant (label) tokens on both platforms — adjust those two
tokens to tune disabled contrast app-wide.
Icons accept platform enum overrides in Blade, matching the fluent API:
Accessibility
Every element accepts a screen-reader label and an optional hint, via Blade
attributes (a11y-label / a11y-hint, or the camelCase spellings
a11yLabel / a11yHint) or the fluent API (->a11yLabel() / ->a11yHint()).
The label maps to accessibilityLabel on iOS and contentDescription on
Android; the hint maps to accessibilityHint on iOS and is appended to the
content description on Android.
Always set a11y-label on icon-only buttons, chips, and tabs — without
visible text there is nothing for VoiceOver / TalkBack to announce. Icons are
decorative (silent to screen readers) unless given an a11y-label. List items
with a trailing icon button take trailing-a11y-label (fluent:
->trailingA11yLabel()) to label that button separately from the row.
Testing
Theme normalization and config write-back are pure PHP — no device, emulator,
or bridge round-trip required. Theme::load() / Theme::merge() resolve
authored color tokens (Tailwind names, red-300/20 opacity modifiers, CSS
#RRGGBBAA alpha hex) to wire-format hex, auto-derive a dark block, and mirror
the effective set into config('native-ui.theme.…'). You can assert every step
of that in a unit test:
Element color and typography props share the same grammar and serialize the
same way. Elements expose toArray(new CallbackRegistry) (via
NativeElementCollector), so you can assert what lands on the wire:
Keeping Theme::pushToNative() off the wire
Theme::load() / merge() fire a NativeUI.Theme.Set bridge call on every
change. In a full Laravel test app, pushToNative()'s runningUnitTests()
guard suppresses it. In plain Pest (no booted app), that guard can't trip,
so mute the bridge in beforeEach() — the same pattern the plugin's own tests
use — and reset() between tests:
License
MIT
