Several payload families
Specialized cards and flexible primitives increased client mapping, rendering and compatibility work.
A contract-first UI platform aligned backend producers, Android and Flutter without turning every product change into a coordinated app release.

Low-level layout freedom and several chat payload families made each new composition more expensive to support consistently.
Specialized cards and flexible primitives increased client mapping, rendering and compatibility work.
Constrained product semantics aligned with platform Design Systems while preserving native rendering.
The contribution spans contract generations, client integration and the initial Universal Card change—not sole ownership of every service or renderer.
Protobuf defines the IDL and generated model boundary. Runtime paths deliver JSON; each client owns its mapping and presentation.
Pages, modals, forms, actions and chat payloads evolve explicitly.
Android and Flutter isolate transport models from product presentation.
Compose/Tiger and Flutter/Barracuda render equivalent semantics independently.
The platform is valuable because contract changes remain reviewable across generators, clients, fallbacks and host actions.
Generate typed models across platforms while keeping transport and rendering concerns explicit.
Trade arbitrary layout freedom for predictability, portability and Design System alignment.
Reduce bespoke chat templates without misrepresenting cards as the whole BDUI system.
Legacy and malformed payload fallbacks preserve product continuity during adoption.
Flutter carries a local generated mirror; snapshot drift must remain visible and managed.
A reusable composition model connects contract governance to visible product behaviour without exposing private schema details.
A constrained composition model covers context, status, content, carousels and actions.
Clients keep draft form state and execute navigation, requests and native actions through explicit boundaries.
Universal Card expanded from its initial chat use to Android, iOS, web, the agent administration interface, and later Flutter, while older payload paths remained supported during migration.
One addition can touch generation, Android, Flutter, Design Systems, tests and release artifacts.
Platform-native presentation, host ownership and compatibility fallbacks.
Universal Card travelled across client and administration surfaces while older payloads remained supported.
Target role · Staff Mobile Engineer (Android + Flutter)
Worldwide remote · English / Russian
Novi Sad, Serbia · hybrid possible