8base lets users build, run and scale powerful mobile and web apps using front-end development skills. With 8base, front-end developers can create new business applications 10x faster without relying on back-end developers and DevOps through features that help simplify the development process.
Capabilities |
|
---|---|
Segment |
|
Deployment | Cloud / SaaS / Web-Based |
Support | 24/7 (Live rep), Chat, Email/Help Desk, FAQs/Forum, Knowledge Base, Phone Support |
Training | Documentation |
Languages | English |
You get automatically created queries and mutations and resolvers are very easy to adapt to special needs
It restricts a bit the capacity with the DB I think at firtst, it would be nice to have ability to do SQL queries
helping people host concerts in their places and all the logistics involved
Database feature set is great - managing tables and relations is very easy. Cloud functions work nicely and documentation is pretty good. As a newer platform its doing well to try and get feature parity with some bigger players whilst adding its own touch.
Pricing model has room for improvement, direct access to the DB would be a great addition and the Front End builder has a long way to go before it can match other players in the Low Code builder scene. More external integrations on both the back and front end would be great.
Easy access to a back end platform without the overheads of managing the infra. A lower effort authentication system that allows the use of external ID providers.
The most interesting functionality for 8base is the queries and mutations it creates when a table schema is created, which makes time efficient. Also the ability to use the UI to make changes in the tables.
There is some stuff that can be improved as for example, the queries that can be used in the tables are quiet limited and very slow sometimes for bulk operations. Another thing that does not make a lot of sense is that relations between tables are created in weird ways that sometimes make it impossible to do certain mutations. Another thing is that the changes made on the tables directly are soft, they are not really 100% reflected on the database and that creates a mix of data that does not make sense at all. Also documentation is tremendously outdated.
Saving time on the creation of the schemas and queries to make operations with the data inside a database