Hey there! I just wanted to take the time to update you all on what the team is working on at the moment.
We will do this every two weeks to increase transparency and gather your feedback on our short-term roadmap more frequently.
We are working on improving the quality of the AI logic generation (workflows). The logic generated from generic prompts rarely works properly, which is disappointing for most users. This is our most complex technical challenge with AI so far, but we are on a promising track. We’ll update you on our progress.
We are working on improving the quality of the UI generated by the AI. The improvement we worked on is already in QA, so it should be in production this week.
We are working on the datagrid improvements as discussed separately in the community. We’ll notably ship:
Datagrid Height: new parameter Fixed / Auto
Column Width: New parameter Fixed / Flex
New type for cell: custom → It’s now possible to drag and drop what you want in it
New Trigger: On row selected
New parameter: on/off toggle for Column Resizable ; Column movable
Ability to “pin” column (frozen column)
These improvements are in QA, so if all goes well it will be live this week if not, the next.
We are working on a long list of advanced components to fill out the add panel and improve the UI gen:
A new, improved calendar
A new, improved file upload
A new, improved Kanban
Breadcrumbs
Gantt
Currency input
Skeleton Loader
Chat
AI chat
Carousel / Image Slider
Stepper
OTP Input
Timeline
Tree View
Comments & Threads
These elements will be gradually shipped between this week, the next and the one after.
We are working on a better system to manage modals: we want to technically detach them from a page to make them “globally” accessible to the project. This will make it easier to re-use them across a project and to maintain them in time. Since this way is more standard, it will also be easier for the AI to use it and fix a few problems we have at the page generation level. We do not have a precise ETA for this feature yet but our best estimation is 4 weeks.
We’re improving the organization of global workflows and edge functions to make them clearer. This week, the team will transform them into “actions,” simplifying how they’re used. Instead of calling a global workflow with an “Execute Workflow” action or triggering an edge function in Supabase with “Invoke Edge Function”, you’ll be able to call them directly as actions. This feature is part of a broader effort to improve the organization in the editor, making projects easier to read, understand, and maintain. We do not have a precise ETA for this feature yet but our best estimation is 3 weeks.
We are working on setting up Vite which should reduce the build time (project deployment time) and facilitate’s our developers’ lives. ETA 2 weeks.
All the above is currently being developed & QA by the dev team. Now here is what the product team is working on:
Revamp of the plugins’ panel: this is part of the broader effort to improve the editor’s organization.
Better source code visibility in the add panel: this will improve the experience of forking coded components.
Environment management with Supabase.
Branching feature: the qualification was nearly complete last summer, but we shifted all our efforts to WeWeb 3.0. We are now reopening this topic and adapting it to the 3.0 version.
Figma integration: our Figma plugin could be largely improved with AI. The product team is working on the improvements qualification.
Thanks for all of these updates! Can you please make sure to add a trigger for “On row deselected”? I recently worked on a project using AG Grid and realized that row selection is really only workable if you can also act on deselect.
The reason being that you’re going to probably want to add the row object to an array so that you can manipulate the selected rows. Let’s say you want to let the user select rows and then click a “delete all” button, which then loops through the rows in the array and deletes them on the backend. If a user adds a row by accident but there’s no way to remove it from the selected array, all of the selected rows will be deleted.
Excellent. WeWeb is always surprising us and improving based on community feedback. I am completing 2 years of WeWeb and it is impressive how much it has evolved. Supabase has advanced a lot and I believe that attention to this integration will be important. One example is working with test and production environments.
yes, I am sorry that support for bugs is lagging behind, but we are currently hiring to improve this.
I checked your tickets, the Supabase one is the most urgent, I’ll have it prioritized in the next batch.
I’m experiencing a bug with AI chat. When undo things made from there, the next prompt won’t have the submit button enabled. I always have to refresh the entire page.
If there’s a properly page to share feedbacks about AI feature, please let me know.
Is there a chance your documentation will see an uplift too. While the overall quality is very high, for new users like myself I would like to see greater breadth to what’s available.
Could you also increase the academy content too please?
