Hi everyone! Here is the latest roadmap update.
First off, apologies for not keeping you all updated, we’ll make sure to share updates more regularly moving forward.
From a roadmap perspective, our main focus today is helping new users succeed with the platform.
Since the launch of WeWeb 3.0 we’ve experienced massive traction and the feedback is now clear: the AI isn’t reliable enough, and, although building the frontend became a lot easier for most users, integrating that frontend with the backend remains difficult and often frustrating.
As a result, we are working on offering built-in backend capabilities that will let users manage databases, handle authentication, and deploy backend functions all directly within WeWeb’s UI.
A second-order benefit of this new feature set is that it will make it much easier for users to work securely with third-party data sources like Airtable or any SQL database - as calls to these data sources can be routed through a backend that’s automatically set up when linking them to WeWeb. This will bring WeWeb closer to market standards in terms of integration capabilities and, once it’s live, we plan to roll out many new integrations.
Finally, this backend will include full export and self-hosting options with no dependency on WeWeb. The entire, full-stack app will be fully portable and deployable anywhere.
As a complement to these new backend capabilities, we will also introduce key UX/UI improvements to make the application easier to read and enhance the experience of working with third-party backends like Supabase and Xano.
One of the most notable updates is a new tab-based layout that will allow users to quickly switch between the frontend environment (the Interface tab), the backend integrations (the Integrations tab), and the WeWeb backend (the WeWeb Backend tab, if you’re using that feature).
As we approach the final stages of this updated UX/UI, @flo will be sharing content to give you a sneak peek of what’s coming.
We are also continuing to invest in AI improvements, with the goal of making WeWeb the best AI-driven Visual IDE. This transition is taking time, we are not done yet, improvements are incremental, and we anticipate it will take another few months before the transition truly feels “complete.” That said, we’re making steady progress and the end result should offer the best of both worlds: an AI that’s genuinely helpful, and visual interfaces that give users full control over their applications.
Finally, we are dedicating time to improving existing features & elements, and fixing bugs based on the feedback we receive - as reflected in our regular release notes.
Regarding the other important topics mentioned in the community:
-
Figma: we released a proprietary WeWeb to Figma plugin 2 weeks ago, we are getting good feedback and will be working on improvements in Q4.
-
Branching: we have decided to postpone this for now. With our focus currently on delivering better backend capabilities, introducing branching would have deep implications across the product. We want to first stabilize the backend features before opening this complex topic.
-
Performances: we will be dedicating full-time resources to this at the end of the year and we expect to see ongoing performance improvements throughout Q1 and Q2 next year.
-
SSR: we are still evaluating whether this should be a priority. Currently, about 88% of use cases built in WeWeb don’t require SSR. That said, we’re seeing consistent demand for it, and we recognize that enabling it could drive meaningful value for users. I’ve read the community comments and really appreciate everyone who took the time to share their thoughts, your feedback is invaluable. We’ll make a firm decision before the end of the year, and if we move forward, SSR will be available towards the second half of next year. You’ll hear back from us on this in November / December.
Based on the broader roadmap direction outlined above, here is a detailed breakdown of the short-term roadmap:
AI Improvements
-
Improving file upload in the AI chat - support for uploading images and files to provide more context to the AI will go live next week or the week after.
-
Improving reliability and UX when building with AI (including coded components) - this is a fundamental focus that continues to keep part of the team busy. We’ll be releasing improvements incrementally as we go.
WeWeb back-end
- Some parts are already being tested in staging, while other major components are still in development. We’re aiming to go live either by the end of this year or early next year.
Supabase
- Ability to choose different project (branch) for each environment - will go live next week or the week after.
Elements
-
Chat - will go live next week or the week after.
-
OTP Input - will go live next week or the week after.
-
Select - ability to have icons or images displayed in the select will go live next week or the week after.
-
AI Chat - ETA end of October.
-
Gantt - ETA end of October.
-
Stepper - ETA end of October.
As always, feel free to share any questions or feedback in this thread!