Hi there, I wondering if any body has built an app and now is in the production phase, could you please share your experience regarding the performance, speed, native functionality and scalability.
Please specify the complicity level of your app whether it is simple or complex, and how long does your app been published ?
And I have a couple of questions as well.
First here is my project brief
The project is simply a kids Dismissal app that secures the daily dismissal process in the schools.
I need to make a Native ios/android for the users (parents) and a web app as a dashboard for the school’s admin.
Does it really good for production phase or just mvp.
Does the workflows has limitations or not, and i see many people in the forum says that many bugs happens while they did the workflows in the right way.
What if i chose to run my app with both of appgyver for the UI and bubble for the backend and workflows is that a good approach ?
How about the capabilities and users if i have 100,000+ users to handle.
Is firebase a good option or should i go with Xano or Backendless since my coding background is not very strong.
Thanks in advance
Hi @mourad_gamal even though this post is from a while ago and I’m sure you’ve already settled on your backend, I felt the need to provide some insights here.
I think all three backend options are excellent choices. With Firebase you may need some more technical/coding knowledge especially when it comes to spinning up APIs since Firebase is primarily just a database. Xano can definitely provide an entire backend that you can use and develop without knowing code and we have lots of tutorials and resources to get you started
We are building our MVP with Appgyver and Xano. It’s quite an ambitious product (a project management tool) and we are curious to see how far we will come with both tools.
So far, we were able to cover all our backend needs in Xano and it should serve us well in the MVP phase.
As for the Appgyver, it’s a tool with a lot of potential and in the beginning it seems everything is possible, until you start running into bugs and have to invest a lot of time in workarounds or just giving up on the idea that you had. The problem is that some of the bugs have been known for quite some time and there is no ETA when they’ll be fixed. Same applies for feature request that would make the platform even more capable. A lot is being promised but the pace is just too slow.
It seems that the development team can’t catch up with all the tasks and is spread to thin since the acquisition by SAP. One would expect the opposite of that.
In the meantime, others are catching up (just take a look how much FlutterFlow team has done in two years) and at the moment I’m not too optimistic about Appgyver’s capability to become more then a tool for creating quick proof of concepts or simple MVPs.
I can’t imagine the reason for the above mentioned problems is lack of financial resources at SAP, so it has to be something else causing it and It’s not my place to guess it. I can only hope they’ll find their mojo again.