What’s your current experience with AI in WeWeb?

Ask us anything
1

I’ve noticed that the WeWeb homepage now looks a bit like Lovable, with a single AI prompt window. That got me curious about how far AI has come in WeWeb.

When AI integrations were first introduced, I tried them out but they didn’t really work as expected. Since then, I’ve mostly been creating my frontends from scratch, and I’ve been quite satisfied with that workflow.

I’d love to hear from you:

  • Have you tried the new AI features?

  • What works well, and what still feels limited?

And maybe most interested:

  • Do you actually use AI in your WeWeb projects, or do you stick to manual building?

Thanks in advance for sharing your experience!

2

Hi Jan, welcome back :waving_hand:

we have been working on improving our AI builder in several ways.
And since your last visit, 6 months ago we:

  • Improved it’s accuracy
  • Reduced token cost
  • Implemented AI → NoCode Workflows
  • Improved context management ( so you can pass as context either a small part or the entire app to the AI)

Among many small changes.
Our goal is to make it more reliable and useful to everyone with each update :raising_hands:

Astro created a video walking through WeWeb’s current state here

Feel free to try it for yourself and let us know your thoughts about it :folded_hands:

1 Like
3

Hi,

I really love WeWeb and use it for all my projects. In terms of the AI it’s always buggy or throws an error about context being too large (for the last 2 months) - but I think the team fixed this now. However, I would stick with Lovable or another AI first tool if you are planning to use AI for 90% + of the work.

2 Likes
4

I also have the experience that the AI is simply not working at all with the context too large error. As of today it’s still happening, even on a new blank page (i’m assuming the context is related to the project size)

5

Hi @Matto

Context issues have been largely resolved. We have updated our documentation showing you how you can remove/add items to your context: Passing Context to AI | Documentation

If you see a red warning sign in your input, it means it’s time to reduce the context size, otherwise AI requests won’t work.

6

First of all, thanks for all the replies. I have built some production apps in WeWeb, so I have some experience.

I really like the way I can build apps in WeWeb. But since the AI world is moving the so fast, concerns have raised :smiley:

I got the context size errors too, so it didň t really work this way. On the other side, I have tried to use prompts for building a frontend of a new app and it worked surprisingly good.

In the end, it is a bit difficult to decide which platform to choose for new projects. I would love to see working AI integrations in WeWeb, that would make the decisions easier.

7

Thank you Daniel - this was indeed user underflow as I didn’t do anything with the context window. After messing with that I was able to make something happen with the AI

I would note that my default context window was everything, which seems different than the default in the video about the context window (elements on page). Not a huge deal now that I know i need to adjust the settings

8

Hey! I use WeWeb nearly every day for a single project. I use AI most days as well.

Most of my AI use cases are around data formatting - eg a bit of custom javascript to put data into the format I need it to display it. I sometimes use AI for creating workflows too, if I’m feeling a bit lazy. I think this stuff is transformative - I’m not a software engineer by background, and for simple things like this it’s a huge benefit.

I’ve generated a few custom components with AI too, to varying degrees of success. Simple things work well.

I don’t really use it for the UI stuff - yet. I don’t really know why not, I suspect it would be better than me at it.

1 Like