Introducing Wapplify – The All‑in‑One Marketplace for Wappler Extensions

[ncx]

Why Wapplify?

Developers – Monetize Your Talent

• Publish once, sell forever.
• Automated licensing & payouts.
• Zero manual install guides—our Desktop App handles the “Install” click.
• Centralized analytics.
• Community feedback & ratings – coming soon.

Creators & Agencies – Build Faster

• Hand‑picked, production‑ready extensions.
• One‑click installation straight into Wappler.
• Continuous updates & instant rollback.
• Skip weeks of coding; launch features today.

Wapplify Web & Desktop – 100 % Wappler‑Made

Our web app and desktop app are coded entirely in Wappler, showing Wapplify is a real, working product.

What Makes Us Different?

• Seamless Sync – Your purchases and sales sync automatically between the web dashboard and desktop app. Manage or buy from either place; installs happen in the desktop app—everything just works.
• Zero‑Friction Installs – Hit Install in the Desktop App and your extension is ready inside Wappler, no ZIPs, no terminal.
• Always Up‑to‑Date – Auto‑update notifications keep your stack bulletproof.
• Global Reach – Sell to the entire Wappler community.
• Quality by Devs: We believe in empowering developers with the freedom to manage their code, and the community helps us identify the most valuable tools. Nevertheless, Wapplify retains the right to delist or disable any extension found to be in breach of security protocols, licensing terms, or established coding standards.

Current Extension Line‑Up

Extension	Use Case
Event Logger	Track every action in your app. Self Service or Cloud option
Directus API	Point‑and‑shoot Directus integrations.
Custom Preloaders	Slick loading animations.
Custom Database Actions	Custom queries always paginated database with JSON support.
Password Generator	Secure passwords on the fly.
SweetAlert2	Gorgeous alerts & modals.
Anti‑CSRF	Harden your forms instantly.
Redis Commands	Super‑fast cache & queues.
Novu Headless	Multi‑channel notifications.
MongoDB	NoSQL power, zero pain.
GitHub Private Repo	Pull private code securely.
Check ZIP Properties	Validate uploads.
ZIP Folder Tree View	Explore archives visually.
ZIP Count and Size	Instant ZIP stats.
Lexical Editor	Text-editor based on Lexical framework by Meta
Shiftly	Visual business-hours & shift-planner that drops straight into any form

Calling All Extension Developers

Earn Recurring Revenue – Set your own prices and reach a global audience.

Disclaimer

Wapplify Marketplace is an independent, commercial platform. It is not affiliated with, endorsed, or sponsored by Wappler (Dynamic Zones International B.V.) or any of its subsidiaries.“Wappler” is a trademark of Dynamic Zones International B.V.“Wapplify Marketplace” is a commercial brand owned by NeuroCortex.ec.All other trademarks belong to their respective owners.

Wapplify Web and Desktop made 100% in Wappler

Beta Starts Soon

Mark your calendar: 20 July 2025 – 12:00 UTC. That’s when I open the doors for beta accounts. Jump in early and be one of the first to test-drive Wapplify.
www.wapplify.cloud

Stop reinventing the wheel. Start Wapplifying your workflow!

[Alexander_Paladines]

Hey everyone!
Just wanted to share a quick update about the project and some important changes happening under the hood.

This project was originally built entirely in Wappler using the Electron base. However, Wappler relies on the @capacitor-community/electron package, which has become quite problematic for building and maintaining Electron apps. The project isn’t actively maintained anymore and causes several compatibility issues, making some things harder to implement compared to using pure Electron.

Because of that, only the Desktop app is now going through a complete refactor using a new stack: SolidJS + Tauri.
The web version will continue to be developed and maintained 100% with Wappler.

More news about this refactor coming soon!

[Apple]

Is this project already open to public? If yes, I wouldn't advise requiring login in the index page, users should be able to view the available extensions without logging-in, even for SEO purposes

[Alexander_Paladines]

Thanks, @Apple!
That’s actually how the first version was built. However, due to Wappler’s limitations when working with Electron, several issues came up.

The original idea was to share the same codebase for both the web and desktop versions, which made maintenance much easier at first. But as Electron started causing more roadblocks, every fix or workaround turned into double work to make it compatible with both environments.

Since Electron apps don’t have a traditional backend, protecting pages and keeping the app secure required a lot of extra effort. After all, it’s still a desktop app that can be easily modified, and with Wappler-Electron that becomes even trickier.

In my experience, Wappler + Electron works fine for small projects that don’t rely heavily on native OS features or advanced API logic. But for more complex use cases, it quickly becomes limiting.

Another issue was the UX: the dashboard included direct actions like an “Install” button and other interface elements, but maintaining those features securely in Electron was complicated. Simply using dmx-show or conditional regions — even with JWT — wasn’t enough.

