Skip to content

Mobile v4 docs: UI component plugins #466

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shanerbaner82 merged 1 commit into from
Aug 10, 2026
Merged

Mobile v4 docs: UI component plugins #466

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions resources/views/docs/mobile/4/edge-components/introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,14 @@ these docs for two reasons:

Drop the prefix for terser templates whenever you prefer — both forms are fully supported.

## Building your own

The components in this section are shipped by a plugin — `nativephp/mobile-ui` — using the same public mechanism your
own packages can use. If you need an element EDGE doesn't have, a
[UI component plugin](../plugins/ui-components) adds a new element type backed by your own SwiftUI view and Compose
composable. If you only need a reusable arrangement of existing elements, reach for a
[nested component](../the-basics/nested-components) instead — no native code required.

## Why Blade?

Blade is an expressive and straightforward templating language that is very familiar to most Laravel users, and also
Expand Down
4 changes: 4 additions & 0 deletions resources/views/docs/mobile/4/plugins/creating-plugins.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,10 @@ php artisan native:plugin:create

This walks you through naming, namespace selection, and feature options, then generates a complete plugin structure.

The first prompt asks which kind of plugin you're building. A **system plugin** adds native capabilities you call from
PHP — the rest of this page. A **UI component plugin** adds new EDGE elements rendered by your own SwiftUI and Compose
code; see [UI Component Plugins](./ui-components) for that path.

<aside>

#### Build Plugins 10x Faster
Expand Down
5 changes: 4 additions & 1 deletion resources/views/docs/mobile/4/plugins/introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@ Plugins have full access to native platform capabilities:

- **Bridge functions** — Call Swift/Kotlin code from PHP and get results back
- **Events** — Dispatch events from native code to your components
- **UI components** — Add new EDGE elements backed by your own SwiftUI views and Compose composables
- **Permissions** — Declare required permissions (camera, location, etc.)
- **Dependencies** — Include native libraries via Gradle, CocoaPods, or Swift Package Manager
- **Custom repositories** — Use private Maven repos for enterprise SDKs
Expand Down Expand Up @@ -63,7 +64,9 @@ components. It's the same model you're already using.

## Getting Started

Ready to build your own plugin? Check out [Creating Plugins](./creating-plugins) for the full guide.
Ready to build your own plugin? Check out [Creating Plugins](./creating-plugins) for the full guide, or
[UI Component Plugins](./ui-components) if what you want to add is a new native element rather than a native
capability.

Or browse the [NativePHP Plugin Marketplace](https://nativephp.com/plugins) for ready-made plugins and the Dev Kit
to build your own.
Loading