Weave Code
Laravel Laravel Package
nativephp/laravel
NativePHP for Laravel lets you build native desktop apps with the PHP and Laravel skills you already have, bundling your code into a standalone application for Windows, macOS, and Linux without learning a new language or framework.
Laravel wrapper for the NativePHP framework
Frequently asked questions about Laravel
- What is NativePHP for Laravel used for?
- NativePHP for Laravel lets you package an existing Laravel application as a native desktop app for Windows, macOS, and Linux. It wraps your app in a native shell with windows, menus, tray icons, notifications, clipboard access, and file dialogs while keeping Laravel routing, Eloquent, queues, and Blade. It is best suited to self-contained apps such as internal tools, field or ops apps, and kiosk-style products rather than server-dependent multi-tenant SaaS.
- How do I install NativePHP in a Laravel application?
- Install it with Composer as nativephp/laravel, then use the package's toolchain commands such as native:install, native:serve, and native:build. The toolchain is opinionated about project layout and expects build-host prerequisites, including desktop tooling on the build machine. For a first evaluation, try it on a small, self-contained Laravel app rather than a legacy app with heavy server-side dependencies.
- Which Laravel and PHP versions does nativephp/laravel support?
- Check the package's stated compatibility matrix before committing, because NativePHP tracks Laravel majors and native shell versions. A Laravel upgrade can become a coordinated multi-repo event, so verify your supported Laravel and PHP version window aligns with the package. Pin versions for production builds and test upgrades in a branch before rolling them into release engineering.
- Does NativePHP work on Windows, macOS, and Linux?
- Yes, the desktop targets are Windows, macOS, and Linux, with native windows and menus plus system APIs for notifications, clipboard, file dialogs, and tray icons. Mobile targets for iOS and Android exist in the broader NativePHP line but have different maturity levels from desktop. Scope roadmap commitments per platform rather than assuming identical readiness across all targets.
- Can I use Eloquent, queues, Blade, and routing in a NativePHP app?
- Yes, NativePHP keeps familiar Laravel conventions, so your routes, Eloquent models, queues, and Blade or Livewire views continue to run inside the packaged runtime. The important architectural difference is local-first execution: many apps use a local SQLite-first store, optionally with sync to a server. Confirm that your data model tolerates that approach rather than assuming a live authoritative database at all times.
- How do I build and distribute a NativePHP desktop app?
- Use the native:build toolchain command to compile and package the application, and rely on the package's packaging and auto-update support for distribution. Decide early who owns code signing, notarization, and store submission, because those are release-engineering and organizational dependencies rather than code dependencies. For mobile targets, also account for app-store policy and code-signing risk before making commitments.
- Is NativePHP a good fit for an existing multi-tenant SaaS?
- Usually not as a thin add-on, because the local-first runtime model changes assumptions about authentication, sessions, and data residency. It fits best when the Laravel app is already largely self-contained, with a Blade, Livewire, or Inertia front end and minimal reliance on server-only services at request time. Internal tools, field and ops apps, and kiosk-style products are better candidates than a shared multi-tenant SaaS.
- How do I test a NativePHP app during development?
- Use native:serve for the local development loop and native:seed to populate the app's local database during development and packaging. Keep your normal Laravel tests for domain logic, but also test the packaged runtime separately because crash reporting, log shipping, and error tracking behave differently outside a server fleet. If your QA or fixture pipeline depends on seeding behavior, verify it against the 1.3.1 native:seed fix.
- What are the alternatives to NativePHP for Laravel desktop apps?
- Most alternatives fall into two camps: Electron or Tauri with a JavaScript front end, or shipping the Laravel app as a web app or PWA. NativePHP's distinction is that it bundles a PHP runtime and native shell so you keep Laravel routing, Eloquent, and Blade without learning a new language or framework. Evaluate alternatives against your target platforms, code-signing requirements, and appetite for maintaining a separate front-end stack.
- How actively is nativephp/laravel maintained and what upgrade risks should I plan for?
- The 1.3.x line is being actively stabilized at the tooling layer, with 1.3.1 fixing the native:seed developer command, which suggests a contained blast radius for that patch. The broader risk is a small maintainer surface relative to framework-level dependencies, so pin versions and keep a vendor or fork contingency. Platform targets also differ in maturity, so scope roadmap commitments per platform and plan Laravel upgrades as coordinated releases.
Weaver
How can I help you explore Laravel packages today?