winPharma
winPharma
Back
Lukoil digital museum
Design System • Product design
Date
2024 — Present
Info
WinPharma is a leading pharmacy software provider, delivering end-to-end platforms for independent and group pharmacies in France. Its products cover dispensing and e-prescriptions, stock and purchasing, billing and reporting, CRM/loyalty, and analytics.
What did I do
I led the creation and rollout of a design system — the company's first structured UI language. We delivered design tokens, a component library, an icon system with searchable SVG/NPM delivery, and web wrappers for native modules. The system reduced front-end effort and standardized UI behavior across products.
WinPharma operates on a mixed legacy stack with offline/VPN Windows clients and uneven React experience across teams. The landscape spans four product lines plus a shared admin console. We had to support 24/7 pharmacy workflows and strict health-data compliance while unifying the UX without forcing a hard single-stack migration.
Standardize interfaces and speed up delivery across all product lines — reducing release defects and support costs — while enabling teams of mixed maturity (online and offline) to ship high-quality features consistently.
Built a design system with dual delivery: tokens, iconography, Storybook, Figma Code Connect, and two component channels — modern React components for web apps and HTML wrappers that render server-generated data consistently for legacy/offline clients. Added a wrapper layer so non-React teams could reuse the same visuals and behavior. Launched an icon pipeline (SVG → React/NPM), a naming red-policy, living docs, lint rules, and enablement sessions, then scaled the system across four product lines and the admin console. In parallel, modernized the admin console (core: filters + pharmacy list) and codified editorial/UX guidelines for domain flows.
• Handoff & defects: 4–8 h/month saved by standardizing tokens/patterns and reducing bug-fix loops;
• Adoption: 3–5 h/month saved via faster ramp-up for new team members and fewer reworks;
• Speed for non-React teams: 2–4 h/month saved by HTML wrappers and ready back-end-to-front contracts;
• Icon pipeline: 1–2 h/month saved on publishing/lookup (SVG → React/NPM, tagged catalog);
• Docs & process: 2–4 h/month saved through living docs, lint rules, Storybook, and PR templates;
• Consistency: 3–6 h/month saved thanks to the red-policy and editorial/UX guidelines (fewer reworks).
