A standard exists. The implementations don't.
ONE Record is the IATA standard meant to replace decades of paper AWBs with a unified data model. The standard is paper. The product is the work.
The brief: build a production-grade shipment platform fully compliant with the IATA ONE Record schema — covering creation, events, services, customs, security, assignations, operators, notifications.
The team scaled to seven contributors. My role: front-end specialist, design direction, UX/UI, shared design system.
Nx monorepo, real-time spine.
Seven apps. Twenty-plus libs. Boundaries enforced by ESLint, not by trust.
A dedicated WebSocket server is the real-time spine: events fire from the worker, hit the WS server, propagate to clients in milliseconds. No polling, no stale state.
A shared language for seven contributors.
With seven engineers shipping in parallel, the design system isn't a nice-to-have — it's the only way the product stays coherent.
I built and maintained the front-end design system: Chat, Calendar, Skeleton, Form, Dropdown, Card, Tooltip. Brand assets too — promotional banners, seasonal logo marks, onboarding illustrations, error states.
When data updates faster than the eye.
Pushing updates is easy. Making them legible is the work.
A row that just transitioned to IN_TRANSIT shouldn't blink. A new event shouldn't reflow the page. We solved it the Nothing way: micro-animations only when meaning changes, opacity over position, deterministic ordering.
- Next.js
- React
- TypeScript
- Tailwind
- WebSocket server
- Event bus
- Worker queue
- NestJS
- Nx libs
- Prisma
- JWT auth
- 268 specs
- E2E (18 entities)
- ESLint boundaries
What shipped.
A standard is paper. The product is the work.
I learned to ship inside a team larger than three, to trade speed for coherence, and to enforce front-end standards as code rather than as Slack messages.
↳ One Record · 2024 — 2025If Malta taught me to think end-to-end, One Record taught me to scale the same vision across a team.