Wappler 8 Roadmap: The Next Big Step Starts Now

[George]

Today we want to share the next big direction for Wappler.

Wappler 8 is underway, and we have started working hard on the beta.

This is not about adding a few isolated features or putting an AI label on the current product. Wappler 8 is about moving the whole platform forward so users can build real full-stack applications faster, with clearer guidance, better production workflows, and more control over the full app lifecycle.

The goal is simple:

Help users go from idea to working, deployable, maintainable apps faster, while keeping the structure, ownership, flexibility, and production control that make Wappler different.

After a short summer break, the focus shifts strongly toward Wappler 8 beta work. If things stay on track, our target is to have the first Wappler 8 beta available in September.

From there, the plan is to grow the beta through gradual weekly releases, with more visible functionality and workflow improvements landing over time.

The final stable Wappler 7 release will remain available as the stable production option throughout the beta period, so users can adopt the new work at their own pace.

This roadmap is being shared as an RFC because we want the community involved while Wappler 8 is taking shape.

The Big Direction

Wappler 8 is about making Wappler feel faster, smarter, more modern, and more complete for real production work.

The main direction includes:

• faster app creation

• practical AI features inside real Wappler workflows

• smarter guided flows for common jobs

• better design and UI workflows

• stronger database, backend, and app-logic tooling

• better support for modern frameworks and architectures

• easier testing, validation, and repair

• stronger Git, publishing, and deployment workflows

• safer environments, dependencies, resources, and secrets handling

• stronger extensibility and a bigger ecosystem

In short, Wappler 8 is about helping users build, validate, deploy, and maintain real apps with more confidence.

The Beta Plan

We want to be clear about how this next phase will work.

Wappler 8 will not arrive as one giant finished drop. The beta will grow step by step.

The plan is:

• Wappler 8 beta work becomes the main product focus after the summer break

• the first beta is targeted for September

• the beta grows through weekly releases

• each release should bring visible product progress, workflow improvements, or reliability improvements

• Wappler 7 remains the stable production choice during the beta period

That means users who want stability can keep building on Wappler 7, while users who want to explore what is next can follow the Wappler 8 beta as it grows.

What To Expect First

The first Wappler 8 beta will not contain everything in this roadmap at once.

The early beta focus is expected to be around a smaller set of visible foundations:

• a clearer and more modern experience in high-visibility product areas

• the first practical AI-guided workflows

• the first direct app-building generators, starting with common app slices such as CRUD or app starters

• early design-time state workflows

• visible Database Manager and/or publishing workflow improvements

• improved onboarding, demos, docs, tours, and first-success guidance

After that, the beta will expand through weekly releases. Some areas will land early, some will mature through the beta, and some are longer-term roadmap directions for 2027 and beyond.

The important point is that Wappler 8 should become useful through visible, usable improvements as the beta grows.

Faster From Idea To Working App

One of the biggest goals for Wappler 8 is reducing the distance between an idea and a usable app foundation.

We want stronger guided workflows for things like:

• app starters

• CRUD and data-backed pages

• database-to-pages generation

• auth and roles

• forms and submit flows

• API and data wiring

• reusable workflow packs and starter app patterns

The goal is faster first success without taking control away from the user.

Wappler should help users start faster, but still leave them with real project structure, real files, real backend logic, and real deployment control.

Practical AI, Not AI For Show

AI is an important part of Wappler 8, but the direction is very deliberate.

This is not about turning Wappler into a generic AI chat app.

The goal is to use AI where it can make real Wappler workflows faster and easier: planning, generating app slices, wiring data, creating forms, reviewing issues, suggesting fixes, and preparing deployment.

That includes roadmap areas such as:

• a stronger AI Manager with clearer guided actions

• AI-assisted app starter creation

• CRUD generation from data structures and tables

• guided auth and role setup flows

• faster data wiring for pages and components

• form-flow creation and submit logic generation

• page polish and common UI improvements

• review, repair, and deployment-readiness guidance tied to real product validation

These AI features are meant to work together with Database Manager, App Connect, design tools, Server Connect workflows, validation feedback, docs, tours, Git, publishing, and deployment tools.

The output should remain editable, understandable, and under the user's control.

That is how Wappler becomes more AI-native while still staying structured, visual, and production-oriented.

Better Design With Real App States

Wappler 8 should also make design work more realistic.

Instead of designing only against static or ideal content, users should be able to work with real app states such as:

• loading

• empty

• populated

• error

• anonymous

• authenticated

