Designing an app · Lesson 10
Summary: what you can build
Nine lessons, one model. A manifest describes an app along nine axes; the runtime carries out all of them, with no code written for the single app; and everything is checked before it runs, which is what lets an agent write manifests and repair its own mistakes. Here is the whole picture, with what the builder actually produced from 370 real startups.
Switch between the totals, the classes and the sectors; hover a bar for its numbers, or read them as a table.
The nine axes of the model
- People (lessons 2, 7). Roles by signup, invite, admin or derived from a record; anonymous visitors; limits per role and plan.
- Data (lesson 2). Collections with 19 field types (files, positions, barcodes, relations…); whose each record is (user, shared, app, org, instance); access by relationship (where); sharing, hierarchies, retention.
- Pages (lesson 3). 20 view types: tables, cards, KPIs, charts, maps, forms, bookings, chats, approvals, dashboards, landings made of blocks and cleaned HTML.
- Appearance (lesson 4). A light and a dark palette, fonts, buttons, the header, several languages.
- Agents (lesson 5). Tasks with placeholders and context, the app’s tools, a result that becomes a record, delegation, memory, teams in sequence or swarm, deterministic Python functions.
- Events (lesson 6). Triggers on records, dates, approvals, payments, webhooks, cron, phone calls; personal agents users create for themselves.
- Human checkpoints (lesson 6). Approvals by a staff role or by the requester, with a deadline.
- Money (lesson 7). Free, credits, subscriptions, metering on real usage, prices per unit, marketplaces with a fee, through Stripe Connect.
- The boundary (lesson 8). Declared external APIs, users’ keys encrypted, ETL pipelines on the platform, Telegram, email, phone, Android and iOS apps.
The families of apps it covers well
- B2B monitoring and signals. Customers, suppliers, risks, regulations, reputation: a scheduled agent checks every day, writes a signal and tells whoever must act.
- Work on documents. Contract review, compliance, appraisals, month-end close: a file is uploaded, an agent extracts and assesses, a person signs off.
- Marketplaces and bookings. Professionals, services, trips, rentals: slots, resources, payments between users with a fee.
- Guided cases with human steps. Onboarding, claims, conveyancing, health and public services: forms, states, approvals on several levels, notifications.
- Intelligence from collected data. Prices, tenders, case law, sentiment: ETL pipelines plus agents that analyse.
- Vertical assistants. With the domain’s knowledge, on the web, on Telegram or on the phone.
- Field apps on the phone. Photos, position, barcodes, notifications, biometric unlock.
- Tools for small teams. A personal agent for each user, periodic reports by email, dashboards for the staff.
Where the model stops
- Interfaces outside the patterns. Visual editors, canvases, real-time collaboration between users, games: the manifest offers views and blocks, not a free interface.
- Heavy custom computation. Python slots run without network or files; large algorithms belong in pipelines or external services.
- Channels not covered yet. Email campaigns, WhatsApp and SMS, sign-in with OAuth, real-time audio and video.
- One level of administration. An admin can do everything; finer permissions are approximated with staff roles and access rules.
- Certified or regulated integrations. A qualified signature, payment accounts: today they are documented extensions.
How to read the classes
Before generating, each startup was classed by hand: A when its product fits the model today, B when it fits with known gaps, C when its core is out of reach (a proprietary algorithm, special hardware, a regulated licence). Even in class C most apps come out valid and working: the builder covers the shell — data, flows, payments, the agents around the core — and writes the core down as an extension.
What to take away
- A model, not a code generator. The app is a manifest; every improvement of the runtime reaches every app already published.
- Checkable by construction. Shape, references, safety and quality are verified before anyone uses the app.
- Wide, with honest edges. Most vertical SaaS fit; what does not is written down as an extension, not hidden.
Next
This closes the path. Next come the same lessons for the Agentic Studio and the Pipeline Designer.
← The whole path