WeWeb - update on what we are working on at the moment

Announcements
129

Hey @Joyce ,

Are you guys planning on introducing any way for us to see what’s being worked on at the moment? It doesn’t have to be roadmap style, just a list of the feedback/high level tickets that are in the pipeline.

Even picking up this thread again on a monthly basis just to give an overview on direction. There’s a few things that are mentioned in the Office Hours video’s every now and again but it’s a bit of a pain to have to get through those just to get an inkling of what may be coming up!

Thanks :slight_smile:

3 Likes
130

Some constructive criticism:

The ‘what we’re working on’ updates in this format and public roadmap weren’t just nice-to-haves. They build community engagement that makes platforms thrive. Now we only have feature requests, no voting, no discussion.

I get that WeWeb wants to execute its vision, but shouldn’t there be balance? Community involvement creates healthy discussions that make the platform better. Strong communities separate successful platforms from forgotten tools. I feel like WeWeb is making a step backwards.

Just my two cents.

8 Likes
131

In my almost 3 years of WeWeb, I can say the roadmap never really reflected what was going on or was followed particularly, it only had more emphasis in the past. I think it would be enough to have a pulse check in this thread from the team every few weeks - even cases saying stuff will get delayed is fine.

8 Likes
132

I feel the same way, I did actually check the roadmap page semi regularly. But it never felt granular or accurate enough to give me a clear picture of what was happening. That’s why I - and probably others - never felt the need to go back to that page frequently.

I think it would be very important to have some way of communicating towards the community. Bi-weekly might have been too ambitious, but lets find an interval that works and stick to it. Or a better roadmap page/tool where more interaction will be possible.

1 Like
133

Hey there :waving_hand:

I 100% agree with all of your thoughts on this.

How about this:

  • Monthly or bi-monthly: Raphaël (our CEO) or Flo (our CPO) to post a new “Roadmap update” topic in the community once a month. I’m thinking a new topic every month would be easier to read and follow than adding to this one where some items have already been delivered but could be wrong.
  • Quarterly: one of them to host a live AMA session on YouTube to provide a bit more context and answer questions in more detail.

Do you think that would be helpful?

15 Likes
134

Yeah the monthly/bi-monthly update would be great - just to keep us in the loop on what’s being worked on!

2 Likes
135

I, like many others are eagerly anticipating SSR and SEO features like dynamic page metadata and dynamic sitemap. I was hoping there was a possibility of getting an update before September?

I would love to continue building in WeWeb because as a solo-entrepreneur, it’s faster to ship with WeWeb and I don’t have to worry as much about technical maintenance. I’ve enjoyed most of my experience so far. But, I am currently exploring other options for my marketplace because SEO features have not been committed to.

If I can at least get an idea the direction that the team is leaning with these roadmap items, that would be very helpful.

3 Likes
136

What options are you considering, @nick ?

137

Hi @Joyce , I’m in the same situation.

I’d love to try your chat feature. Could you please share it with me? Also, if there’s a beta or early access version, I’d like to test the chat component that you’re finalizing.

Thank you !

138

Yes please count me in as well

139

Same here. I’ve been a customer since 2023 and love the building experience. But we build to gain customers, and the clear lack of SEO priority will get me to switch…

despite the obvious waste of time of doing so.

1 Like
140

Hello :waving_hand:
Beginning of September, I was wondering if we would get any news from the team.

The communication from the team on the roadmap is non-existant, and as a dev with growing needs, it’s getting frustrating.
It seems that the direction is to acquire more “beginner” users that would build MVPs with AI, rather than have complex apps that require more complexity.

It’s okay to go that direction, but what’s not okay is to say a feature is going to be released when it’s not.

I would be good to have communication, on where weweb is heading, so that we, developers, can make informed decision on which tool to use for a specific project…

A lot of requested features (branching, SEO, Environment, …) are pretty standard for other no-code low-code tools, and for web development.

8 Likes
141

I keep checking back every other day to see if we have any updates :))

They have to be working on something…

2 Likes
143

Branching has been forgotten. It’s all AI now. Can’t believe there is no attention paid to branching

3 Likes
144

There is no attention paid to anything but AI :slight_smile:

6 Likes
145

I don’t talk much here, but would like to give my input.

With the roadmap gone and the last update in this thread being back in May, my own planning is starting to feel like a bingo board (hehe).

I’d love to suggest a simple 80/20 approach. Doesn’t have to be exact, and of course I realize there’s a lot happening behind the scenes that we don’t see, so this isn’t meant to sound like it should take 100% of the team’s time. More just a framework for balance and visibility:

  • 80% → A clear, public roadmap covering bugs, planned features, what’s in progress, and what’s delivered. This gives the community a shared space to upvote, discuss, and see progress on the things that matter most to us. IMO it’s a low-maintenance job.
  • 20% → Internal priorities like AI progression, backend changes, or other strategic bets the team wants to push forward.

I want to acknowledge the great work you’ve done with AI. It’s getting more stable, and I see how it lowers the barrier for new users. AI is definitely useful for everyone, but maybe not useful enough that all energy should go into it (if that’s what’s happening: from the outside, it’s hard to tell - but community seems to think this).

At the same time, I think there’s some confusion in the community around the priority and use case of AI.

AI is a great entry point, but I’d assume churn could be high if new users are “lured” in thinking “AI will build my app,” only to realize that once things get complex, the hard work is still in debugging and connecting everything. At that point, many might fall back to simpler tools like Lovable.

