I mostly agree with JonL.
Regarding the features of the ‘new design’ and ‘new login experience’. I feel like those aren’t features but necessary for the marketing / overall support of Wappler.
I understand the necessity but it is a bit of a let down to expect improvements / new features and get something that in my view is not necessary. I could login fine and thus don’t need a new system.
(Again, you will have your valid reasons to update it, so this is more about communication than not doing the right thing. It would be received better by me if it’s not sold as a feature, but if you’d say: this week we took a break from building features because our login system really needed an update.)
You start with one thing and then you move to another one without following through.
This line.
This really resonates with me.
By now I’m using many external tools because all the things in Wappler are great, yet 80% finished in my view.
For example, these 2 features for the database manager means I can stop using my 3rd party db manager daily. And just use it once a month or so for some more complicated stuff.
- It needs a better way to filter columns easily. And allow me to write a custom query there.
- Give me multiple windows / tabs in Wappler. I want to for example compare some data from dev and production… I can’t view it side by side.
More examples:
- Stripe integration, it misses a few thingso I can 100% use Wappler’s code. Now I have added 2 lines of codes in stripe.js files which does what I need (my use case is for Stripe connect)
This is a good example of how it really feels ALMOST finished. Just a few more lines of code needed…
-
Resource manager: I can’t find a use for it at this stage. I would love it to be able to manager things like portainer and traefik though. Let me manage the docker-composes there. Let me redeploy them there.
-
Deployment flow: I am using the ‘deploy’ button to manage deploying my app. Now there’s one thing missing from it being fully automated: applying database migrations (How to run database migration through CLI?)
I’m still eagerly awaiting to see an update based on all the feedback in this thread Wappler 4 RFC: Rethinking of the deployment workflow and target settings
Also soon I’ll need better CI and run for example cypress tests before deploying, I would love it to be able to extend/integrate with wapplers deploy button.
Now I could list more but I’m derailing this thread.
TL;DR: my 2cents: be more transparent about what the oadmap is, don’t call things features that aren’t really features
PS @JonL do you perhaps have a good example of such a roadmap somehwere? And/or a (open source) tool to set this up?
Asking for myself 