I have been using your product for 2 years now, I can say that I am a regular customer. As someone who has worked in project management for more than 15 years, I would like to recommend you to the team because I do not want to see the product that I love die.
It is good to add new features. Focus on the necessary or requested features first. Do not touch on small changes that are not related to the important features such as adjusting the usage of plugins or messing with things that affect the structure of the system related to users that may cause serious bugs.
Many parts of the UI lack good UX design. Your team should find people with UX experience to work. For example, I encountered a recent problem where the system notified me to migrate the old members to the new version, which did not work automatically. Then, when I pressed some buttons to check, it immediately charged me. In my entire life of using the internet, I have never encountered anything like this. This is a very bad experience.
Your support team’s response is very slow. For example, the bug that I reported in November last year, but your team responded in the support system at the end of January. Some bugs I encountered and waited for months without any answer until I had to find a way to fix it myself. I recommend hiring an additional support team. I suggest that you at least hire a team from India or the Philippines to help solve simple problems for customers. The main team should focus on serious problems.
You should hire an additional bug checking team, or hire programmers from India to help. From what I’ve seen, almost every update in the past has serious bugs. It shows that there is no good bug checking before releasing the update. Don’t forget that your product affects many projects, not just products that users use for personal purposes. Therefore, you need to be more careful than general products.
Before updating, you should do a beta test version for volunteer users to test first to find serious bugs. when volunteer users use it for a while and don’t find any bug, release it as open version.
You shouldn’t release a new version for general users immediately because it will have a widespread impact and you will have to fix the problems for each user, which is a waste of time and resources.
This is my advice from the bottom of my heart. I’m sorry for posting here because there is no forum in the additional advice group. I hope you will take the advice to improve your service and products.
All good advice. After reading many comments on this forum since the release, I’m a bit scared to push anything to production that could result in downtime. I’ve got paying users that rely on my app for their businesses and any length of downtime is not acceptable.
I’d also add that the change in pricing is confusing. The new AI for coded components should have just become an add-on with the original co-pilot left alone for basic help.
From my two years of testing, if in the production section, there is almost no downtime.
However, for the editor, I often encounter bugs when there is an update and sometimes if we fix the system at that time, we may encounter problems, such as in the NPM extension and plugins or modules that are declared deprecated, which requires time to rebuild.
Actually, I have searched and tested almost every no-code / low-code tools in the market. WEWEB is probably the best, especially the feature that allows exporting a rendered web app to our own on-premise server. There are very few that have this feature. In terms of logic, it works very well, even though it is more towards low code. But in the past, AI has helped a lot, except the new AI is not very good, almost not as good as the old one.
there is literally the possibility to self-host now, it has been moments in the past where some period would have justified critics, currently doesn’t seem it is at least fearing to push to push to production seem pretty extreme reaction
tbh
agentic ai and context based model use is the secret recipe for effective and cost efficient on the weweb to meet those two task to put it simply (content understanding, image to text to code,) and fully dedicated (and way more cheaper only for coding task, to avoid maybe “complexity” or cost, gemini with 2M token context, can be a very interesting choice if one would find a ai chat with the full context of a given project to ease the prompting to code js/else
just throwing idea hehe
(Claude is actually now clearly not anymore in the top tier, but is one of the most expensive one still !)
As I said, Weweb is probably the best no-code/low-code tool on the market right now, and rendering to vuejs/html is awesome, faster than many products on the market, so I hope the team will continue to improve to help developers build better apps.
I think so. Actually, AI should be divided into two parts: one part that helps in writing javascript functions or formulas, and another part that is used to generate UI or whatever. Because now it seems that the formula part has been removed and the new AI seems to be unable to answer questions, so I have to ask ChatGPT instead to get answers, which is very difficult to work with.
if you are using the GPT Assistant (WeWeb Assistant by brsdhdg forgothow i name it ) just know that it an assistant made more than 1 year ago and I back then only subscribe one month to ChatGPT plus, so i have no view oir way to analyze/edit/access it, it should be able to do web searching, update the weweb’s documentation each X time (forgot exactly) and be able to self-improve based on potential feedback
tldr: use this chatgpt assistant with caution as well too might not give the latest of the latest very recent updates
