hehe, Iām screenshotting all the feedback and sharing the product team so they can explore possible updates in the coming weeks 
1 Like
okay thanks @Joyce for your reply. Indeed, itās not very intuitive but I understand the constraint behind it.
Maybe you could display explicit hints or use cases somewhere e.g. āYouāre using Supabase the old way ? Do thisā, āYou want to try Wewebās backend ? Do thisā
This is not an easy subject. Many users have also mentioned that logs are hard to read and make it difficult to understand what is happening. Thatās why we transitioned to displaying workflows and allowing you to see results for every action. We are actually planning to add an expand button there soon to improve readability.
If you wish to see data in the main panel now, you can add a Log action to your workflows to see the results there. However, I understand your frustration and know that adding log actions manually is cumbersome.
I have a feeling that the priority for you is seeing what I call ānetwork actions.ā Would a dedicated panel that displays all calls made and results received work for you?
2 Likes
Quick question on the pricing (sorry idk if this is the place to discuss like this but maybe that will help others), Iām building apps as a freelance and I have my clients. Iām on the partner plan.
What is your recommandation as a building and workflow pricing ? Should I build everything on my side, and then when itās done, I transfer the project to my clientās, who can only subscribe to a front-end only plan ? My point is, is it possible for my clients to pay only for hosting the app, as they donāt build, and on my side Iām paying my partner plan so I can build.
or maybe a little ā+ā button below the log to add the log action and details in a handy way ? You keep your logic and the user is not frustated anymore, he can easily chose to add it or not
When I perform custom authentication and save the API key as an environment variable, I always get the ānot authenticatedā error. But the API call works in n8n.
Hey Bastian 
Would you mind creating a separate topic with some screenshots or a short video walking us through what you are trying to do and where youāre stuck or, if you believe itās a bug on our side, create a ticket here?
Itāll make it easier for us to follow up and find a solution for you 
Hello!
Your customer must have a paid seat plan, regardless if they develop the app or not.
Regarding the development flow, there are two options. Both assume you have a Partner Workspace.
- You can develop the app in your workspace. When ready, you can transfer the app to your customerās workspace. There is an option for that in āSettingsā of the project. You must be a member of your customerās workspace. After you transfer their app to their workspace, they can either export and self-host it or purchase a WeWeb Cloud plan to host it on WeWeb.
OR
- Your customer invites you their workspace. You develop the app in their workspace. When ready, they can either export and self-host the app or purchase a WeWeb Cloud plan to host it on WeWeb.
2 Likes
I was surprised seeing the release with the same imperfections Iāve highlighted to @Aneeq. Some of them are very annoying:
- When I use new āparametersā property of the page url, I canāt see it as a variable.
- Iāve found the collections, but I wonder, why canāt we access the new backend views similar to how we did it before? Do you wanna scare the old developers having two types of working with sources? Collections were the killer feature of WeWeb, unlike Webflow, Webstudio, Bubble or any other lowcode tool. The way to see all the data clearly.
- I expect it to work for redirection, it has no ānavigate toā option, so I need to work old way, from checking the previous step. When I open it and create a OnAfter workflow, thatās not obvious hot to go back to upper workflow.
- You have 4 āGear-typeā icons. The 6th feeling doesnāt help/
- Thereās no UI zoning. Project-specific actions are mixed with visual editor settings. Please move all vision-mode-changers at the same place, if the button āpreviewā jumps to the top-right, leave it there. āDeployā button can be on the left from āPreviewā, like in Bubble, because usually we preview before deploy. Also, you can extend the help with hotkeys. Please rely on key codes, not codepages (in Serbian and Russian hotkeys stop working).
- My avatar now has no real meaning except when we work together with someone (I have no stats, how many users use this mode). It can open the settings, it will be more intuitive. You can move it with Undo/Redo to the left, near the āHelpā button, extending āUndo/Redoā to backend changes.
- All editing-related stuff can be placed inside the editor canvas. Please zone the elements to āproject-relatedā, āuser-relatedā and āeditor-relatedā.
Some additional wishes:
- If itās possible, extend the canvas width switcher to make it possible to set custom breakpoints. Like in Webflow and Bubble.
- Please update āJS Collectionsā with a bug editor and fix a field overlap bug.
1 Like
As a temporary solution could we at least get the old return format (below) as a toggle in the code editor settings?
Above is definitely better for readability than below.
Or better solution, restore the old return format and if people want access to the raw response instead add some buttons like the other helpers (toggle, find, replace) to make it appear. Maybe even a copy button that copies the raw response to the clipboard.
Some news:
- We donāt have a workflow editing option from the page settings. It means, If we have some redirects in āon page loadā, weāre no longer have an access to them and the page is ruined, including everything in it.
- Some calls now return a veeery detailed error json, which is not useful at all, because before the update everything just worked.
This looks good, Iāve had a quick use of it and Iām impressed considering itās only in Alpha.
@Raphael @Joyce just curious, what features and improvements are the team going to be working on now?
This man knows what the people want
Hey @TechaSoftware thanks for asking!
Short term (April - May):
- Improve the new UX/UI based on usersā feedback.
- Improve the quality of AI generation quickly (Iām very excited about this, I believe it will work really well fairly soon thanks to the new AI system we built).
- Add a few things that are missing in the new WeWeb backend: the ability to easily copy/paste data between environments (editor / prod / staging), the ability to import data easily (from a csv for example), automatically set up auth workflows & pages when a user sets up WeWeb auth and support for CRON jobs.
- Improve support for workflows involving AI calls: add more native actions + give users the ability to either use their own AI API key or use our infrastructure to run AI workflows.
- Improve the Stripe integration and add more integrations.
- Resume work on ready-made elements.
Then, the prioritization will mostly depend on user feedback, but here are a few things we want to cover in the months to come:
- Roles & Permissions (RBAC)
- Branching
- Release a WeWeb CLI so users can do things in WeWeb from Claude, Codex, Cursor, etc.
- Add audit features (performance, security, compliance, etc.)
- Ongoing: bug fixes and improvements based on feedback (on AI, the WeWeb editor, the WeWeb backend, etc.)
What do you think about this list? What would you like us to focus on?
5 Likes
Hey @raphael,
Thanks a lot for the update, really exciting direction! The new version is honestly great, and building with WeWeb has become a real pleasure.
One thing that would be amazing to include is database triggers. Theyāre key for handling data consumption and aggregation efficiently, especially for more advanced use cases.
Also, weāve noticed that some videos are starting to be published on YouTube, which is great. It would be incredibly valuable to have a full end-to-end tutorial showing how to build an app from A to Z using a pure WeWeb backend, covering all the main aspects.
On my side, Iām currently building with Xano, but my next app will definitely be built using WeWeb Tables really excited about the direction youāre taking there.
Keep up the great work 
4 Likes
yes that sounds great, a cli would be great for weweb. is it plan to create also supbase ai functions for example that the ai create a new supabase table field or is it only plan for weweb database?
Perfect! We are putting together a build guide video that will cover building a fullstack app from A to Z. It should come online in May. Noted for the db triggers!
1 Like
Thanks for asking! The first version will be WeWeb focused, then weāll adjust depending on usersā demand. But thinking outloud, I think it would probably make more sense to use both Supabase MCP & WeWeb CLI from your IDE / Terminal rather than looping everything through the WeWeb CLI. To be confirmed as we build it!
2 Likes
Are the new integrations coming soon going to be available for front end only as plugins?