Back4app is the backend behind CRM apps. For Android you get the Parse Android SDK with Kotlin, offline pinning, and Live Queries for contacts and deals—no server to write or host.

Android Template

CRM App Backend Template
Android — Schema, API & AI Guide

Q: Why use Back4app for an Android CRM app?

Back4app fits Android CRM: Kotlin, coroutines, typed models for Contact and Deal, offline pinning, and Live Queries for pipeline updates.

Q: How do I query deals by stage in Kotlin?

Use ParseQuery.getQuery(ParseObject::class.java, "Deal").whereEqualTo("stage", "qualified").orderByDescending("expectedCloseDate").findInBackground().

Q: Does the Android SDK support offline CRM?

Yes. Pin Deal and Contact objects after fetch; query from local store when offline. Sync when back online.

A production-ready Android CRM backend schema and Starter Kit on Back4app: Contact, Company, Deal, Activity, pipeline stages, ER diagram, data dictionary, JSON schema, API playground, and a one-click AI Agent prompt to deploy in minutes.

Build with AI Agent

Key Takeaways

On this page you get a production-ready CRM schema, a one-click AI prompt, and step-by-step Android code — so you can ship a CRM app without building the backend.

Deploy in minutes — Paste the AI Agent prompt and get a running app with contacts, companies, deals, and pipeline.
Secure by default — ACLs and role-based access so users see only their assigned deals and data.
Android-native SDK — Typed objects, async/await, offline pinning, and Live Queries for pipeline updates.
REST + GraphQL — Both APIs auto-generated; filter deals by stage, list activities by relatedTo.
Five classes — _User (built-in), Company, Contact, Deal (pipeline), Activity (tasks/events).

What Is the Android CRM App Backend Template?

Production-ready CRM backend for Android (Kotlin) on Back4app. The Parse Android SDK provides typed models for Contact and Deal, coroutines-friendly APIs, and local pinning for offline pipeline and contacts. Build field-ready CRM apps with Live Queries for real-time updates and no custom server code.

Best for:

Sales teamsCRM buildersRapid prototypingField repsMVP launchesTeams choosing a BaaS for CRM

Overview

Android CRM apps need typed models, offline support, and real-time pipeline updates. The Parse Android SDK on Back4app provides Kotlin-friendly APIs, local pinning for Deal and Contact, and Live Queries so the pipeline stays in sync without polling.

The schema (_User, Company, Contact, Deal, Activity) is the same across all platforms. In Kotlin you use ParseQuery.getQuery(ParseObject::class.java, "Deal").whereEqualTo("stage", "qualified") and optional pinning; the SDK handles JSON and sync.

Core CRM Features

Android CRM backend with Kotlin and the Parse SDK: contact management, deal pipeline, offline pinning, and built-in ACLs for assigned deals and contacts.

Contact management

Store and manage contacts with name, email, phone, company, and notes. Ideal for Android apps.

Company management

Track companies with name, website, industry, and address. Links to contacts and deals.

Deal pipeline

Sales pipeline with stages, amount, expected close date, and assignment. Built for Android backends.

Activity tracking

Log calls, emails, meetings, and notes linked to contacts and deals. Works with Android SDK.

User & permissions

Built-in user model and pointers for ownership and assignment. ACLs out of the box for Android.

Why Build Your Android CRM Backend with Back4app?

Back4app gives Android apps a typed SDK and offline support so you can build a field-ready CRM.

•Kotlin and coroutines: Use the Parse Android SDK with suspend functions and coroutines; type-safe models for Contact, Deal, Activity.
•Offline and sync: Pin Contact, Deal, and Activity to the local datastore; query from local when offline and sync when back online.
•Live Queries: Subscribe to Deal and Activity changes for real-time pipeline updates without polling.

Ideal for Android developers building CRM or sales apps with Kotlin and modern async patterns.

Core Benefits

A production-ready CRM backend so you can ship faster and focus on your app.