For that reason, the web version remains the original one — 100% built with Wappler (for now). In the future, that could change, especially since the new Tauri desktop app will have its own independent UI and architecture.

In the end, it made more sense to rethink the entire flow with a proper login system and move away from Wappler-Electron for the desktop version.

[Alexander_Paladines]

A sneak peek at the current Desktop App (SolidJS + Tauri)

[franse]

@Alexander_Paladines looks very nice, tried a few things with tauri and is growing very fast..
But can you share what kind of issues do you have with capacitor electron since I'm in a very small project?

[Alexander_Paladines]

The issue isn’t with Capacitor itself, but with @capacitor-community/electron, the outdated template Wappler uses for its Electron layer. It hasn’t been maintained for about two years, which led to problems at least for me like:

1. Deep linking and multi-layout handling – only one route file per project is supported.
2. Node integration issues – caused by the capacitor-community layer, not present in pure Capacitor + Electron setups.
3. Unstable IPC communication between ipcRenderer and ipcMain.

I managed to fix most of them with custom code, but maintenance became too complex. That’s why I decided to refactor the desktop app with a more modern stack.

Still, for small projects that don’t rely heavily on JWT APIs or native OS features (like file access), Wappler + Capacitor works fine — and likely remains great for mobile apps, even if the Electron layer stays outdated.

[kfawcett]

It is possible to build secure desktop and mobile apps with Wappler. APIs should always control access to data whether web or desktop and there are ways to force/redirect to a login page if a user isn't logged in. You could check out https://brightyard.co for what is possible. Downloads are available in the dashboard for MacOS and Windows.

Configuring Electron, MacOS, iOS, and Android really falls outside the scope of Wappler at this time. Hopefully the integrations will improve if enough of us use them. Currently, they only “minimally” integrate them with the ability to modify the files and one click build/pack the apps, without having to use a CLI.

I have successfully configured deep linking (after lots of trial and error, and a little help from @franse on a bug that was occurring after the app received the deep link) and JWT, and the same code can run on the web and desktop/mobile apps.

Although, it's not really ideal for the code you write for a desktop/mobile app to be used for web applications since it's just HTML, CSS, and JS. You could port most of the code between the two, but there are slight differences, like using App/Page Flows in mobile apps for third-party APIs. In web applications you would typically put all of that in server-side APIs (i.e Server Connect APIs), there's typically no need for App/Page Flows for that type of action.

Generaly in web applications you want to use a web server (e.g. Express for node.js) and take advantage of partials/includes to build the page dynamically, leading to centralized portions of your page (header, footer, menu bar, etc).

Let me know if you need help if you decide to continue using Wappler for non-web clients.

[Alexander_Paladines]

Correct, @kfawcett — exactly! I managed to fix all those issues with custom code, just like you did.

@Alexander_Paladines

I managed to fix most of them with custom code, but maintenance became too complex. That’s why I decided to refactor the desktop app with a more modern stack.

The web part (wapplify.cloud) is still 100% built with Wappler + NodeJS. The only part being migrated is the Electron desktop app, which is now moving to SolidJS + Tauri.

The desktop version of Wapplify is designed to handle file operations — creating, deleting, managing folders, securely downloading and unzipping files from S3 (where extensions are hosted), and running several custom frontend scripts to communicate with Electron using ipcRenderer, apiServices, and JWT logic with native Electron safeStorage.

All of that was possible with pure Wappler at first, since the idea was to keep a single shared codebase for web and desktop. But in practice, that doesn’t scale well in Wappler’s Electron setup. Most of the core functionality ended up being custom code, and at that point, it could’ve been done from scratch with any IDE — especially now with AI coding assistants helping so much.

After noticing that @capacitor-community/electron is basically an abandoned project, I realized it wasn’t worth maintaining long-term. Maybe the Wappler team will fork it someday or even add Tauri as an official alternative. But for new projects, using that stack doesn’t seem like a great idea.

For now, wapplify.cloud stays 100% Wappler-made, and the desktop app will continue its migration to SolidJS + Tauri. The old Wappler-Electron version will remain as-is, without further updates — at least for now.

Still, if at some point I manage to get investment or new collaborators interested in the project — which is ultimately commercial — I’d love to explore improving the Electron side properly. That could even help the Wappler team consider adding better long-term support for desktop or mobile applications in their roadmap.

[George]

@Alexander_Paladines

After noticing that @capacitor-community/electron is basically an abandoned project, I realized it wasn’t worth maintaining long-term. Maybe the Wappler team will fork it someday or even add Tauri as an official alternative. But for new projects, using that stack doesn’t seem like a great idea.

Yes that is exactly the reason we are looking also for alternatives, for some time now, to replace capacitor electron and indeed Tauri is the most promising one.

So we will be definitely working on integrating Tauri.
It is a perfect fit with its small runtime, great security and it also work well with App Connect.