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.
