Remember that weekend project you never finished?
Mine started as a Saturday "let me try running Laravel inside a Tauri webview" thing some weeks ago. I thought it would be a joke. Today both the iOS and Android Portal apps just hit the stores, and you can boot a real Laravel + Livewire app on your phone in under 10 seconds without compiling anything.
What is NativeBlade
It is a framework that runs your Laravel + Livewire app inside PHP-WASM, packaged as a Tauri 2 native shell. Same Blade, same Livewire components, same Eloquent, same artisan, same routes. Plus the native plugins (camera, biometric, NFC, push, geolocation, haptics, filesystem, clipboard, scanner) exposed through a NativeBlade:: facade.
You write this:
public function checkIn()
{
return NativeBlade::biometric(fn ($b) => $b->reason('Confirm check in'))
->vibrate()
->toResponse();
}
And it runs offline, on the device, with the user's fingerprint prompt, and Livewire stays in charge of the UI.
Portal is live on both stores
Portal is the companion app that loads any NativeBlade bundle from a URL. You point it at a hosted bundle or at your laptop running nativeblade:dev, and your app boots in seconds. No Xcode, no Android Studio, no rebuild loop while iterating.
Try it without installing PHP, Laravel, or anything
Install Portal from one of the links above, open it, and paste this URL:
https://nativeblade.github.io/demo-bundle
That URL serves a pre-built Laravel + Livewire bundle the same way php artisan nativeblade:dev --platform=portal would serve your local app, and the same way php artisan nativeblade:bundle packages a bundle for production. The Portal app downloads it, boots PHP-WASM, and you are inside a working app in a few seconds.
When you want to build your own:
composer require nativeblade/nativeblade
php artisan nativeblade:install
php artisan nativeblade:dev --platform=portal --host=192.168.0.10
Scan the QR in the terminal and Portal loads your local app live. Edit a Blade file, watch HMR push the change to the device.
Your AI assistant already speaks NativeBlade
The framework ships a built-in MCP server (Model Context Protocol). Claude Code, Cursor, and Windsurf can connect to it and introspect your live project: which plugins you declared, every method on the NativeBlade:: facade, the architecture recipes, and the framework docs. So instead of the agent hallucinating outdated Laravel patterns, it queries the real source of truth in your repo.
Practical effect: you can ask the AI "build me a checkout screen with biometric confirmation and a barcode scanner" and it will know the exact facade signature, the right Form Object pattern, the state wrapper convention, and the matching Blade components — because the MCP server told it.
To go even faster, point the agent at the right UI kit for your form factor:
Mobile — nativeblade/ui-mobile. Konsta-inspired Blade components, iOS and Material themes auto-detected per platform. composer require nativeblade/ui-mobile.
Desktop — The README recommends Flux UI (the official Livewire UI kit by Caleb Porzio). Any Livewire-compatible library also works (Filament, mary-ui, TallStackUI, Wireui).
With MCP plus a UI kit, the AI has structural knowledge of the framework and the component vocabulary to use. From zero to working screens is measured in minutes.
What is actually shipping in the box
Full Livewire 3 with wire:nb-navigate for native-feeling transitions
SQLite on device, auto persisted to IndexedDB so it survives cold starts
Cache::* auto wired to the same SQLite, no config
Native plugins: camera, gallery, video picker, biometric, barcode/QR, NFC, push (FCM and APNs), geolocation, haptics, clipboard, opener, OS info
OTA bundle updates without going through the store
Component primitives: header, bottom nav, drawer, modal, safe area, animate, icon, image
Codegen for the AppServiceProvider config flowing into the Android manifest, iOS Info.plist, Tauri capabilities, and Cargo features
Why I think this is worth your time
If you already know Laravel and Livewire, you do not need to learn React Native, Swift, Kotlin, or even Tauri internals. You write a Livewire component, you ship it on iOS and Android. The framework handles the bridges.
The repo is here: github.com/NativeBlade/NativeBlade
Docs, recipes, and the architecture guide are in the README. I would love to hear what you try to build with it, and what breaks. Issues, PRs, and "this is dumb because X" comments all welcome.
