We don't think of it as BaaS. Instead, we think of it first as a spreadsheet-like UI, and it also has an API.
The use cases people have been most excited about need both. For instance, set up a configuration database or CMS for your app--an engineer can create the schema and read via the API, then anyone on the team can view and edit the configuration.
With the BaaS offerings I've seen, you get the database and API, but you have to build any UI you want yourself, including any web or admin UI.
The use cases people have been most excited about need both. For instance, set up a configuration database or CMS for your app--an engineer can create the schema and read via the API, then anyone on the team can view and edit the configuration.
With the BaaS offerings I've seen, you get the database and API, but you have to build any UI you want yourself, including any web or admin UI.