First and foremost, I think weweb is a great app with great people behind it. I don’t want to encourage ANYONE to move away from weweb, or not to start in it. I did learn a lot from learning about other people’s use cases to find out whether weweb is the best fit for me (which I thought it was in the beginning) so I wanted to share…
I’m building a niche marketplace with product registration and lost&found. I’ve started building in weweb about 1,5 yrs ago (side project, and perfectionist…). Since this is not an internal app or tool, weweb was kind of a questionable choice to begin with but I didn’t see many good alternatives back then.
weweb helped me completely work out my mvp, I built my backend in xano as I was building in weweb, making workflows visually helped me really think out all the required steps, it’s been an amazing workflow!
Where it’s been lacking: it started with discovering its SEO limitations and lack of (removal?) SSR. Since SSR was or wasn’t pending on the roadmap for months, I decided to take the chance and hope it would make it back to the roadmap. Sadly it didn’t make it back. Other things that I slowly started missing was better multilingual/translation support, an easy way to make simple things like an actual compliant cookie banner, but also the amount of work needed to polish things with simple animations to make everything feel more professional. In the end, seeing the new MCP missing so many features like working with xano, and so many reported bugs, that was my final straw.
If you’re building an app that doesn’t need to be found on google because you build a separate marketing page, or because it’s internal, I think weweb will be great. If you don’t mind manually building all the pages because the AI isn’t quite there still and neither is the Figma import, then it’s also great.
My weweb project has 32 pages, with everything from profiles, ad listings, chat with xano realtime, notifications, the whole shabam. I have it deployed through the weweb hosting. I used Claude Fable to inspect each page in the chrome browser, and I pasted we web’s workflows as json into claude for each page. Claude also has full read access to my xano backend. This way I was able to fully rebuild the entire project in about 4 evenings (going per-page, manually checking every functionality and iterating on design).
Again, I think weweb is a great tool and part of me feels I shouldn’t post this because it might have a negative effect, but I think in the end the platform should have users that use it exactly for the things it’s good at, and not what it shouldn’t be used for… I don’t regret building in weweb first, I don’t think a fully vibe-coded front-end would’ve come out as solid as it did, if I didn’t have the weweb mvp as an example in the first place…