App Studio — Visual Backend Modeling

App Studio is Amoga's visual backend modeling surface — used by implementation engineers to stand up customer deployments without writing backend code. You drag-and-drop objects, relations, aggregations, and workflow steps; the system compiles your visual model into runtime-ready configs consumed directly by Prisma, Cube.js, and Temporal. I owned the complete frontend — the modeling canvas, the compilation pipeline, and the workflow engine migration.

• Owned the visual data modeling canvas — users define objects, attributes, and relations through a drag-and-drop interface that maps directly to Prisma schema.
• Built parsers that compile visual data models into Prisma schema configs, aggregation models into Cube.js manifests, and workflow graphs into Temporal workflow definitions.
• Built the aggregation modeling surface — users compose metrics and dimensions visually, which the parser compiles into Cube.js-compatible aggregation configs.
• Designed the visual workflow editor — a node-and-edge graph where users define state machines that compile to Temporal workflow code.
• Led the frontend migration from Flowable to Temporal as the workflow engine — including migrating the visual model, the serialization format, and the compiler.
• Shipped PWA + Service Worker support for offline usage in App Studio.

• → Implementation engineers now stand up complete customer deployments — data models, analytics, and workflows — without writing backend code.
• → Successful migration from Flowable to Temporal with zero data loss and no regressions in the visual model.
• → Parsers handle the full Prisma data model surface: objects, scalar types, relations (1:1, 1:N, M:N), and constraints.