Hi everyone! Here is the latest roadmap update, apologies for the extra week I took before updating you all:
-
Improving the quality of the AI-generated UI & logic: this will go live tomorrow or Thursday! The AI generation has improved by an order of magnitude on the front-end, the UI generation is much better, and logic handling is significantly more reliable (it finally works!). We haven’t yet focused on enhancing the AI’s integration with Supabase, that’s planned for a later phase. Our next priority is getting the AI to work with the design system, so it can produce consistent designs across pages. This will require 3-4 weeks of work. During that time, we’ll also collect your feedback to further improve and stabilize the new AI generation.
-
Datagrid improvements:
- Custom colors for the tick box - in production
- Add Range selection border color property and checkbox selected background color property - in production
- Expose filters & sort and add init filter and sort properties - in production
- Add a property
lang
in the settings tab to allow translations - in production - Fix when you filter the column and use the select all option, it ignores your filter and selects the entire collection - in production
- Ability to drag / reorder rows - under development, should be live towards the end of June.
- We haven’t prioritized any additional improvements to the datagrid for now, but let us know if you think we’re missing something important.
- Here is the progress on our long list of components:
- Gantt - in QA
- Chat - in QA
- AI chat - in QA
- Currency input - in QA
- OTP Input - in QA
- Stepper - in QA
All of the above should go live between this week and the second week of June.
- We are also working on the following improvements for our existing elements:
- Add a focus and a blur trigger for the input-mask element.
- Add an active state for the button element.
- Add a focus state for the select element.
- Add an option to customize the font family for the select element.
- Enable the binding of an array for the select element.
- Make sure the select element triggers the workflow when using unselect.
- Enable the reorganization of tabs & slides from the side bar for the tab and slider elements.
All of the above should go live between next week and the end of June.
-
Detaching modals from pages and making them accessible at project level: This will also go live tomorrow or Thursday. We’re currently putting the documentation together, and we hope you’ll like what we’ve built. We’re excited to hear your feedback so we can keep improving the new system on the fly.
-
New organization of global workflows and edge functions + revamp of the plugins panel: This is currently in QA and is expected to go live around mid-June. Once released, it will also unlock the ability to create backend workflows for Supabase directly within WeWeb, using a no-code interface similar to our existing workflow builder. It’s an exciting improvement for Supabase users.
-
Vite setup to reduce the build time: After running a few tests, we’ve decided to postpone the release. We identified a few areas that need improvement before going live. The release is now planned for mid-June, we’ll keep you posted as we get closer.
-
We have the following fixes planned on the roadmap:
- Fix the fact that the name is not saved when saving a template into the library - in production
- Fix the calendar issue binding events - in production
- Add a Help button to the top bar of the editor so users can easily access chat support - in production
- Fix tooltips in the add menu (they are not displaying right now) - will be in production tomorrow or Thursday.
- Fix the issue where changing the language on a dynamic page causes the parameter to become undefined - in QA, should be live soon.
- Fix the input’s On enter event bug - in QA, should be live soon.
- Fix the fact that the color property of icons from the ‘Phosphor Fill’ icon set does not work - in QA, should be live soon.
- Fix a copy paste issue on the Code element (when pasting, the first character is not pasted) - under development, should be live in 2-3 weeks.
- Fix the fact that it became impossible to create dropzone in components - under development, ETA TBD.
- Make sure dropdowns can be opened in the datagrid - under development, ETA TBD.
- Fix the fact that while setting the progress bar’s color the gradient color menu opens, while it should open the standard color menu - under development, ETA TBD.
- Other topics on the roadmap:
- We’re implementing MFA (Multi-Factor Authentication) for accessing the WeWeb editor. It won’t be activated automatically for all users, but teams that want to enable it will be able to do so directly from the dashboard - should be live early June.
- We are adding custom domain when connecting through SSO for Supabase - should be live late June.
- Support & ticketing system: Our new ticketing system is live! We’re now using Intercom, which should make it easier for you to track the status of your tickets. We’re also revamping the ticketing app, the new version is expected to go live around mid-June. And last but not least, we’re super happy to welcome @rivan_sigarlaki to the team as a Customer Care Engineer, helping us further strengthen our support capabilities.
- Other topics under qualification:
- SSR: Our exploration confirmed that this is technically feasible, which is great news. However, it would require about 4 months of roadmap from many of our developers to build. Given the effort involved, we’ve decided to postpone development for now and focus on other priorities. The good news is that we now have a clear understanding of what’s needed to make it happen, so we’ll feel more confident prioritizing it in the future. We will re-evaluate the opportunity in September.
- Branching: Branching, in its current stage of qualification, is a substantial piece and is still under technical review. We’re not ready to share precise conclusions yet, but we do know it will require a significant development effort (we’re currently working to better estimate how long that will take). Once we have better visibility, we’ll keep you informed, but I suspect this will end up being postponed to later this year, for the same reasons as SSR. We know this feature is highly anticipated by many of you. Some large teams (>20 developers) have already found interesting ways to organize their workflows using smart substitutes for branching. To support you in the meantime, we’ll publish an educational piece this summer to help you structure team collaboration more effectively.
- Figma plugin: this is under qualification, we hope to be able to prioritize it in the weeks to come. I’ll update you once we know more.
As always, feel free to comment and add your feedback in this thread in case you feel we missed something important!