• role-based

• mobile and desktop variations

This should make it easier to design complete interfaces from the start and avoid surprises later in development.

It is also a very visual area of the roadmap, and one we think can make Wappler feel immediately more modern and practical.

Better UI Flow, Onboarding, And First Success

Wappler 8 is also about improving the everyday product experience.

We want to make Wappler easier to understand, easier to move through, and better suited to long building sessions.

That includes:

• clearer product area boundaries

• improved navigation and workflow entry points

• cleaner and more focused UI surfaces

• stronger onboarding and first-success flows

• better demos, tours, docs, and in-product guidance

• more direct help where users are actually working

The aim is not only to add power, but to make that power easier to discover and use.

More Modern Frontend And Architecture Workflows

We want Wappler to stay relevant as frontend and full-stack workflows evolve.

That means stronger workflow coverage around areas such as:

• Astro

• Tailwind CSS

• component-driven workflows

• design systems and reusable UI patterns

• stronger reusable blocks, snippets, and app parts

• progressive web app workflows

• static, dynamic, and hybrid site workflows

• composable and API-first architectures

• modern Git-based delivery pipelines

The aim is not to chase trends for their own sake.

The aim is to make Wappler a stronger visual platform for the modern stacks and delivery models developers actually want to use.

Stronger Database And Backend Workflows

Database and backend workflows remain a major part of Wappler's strength, and Wappler 8 should push them further.

On the database side, planned roadmap areas include:

• releasing and expanding the database diagram editor

• richer schema editing

• index creation and editing

• database view creation and editing

• better database tuning and optimization guidance

• backup and maintenance flows

• easier migration handling in publishing and release workflows

On the backend and app-logic side, we want stronger workflows around:

• Server Connect productivity

• data-action productivity

• metadata-driven logic tied to schema and app structure

• auth, access-control, and security workflows

• clearer debugging and validation loops

• API and service integration patterns

This is important because database and backend structure can power better generation, better validation, and more reliable full-stack workflows across the product.

Stronger Testing, Validation, And Repair

Wappler 8 should help users build faster, but also verify their work with more confidence.

That means improving the quality loop around real projects.

Planned directions include:

• a stronger Problems Panel and broader quality workflow experience

• better validation loops around generated work

• smarter repair guidance

• AI-assisted fix suggestions tied to real validation signals

• workflow-completion and deployment-readiness checks

• better visibility into what is working and what still needs attention

This is one of the most important differences between simply generating something and helping users build something they can trust.

Easier Git, Publishing, And Deployment

Shipping matters just as much as building.

Wappler 8 is planned to improve the operational side of app development through:

• easier Git-based workflows

• Git Publish as a first-class publishing path

• clearer Publish Manager target models

• managed deployment flows such as Dokploy

• broader provider-friendly deployment workflows

• safer project-history and release behavior

• clearer release logs, summaries, and handoff output

The goal is to make Wappler stronger not only at building apps, but also at getting them live and maintaining them cleanly across modern environments.

Safer Environments, Resources, Dependencies, And Secrets

As Wappler grows as a production platform, project configuration needs to become safer and more predictable.

Longer-term roadmap areas include:

• improved Resource Manager workflows

• reusable resources where appropriate

• stronger cloud-provider setup flows

• better environment-aware configuration

• safer secrets handling through secure references

• project-scoped versioned extensions

• exact dependency pinning per project

• clearer upgrade and compatibility visibility

This is especially important for agencies, teams, and long-lived production projects.

A Bigger Ecosystem Around Wappler

Another longer-term direction for Wappler 8 and beyond is making the platform more extensible.

That includes:

• better extension APIs and packaging

• stronger support for Wappler-built and community-built extensions

• clearer compatibility and update visibility

• a new Wappler extension marketplace

• broader extension hooks across managers, editors, generators, workflows, and reusable UI surfaces

This is not only about adding more extensions. It is about making extensions safer, more discoverable, and more predictable inside real projects.

Looking Into 2027 And Beyond

As the Wappler 8 beta matures, the roadmap naturally expands further.

The broader direction includes:

• broader framework and component support

• broader AI-assisted workflow coverage

• stronger backend and app-logic workflows

• wider cloud, edge, deployment, and integration coverage

• richer ecosystems and extension growth

• stronger collaboration and agency workflows

• deeper guided app-building flows

The long-term direction is to make Wappler one of the most complete and exciting ways to build real modern web applications visually, with strong full-stack power and strong developer control.

What This Does Not Mean

This roadmap does not mean every item will be available in the first beta.

It also does not mean Wappler is moving away from visual development, real project files, direct backend control, or self-managed deployment.

Wappler 8 is about adding more guided, modern, and AI-assisted workflows while keeping the ownership, flexibility, and production control that existing users depend on.

The beta will grow step by step, and community feedback will help shape the order and quality of what lands.

In Short

Wappler 8 is about making Wappler:

• faster to build with

• smarter without becoming vague or uncontrolled

• more modern across frontend, backend, database, and deployment workflows

• stronger for real production delivery

• safer for teams and long-lived projects

• more extensible as a platform

• easier to learn, easier to try, and easier to keep moving with

We are excited about this next phase, and we are looking forward to sharing it with the community step by step.

We Want Your Feedback

This post is in the Request For Comments category on purpose.

We would especially like your feedback on:

• Which beta areas would make the biggest difference in your real projects?

• Which generators or guided workflows should come first?

• What would make Wappler 8 feel clearly better than Wappler 7 in daily use?

• Which deployment, Git, database, or framework workflows are most important to you?

• What concerns do you have about the beta direction?

As the beta starts to land, your feedback here can help shape the next waves.

That is the direction for the Wappler 8 beta, for 2027, and for the product beyond.

[Freemath22]

It would be convenient for me to be able to move parts of a project from one project to another. Right now, this isn’t possible (it can only be done manually, and I’m not sure if I’m creating a mess in the project), and it’s even impossible, for example, to copy something from one Server Action to another. Or to move a Server Action to the Library....

I’d like to develop a website template with basic features (users, payment, statistics) and then use that as a basis for my own projects. In Wappler, when creating a new project, you can even choose a template.

I’m also thinking about how I could apply changes made to a template project to a live project.

Basically, the idea isn’t new; I’d like to reuse what’s already been done.

[Teodor]

@Freemath22

for example, to copy something from one Server Action to another.

That’s already possible, you can copy steps from one server action to another

[Freemath22]

@Teodor

That’s already possible, you can copy steps from one server action to another

I figured out the issue with copying steps in Server Actions. You can only copy by right-clicking on an existing step. If you create a new Server Action without any steps, I couldn’t find a way to copy them. You have to right-click on an existing step. Well, great—it works. The key is just to know this quirk

[Freemath22]

One more thought. Ever since I started using Wappler, I’ve had issues with the database. Things got really bad whenever I tried to roll back changes. As a result, I stopped using Wappler for database work entirely and now handle that part in DBeaver. I’m perfectly fine with that. Personally, I don’t think it’s worth spending time creating a DBeaver clone in Wappler—Wappler isn’t meant for creating databases. In any case, it would be convenient for me if the option to work with databases in a third-party application remained.

[Teodor]

@Freemath22

You can only copy by right-clicking on an existing step

You can ctrl+click / cmd+click multiple steps and ctrl+c / cmd+c then paste them in another server action.

@Freemath22

If you create a new Server Action without any steps, I couldn’t find a way to copy them.

I don't really understand what you mean here.
How would you copy any step that does not exist in the server action?

[mark1]

Thank You for the most excellent draft outline of our future. Thank you also for consulting the community (as you always do) as we move forward. I am glad to be here and look forward to seeing database management get some love in these 5 areas:

• releasing and expanding the database diagram editor
• database view creation and editing
• better database tuning and optimization guidance
• backup and maintenance flows
• easier migration handling in publishing and release workflows

WapOn!
Mark1

[Freemath22]

@Teodor

How would you copy any step that does not exist in the server action?

Create a Server Action named “One” and add several steps to it. You can then select the steps and copy them.

Now create a Server Action named “Two.” How do you paste the copied steps here? If you click anywhere on the empty Server Action, the “Paste” option won’t appear in the menu.

However, if you create any step within Server Action “Two” and then click on that step, the “Paste” option will appear in the menu.

ctrl+v not working in empty Server Action too….

[Teodor]

@Freemath22

How do you paste the copied steps here? If you click anywhere on the empty Server Action, the “Paste” option won’t appear in the menu.

Well, simply select execute and paste them:

[sitestreet]

I'm really pleased to see a new roadmap as it's been a while since the last one.

My initial thoughts are that this is definitely bold and going to make Wappler much better in lots of ways.

But, will this be backwards compatible so existing projects can seemlessly move into v8 without issues?

