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: May 6, 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.

Already available on the master branch

These marquee features are complete and ready to use right now:

• All element types need to be, split up and converted to have their own classes — - [x] derived - [ ] insert break (text for display both columns) - [ ] areamodif (text for display left/right columns) - [x] textboxes - [x] textarea boxes -…

Coming in version 8.2

• 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…

• Tidy up of list-of-entries screen Entries and Interface tabs — Design already prepared (for Actua). Columns lists need to include only the forms that are directly connected to this form in a one-to-one (or are on the many side of…

Version 8.3

Coming in version 8.3

• New consistent theme — There are inconsistencies and bad things in the spacing and layout of modal forms, and subform rows, etc, lots of places. A new theme is in order in general, and…

Version 9.0

Coming in version 9.0

• More types of lists — Like we now have simplified elements, that are variations on the formerly complex “select” element (through classes that extend the select class and admin templates that streamline options), we could…

• 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 it specifically triggered through the button….

• MCP updates — Some things we could/should do… - [ ] Return the complete data from the entry that was just written, in create_entry and update_entry. This would give the AI insight into…

• Configuration as code — - [x] ele_order should simply be determined by the order of the elements in the json file - [ ] need to support a mixture of .json files in the…

• 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

Coming in version 9.1

• Reorganize/prefix all database tables, clean 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 GitHub issues at each site build. View all milestones on GitHub for the full picture, or join the discussion to share feedback on priorities.