Why We Built NativePHP#

For decades, application development has been defined by an assumption that most developers simply accepted: the web, desktop, and mobile were separate worlds.

If you wanted to build a web application, you reached for frameworks like Laravel. If your users later wanted a desktop application, you rewrote it in Electron or a native language. If they wanted a mobile app, you started over again with Swift, Kotlin, React Native, or Flutter. Every new platform meant a new codebase, a new toolchain, and often an entirely new team. This division has shaped the software industry for years.

We believe the time for such division has come to an end.

Several independent trends have converged over the past few years. Devices have become dramatically more capable. PHP itself has matured into a modern language and continues to grow. Laravel has evolved from a web framework into a complete application platform. Livewire has shown that rich, reactive user interfaces no longer require abandoning PHP, and the surrounding Laravel ecosystem now provides nearly every piece required to build sophisticated software from start to finish.

At the same time, AI-assisted development has fundamentally changed how software is written. The cost of producing code continues to fall, making developer productivity less about typing code and more about choosing the right abstractions. The frameworks that will thrive in this environment are those that allow developers to solve problems once instead of repeatedly translating the same ideas across multiple platforms.

The Opportunity: One Stack, Every Platform#

Historically, supporting desktop and mobile dramatically increased the cost of building software. Every platform introduced another engineering organization, another release process, another backlog, and another set of platform-specific problems. Even when business logic remained largely identical, teams found themselves maintaining multiple implementations of the same product.

Cross-platform frameworks have significantly improved this situation, but they still begin with the assumption that you're building a mobile application first. If your business already exists in Laravel, adopting another framework often means recreating years of work before you can deliver value.

We think the opportunity is larger than making mobile development easier; it's about making building fully native mobile experiences as simple as building for the web.

Instead of asking developers to choose between web and native, we believe the framework they already use should naturally extend to every device their users own.

Why NativePHP?#

NativePHP exists because we believe Laravel is capable of being much more than a web framework.

Millions of developers have spent years learning its conventions, building businesses around it, and creating applications that power real companies.

That investment shouldn't lose its value simply because users expect a native application in an app store.

Rather than introducing another abstraction layer, NativePHP allows Laravel itself to become the application. PHP runs directly on the device, Laravel continues to power routing, validation, queues, Eloquent, Livewire, and the rest of the framework, while NativePHP provides access to the operating system through familiar APIs.

NativePHP for Mobile alone is on track to more than 10x adoption in 2026 vs 2025. PHP has one of the largest developer communities on the planet, with conservative estimates at 5M developers globally and it's still growing.

With Laravel and PHP's strong presence in LLM training data, leveraging AI tools to build mobile apps with PHP is a no-brainer. Thousands of developers are already seizing the opportunity and taking advantage of the faster speeds and lower costs of development.

The result isn't a different way of building applications; it's the same Laravel development experience targeting entirely new platforms.

That distinction matters. Developers aren't learning another framework. They're extending the one they already know.

Why Now?#

Five years ago, this would have been extraordinarily difficult.

Modern smartphones weren't as powerful, embedded PHP runtimes were largely unexplored, and many of the tools that developers now rely on simply didn't exist. More importantly, Laravel itself hadn't yet evolved into the cohesive application platform it is today.

Today, those pieces have aligned.

The remaining challenge wasn't convincing developers they wanted this. It was building the infrastructure that made it possible. Running PHP inside native applications, exposing platform APIs, packaging Laravel for desktop and mobile, supporting development workflows, and integrating with existing Laravel projects required years of engineering before developers would ever write their first line of application code.

Infrastructure often goes unnoticed when it succeeds. That's exactly how it should feel.

Looking Ahead#

We believe the boundaries between web, desktop, and mobile will continue to disappear.

Users don't think in terms of platforms anymore; they simply expect software to be available wherever they are.

Developers shouldn't have to think in terms of platforms either. They should be able to focus on building products while the underlying infrastructure adapts to the environments those products need to run in.

That's the future we're building toward with NativePHP.