I don’t know what are you basing your opinion on and how much time have you invested in Appgyver (AG) till now, but I have to disagree with certain things you have written and offer some more insights into the state of things in AG, at least from our team’s perspective. I think it is important to talk frankly so that everyone who is evaluating this platform as their tool of choice could make a fact-based decision.
A little bit of background first. We are a team of two, both low-coders and self taught. We have 2-3 years of time invested in AG between the two of us. We have started building an MVP for a project management app in AG. It’s a mobile first solution with web deployment too. Our goal is not to develop a prototype, but a functional product. We are using Xano as our backend and are very happy with it.
In the beginning of every journey in AG, everything seems delightful. One is able to quickly create something that feels as a real app and do that without code. For someone who is not a developer, you suddenly feel like a super hero. Ideas start flowing and you are excited to finally turn one of them into a product or a startup. This is amazing and I salute AG, Bubble, FlutterFlow, Xano and all other companies out there who are democratising software development and making technology accessible in this way.
Once you start digging deeper into your project, you start running into issues and limitations. The funny thing is, that those issues are actually simple things and not advanced at all. I am not talking here about the fact that we can’t import 3rd party react native plugins in AG, no, no, I am talking about simple, every day things that are causing you to spend countless hours in trying to come up with workarounds. You start searching forums and watching every youtube video out there, thinking you might find a solution for it. Eventually you run into a bug report about it, that is two years old and still in the queue. There is no feedback if someone is working on this and will it be ever fixed. Now, multiply this by a factor of 10 and you end up with a tool that can’t fulfil your business goals. You love it and hate at the same time.
For us, this is a real operational and business challenge, to say the least. We have invested considerable amount of time and money into our project and are struggling to deliver on promises to our piloting customers. As the app grows and grows we are running into performance issues too. Things are not as smooth and as fast as they were in the beginning. Simple things that you haven’t noticed before are turning into headaches.
Well, we said to ourselves, let’s switch to the payed version of SAP Build Apps, hopping to find some magical version of AG that works better. After having to wait 2 weeks for the approval by SAP, we finally got it. What did we find there? The same good old AppGyver. It’s not some other tool that has more features, is quicker or doesn’t have certain bugs. Nope. It’s the same thing, it’s just called different. Well, it’s actually less than the community edition, since building the native app is (currently) not supported.
We would happily pay for AG, but I think the pricing has to be similar to FlutterFlow (25-75€ plans) and not some 1.000€ / month plans that are coming from the SAP world.
For all the above mentioned reasons, I would suggest someone who is just entering the field of low-code/no-code to put their bets on another tool. From everything I am seeing, FlutterFlow seems to be doing all good things, but there are others too.
Alternatively, if someone chooses AG as their tool of choice, they should keep in mind the limitations and lower their expectations before you go that deep, that it’s costly to get out.
A year ago, when FlutterFlow (FF) was behind AG in certain things, it was much easier to make this decision. One year after, everything has changed. AG has stagnated and is drowning in the SAP’s world, while FF is a flying rocket.
I want to finish be listing some of the things that are causing us headaches, thus demonstrating we are mostly not asking for advanced things:
As you can see, some of these issues can be tracked to 2,5 years ago. This is not a definitive list by any means, just the top 10 that I could think of off the top of my head.
I haven’t even mentioned the slowness of the composer when a component is selected and styling needs to be changed, or that there is no pagination, filtering and sorting control via variables on the REST API endpoints (making data components useless and making lazy loading not possible), or that the “tree” window and “control” window should be separated in two for better usability, etc, etc. It all adds up very quickly once you try to make something production-ready.
I don’t know what is happening inside SAP and why has the team lost the momentum they had. I presume they are not getting enough resources, since AG is probably just a hobby for SAP, but it is not my place to make a definitive opinion about the unknown facts. Maybe some key people left because of the buyout and they were not able to recover from it. I just know that our team is not in a great position and we would love AG team to know that all the decisions that are being made over there have real consequences to us and our business.
I think this is my last call for something to change soon, otherwise, we will have to think about a plan B and start executing that ASAP.
If that happens, I will be grateful to this group of people for contributing to the democratisation of software development by creating such a great tool and would be very sad that it didn’t work out.