And the other aspect I've been waiting a long time for is updated and new Server Actions. I can't see much mention of this in the roadmap. Some examples are Google reCAPTCHA v3, 2FA added to Security Enforcer, replacement for Summernote, image manipulation client-side before uploading, etc.

The main selling point of Wappler (in my view) is the speed of app development. There are lots of server actions which are fantastic and make the app building process a fast and easy one. So adding to that library and updating some of the existing ones would be the priority I would put above software performance which, I would say, doesn't need urgent improvement. It's rock solid and fast to work with.

I hope this is all helpful. I am excited for v8 and will be working with it throughout the beta cycle as I always do.

And just to throw something in at the end.... is Go on the horizon at all? I would say it's the best language for web app development and deployment. It feels like it would be the perfect fit for Wappler and would really give you a massive cutting edge above what you already have.

[patrick]

@sitestreet

And the other aspect I've been waiting a long time for is updated and new Server Actions. I can't see much mention of this in the roadmap. Some examples are Google reCAPTCHA v3, 2FA added to Security Enforcer, replacement for Summernote, image manipulation client-side before uploading, etc.

While they are bundled with Wappler they are separate frameworks and not directly part of Wappler. There is no major update planned for App Connect and Server Connect but there will be updates coming and new components etc.

[brad]

This all sounds great. Though I don't understand what the majority of it means or how it will effect my daily workflow. Maybe we will finally get a Summernote replacement. My main concern is backward compatibility for current projects and if bugs in 7 will still be addressed. I will of course, as always, be experimenting with the Beta. Congrats to the team.

[George]

@sitestreet

But, will this be backwards compatible so existing projects can seemlessly move into v8 without issues?

Well that is why we will be working on Wappler 8 beta first so we can ensure all transitions go fine.

[sid]

@George

More Modern Frontend And Architecture Workflows

This

I have worked a little with newer frameworks in the past couple of years, and they have their positives and negatives compared to AppConnect framework - but the positives out-weight negatives easily.

If Astro is not locked-in, Svelte could be a good alternate too. There are major differences between the two - so not sure if Svelte will be a good fit for Wappler’s visual low-code approach.

Assuming this will replace the front-end AC framework, it will be a breaking change - an LLM driven upgrade path (skills/agents/rules etc) - would be a great addition for converting existing projects.

I can only image what a huge undertaking this would be - looking forward to it.

Other points around keeping the visual identity, stronger DB and Git support with testing tools - all sound great additions for the next version.

[Digo]

I have to admit I don't really know how to feel about this. I'm super happy there's going to be new front end frameworks but as Brad said

@brad

Though I don't understand what the majority of it means or how it will effect my daily workflow.

I know the start of the post says it's not about putting an AI label on the product, but most of this post feels like it's been either assisted by or written by AI, and it's giving a little bit of that classic "We're adding AI!" marketing with buzzwords and the same info written out multiple times. I just don't see the point of adding even more AI to Wappler when it's already starting to out-price the regular consumer (and I'm sure we'll see more of this over the next couple of years). Not to mention it's usually more cost-effective to use the standalone Claude/Codex apps which work with Wappler perfectly (more on this below).

Whenever I see the words "Practical AI, Not AI For Show" or something along them, I get worried. A company I'm with already had to drop a $6k/m bill for a popular helpdesk provider because they went the adding AI label on everything direction and made the normal product totally unusable.

What makes Wappler perfect to me is that it's so straight to the point. I can know what I want to do, and just do it (for the most part, we all get sometimes confused). AppConnect and ServerConnect is what set's Wappler apart, so it's a little sad to see there won't be any major updates to them. There's so many features and/or components that have been requested for ages.

Also, I totally get this is personal opinion, but I think things like the database manager are already and other parts of Wappler that already have existing tools are in a good place. I am personally preferring using exists established database tools rather than the ones in Wappler. I don't think it's really all that useful to put time into making alternatives in Wappler when I'd assume the majority of us here use other tools anyway (I could be wrong, It's just from what I've gathered looking at the forums over the last couple years). Same with AI, I've found the Codex and Claude Code desktop apps/cli work much better by themselves than using the AI in Wappler. I wish time was instead put into completing the roadmap from a few years ago where most of what was mentioned was never implemented.

I don't mean to shit on anyone's parade, but with the enshittification of seemingly every single tool that talks about how they're adding even more useful AI recently and then jacks up the price, I think it's good to be cautious.

