Based in
Nantes, France
Experience
10+ years
Hats
Design & Dev
Availability
Open to projects
A path in two acts: a hybrid design + engineering education, then ten years split between studios, entrepreneurship and freelancing — always on products where the line between design and code is a blurry one.
Five years between Nantes and Laval bridging two disciplines that barely talked to each other back then: user-centred design and real-time 3D. That is where my hybrid approach took shape.
École de Design Nantes Atlantique
ENSAM Laval
First clients alongside my studies. Designing and building websites for freelancers, artists and small organisations — where I learned to carry a project end to end, from brief to launch.
A startup built around one intuition: point your phone at an event flyer or poster and watch the artwork warp in time with the music line-up — then book a ticket or RSVP straight from the app. A project mixing augmented reality, interaction design and music programming.
Three years leading the design and development of augmented reality apps for major brands: in-store experiences, product configurators, event activations. Managing a small team, owning the Unity architecture, and working directly with the clients' design teams.
Built v2 of the app, then ran a full UX/UI redesign and built v3. Both hats, fully owned: I design the experience, I code the app, I take part in product decisions. This is the context where my way of working sharpened the most.
Back to school — on the other side of the desk. I teach students Framer, Spline, Figma, UX/UI and vibecoding (coding with AI). Teaching forces me to put into words what I have been doing on instinct for ten years.
Design
Good design isn't an 80-screen Figma file. It's three decisions that make the other 77 screens obvious.
01
One hour of user interviews beats ten hours in Figma. I always start by framing the real problem — not the one I was handed.
02
The first flows are born on paper or on a tablet. Fast, disposable, and without falling into pixels before the structure is solved.
03
I move to development once the system (tokens, components, rules) fits on a single page. Everything else follows from it.
04
Rather than mocking up 10 screens to test a feature, I'd take a 3-screen interactive prototype. Faster to build, and a far better test of the overall experience.
Development
A well-built product reads like a well-organised design file. Same principles: clear hierarchy, reusable components, and very little hidden magic.
01
React, React Native, Firebase, Tailwind, shadcn/ui. A stack I know inside out, covering prototype to scale without rebuilding the foundations every project.
02
My React components carry the same names as my Figma components. A Button stays a Button. The mapping reads cleanly from both sides.
03
AI handles the plumbing: boilerplate, refactors, docs. I keep the architecture, the product calls and the overall consistency. Real time saved, without delegating judgement.
04
Production isn't a finish line. I ship early, watch how people actually use it, and v2 of a feature lands before v1 has time to set.
Available for product design work, development work, or long-term collaborations.