Ship Faster, No Backend Code

REST & GraphQL APIs and a ready-to-use schema — connect your app and go.

Secure by Default

ACLs and class-level permissions; restrict by assignedTo and createdBy.

Real-Time Pipeline

Live Queries over WebSockets for instant deal and activity updates.

Built-In Auth

User sign-up, login, and session handling out of the box.

Works Offline

Local pinning keeps contacts and deals available offline and syncs when you reconnect.

Deploy in Minutes

Use the AI Agent to create and deploy your CRM app from this template.

Ready to try it?

Let the Back4app AI Agent create your CRM app backend, connect the Android frontend, and deploy — all from a single prompt.

Build with AI Agent Try the API Playground

Free to start — 50 AI Agent prompts/month, no credit card required

Technical Stack

Everything powering this CRM app template at a glance.

Frontend

Android

Backend

Back4app

Database

MongoDB

Auth

Auth & Access Control

APIs

REST & GraphQL

Deployment

AI Agent / Dashboard

ER Diagram

Entity-Relationship diagram for the Android CRM app data model.

ER Diagram

View diagram source

Mermaid

erDiagram
    _User {
        String objectId PK
        String username
        String email
        String password
        Date createdAt
        Date updatedAt
    }

    Company {
        String objectId PK
        String name
        String website
        String industry
        String address
        String notes
        Pointer createdBy FK
        Date createdAt
        Date updatedAt
    }

    Contact {
        String objectId PK
        String name
        String email
        String phone
        Pointer company FK
        String notes
        Pointer createdBy FK
        Date createdAt
        Date updatedAt
    }

    Deal {
        String objectId PK
        String title
        Number amount
        String stage
        Pointer contact FK
        Pointer company FK
        Date expectedCloseDate
        String notes
        Pointer assignedTo FK
        Date createdAt
        Date updatedAt
    }

    Activity {
        String objectId PK
        String type
        String subject
        String description
        Date dueDate
        Date completedAt
        Pointer relatedTo FK
        Pointer createdBy FK
        Date createdAt
        Date updatedAt
    }

    Company ||--o{ Contact : "has"
    Company ||--o{ Deal : "has"
    Contact ||--o{ Deal : "has"
    _User ||--o{ Deal : "assignedTo"
    _User ||--o{ Activity : "createdBy"
    Contact ||--o{ Activity : "relatedTo"
    Deal ||--o{ Activity : "relatedTo"
    _User ||--o{ Company : "createdBy"
    _User ||--o{ Contact : "createdBy"

Integration Flow

Auth-to-CRUD sequence: how your Android app talks to Back4app — login, then query contacts and deals, update pipeline.

ER Diagram

View diagram source

Mermaid

sequenceDiagram
  participant User
  participant App as Android App
  participant Back4app as Back4app Cloud

  User->>App: Login
  App->>Back4app: ParseUser.logInInBackground(username, password)
  Back4app-->>App: Session token
  App-->>User: Logged in

  User->>App: Load contacts and deals
  App->>Back4app: ParseQuery<ParseObject>.findInBackground()
  Back4app-->>App: List of Deal / Contact
  App-->>User: Show pipeline

  User->>App: Create deal or contact
  App->>Back4app: deal.saveInBackground() or contact.saveInBackground()
  Back4app-->>App: Deal (objectId)
  App-->>User: Updated list

Data Dictionary

Complete field reference for every class in the schema.

Field	Type	Description	Required
objectId	String	Auto-generated unique identifier	auto
name	String	Full name of the contact
email	String	Email address	—
phone	String	Phone number	—
company	Pointer<Company>	Company this contact belongs to	—
notes	String	Free-form notes	—
createdBy	Pointer<_User>	User who created this contact	—
createdAt	Date	Auto-generated creation timestamp	auto
updatedAt	Date	Auto-generated last-update timestamp	auto

9 fields in Contact

Security & Permissions

How ownership, ACLs, and class-level permissions protect data in this CRM schema.

Row-Level ACLs

Use ACLs and pointers (assignedTo, createdBy) so users only see and edit their assigned deals and related data.

Class-Level Permissions

CLPs restrict which roles or users can create, read, update, or delete objects at the class level.

Pointer-Based Ownership

Deal.assignedTo and Activity.createdBy link to _User; Cloud Code can enforce visibility and edits by role.

Schema (JSON)

Raw JSON schema definition — copy and use in your Back4app app or import via the API.

JSON

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

{
  "classes": [
    {
      "className": "Contact",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "name": {
          "type": "String",
          "required": true
        },
        "email": {
          "type": "String",
          "required": false
        },
        "phone": {
          "type": "String",
          "required": false
        },
        "company": {
          "type": "Pointer",
          "targetClass": "Company",
          "required": false
        },
        "notes": {
          "type": "String",
          "required": false
        },
        "createdBy": {
          "type": "Pointer",
          "targetClass": "_User",
          "required": false
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    },
    {
      "className": "Company",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "name": {
          "type": "String",
          "required": true
        },
        "website": {
          "type": "String",
          "required": false
        },
        "industry": {
          "type": "String",
          "required": false
        },
        "address": {
          "type": "String",
          "required": false
        },
        "notes": {
          "type": "String",
          "required": false
        },
        "createdBy": {
          "type": "Pointer",
          "targetClass": "_User",
          "required": false
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    },
    {
      "className": "Deal",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "title": {
          "type": "String",
          "required": true
        },
        "amount": {
          "type": "Number",
          "required": false
        },
        "stage": {
          "type": "String",
          "required": false
        },
        "contact": {
          "type": "Pointer",
          "targetClass": "Contact",
          "required": false
        },
        "company": {
          "type": "Pointer",
          "targetClass": "Company",
          "required": false
        },
        "expectedCloseDate": {
          "type": "Date",
          "required": false
        },
        "notes": {
          "type": "String",
          "required": false
        },
        "assignedTo": {
          "type": "Pointer",
          "targetClass": "_User",
          "required": false
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    },
    {
      "className": "Activity",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "type": {
          "type": "String",
          "required": false
        },
        "subject": {
          "type": "String",
          "required": false
        },
        "description": {
          "type": "String",
          "required": false
        },
        "dueDate": {
          "type": "Date",
          "required": false
        },
        "completedAt": {
          "type": "Date",
          "required": false
        },
        "relatedTo": {
          "type": "Pointer",
          "required": false
        },
        "createdBy": {
          "type": "Pointer",
          "targetClass": "_User",
          "required": false
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    },
    {
      "className": "_User",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "username": {
          "type": "String",
          "required": true
        },
        "email": {
          "type": "String",
          "required": true
        },
        "password": {
          "type": "String",
          "required": true
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    }
  ]
}

Build with AI Agent

Use the Back4app AI Agent to build a real CRM app from this template: it will create the frontend, the backend (this schema, auth, and APIs), and deploy it — no manual setup. The prompt below describes this CRM stack so the Agent can generate a production-ready app in one go.

Back4app AI Agent

Ready to build

Create a CRM app on Back4app with this exact schema and behavior.

Schema:
1. _User (use Back4app built-in): username (String, required), email (String, required), password (String, required); objectId, createdAt, updatedAt (system).
2. Company: name (String, required), website (String), industry (String), address (String), notes (String), createdBy (Pointer to _User); objectId, createdAt, updatedAt (system).
3. Contact: name (String, required), email (String), phone (String), company (Pointer to Company), notes (String), createdBy (Pointer to _User); objectId, createdAt, updatedAt (system).
4. Deal: title (String, required), amount (Number), stage (String; e.g. lead, qualified, proposal, negotiation, won, lost), contact (Pointer to Contact), company (Pointer to Company), expectedCloseDate (Date), notes (String), assignedTo (Pointer to _User); objectId, createdAt, updatedAt (system).
5. Activity: type (String; e.g. call, email, meeting, note), subject (String), description (String), dueDate (Date), completedAt (Date), relatedTo (Pointer to Contact or Deal), createdBy (Pointer to _User); objectId, createdAt, updatedAt (system).

Security:
- Set ACLs so only authenticated users can access data; use role-based or owner-based rules where appropriate (e.g. assignedTo, createdBy).
- Use Class-Level Permissions so only authenticated users can create/read/update/delete these classes.

Auth:
- Sign-up (username, email, password) and login; support logout/session.

Behavior:
- Full CRUD for Company, Contact, Deal, and Activity.
- List deals with filter by stage and order by expectedCloseDate or updatedAt (pipeline view).
- List activities by relatedTo (Contact or Deal).
- Optional: real-time Live Queries for Deal and Activity for dashboard/pipeline updates.
- Optional: offline pinning for mobile (Contacts, Deals, Activities).

Deliver:
- Create the Back4app app with the schema above, ACLs, and any Cloud Code needed.
- Generate the frontend and connect it to this backend; deploy so the app is runnable end-to-end.

Press the button below to open the Agent with this template's prompt pre-filled.

Deploy in minutes50 free prompts / monthNo credit card required

API Playground

Try the REST and GraphQL endpoints for the CRM schema. Responses from the example data above — no Back4app account needed.

Loading playground…

Uses the same CRM schema (Contact, Company, Deal, Activity) as this template.

Step-by-Step Android Integration

Connect to your Back4app backend from a Android app using the Back4app Android SDK.

Step 1: Install Back4app Android SDK
Add the Back4app SDK for your stack (e.g. npm, pubspec, or package manager).
Kotlin
1
2
3
4
```
// build.gradle.kts (app)
dependencies {
    implementation("com.github.parse-community.Parse-SDK-Android:parse:4.1.0")
}
```

Step 2: Initialize Back4app in your app

Initialize the Back4app SDK at app startup with your App ID and server URL.

Kotlin

// Application class or Activity
Parse.initialize(
    Parse.Configuration.Builder(context)
        .applicationId("YOUR_APP_ID")
        .clientKey("YOUR_CLIENT_KEY")
        .server("https://parseapi.back4app.com/")
        .build()
);

Step 3: Query contacts and deals

Use the SDK to fetch Contact and Deal objects; filter deals by stage for the pipeline.

Kotlin

suspend fun getDeals(stage: String = "qualified"): List<ParseObject> = withContext(Dispatchers.IO) {
    val query = ParseQuery.getQuery<ParseObject>("Deal")
    query.whereEqualTo("stage", stage)
    query.orderByAscending("expectedCloseDate")
    query.find()
}
suspend fun getContacts(): List<ParseObject> = withContext(Dispatchers.IO) {
    ParseQuery.getQuery<ParseObject>("Contact").find()
}

Step 4: Create a contact or deal

Create a new Contact or Deal with the required fields and pointers (company, contact, assignedTo), then save.

Kotlin

suspend fun createDeal(title: String, stage: String = "lead", amount: Int? = null) = withContext(Dispatchers.IO) {
    val deal = ParseObject("Deal")
    deal.put("title", title)
    deal.put("stage", stage)
    amount?.let { deal.put("amount", it) }
    deal.save()
}
suspend fun createContact(name: String, email: String? = null, phone: String? = null) = withContext(Dispatchers.IO) {
    val contact = ParseObject("Contact")
    contact.put("name", name)
    email?.let { contact.put("email", it) }
    phone?.let { contact.put("phone", it) }
    contact.save()
}

Step 5: Update deal stage and activities

Update Deal.stage when moving in the pipeline; create and list Activity by relatedTo.

Kotlin

// Update deal stage (e.g. move in pipeline)
suspend fun updateDealStage(objectId: String, stage: String) = withContext(Dispatchers.IO) {
    val query = ParseQuery.getQuery<ParseObject>("Deal")
    val deal = query.get(objectId)
    deal.put("stage", stage)
    deal.save()
}

// Delete a deal
suspend fun deleteDeal(objectId: String) = withContext(Dispatchers.IO) {
    ParseQuery.getQuery<ParseObject>("Deal").get(objectId).delete()
}

State Management Integration

Integrate the Back4app SDK with your app's state layer (e.g. context, store, or services) for pipeline and contact state.

Full Data Model

Copy a complete CRM model for type-safe serialization (e.g. class, interface, or type definition).

Kotlin

// Deal.kt — matches Back4app schema
data class Deal(
    val objectId: String?,
    val title: String,
    val amount: Double?,
    val stage: String,
    val expectedCloseDate: Date?,
    val contact: ParseObject?,
    val company: ParseObject?,
    val assignedTo: ParseUser?,
    val createdAt: Date?,
    val updatedAt: Date?
) {
    companion object {
        fun from(obj: ParseObject): Deal = Deal(
            objectId = obj.objectId,
            title = obj.getString("title") ?: "",
            amount = obj.getDouble("amount"),
            stage = obj.getString("stage") ?: "lead",
            expectedCloseDate = obj.getDate("expectedCloseDate"),
            contact = obj.getParseObject("contact"),
            company = obj.getParseObject("company"),
            assignedTo = obj.getParseUser("assignedTo"),
            createdAt = obj.createdAt,
            updatedAt = obj.updatedAt
        )
    }
}

Offline-First & Local Datastore

Use pin() and unpin() so contacts and deals are available offline and sync when back online.

Supported SDKs include a local datastore. Pin Contact, Deal, and Activity objects to keep them on device; query pinned data when offline. When the app is back online, sync with the server.

Below: pin results after fetch, and unpin when you no longer need local copies.

Kotlin

// After fetching, pin for offline
ParseObject.pinAllInBackground(deals).await()

// Query from local datastore when offline
val query = ParseQuery.getQuery<ParseObject>("Deal")
    .fromLocalDatastore()
    .whereEqualTo("stage", "qualified")
    .orderByAscending("expectedCloseDate")
val localDeals = query.find()

// Unpin when no longer needed
ParseObject.unpinAllInBackground("Deal").await()

Frequently Asked Questions

Common questions about the CRM app backend template.

What is Back4app?

Why use Back4app for an Android CRM app?

How do I query deals by stage in Kotlin?

Does the Android SDK support offline CRM?

Trusted by developers worldwide

Join the community building the future of apps

Ready to Build Your CRM App?

Start your Android project in minutes. No credit card required.

Build with AI Agent

CRM App Backend TemplateAndroid — Schema, API & AI Guide

Key Takeaways

What Is the Android CRM App Backend Template?

Overview

Core CRM Features

Contact management

Company management

Deal pipeline

Activity tracking

User & permissions

Why Build Your Android CRM Backend with Back4app?

Core Benefits

Ship Faster, No Backend Code

Secure by Default

Real-Time Pipeline

Built-In Auth

Works Offline

Deploy in Minutes

Ready to try it?

Technical Stack

ER Diagram

Integration Flow

Data Dictionary

Security & Permissions

Row-Level ACLs

Class-Level Permissions

Pointer-Based Ownership

Schema (JSON)

Build with AI Agent

API Playground

Step-by-Step Android Integration

Step 1: Install Back4app Android SDK

Step 2: Initialize Back4app in your app

Step 3: Query contacts and deals

Step 4: Create a contact or deal

Step 5: Update deal stage and activities

State Management Integration

Full Data Model

Offline-First & Local Datastore

Frequently Asked Questions

Trusted by developers worldwide

Ready to Build Your CRM App?

CRM App Backend Template
Android — Schema, API & AI Guide