With that said, I hope I'm proven wrong. There is nothing like Wappler out there and it's still one of the best subscriptions I have to date. Genuinely, nothing comes close. I think the existing direction was a good direction. I'm looking forward to the new frontend frameworks, especially Tailwind.

[Journeyman]

I think this sounds like a really exciting direction for Wappler. I’m around 80% of the way through developing an application which is currently in user testing, and one of the biggest lessons I’ve learnt is that if you let AI completely take over development, you can quickly end up with an unstable or broken app. It has definitely made me much more disciplined with version control and uploading to GitHub more regularly.

I absolutely think AI should be part of the development process and available where we want to use it, but I also think developers still need visibility and control over what is happening underneath. One of Wappler’s strengths is that you can still understand and manually control the underlying processes, and I think it’s important not to lose that.

As my projects have become more operationally critical — particularly around membership systems, payments, communications, and staging/live deployments — I’ve found there are still some gaps around database and operational management once systems move into production.

The database manager also feels a little flaky at times. It works well initially, but when a migration or schema change goes wrong and throws an error, it can be quite difficult to recover cleanly. Because of that, I’ve gradually reverted to using DBeaver for most database tasks as I find it gives more visibility and control when troubleshooting issues.

Areas where I think Wappler could evolve further include:

• Better database migration, schema comparison, and rollback tools
• Improved import/export and CSV validation tools
• Easier backup, restore, and anonymised staging databases for GDPR compliance
• Stronger security, permissions, and environment awareness
• Built-in audit logging and change tracking
• Better support for encrypted database fields
• Warnings before running destructive SQL queries
• Improved multi-environment deployment and SaaS-style operational tooling
• Built-in security scanning and penetration testing tools

Cyber security is also becoming much more important. As AI-generated applications become more common, AI will also inevitably be used to find vulnerabilities and attack systems. The application I’m currently developing uses encrypted data quite heavily, and I’ve had to create some custom library routines to properly support this.

I also think there is an opportunity for Wappler to include more built-in security testing, such as vulnerability scanning, dependency checking, OWASP-style checks, and some basic penetration testing tools. Even automated checks for things like exposed API endpoints, insecure permissions, SQL injection risks, weak authentication setups, or missing HTTPS/security headers would add a lot of value, especially for smaller developers who don’t necessarily have dedicated security knowledge.

Overall, I think Wappler is already an excellent rapid application development platform, but there is a real opportunity to strengthen the database management, operational management, and cyber security side of the platform as projects become more business-critical and move into live production use.

Regards

[George]

Also as an addition to the above general directions, we will be actually be rebuilding Wappler from the ground up during the Wappler 8 beta, to fully follow the latest technology stacks and best practices.

The goals are big and will have great impact:

• achieving almost zero startup time and ultimate speed
• having great UI responsive and fast UI
• switching projects mighty fast without visible delay
• integrating a whole new build system with support for latest bundlers and also frameworks like Astro and Tailwind CSS
• a whole new generators system for super quickly generating parts of your project and even whole projects. This can be used by both the user directly by offering wizards alike interfaces or the AI to automate things.
• a whole new component editors for creating components - either App Connect, Web Components or Astro components
• making a whole new installer system, with partial updates and the latest Electron 43
• separating the global Wappler extensions and making them install locally per project, this will allow more strict version control per project and avoid braking changes in the future.
• this will allow is to make more major changes and version to App connect and Server connect frameworks without breaking older projects
• the new extensions will be also available fully versioned in a Wappler market place, so you can easily switch and update as needed.
• complete rebuild of our code base and moving to modern es6 modules

So as we will be starting from zero, and rebuilding from the ground up many of our internal frameworks and UI, the Wappler 8 beta will grow gradually from basic functionality to more and more functionality and UI being included.

So the beta will definitely be very basic and rough in the beginning as it won't have all the functionality, but will be gaining more and more as it grows.

The Wappler 8 beta will be also completely separate from the Wappler 7 stable - so you can easily run them together, this is also what we will advise - use the stable for all your production work and try the beta to provides us with specific feedback so we can all make it better.

[sid]

@George

we will be actually be rebuilding Wappler from the ground up during the Wappler 8 beta

A VSCode fork?

[TomD]

@George

The Wappler 8 beta will be also completely separate from the Wappler 7 stable

It would be great if it remained possible to run both versions, permanently, even when v8 is out of beta.

[raymantle]

Please keep ASP support included in the updates if possible. I understand there is a strong industry shift away from ASP support, however there are still existing Wappler users, including myself, who continue to rely heavily on ASP across production projects.