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.

Would rather hear about new releases by email? Join the mailing list.

Version 8.3

Projected release: October 7, 2026

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

Features still under development

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 friendly. We also need to retain all the flexible features…
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 about using saved views vs specifying the columns manually. There…

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.

Features still under development

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 that the custom buttons allow, and add to them. And…
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… - [x] New tools for form and element creation and…
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 they can be moved between systems, and committed to version…
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 tools IFTTT, etc, to respond to Formulize. Ideally, eventually, some…

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.

Features still under development

A Questionnaire for the “Formulize method” — The Formulize Method is the process of understanding what application needs to be created and how it needs to work. The features and options in Formulize correspond to decision points and requirements that arise in an application, but translating requirements…
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, that was designed to receive certain standardized bits of inputs,…
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. Then we realized that we kept using the same options…
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 reference the data table names! This will make it easier…

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.