For context: I learned no-code 3 years ago without knowing what an API even was. If I had been handed an AI-generated frontend at that stage in WeWeb, it wouldn’t have been very useful (IMO) because I wouldn’t understand how it all fit together, and most of my learning came from troubleshooting, YouTube and self-exploring (putting the bits togehter). So while I see the appeal for a subset of users, I’m not sure it fully aligns with the journey of either beginners or advanced builders.

If I look back at WeWeb’s evolution (llm summary):

  • 2021–2022: Survival & foundations → basic builder + integrations
  • 2023: Professionalization → richer components, workflows, Figma import
  • 2024: Platformization → marketplace, CDN performance, first AI integration
  • 2025: Transformation → AI-first identity (majority of big updates are AI-related)

That’s a great story of progress, but it leaves some questions: What’s next? What are the users saying? Where is the balance between AI and the other things we’re all asking for? AI was a big focus in 2025.

I think the takeaway is that everyone has different needs, but we all benefit from clarity. Whether it’s a roadmap, monthly updates, or another format, the most important thing is that the communication is !!!consistent!!!. That way we can make informed decisions, contribute meaningfully to discussions, and feel confident investing our time in WeWeb.

Most SaaS companies keep this simple: roadmap + release notes. It doesn’t have to be fancy, just consistent and easy to follow. Even a lightweight system like Xano’s has worked really well for them.

Here’s an example from Xano’s board (which I’m sure you’re well aware of):

Screenshot 2025-09-09 at 14.18.35
Screenshot 2025-09-09 at 14.18.351920×879 99.9 KB

At the end of the day, we’re all here because we believe in what you’re building.

Keeping the community in the loop in a consistent way would make a huge difference for everyone, both old and new users alike. :folded_hands:

6 Likes
146

Hello everyone,
Thank you so much for the kind and constructive messages, it really means a lot!

I’m sorry for the long silence. We’ve been working on an update, which we’ll share here next week.

In a nutshell for September and Q4:

  • AI improvements

  • UX/UI enhancements

  • A new plug-and-play backend integration

  • Ongoing improvements to the Figma plugin

  • Still deciding on whether to implement SSR

  • Branching postponed (with reasons to follow)

1 Like
147

Hi @Raphael and thanks for talking to us. Just to let you know that the editor is falling apart!! I am not even exaggerating small bits here and there are just breaking down. I honestly think the team should proritize STABILITY. Before throwing in another “shiny“ integration, please make sure everything in the current product is actually working and the integration will not break another thing. Please prioritize the things on the roadmap you told us about before too.

Look around at the community, check the threads, do you see anyone jubilating as much about many new updates anymore? When was the last deluge of 3rd party content you saw in our forum? Do you remember how excited people were when the supabase 2.0 pluging dropped a few years ago?? The wave of 3rd party content? The product is buggy now, and that is making everyone groan.

I genuinely think everyone here will happily tell you to do the “big” things in the road map SEO-friendliness, fix the docs so they are up-to-date (seriously :folded_hands: ), Branching and fixing the editor so it loads FAST and it stops crashing. To be fair, if that is stable, with how far you guys have come with the AI push, I don’t think anything will be impossible for your team. Thank you and best wishes :folded_hands:

4 Likes
148

Thanks for the update Raphael!

Since you’re writing “still deciding on ssr” - I’m seeing an opening for me to weigh in, haha! For me, I built my first website back in the 90’s just before html 4.0 came out, so I’ve been in the space for a while… but I’ve never really enjoyed coding (or learning the syntax anyway). I’ve built many websites I’m proud of, but most were not the result of just my imagination, but a result partly steered thanks to what snippets I could find and adjust from tutorials, others’ sources, on stack overflow, templates etc. Webflow came along and it’s great but also very limited. Weweb is the first tool that has allowed me to build something truly how I want it to work! It’s been a joy learning it and using it. It’s allowing me to make things function exactly how I want it to! It’s truly the tool I’ve always wanted to have and some of the AI features (formulas / js mostly) is making the process so much faster! I’m really becoming a big fan, and I have some other projects I’d like to rebuild in weweb because they would become so much better…

There’s only 1 thing that’s making me a) doubt if I made the right decision building my current project in weweb and b) stopping me from starting new projects in it - and that’s SEO / SSR.

My guess is you / the team had weweb in mind mostly for web apps that don’t rely on seo as much, but sometimes you launch something, and your users take it a different direction than you may have intended or expected (like building marketplaces, directories, or just simple webpages). And I think improving the AI will only draw in more people that will want to use it for cases that end up requiring excellent SEO.

Sorry for the long story, but it’s because I don’t want to have to move away from weweb, just because of SEO/SSR! One, because I love using it, but also because there’s no good alternative (which means there’s an opening that you can take, before something like nordcraft takes it).

Just my 2 cents :slight_smile: . Meanwhile I’ll keep on building my mvp in weweb, trusting things will work out, haha!

3 Likes
149

Hi @Raphael, thanks for the update :raising_hands:

Just want to add my voice in support of SSR. We love WeWeb, but performance, SEO, and speed are the main things making us consider alternatives right now. Solid SSR would be a game-changer — faster loads, better SEO, and more confidence to scale projects. Really hope this gets prioritized, it would keep us happily building here :flexed_biceps:

7 Likes