Author / Maintainer
Flow-UI
Open-source server-driven SwiftUI library for teams that cannot rebuild UI architecture every sprint.
SwiftUIServer-driven UIOpen SourceiOS
Problem
Most product screens are composition: lists, cards, forms, headers. When those screens are hardcoded in SwiftUI, every layout experiment becomes an App Store release. Industry writing on server-driven UI (SDUI) frames the same idea Uber-scale and Shop-style apps already use: the client ships a native component registry; the server sends the tree as data; UI changes ship as JSON, not as a binary.
Indie and mid-size teams still pay the rebuild tax because public SwiftUI SDUI tooling is thin, and most tutorials stop at a toy registry. Flow-UI exists to close that gap with a library other iOS engineers can actually integrate.
Approach
Flow-UI treats screens as structured JSON rendered through a SwiftUI registry. The contract stays small on purpose: schema, server payload, component registry, recursive renderer. That matches the four-piece SDUI model described in modern SwiftUI SDUI tutorials and production writeups (Shopify Shop, Yelp CHAOS-style systems, backend-driven SwiftUI essays).
The library is open source so teams can adopt the pattern without inventing a private architecture. Documentation ships as a dedicated Next.js docs zone, proxied under Cognitain at https://www.cognitain.in/documentation/flowui/ via multi-zone rewrites. The Cognitain homepage exposes live vs coming-soon mode so waitlist and docs can move independently of the marketing site.
Stack
SwiftUI · SDUI JSON contracts · component registry + renderer · open-source packaging · Cognitain multi-zone docs (Next.js)
Outcome
A public docs and product surface for server-driven SwiftUI, aligned with how large apps already ship remote UI, but packaged for teams that need native performance without waiting on App Review for every composition change.