Hey Everyone!
I’m still using Wappler 3.9.9, is the Wappler 4 stable? Are you using it without any problems already?
Thanks!
1 Like
Yes I am using Wappler 4 
2 Likes
Very stable. Not one issue.
1 Like
On 4.0.1. PHP Projects all good, Node all good, Node and Docker all good, Cordova all good (only issue there is having to elevate to Administrator/root to compile builds but sure that will be rectified). So, all good!
1 Like
Hello. I switched to Wappler 4 from 3.9.9, but I admit that 3.9.9 was more stable for me personally. Working in 4.0.1 sometimes causes minor, non-critical problems. Sometimes it happens that some functionality stops working, for example, it is impossible to call the flow editor on the page (nothing happens when you click on the button). Sometimes the page is no longer displayed in the design view. And other minor troubles. At the same time, the Wappler does not issue any errors and everything comes back to normal if you reboot the Wappler. I am glad that I have not yet encountered anything serious, because of which I would have to go back to version 3.9.9. From the point of view of functionality, I like everything so far. Some points are still unusual compared to version 3.9.9 (working with the connect server tabs), but after I adapt, I’m sure it will be convenient.
My OS: Windows 10
1 Like
The flow not being called is an important issue to me 
1 Like
For me, too. But at the moment, all the problems that I encountered were eliminated after restarting the Wappler.
1 Like
I’m using 4 in mostly ASP projects. I find it fairly good with a few minor bugs here and there that restarting seems to fix. Have to restart multiple times throughout the day. Still trying to figure out some of them so can get them reported.
2 Likes
Im using v3.9.9 
for 3 reasons:
-
I have a lot of work at the moment and I don’t want to deal with new potential bugs that slow down my work.
-
There is nothing new that has version 4.0.1 that I am dying to try, except for the themes
, but I already tried them in the beta versions. -
The most important reason: the new tab system in the server actions does not make any sense to me at this moment and it only slows down my workflow having to open an action that occupies the whole screen, making a change while saving , changing the tab, review the change, if it doesn’t work, change the tab again and start the process all over again.
On the other hand, with version 3.9.9 I make the change, save it and that’s it.
It may seem like a small thing to have to change or close each tab, but in day-to-day work it adds up to a lot of wasted time.
When the Wappler team incorporates split tabs I will probably make the switch, so maybe I’ll stick to 3.9.9 until next month or next year who knows!
2 Likes
I have been using W4 right from beta 4. sometimes certain actions become unresponsive but generally a restart restores functionality. Generally it is pretty stable.
1 Like
I’m still on 3.9.7.
Wappler 3.9.7 is super stable and reliable, and my app development is flying as every little button click is totally familiar to me.
4.0 won’t bring me any more functionality but will put me through another little GUI learning curve, and give me some minor irritations I see as I read this thread… so I’ll stay where I am for a while longer I think until those minor irritations have gone away and I feel the space to deal with the new user interface things to learn.
Much of my use of Wappler follows the good old KISS strategy!
4 Likes
I’m still on 3.9.9. I’ll probably switch to v4 when I’ve finished the project I’m working on. There are some features I’m looking forward to in v4 but also some changes I’m not looking forward to.
In the current version I very much like ‘seeing’ both sides of the project at once - essentially, the backend/server connect on the left and the frontend/App Connect on the right, with the code and design view visible. When working with Server Connect in v4, the right side will be replaced by a large blank space (but at least I have some choice for the colour of the blank space). Hopefully future changes will restore this loss.
I think modals such as the one for Query Builder will be replaced soon, which will be great. However, in the meantime, I don’t think it’s possible to maximise QB in v4. Maximising the window wasn’t a great solution, but it was a lot better than working in the little modal, for queries with many paramters. If only all these little text boxes and modals could be resized - if that were possible I wouldn’t hesitate to switch to v4. It seems there must be a reason why this isn’t feasible. As it stands, it’s the biggest problem with the UI (IMO).
6 Likes
This! I use a lot of server actions and after trying to work with the new layout I really dislike it...
3 Likes
I’ve moved to v4.0.1 but really miss the dual displaying of Server Actions and the front-end page. I’m going with it to make sure I have the latest features and fixes but am very keen for the split tabs feature to be added. If v3.x was going to continue to receive bug fixes then I would probably stay with that for the time being.
4 Likes
I’m still using 3.9.9 for existing live sites as that was stable and I’m used to the interface workflow. I did start using the V4 beta for new projects but not totally comfortable with it at the moment, think it just takes a while to get used to new interfaces especially if you have spent hours using the old one.
2 Likes
I’m using 4.0.1
1 Like
I’ve had a few issues on Mac with 4.0.1 so I’m now back using beta 4.13 and I’m not getting the issues.
I am loving the progress Wappler has made and is still making.
The performance alone makes it worth the upgrade. I’d love to see statistics on how much faster version 4 is, 10x? 20x? 100x?
1 Like
I Like Wappler 4 and look forward to swapping over from 3.9.9 which is stable and even with a few minor issues is working solidly, but for me there are still a few bugs in 4 that need to be sorted first.
I am sure they will get addressed when the team get back off holidays.
1 Like
Yep I agree with this!