Plant an App Product Roadmap
At Plant an App, we are constantly evolving to help you build better and faster with low-code. Below is our product roadmap. While we aim to deliver these features on schedule, priorities may change based on customer feedback and emerging needs.
Q4 2026 — Version 2
Forms 2.0
A complete rebuild of how forms are designed, run and secured. Forms 2.0 becomes the recommended choice for every new form, and existing forms move over with a guided migration. See Forms 2.0.
Building forms
- Visual Form Builder: a live drag-and-drop canvas organized around two tabs, Build and Settings, instead of four configuration tabs. See Form Builder.
- Layouts: layout containers arrange fields vertically, horizontally or in a free-form grid, and can be nested for multi-column and panel layouts. See Layouting.
- Responsive and Accessible: preview the form at different widths while you build. Forms adapt to any screen, down to a phone, and work with a keyboard and screen readers.
- AI Form Assistant: describe a form in plain words, for example "a contact form with name, email and a required phone", and the builder creates it.
- Custom Widgets: build your own field with HTML, CSS and JavaScript, such as a third-party embed or a control the standard fields don't offer. Its value is submitted with the form like any other field, and its scripts are compatible with a Content Security Policy.
- JavaScript API: read and change the form from front-end code. See JavaScript APIs.
- Productivity: duplicate fields, copy and paste fields, Ctrl+S to save, and inline help on every setting.
Secure by design
- Tamper-Proof Forms: the form's definition stays on the server. People filling in a form can't add, remove or change its fields, including fields added at runtime.
- Server-Side Validation and Sanitization: submitted values are validated on the server, not only in the browser, and text values are sanitized.
- Server-Side Access Rules: whether a form or a field is active, visible or editable can be decided on the server, for example by role.
- Minimal Data Exposure: what the form sends to the browser leaves out configuration and other details that the people filling it in don't need.
- Safe Content: content blocks display only safe content. Scripts, styles, frames and external includes are removed.
- Content Security Policy Support: form scripts load in a way that works with a strict Content Security Policy.
- Secure Files: uploads are checked against the file types and size limits of both the form and the site, and files in secure folders are served only through permission-checked links.
Smarter forms
- Dynamic Forms: fields and containers added, shown, hidden and changed at runtime by the form's own logic. See Dynamic Forms.
- Repeaters: repeating groups of fields, such as line items or addresses, with their own validation.
- Multi-Step Forms: long forms split into steps, with progress shown to the person filling them in.
- Validation: validation scopes, input masks, field hints, and buttons that can skip validation.
- Button Confirmation: "Are you sure?" prompts on form buttons, without a second form.
- Auto-saved Drafts: in-progress answers are saved as the person types, so a partially completed form isn't lost.
- Localization: labels, hints and messages translated into every language of the site.
Moving to Forms 2.0
- Guided Migration: a migration plan shows what moves over, field by field and event by event, before anything changes. The original form keeps working until you switch.
Long-Running Workflows
Workflows gain the ability to wait. A workflow can now run for days or weeks, so one workflow can model a whole business process. Existing workflows keep working unchanged. See BPMN 2.0 Workflows.
- BPMN 2.0 Execution: the diagram you draw is what runs on the server, with loops, paths that join anywhere and errors that take their own path.
- Pause and Resume: a run waits for a timer, an event, a person or another workflow, and continues when it's due. Waiting runs are saved and survive restarts. See Waiting.
- People in the Process: a step creates a task for a person and waits until it's done. See User Tasks.
- Testing and Debugging: breakpoints, step-by-step execution, values you can read and change while paused, the run's path drawn on the diagram, and a replay of every step. See Testing and Debugging.
- Run History: active, completed and cancelled runs, with every step of each run. See History.
- Step-by-Step Upgrade: upgrade existing workflows one at a time, when you're ready. See Upgrading.
- Standard Format: export the process as a
.bpmnfile. - Workflow Permissions: decide who can run each workflow, whoever calls it. See Workflow Permissions.
Entity Lifecycle
States and transitions for any entity, with no workflow to build. Define the steps a record goes through, such as draft, submitted, approved and closed, and the platform enforces them everywhere. See Entity Lifecycle.
- Visual Lifecycle Designer: draw the states and the transitions between them on the entity. See Lifecycle Designer.
- Rules on Every Transition: who may run it, what must be true, and which fields are required. A record can't skip a step, whether the change comes from a form, a workflow, an import or the API. See Transitions.
- Generated User Interface: state badges and transition buttons on the generated list and detail pages, shown only to people allowed to use them.
- Field Rules per State: for example, a field becomes read-only once a request is approved.
- Record History: an audit trail of every change and every transition, with who made it and when. See Record History.
- Record Owners and Read Permission: a record has an owner who can change over time, and reading data is a permission of its own, separate from seeing pages. See Record Owners and Can Read.
Built-in Tasks
Work that waits for a person, managed by the platform. Create tasks from any workflow, from a lifecycle state, or from a BPMN 2.0 step. See Built-in Tasks.
- My Tasks: one list of everyone's work, across every application on the site. See My Tasks.
- Assignment: to a person, or to a role where any member can take the task, with delegation and reassignment.
- Due Dates and Escalation: overdue tasks are flagged, and escalation steps run automatically. See Due Dates, Escalation and Events.
- Task Types: define the outcomes, who gets the task, the due date and what happens on each event, once per kind of task. See Task Types.
- Checklists: a set of tasks a record gets when it enters a lifecycle state. See Checklists.
- Task Actions and Data Source: create, assign and complete tasks from workflows, and build your own task lists. See Tasks Actions.
Dashboard Builder
The Dashboard module grows from a row of KPI tiles into a full dashboard builder, with a visual grid, charts, drill-downs and an AI assistant. Existing dashboards keep working.
Building dashboards
- Visual Grid Layout: drag and resize widgets on a grid, in a builder that works like the Form Builder. On narrow screens, widgets stack in reading order. Hand-written HTML dashboards keep working as a Custom layout.
- AI Assistant: describe a chart in plain words. The assistant writes the query, picks the chart type and columns, and places the chart on the dashboard. It works from the database schema only and never sees the application's data.
Widgets and chart types
- Charts: line, area, bar, horizontal bar, pie, doughnut, scatter and bubble charts, and tables.
- Combo Charts: bars and lines in one chart, with a second axis on its own scale.
- Stacking and Series: stacked bars and areas, and a series per category, for example orders per month for each region.
- KPI Tiles and Trends: single values, and trends that show the latest value, its change and a sparkline.
- Thresholds: tiles and chart values change color when they cross the limits you set.
- Descriptions: an info icon on each widget explains what its data means.
Data sources
- Entities: with the viewer's permissions applied. Count, Sum, Average, Minimum or Maximum, grouped by day, week, month, quarter, year or any property.
- Database Tables and Views: with the same aggregation and grouping, done in the database so charts of large tables stay fast.
- SQL Queries: read-only queries with time and row limits, on the site's database or on other databases through Database connectors. Only Low-Code Engineers can write them.
- Workflows: any output of the application's workflows, run as the viewer.
- Tokens and Constant Values: for values computed elsewhere, or typed in.
- Page Context: tokens such as the page's query string let one dashboard show, for example, each region's data.
Interaction
- Drill-Down: click a point on a chart or a KPI tile to open the records behind it in a popup. The list is a regular Listing, generated from the chart and fully customizable.
- On Click Actions: run actions when someone clicks a point or a tile, before the drill-down opens.
- Show Conditions: hide a widget from some people. Its data is never sent to them.
Performance and freshness
- Caching: each widget's data is kept for a set time (5 minutes by default), so a dashboard open in 50 browsers reads its sources once per period, not 50 times. Data that depends on the viewer, such as entity permissions, workflows and per-user tokens, is kept separately for each viewer.
- Automatic Refresh: widgets reload as their data expires. Tabs in the background wait until they're shown again.
- Data Age: a clock on the widget shows when its data is out of date, and one click updates it.
Mobile
- Plant an App Mobile App for Android and iOS: one app for every Plant an App site. It includes pages, lists, forms, tasks and notifications, and lists and forms can keep working offline. See Mobile App.
AI
- MCP Server: AI assistants such as Claude, ChatGPT and Copilot Studio can read an application's data and run its workflows, as the signed-in user and within their permissions. Sign-in uses OAuth.
Low-Code Developer Experience
- Error Tracing: clear, readable errors that show which application object failed and why.
- Admin Gear and Modern Skin: quick page editing on any skin, and a refreshed PageBuilder skin.
- Records Named by Id: entities without a natural name (orders, tickets, logs) can be identified by their Id.
Platform, Security and Accessibility
- Bootstrap 5 Only: Bootstrap 3 support is removed from every module.
- Security Hardening: updated front-end and back-end dependencies, stronger cryptography, and a more secure rich text editor.
- Performance: asynchronous action execution.
- Linux: the Document Management System runs on Linux, on .NET 10 (LTS). See Long-Term Support › Operating Systems.
- Long-Term Support: Plant an App 2 is a long-term support version, with incremental updates in minor versions and hotfixes for each of them. See Long-Term Support.
2027 — Looking Ahead
- AI-Driven Development: an AI agent that builds complete applications from a description, end to end: the data model, forms, lists, pages, workflows, automations, APIs, roles and sample data. It builds with the same low-code objects a developer uses, so everything it creates can be inspected and changed by hand. Changes are shown before they're applied, and the agent keeps refining the application as the conversation goes on. This extends the AI assistants in Forms 2.0 and the Dashboard Builder, and the MCP server, from single builders to whole applications.
- Kubernetes-Native Deployment: Plant an App already runs in Windows containers on Kubernetes, and the Document Management System in Linux containers, on premises or in managed services such as Azure AKS and Amazon EKS. Next, official Helm charts for a guided setup and upgrades. Platform services, such as PDF and HTML generation, web crawling, vector search and multi-environment publishing, will also run as separate services that scale on their own.
- Accessibility: a platform-wide iteration that strengthens accessibility across every module, aligned with WCAG 2.1 AA and EN 301 549, the European standard for public-sector accessibility. It includes builder checks that help low-code developers keep their applications accessible, and a published accessibility conformance report.
- Event-Driven Integration, Built In: applications already react to events: automation triggers on database inserts, updates and deletes, schedules, APIs that external systems call, and events that BPMN 2.0 workflows wait for. Next, a native message broker:
- actions that publish messages;
- triggers that start workflows when a message arrives;
- durable queues that retry after a failure;
- connections to external brokers such as Azure Service Bus and RabbitMQ.
- Data Privacy and Retention Controls: Plant an App already supports encryption at rest and in transit, encryption of sensitive fields, per-record access control and a full audit history. Next, more privacy controls out of the box:
- marking which entity properties hold personal data;
- retention policies that delete or anonymize records after a set time;
- exporting or erasing a person's data on request, for GDPR;
- reports of who accessed personal data.
- One-Click Deployments: Plant an App already moves changes between environments through the Multi-Environment Orchestrator and Git-based version control. Next, a guided promotion from development to test to production:
- create a new environment from an existing one;
- see exactly what changed, object by object, before publishing;
- publish to the next environment in one step, or pull changes from a higher one;
- settings that differ per environment, such as connectors, addresses and credentials, kept apart from the application;
- a history of every deployment, with the option to roll back.
- App Templates and Public Library: start new applications from ready-made templates instead of a blank site:
- templates for common needs, such as requests and approvals, case management, asset tracking and CRM;
- one-step import of a complete application, with its entities, pages, forms, lists, workflows and automations;
- a public library of reusable workflows and building blocks, from Plant an App and the community;
- export of your own applications as templates, to reuse them across sites.
- Find All References: see everywhere a low-code object is used before you change or delete it:
- where an action type, a workflow, an entity or property, a connector or a token is used, across forms, lists, workflows, automations and pages;
- one click from each usage to the place it's configured;
- warnings before deleting or renaming something that's still in use.
- Process Analytics: insight into how processes actually run, from the BPMN 2.0 run history, Built-in Tasks and Entity Lifecycle record history:
- how long processes and each of their steps take, and where they wait the longest;
- tasks completed, overdue and escalated, per person, role and task type;
- how records move through lifecycle states, and how long they stay in each;
- ready-made dashboards in the Dashboard Builder, and data sources for building your own.
- Decision Tables (DMN): business rules that business users can read and maintain without changing a workflow:
- rules written as tables of conditions and results, for example approval limits, discounts or eligibility;
- used from workflows, BPMN 2.0 gateways, lifecycle transitions and forms;
- tested with sample inputs before they're published;
- based on the DMN standard, so decision tables can be imported and exported.
We can't wait to bring these innovations to life with your feedback and partnership!
This roadmap is tentative and subject to change.