Mobile Builder Technical Specifications

Every Aeion-built app ships as a thin native runtime that fetches its component tree from the Aeion runtime API on launch. The component tree is a typed JSON structure — what to render, what props, what data to bind, in what order:

typescript interface ComponentNode { id: string; type: string; // a component from the native library (346 available) props?: Record<string, any>; children?: ComponentNode[]; slots?: Record<string, ComponentNode[]>; } `

When you change a button color, add a screen, or re-bind a list to a different collection, you Publish in the admin UI. The runtime API immediately starts serving the new tree, and every device that launches the app from that point forward renders the new layout — no App Store re-submission, no Apple Review, no Play Console rollout.

Tree validation caps nesting at 10 levels deep so you can't accidentally publish a runaway recursive layout. Every save validates component IDs against the registered component catalog and checks that bound collections exist in your tenant.

Every list, card, chart, or map component can be bound to an Aeion collection without writing code. In the canvas, select a component → Data Binding panel:

json { "type": "collection", "collectionSlug": "commerce_products", "filters": { "status": { "equals": "active" }, "category": { "equals": "electronics" } }, "limit": 50, "sort": [{ "field": "createdAt", "direction": "desc" }], "fieldMapping": { "imageUrl": "images[0].url", "name": "title", "price": "salePrice ?? price" } }

Filter operators include equals, not_equals, gt/gte/lt/lte, in, contains, starts_with, ends_with, plus the full Aeion QueryBuilder for complex predicates.

Field mapping translates between collection field names and component prop names — so a ProductCard expecting imageUrl can render from a product collection that calls it images[0].url without a custom transform.

Context variables like $currentUser, $tenant, $now are supported so a Fleet driver app can show only "tasks where assignedDriver = $currentUser" without per-user configuration.

Out-of-the-box bindings exist for every Aeion module: CRM (contacts / deals / activities), Commerce (products / orders / customers), Fleet (vehicles / drivers / tasks / geofences), Hospitality (reservations / rooms / services), Health (patients / appointments / medications), Events (attendees / sessions / check-ins), plus any custom collection.

Triggering a native build creates a build record in the admin UI and submits to EAS Build (Expo's cloud compilation service). EAS provisions a macOS build VM for iOS or a Linux build VM for Android, compiles your React Native app, signs it with your stored credentials, and returns a downloadable artifact (.ipa for iOS, .aab for Android).

Build profiles are defined in eas.json — development, preview, production. Each profile can specify different resource classes (macOS version, Xcode version, Node version).

Build types:

• full_app — Complete native app binary
• app_clip — iOS App Clip (lightweight version that launches without install)
• instant_app — Android Instant App equivalent

Status polling + webhooks — the admin UI polls EAS for status; EAS also calls our webhook on completion. Both pathways update the same build record, so you always see the truth.

Signing credentials are stored encrypted, per-app — iOS provisioning profile + .p12, Android keystore + key alias + store password. A workflow trigger fires 30 days before any credential expires so you renew proactively rather than discovering it during a release.

Each template is a complete starting point — navigation, default screens, theme, permissions, and data bindings already wired. Pick a template, change the name + bundle ID + brand colors, and you have a working app:

eventsHardwareKiosk, fleetDriver, hotelGuest, patientPortal, shoppingApp, businessPhone, employeePortal, lmsStudent, diningStaff, legalClient, eventAttendee, hotelStaff, crmMobile, diningGuest, fieldService, gymMember, productionCrew, scmOperator, eventsStaff, smartSpace, recruitPipeline, marketingDash, expenseApprover, healthProvider, helpdeskAgent, warehousePicker, securityOfficer, teamCollab, eventsExhibitor, authorCompanion, manuscriptReader, loyaltyMember, constructionField, workspaceEmployee, conciergeStaff, teamInbox, communityForum, interactiveRetailCompanion, smartCampusKiosk, productionScriptSupervisor, productionCameraDept, productionHMUCostume

Templates declare their required Aeion modules (e.g., Fleet Driver requires the Fleet module) and recommended pricing tier. Some screens may be locked behind a tier — those screens show a paywall fallback at runtime if the tenant hasn't licensed the required module.