Data model

Data models form the foundation of your application. Similar to a database table or a spreadsheet sheet, a data model represents a specific entity in your app (such as a User, Post, Product, or Order) and defines three essential aspects:

  • Structure: What does your data look like?
  • Relationships: How are different models connected to one another?
  • Access Control: How can different users access and interact with the data?
Data model editor overview
Data model editor

What does your data look like?

A data model contains several data fields to store various types of information (text, images, locations, dates, etc.). For example:

  • A User model contains an email, a name, and an optional avatar.
  • An Apartment model contains a location, description, rental-price, and several photos.

Each field can be tailored with specific properties—such as making it required, unique, sortable, or protected.


Real-world applications rarely exist with isolated tables. Data models connect with each other through relationships that mirror your business logic:

  • A User writes many blog Posts (One-to-Many).
  • A Post has many Comments written by different Users (One-to-Many).
  • An Apartment has many Photos, and each Photo belongs to an Apartment (One-to-Many).

Once relationships are established, Doypp automatically manages bi-directional linking and makes related data available across your app’s screens and navigation flows.


How can users access your data?

Doypp allows you to configure granular permissions based on user roles and contexts:

  • Role-based permissions: Both a Manager and an Employee can read a performance Review, but only a Manager can create or edit one.
  • Ownership-based permissions: A User can create and edit their own Post, but cannot edit or delete posts written by others.
  • Field-level protection: Certain fields (like status or is_verified) can be made read-only for standard users and editable only by administrators.

Table of contents