Page elements & layout components

Table of contents

  1. Multi-column layouts
  2. Tabbed views
  3. Child views
    1. Pattern 1: Embedded Child List on Detail Pages
    2. Pattern 2: Nested Child Lists inside Cards
  4. Dynamic data fields
    1. Linking Fields to Pop-up Pages
    2. Field Styling: Bold Text & Text Alignment
  5. Static content
  6. Action buttons
    1. 1. Adding Private Sub-Records
    2. 2. One-Tap Status Updates & State Transitions

Page elements are the modular building blocks used to construct views and screens. In Doypp, you can combine four core element types to design rich, interactive interfaces:

  • Child views: Embedded sub-views displaying related child records (e.g., comments on a post).
  • Data fields: Dynamic elements bound to your data model (e.g., title, avatar, price, location).
  • Static content: Non-database assets for branding and structure (e.g., banners, help text, static maps).
  • Action buttons: Interactive triggers for status transitions, workflows, and submission forms.

Multi-column layouts

Page elements can be organized into responsive columns. A page—as well as individual views inside a page—supports up to 3 columns:

  • Drag-and-Drop Positioning: Move elements between columns using the drag handle.
  • Adjustable Column Widths: Adjust proportional column widths by dragging the splitter between columns.
  • Adaptive Stacking: Multi-column layouts automatically condense into single-column vertical flows on small smartphone screens while preserving side-by-side presentation on tablets and desktop browsers.

Example: 1-column, 2-column, and 3-column layouts of a User profile screen:

1-column layout
2-columns layout
3-columns layout
3-column layout on tablet
3-columns layout displayed on a tablet screen

Tabbed views

When a view contains numerous fields and related lists, stacking them vertically can force users into tedious scrolling. Enabling a Tab view organizes sections into clean, horizontal tab headers.

To enable tabs, click the “Toggle tabs” button in the view editor, then group your elements into distinct tabs (such as Profile, Posts, and Comments):

Tab 1: User profile details
Tab 2: User's posts
Tab 3: User's comments

Child views

A Child view is a view embedded inside a parent page or card to display related records via direct or indirect relationships:

Add a new child view
Add new child view to page

Pattern 1: Embedded Child List on Detail Pages

On a post detail screen, embed a child list view displaying all comments associated with that post:

Parent detail view
Embedded child list view
Post detail with embedded comments

Pattern 2: Nested Child Lists inside Cards

Rather than requiring users to open a popup to inspect child items, you can nest child lists directly within parent cards in a feed:

Parent list view
Parent list view
Child list view
Child list view
Nested list view in app
Nested list view in feed

[!TIP] A single page can contain multiple child views simultaneously (e.g., an Order detail page holding both a Line Items list and a Shipping Updates list).


Dynamic data fields

Dynamic fields display live data stored in your models:

Add new data field
Add a data field to the view

Linking Fields to Pop-up Pages

Just like list items, dynamic fields representing related entities can be configured as interactive links that launch pop-up detail pages.

Example: Tapping the author name on a post card opens that user’s profile popup:

Configure link to popup
Link field to popup page
Tap on user name
Pop-up: User detail

Field Styling: Bold Text & Text Alignment

Customize the visual weight and alignment of data fields using the display settings toolbar:

  • Bold Styling: Emphasize headings, titles, or metrics.
  • Alignment: Align content to the left, center, or right (e.g., right-aligning currency or numeric quantities).
Editor: enable bold typography
Post title rendered in bold
Editor: configure text alignment
Center-aligned field in app

Static content

Static elements do not bind to database records; they provide fixed headings, instructions, imagery, and external navigation:

  • Static Text: Headings, section dividers, instructions, and disclaimers.
  • Static Image: Logos, hero illustrations, and decorative banners.
  • Static Location / Map: Fixed physical office locations, venue maps, or meeting points.
  • Static URL: External links to documentation, privacy policies, or external web services.
Add a static image
Add static image
Add a static map
Add static map
Static content in app
Static content displayed in view

Action buttons

Action buttons trigger specific application operations with a single tap. They are commonly used for two major workflows:

1. Adding Private Sub-Records

Launch an input form for a child model without having to display the complete list of existing records on that page.

Example: An apartment listing features a “Contact Host” button that lets visitors send private inquiries to the host without displaying the entire history of past inquiries publicly:

Button configuration for child item
Button action: Add child record
Tap "Contact host" button
Write inquiry form
Submit inquiry form

2. One-Tap Status Updates & State Transitions

Update a record’s state or advance a workflow directly without requiring the user to open and submit an edit form.

Example: A maintenance technician taps “Work Complete” to advance a task from Assigned to Completed:

Button configuration for updating status
Button action: Update status
Tap state transition button
Advance state to Work-Complete
Confirmation alert
Status updated confirmation