Separate the app, backend and admin panel

The Android app is the interface on the user's phone. A backend handles shared data and rules outside that phone, whether it is a service you already use, a managed platform or custom software. An admin panel lets authorised staff perform the business tasks that the product needs.

For example, changing a course description is an administration task. Deciding whether a student may open a paid lesson is an access rule. Displaying that lesson is an app task. A quote that includes only the last part may omit work required to run the product.

A decision table for your first release

RequirementWhat to discuss with the developer
Personal records on one phoneLocal storage may be sufficient. Agree deletion, backup and device-change behaviour.
The same records on multiple devicesIdentify the shared data source, identity rules, conflicts and offline behaviour.
Different people see different dataSpecify roles, permissions and where access decisions are enforced.
Staff update products, courses or usersList the admin actions and who may perform them; decide whether an existing panel is sufficient.
An existing CRM or website holds the dataCheck its API, permissions, limits and ownership before commissioning another backend.
Payments or external services affect accessPlan verified events, failed requests, retries, reconciliation and support responsibilities.

Three published products, three different needs

Gut Elements has no account and keeps its current diary on the device. That meets a different requirement from Learn, where enrolled students sign in and continue across web and app. Pulse provides an interface for WhatsApp API conversations, contacts and tags.

These examples describe product behaviour, not a claim that all three use one architecture. Start with the behaviour your business needs, then ask which existing or new services should support it.

Can my Android app use my existing website login and data?

It may be able to, once the team checks how the website exposes accounts and records to another application. Ask your current supplier for documentation of the API, the connection through which the app would read and update data. Share documentation and a test environment through agreed project channels.

During scoping, check whether the same person can sign in on web and Android, which records they can access, how updates appear in both places and what happens when a request fails. Also establish who maintains the existing service and what changes require their involvement. If the website does not offer the needed connection, the quote should explain the additional work.

Learn is an example from our own portfolio where enrolled students use lessons and progress across the web and app. Use that behaviour to describe what you want users to experience across your own products.

How does an action in the app reach my staff?

Illustrative workflow for an equipment inspection app

  1. A technician opens an assigned job and records the inspection on an Android phone.
  2. The app saves a draft locally when there is no connection and shows that it is waiting to be submitted.
  3. On submission, the backend checks permission and stores the record. The app shows whether it succeeded.
  4. A coordinator opens the web admin panel, filters submitted inspections and records the next action.

Ask the team to demonstrate the complete sequence. Include a failed submission and a retry in the acceptance checks, so both the technician and coordinator can tell which record was received. Write down who is allowed to change a submitted inspection and how those changes are recorded.

Describe admin actions, not just an “admin dashboard”

Write down the work a staff member must complete: create a course, correct a customer record, suspend access, review an order or export an agreed report. Each action needs inputs, permissions and an observable result. A dashboard of charts may not help someone perform any of those tasks.

For a course app, an access rule might distinguish an enrolled student from someone who only installed the app. For an inspection app, a coordinator might assign work without being allowed to edit a technician's submitted record. These are scope questions to resolve before a generic admin panel is treated as complete.

A managed service can reduce custom development, but it still needs configuration, access control, integrations and an operating owner. Ask what the supplier is buying, building and connecting, and who pays the service bills.

Decide what happens when the connection fails

Offline reading, offline editing and offline submission are different requirements. Reading previously downloaded content is different from changing shared data while disconnected. If a record changes on two devices, the product needs an agreed way to resolve the conflict.

Google's offline-first architecture guidance explains the distinction between local and network data. For your brief, the practical questions are simpler: what must still work, what must wait, and how will the user know whether a change reached the shared system?

Ask for a small system map with the quote

Ask the team to identify the phone app, shared services, database, staff interface and external integrations. Beside each, record who owns it, who maintains it and whether it already exists. This map should describe responsibilities in plain language.

Then check that the build estimate and operating budget cover those responsibilities. Keep the map with the project brief so suppliers estimate the same system.

Questions and answers

Does every Android app need a server?

No. Some personal or offline workflows can work with data on the device. Shared records, cross-device access and integrations introduce different requirements that need to be scoped.

Is an admin panel the same as a backend?

No. The backend handles shared data and server-side rules. An admin panel is an interface staff use to manage agreed parts of the product.

Can my app use an existing backend?

Sometimes. The team needs to check the existing API, permissions, data model, limits and operational ownership before confirming whether it meets the app requirements.

Our own published apps

The product examples refer to apps we build and run ourselves. Their pages link to the published listings and explain the relevant scope.

Primary sources

Check the platform’s current requirements before planning a release or account change.