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

Announcements
212

:joy::rofl: :joy:

213

thank you :heart_hands:

1 Like
214

:rofl::rofl: :rofl:

215

Hi everyone! Here is the latest roadmap update.

No major changes to the focus for now:

WeWeb back-end

  • Weā€™re still aiming to go live either by the first week of December or early next year. We should soon be able to invite some of you in a closed beta to get feedback. @flo will keep you posted on this.

  • The first tests we are running internally are really exciting.

AI Improvements

  • At the moment we are mostly focusing on making the AI building experience full-stack since it is front-end only today.

  • As a next step we will be working on improving reliability and UX when building with it + optlmizing the token consumptions.

  • The next step will be to improve the experience of building custom components - most likely by enabling it through MCP, so users can create components using Claude, ChatGPT, or any other MCP-compatible client.

  • All of the above will happen between December and the end of Q1.

ChatGPT Apps

  • OpenAI recently announced Apps in ChatGPT. Many of you already reached out to us to check if WeWeb would be able to help building ChatGPT Apps and the answer is yes.
  • We have spent some time working with their SDK and it seems like WeWeb is a great fit to become the first no-code ChatGPT Apps builder.
  • Since we are becoming full-stack, the entire process will be much easier for our users. Broadly speaking, users will be able to expose their services (like databases or backend workflows) through the WeWeb backend and make them available as tools (via MCP server) with a single click. From there, they can build the relevant front-end components in WeWeb, automatically expose them to ChatGPT, and the app will be ready to go.
  • We are aiming to enable this capability as soon as Q1 next year.

Elements

  • Gantt - on-hold, all the team is focused on the items above for now.

  • Stepper - on-hold, all the team is focused on the items above for now.

Improvements & bug fixes

  • As always we are working on UX/UI improvements and bug fixes as they come our way.

SSR is still under discussion. As mentioned, weā€™ll aim to make a firm decision on whether or not to enable it in 2026 by the end of the year.

Feel free to share any questions or feedback in this thread! And if youā€™re a ChatGPT Apps enthusiast, please reach out to me at raphael@weweb.io, Iā€™d love to hear about your needs.

9 Likes
216

Sounds great, thanks for the transparent update Raphael!

The amount of little side projects I see myself rolling out when things move even quicker with an integrated backend excited me (given that youā€™ll decide to move forward with SSR :smiley: )

Wondering what youā€™ll do with asset management when integrating the backend? Would be great if we donā€™t need to call cloudflare anymore and get native front-end uploads that support compression but mostly transformations - that would make for a game-changer!

1 Like
217

Sorry Iā€™m a bit confused. Are you going to take a firm decision about yes or no with SSR by the end of the year on whether you will proceed to its implementation in 2026 or do you mean that you will take a decision by the end of year and you will ship it in 2027 if itā€™s a yes?

218

sorry if it was not clear: we will take a decision by December 2025 wether or not we implement it in 2026.

2 Likes
219

Amazing, thanks for the clarification. If you want beta users and/or perspective into our needs we will make us available at your convenience. Thank you so much!

2 Likes
220

What the community wants:

  • SSR
  • proper versioning and branching
  • design framework support
  • better marketplace
  • bugfixes for hundreds of bugs in the non-customizable plugins

What the Community gets:

  • ChatGPT App Builder (?!?)
13 Likes
223

Your feedback is understandable, though biased given the data we have, which (understandably) you can not be aware of.

Regarding the bugs you mentioned, were they reported through the bug tracking app? Itā€™s true we have bugs in the backlog, but ā€œhundredsā€ is an overstatement, unless many havenā€™t been logged.

224

Hi Raphael,
Thanks for the updates ā€” itā€™s great to see WeWeb evolving so fast!
I was wondering if you plan to release any training materials or tutorials for the new editor, especially around the backend features you mentioned.
Also, will the WeWeb Academy be updated to reflect these changes?
Right now, there are still very few learning resources about WeWeb available online, so updated official content would be really helpful for the community.

1 Like
225

Sure! @Matthew_S (our Education Lead) is working hard on that, Matt can you tell more about your plans to Farouk?

226

Hey Farouk,

Yes, as Raphael mentioned, we plan to have plenty of educational material about the new backend ready for launch. All core features will have dedicated written documentation, and weā€™ll also have recorded build guides demonstrating how to practically use the new backend features.

Once the backend is live, the main focus will be updating the existing documentation and the academy. The academy revamp will likely begin in January and take a few months to complete, as we want to make sure itā€™s done to a high standard.

3 Likes
227

Hi Raphael, Hi Matthew,

Thatā€™s fantastic news, really glad to hear that dedicated documentation and build guides are planned!
I think it will make a big difference for both new and experienced users, especially as the backend opens up so many new possibilities.

2 Likes
228

Hey Niels,

We have compression and transformation features in mind for the upcoming storage feature, but theyā€™ll come later.
The first version will focus on classic storage with public and private options for media assets.

Since file compression and transformation will take time to implement, weā€™re also exploring integrations with media management tools like ImageKit and Cloudinary in the meantime. ImageKit, in particular, offers a very solid free tier.

I should have more details by the end of next week.

1 Like
229

Hi, Iā€™ve been a silent observer on SSR, but I thought it was important to share my use case.

I have a typical pattern for my SaaS, featuring a web app for management built with WeWeb. Each tenant defines details and produces content/product details to share with the public. The tenants want their customers to use an iOS or Android app, so this side is developed in FlutterFlow.

The mobile transactional items are created within the FlutterFlow ecosystem, but the shared content/product detail is accessed via a FlutterFlow WebView to a static page. This is how the tenantā€™s customers will search for and find items to add to their cart. Of course, this is vital!

The static page is essential for speed. So you know, I recreated the experience dynamically in FlutterFlow, but it is noticeably sluggish. A generated static page is super fast.

I spent weeks attempting to create the experience with WeWeb static collections. The static collection/detail page was functioning well until a month ago when it suddenly stopped working. This reinforced my belief that the process was fragile, but I recognize that it could have been something I did.

Because of the decision with WeWeb SSR, I plan to code my way through an Astro-generated SSR over the next few weeks for the content/product page. For my multi-tenant usage, producing an ultra-quick product detail page is the key differentiator.

I truly appreciate what WeWeb offers me as a creator. Actually, I donā€™t just enjoy it; I love it!

Thank you for letting me share my thoughts.

Joseph

5 Likes
230

We also need a functional XANO plugin that doesnā€™t require to refresh the metadata connection every 5 minutes, itā€™s untenable atm.

I know itā€™s been an ongoing problem, and solutions have been attempted, but itā€™s really not hard to repro (new instance, new xano, boom)

1 Like
231

Makes total sense, thanks for the input Joseph!

232

Hey everyone :waving_hand:

FYI, RaphaĆ«l and Flo will be doing a live stream on YouTube on Wednesday to show you a sneak peek of the upcoming backend, answer your questions and update you on all things WeWeb. Hereā€™s a link to add the event on your calendar.

1 Like
233

Should we do a poll on the SSR decision?

  • SSL on the roadmap for next year
  • No decision
  • SSL NOT on the roadmap for next year
0 voters

Still looking forward to the UI change. Iā€™m a sucker for that :))

1 Like