Formulize Roadmap

The master branch of Formulize is always stable and ready to install. Features completed for an upcoming release are available immediately — you don’t have to wait for a formal release to get new capabilities.

Version 8.2

Projected release: June 8, 2026

This release is focused on reorganizing the admin-side homepage, and integrating the management of users and groups with the management of forms and data. This is the last major part of the version 8.x vision for simplifying the ways you use Formulize to create complex applications.

Features available now on the master branch

• Apply new/changed default values for elements to existing entries — When you add an element to a form, you might need existing entries to receive the default value. Now you can apply the default value to entries where there is…

• Map Screens — You can now display entries on a map, if they have latitude and longitude data. You can also choose from three basic map types: roads, terrain, or satellite imagery. Or…

• Support sorting by multiple fields — You can now SHIFT-click on a column to add it as a secondary (or tertiary…) sorting level. So you can sort first by Province and then by City, for example….

Features still under development

• Simplified, Unified System Admin Controls — The separation of Formulize and XOOPS/ICMS system admin stuff is very confusing for users. In general, users need easy access to these features: 1. User management, including which group they’re…

Version 8.3

Projected release: August 3, 2026

The major feature for the 8.3 release will be a new look, with an all new theme.

• New consistent theme — The current theme, called Anari, is now six years old. That’s way too long in web years. We need a more modern theme, that is mobile first, not just mobile…

• Tidy up of list-of-entries screen Entries and Interface tabs — In the admin interface for List of Entries screens, the Entries tab and the Interface tab have a lot of powerful options, which are not well organized. Especially the parts…

Version 9.0

Projected release: February 15, 2027

Version 9 is all about better tools and techniques for creating applications, and managing existing applications.

You will be able to import and export applications, using the config-as-code features, that will be expanded to provide comprehensive support for all major Formulize features. This will make it possible to have a library of default applications, and even an app bazaar made up of community contributed applications. This will also make it possible to commit your configuration to version control.

The MCP server will be complete by version 9 (or sooner) so that you can use AI assistants to do everything in Formulize that you can do through the administration UI. And the public API is also a priority, so that you can easily integrate Formulize with other systems.

• Automated entry creation workflows — This is a critical function in formulize that we have been coding manually for ages, the custom buttons allow for some of this, but we need to generalize the behaviours…

• MCP updates — There are various improvements and updates necessary in the MCP server, to access more Formulize features, and to streamline and improve how current capabilities work. Some things we could/should do……

• Configuration as code — This feature is critical to the future of Formulize, as the basis for importing and exporting applications. We need to be able to store all configuration settings in files, so…

• Public API — Need a rest API for events (add, update, delete), and also for updating records and proper rest API for makecsv capability. Litmus test for this is using Make or other…

Version 9.1

There will be polishing and nice-to-have features that couldn’t make it into the 9.0 release. That’s what 9.1 is for. As things progress on 9.0, more issues will be added to 9.1.

• Proper controller architecture — Formulize has never had a strong, separate controller. The “smart dumb functions” like displayForm and displayEntries actually manage a lot of the controller work. If there were a strong controller,…

• More types of lists — In the beginning, the display of lists was hard coded. In the second version, it was still hard coded, but it was now encapsulated in the “smart dumb function” displayEntries….

• Reorganize/prefix all database tables to improve semantics of config storage — All data tables with user data should be formulize_data_ and other tables should be formulize_config_ This will require some changes under the hood, in all parts of the code that…

This roadmap is generated from the GitHub issues for Formulize. View all milestones on GitHub for the full picture, or join the discussion to share feedback on priorities.