The mechanism
One definition, every surface.
An entity is defined once — fields, formulas, validations. Every screen, view and API is generated from that single definition, so nothing drifts.
Entity definition
Outlet · 4 fields
Fields, a credit_ok formula and a 10-digit phone rule — saved once, and the REST & OData endpoints exist.
Web form
Outlet form · generated
Outlet name and the delivery-window picklist render from the definition, validations included.
List & Kanban views
Outlets · generated
List and board views read the same fields — no separate view to maintain.
Native mobile screen
Outlet screen · offline sync
The same definition renders as native UI on the rep's phone.
REST / OData
/odata/outlets · generated
GET returns Apex Mart with its Thu AM delivery window — no API written by hand.
One definition, every surface — the form, the views, the mobile screen and the API all read the same entity, and a saved layout change reaches the rep's phone over the air, without an app-store release.
App Builder architecture.
Model
Fields, formulas & validations defined once
Design
Forms, views & mobile screens are laid out visually
Preview
Try the app on web & mobile before anyone else sees it
Publish
Live everywhere — no app-store release
From data model to running app.
For the people who will actually build on it.
The details an RFP answer needs — all verifiable in a demo.
One application, every audience.
Rename the business language per tenant — your “outlets”, their “counters” — localize labels without waiting on a release, brand each app as its own, and let every surface follow light or dark mode.
Everything in App Builder.
Custom entities & fields
Your objects, first-class.
Model outlets, schemes, claims — anything — with the same depth the built-in entities get. Each is API-ready on save.
Formula & calculated fields
Fields that compute themselves.
Derive values server-side — margins, ratios, flags — so every screen and report shows the same answer.
Record types
One entity, several shapes.
A retail outlet and a wholesale outlet can share data but differ in layout, picklists and process.
Validation rules
Bad data stops at the door.
Declared once, enforced on every write — web, mobile, API and import alike.
Global & dependent picklists
Choices that stay consistent.
Shared value sets across entities, and picklists that narrow based on a previous answer.
Web layout designer
Forms without a frontend team.
Drag-and-drop layouts with sections, related lists and conditional visibility.
Mobile layout designer
Designed for thumbs, not shrunk.
A dedicated designer for native mobile screens — because the field is not a desktop.
Card & list-view designer
Lists that carry meaning.
Design list, card and Kanban views per entity — what a rep scans first is a decision, not a default.
App composition
Whole apps, assembled.
Navigation, role-scoped pages and KPI widgets compose into an app users log into — not a pile of forms.
Instant APIs per entity
Integration-ready by default.
REST and OData endpoints exist the moment an entity is saved. No API project.
100+ widget library
A running start on every page.
Charts, KPIs, lists, timelines and more — prebuilt, themeable, extendable with custom React components.
Over-the-air layout delivery
Ship a change at lunch.
Layout changes reach every device without an app-store release or a reinstall.