A regulated industry, an analog workflow.
Since 2022, French construction sites must digitally track every type of waste they produce. Most still do it on paper.
Wastern is the SaaS that closes the gap: order skips, track flows, generate compliant BSD documents, access a supplier directory. Three personas served — promoters, BTP companies, waste collectors.
I joined as an apprentice for two years, wearing two hats: product designer and front-end developer.
Designer in the morning, dev in the afternoon.
The boundary between design and code didn't exist on this team. By the end, I could go from a user interview to a shipped feature without changing toolkits.
Designed for hard hats, not designers.
Wastern users wear gloves. They use the app on a job site, in bright sunlight, often with concrete dust on their phone.
The constraints were unforgiving:
- Tap targets at 56px+ (gloves don't have fingertips)
- High contrast everywhere (sunlight kills greys)
- Number-first hierarchy (operators care about cubic meters)
- Single-tap actions for the 80% workflow
I built a utilitarian design system in Figma — tokens, components, BSD documents, status pills. Every screen got the gloves test.
React app + Webflow site, one brand.
Same brand assets, two ecosystems — kept in sync by treating the design system as the source of truth.
- React
- TypeScript
- Tailwind
- shadcn/ui
- Webflow
- HubSpot CMS
- Forms API
- TrackDéchets API
- BSD generator
- PDF export
- Figma
- Design tokens
- Brand kit
What shipped.
Where design stops, code starts. Then everything blurs.
Two years as an apprentice gave me what no senior role would: the time to mess up, iterate, and rebuild things from scratch — multiple times. If I'm a hybrid designer-developer today, it's because Wastern let me become one.
↳ Wastern · 2022 — 2024The artificial line between design and code is just a job description. When you own both, the feedback loop tightens and the product gets better.