Index

I made 4 plugins for NativePHP

Published

Tags

I've been involved in one way or another with the NativePHP team since the rise of the desktop version. I've followed their journey from the backstage and helped them when I could. I'm extremely proud of what they have accomplished until now.

When Shane and Simon introduced me to the plugin system, I knew I wanted to explore its full potential.

Let me tell you, there are no limits to what you can achieve.

I created four basic plugins to meet my needs and decided to publish them.

But I assure you, you can run any native code you want with NativePHP; it's fast and reliable.

The plugins

nativephp-mobile-screen (free)

A small plugin to keep the screen awake and control brightness from your NativePHP mobile app. Useful for anything that stays on display: dashboards, readers, kiosk-style apps.

Grab it on GitHub.

nativephp-mobile-contacts (paid)

Read and write device contacts straight from PHP. Handy when your app needs to pick a recipient, sync with the address book, or add a new contact after an in-app action.

Available on the NativePHP marketplace.

nativephp-mobile-calendar (paid)

Create, update and read calendar events from your NativePHP app. Great for booking flows, reminders, or any feature that needs to land on the user's calendar without leaving your app.

Available on the NativePHP marketplace.

nativephp-mobile-screenshots (paid)

Capture the current screen programmatically — for in-app bug reports, share sheets, or "save this view" features.

Available on the NativePHP marketplace.

Why paid?

The three mobile plugins above ship with native Swift and Kotlin code I had to test and maintain on both platforms. Selling them on the marketplace is what makes it sustainable to keep them up to date as iOS and Android evolve.

nativephp-mobile-screen stays free and open source — it's a good starting point if you want to see how a NativePHP mobile plugin is structured.

What's next

I have a few more ideas, but I want to see if those will sell first.

Maintaining code is a full-time job, and I want to be compensated for it.

If those three are successful enough, I will likely continue creating new plugins.

At the very least, I will develop one more that I need for an app.

Syntax highlighting provided by torchlight.dev.