If you’ve ever wanted to ship a native desktop or mobile app without leaving PHP, NativePHP is the answer. It’s not a web view wrapper—it embeds a PHP runtime and Laravel into real native shells for Windows, macOS, Linux, iOS, and Android. No web server, no new language to learn.

Quick answer: NativePHP is a framework that bundles PHP (and typically Laravel) with native shells and bridges so you can build installed apps using the stack you already know. As of February 2026, NativePHP for Mobile v3 is free and open source (MIT); desktop support exists separately. Use it when you want one codebase for web, desktop, and mobile without hiring Swift/Kotlin teams. Skip it when you need maximum native UI control or app-store-first design systems.

What NativePHP Actually Is (and Isn’t)

NativePHP is a bridge layer: it takes your PHP (and usually Laravel) app and runs it inside a native application shell. The app lives on the user’s device and runs entirely on-device—no server required. You get access to native APIs (notifications, menus, clipboard, file system, camera, etc.) through PHP functions instead of Swift or Kotlin.

It’s not “PHP in a browser.” There’s no mandatory web server; the PHP runtime is bundled with your app. It’s also not a replacement for learning native code if you need deep platform customization—but for many business apps, dashboards, and tools, it’s enough to ship without touching Xcode or Android Studio.

How It Works: Runtime, Shell, and Bridges

The model is simple: your PHP code + embedded PHP runtime + native shell + bridges to OS APIs.

You write business logic in PHP and Laravel; NativePHP handles the glue to the OS. Official docs describe it as: “By embedding a pre-compiled PHP runtime alongside Laravel, and bridging directly into each platform’s native APIs, NativePHP brings the power of modern PHP to truly native mobile apps.” Same idea applies to desktop.

NativePHP for Mobile v3: Now Free and Plugin-Based

As of February 2026, NativePHP for Mobile is free and open source (MIT). Not a trial—the core and many plugins are free. v3 also moved from a monolithic core to a plugin architecture: you install only the native features you need (camera, file, share, etc.), which keeps apps smaller and eases app store review.

Free (MIT) plugins include Browser, Camera, Device, Dialog, File, Microphone, Network, Share, and System. Premium (one-time purchase) plugins cover Biometrics, Geolocation, Push Notifications (Firebase), Scanner, and Secure Storage. The core “NativePHP Air” shell is minimal by design.

Upgrade from v1/v2: remove the old repo, composer remove nativephp/mobile, then composer require nativephp/mobile and register the plugins you use. The team states you shouldn’t need to change app code beyond plugin registration.

Desktop vs Mobile: One Stack, Multiple Platforms

You can build web + desktop + mobile from one Laravel codebase. That’s the main sell: one PHP team, one codebase, multiple distribution channels.

Jump and Mimi: Test and Ship Faster

Jump lets you run your Laravel app on a real device without compiling. Install the Jump app on your phone, run php artisan native:jump (or ./native jump), scan the QR code, and the app loads from your dev server. Handy for quick iteration; full HMR support is planned.

Mimi (via Bifrost) is a “vibe coding” add-on: describe what you want in natural language (or voice), get generated NativePHP app code, and test in Jump. Useful for prototyping; subscription required.

When NativePHP Wins (and When to Skip It)

Use NativePHP when: You’re a PHP/Laravel team and need a desktop and/or mobile app without hiring Swift/Kotlin devs. Internal tools, MVPs, dashboards, and “wrap our web app for the store” are strong fits. Offline-first or on-device logic fits the model. The fact that Mobile v3 is free lowers the barrier to try it.

Skip or be cautious when: You need pixel-perfect native UI everywhere, complex animations, or platform-specific design systems that go far beyond what a web view + native chrome can do. If your product is a game or highly interactive native experience, a dedicated native or cross-platform UI stack (e.g. Flutter, React Native) may still be better. Also verify desktop licensing and support for your target platforms.

Quick Start and Next Steps

Mobile (v3):

laravel new my-mobile-app
cd my-mobile-app
composer require nativephp/mobile
php artisan native:jump

Install the Jump app on your device and scan the QR code to run the app. For production builds and store submission, use the official deployment docs.

Next step: If you’re already on Laravel, spin up a small project and try Jump. If you’re weighing PHP for backend and native for clients, see PHP in 2026 and Best PHP framework 2026 for context. To ship a Laravel app quickly, start with Laravel 12 todo list tutorial.

References