We discussed the Fireback limitations in another document, in this document we are going to explain why and when you can use fireback.
In my personal experience, 99% of projects I have seen do not cover the basic needs of user authentication flows, even the basic ones. Developers usually tend to only deliver the signup and signin form, without much error handling, without giving the user alternatives to change their email, update their profile, generate tokes, OAuth features, and many more.
Interestinglly, many of these features are repeated in almost every project, and lack of details makes the users feel uncomfortable and requires the support to be involved with every user interaction. By installing Fireback as your project foundation, you will instantly having most of these features without any coding, available as public REST API, for your React Native, React and front-end project.
Important: Fireback is not cloud service, rather a executable file, which you need to host yourself, and stores all data on your own server in SQLLite or MySQL.
Fireback supports user signup by email, SMS, password recovery, user settings, roles, multiple teams (workspaces) full permission management per user, complex and large file uploads, complex queries and many more along these lines.
Let's go and discuss the scenarios which you might consider Fireback.
If you are an startup and not having so much man power, instead of building login flow, user management and many more, focus on building your own product. Fireback as many users of experience into, it's rather hard to build such software by an small team, and even if you can build it.
If you are looking for classic and standard user operations without any complexity yet, you can use Fireback.
Fireback is a good school with lots of details into it, that shows how a real backend show behave. If you are mid-level programmer and want to improve and expand your knowledge, download a copy of Fireback, start your first user login/signup form withit.
If you are too busy to build most part of your backend, use Fireback for now. We have implemented GRPC, HTTP, Socket with "Google Json Styleguide", one of the most standard ways of creating APIs.