Who is this for?
Mobile application and backend teams.
Before you start
An owned staging environment, sample user journey and access model.

The short answer: put an API in between

A mobile application should access data through an HTTPS API. SQL passwords stay on the backend. The client sends session information, and the API decides which records are accessible. This creates an explicit boundary between devices, business rules and data.

Passwords in an app are not secret

Mobile packages can be inspected. Hiding the user interface is insufficient when a permanent SQL password or service key is packaged inside. Keep these credentials on the server. Clients need an application-specific API response, not a general SQL connection.

Separate identity from permission

A valid token does not grant access to every order. After validating the session, the API checks organization, role and record ownership. A user_id supplied by a device should not replace the authenticated session identity.

Design responses for the mobile experience

Paginate lists and omit fields a screen does not use. Loading, empty, connection failure and permission failure are different states. An error should explain the next useful action without exposing internal connections or queries.

An example request flow

The following is an illustrative API contract for a customer app, not a working Uygulama Cloud control API endpoint. The backend verifies the session, queries only this user’s orders and returns necessary fields.

GET https://api.example.invalid/v1/orders?cursor=<next-page>
Authorization: Bearer <session-token>
Accept: application/json

Plan retries on mobile networks

After a failed request, a user may press the same button again. Consider idempotency keys and server-side deduplication for writes such as orders or payment initiation. Bound read retries; endless attempts and duplicate actions harm the experience.

Files and background work

The API should authorize uploads; permanent storage credentials stay off devices. File conversions and reports can move to workers. This is an example architecture: live storage and customer workers are not available on Uygulama Cloud yet.

Three questions before you begin

Are there permanent secrets in the client package? Does the API check ownership for every record? Can a retry create the same action twice? Clear answers establish a data boundary before framework selection.

7. Distinguish an API from a policy-based data layer

A custom API owns token checks, business rules and private SQL access. A policy-enforcing service can expose selected APIs directly to authenticated clients, relying on correct grants and RLS. This is different from distributing a general SQL password. Privileged server material belongs on neither client.

7. Distinguish an API from a policy-based data layer
ModelBoundary
Custom APIIdentity, authorization and scoped queries
Policy-based data APIUser identity, grants and RLS
Shared SQL credentialsDo not distribute in the app

8. Measure complete data flows

Limit fields and page size. Avoid per-record requests and separate media from relational response bodies. Engine choice does not replace indexes, a clear contract and cache policy. Prototype two accounts, growing lists, expired sessions and disconnected devices. Cached records must not cross account boundaries.

  • Keep SQL secrets off devices.
  • Test ownership per operation.
  • Separate data and media.
  • Document offline and write rules.

Action summary

  • Distinguish an API from a policy-based data layer
  • Measure complete data flows

Common questions

Does this enable live Uygulama Cloud resources?

No. Customer provisioning is closed; adapt the architectural examples to your environment.

What counts as validation?

Verified data, permissions and failure cases for your workload, rather than one successful screen or a backup file.

Sources and scope

Technical references are listed below. Examples illustrate implementation in your own environment; they are not customer benchmarks or claims of live Uygulama Cloud services. Check the current provider documentation before applying settings.

Sources checked:

Read next

Browse all articles