Mobile apps

A PostgreSQL backend your mobile app can call.

CubiBase fits a mobile app that needs relational data, user accounts, and a REST API, without a separate backend service for every screen. The app calls https://{slug}.api.cubibase.com over HTTPS: /auth/v1 to sign users up and in, /rest/v1 for the data.

A concrete shape

Imagine a field inventory app. Products, stock counts, and tasks live in the project database. The iOS or Android client lists tasks with GET /rest/v1/tasks and writes a count with POST or PATCH. There is no CubiBase mobile SDK. The client uses its HTTP stack.

  • Put the publishable key in the client. It identifies the project and does not return rows alone.
  • Sign the person up or in through /auth/v1 and keep the refresh token in secure device storage.
  • Send the access JWT on every Data API call, and refresh it when it expires.
  • Store that person’s id in a text column, and set that column as the user column, if each person should only see their tasks.
  • Leave tables unexposed until the app is ready to call them.

What you still build

CubiBase does not sync an offline store, push notifications, or photo uploads. If the app must work offline, that cache lives on the device. If you need files, you need storage outside the current engine. The relational records can still live in CubiBase.

Questions

Which mobile platforms are supported?

Any platform that can send HTTPS. CubiBase does not ship a native SDK, and it does not depend on a particular app store.

Can the app create the end user’s account inside CubiBase?

Yes. POST /auth/v1/signup on the project host creates the user and returns an access JWT and a refresh token. Sign-in, refresh, logout, and TOTP MFA are on the same host. If you already use an identity provider, CubiBase can verify its RS256 tokens instead.

Start with one project.

Add another project when the next application needs its own database.

first request
GET /rest/v1/customersapikey: cb_pub_…Authorization: Bearer <JWT>200 · { "data": [ … ] }