First some criticism and hopefully taken as constructive.
I’ve been thinking about writing this post for quite some time now. It all started growing since the last great release 4.0. New UI, moving features to tabs, globals, migration to electron, websockets, etc.
For me everything since then has been quite underwhelming except for the performance boost and the new branding and I could easily live without them. The rest of “major” features for 5.0 haven’t ticked for me: new login experience, OS theming sync, design view improvements, working modes, ngrok and resource manager.
I’m still subscribed to Wappler because of 3.0 and 4.0 which are still worth every penny. If it were for 5.0 I wouldn’t. To put it in other words: Wappler 5.0 is the new Iphone 14. If you were selling licenses for every major update to Wappler I wouldn’t have migrated to 5.0
One of the main reasons from my perspective is that you lose focus on delivering features. You start with one thing and then you move to another one without following through. And to be fair and honest this also happens to me and I believe it happens to a lot of people, specially developers. It’s commonly known as the “da Vinci” syndrome because the guy started more projects than he finished. He was always looking for the next shiny thing.
The ask:
If you are planning on continuing building a user-driven product please migrate to a proper voting and roadmap solution because right now we don’t have a clue of what’s being built and the votes in the feature request section make no sense. Features are being built based on the amount of crying people do. Sometimes even crying doesn’t work.
It should have at least these features:
1) Roadmap
We don’t need specific dates nor approximated dates like Q3 2023. We just need an under consideration, rejected, planned, next and completed sections so we can somehow plan our projects accordingly.
2) User voting
Limit the number of votes each user gets to 10 or something like that. If everyone gets infinite votes we as users don’t prioritise our needs so you guys don’t get the real picture of our needs. If a user has reached his limit and wants to vote on another thing he should remove his vote from another feature unless that feature is currently being developed. Votes should be freed if a feature is built or rejected.
3)Voting cleanup
Scheduled cleanup to remove votes from users that have not been subscribed for some time.
4)Moderation
Someone has to review, merge and perform moderation actions on the ideas.
5) SSO
Just because.
Last updated: