App design system
Has your brand aged faster than expected? Are your teams lost between ten versions of the logo? Has your rebrand been dragging on for eight months and you're launching in three weeks?
Good news, that's what we're here for.
Too much complexity, not enough impact.More time was spent getting organized than actually producing. Deadlines slipped, feedback piled up, and the creatives ended up burning out...
A continuous workflow to create your new brand, and bring it to life
The art direction is crazy, but our method isn't. Thanks to our working methodology, we co-create your brand with your teams through successive 48–72h iterations. Every deliverable is justified by your senior lead designer
A dedicated team, from the first wireframe to launch
A senior lead designer driving the project, a project manager steering it day-to-day, and Geoffrey developing it in Framer. The same people from kick-off to training, plus a video with every delivery so you never lose track.
A version every 48 to 72 hours
A traditional agency leaves two to three weeks between presentations. At Dafolle, each task is estimated in credits before starting, then delivered in short iterations. You provide immediate feedback, and the project never gets bogged down.
Designed in Figma, developed in Framer, editable by you
The pages are designed in Figma, approved on your phone, and then Geoffrey builds them in Framer. Once live, changing text takes just two clicks, and the site connects to your AI tools via MCP.
What does a rebranding project look like?
Before starting a project, we agree together on the list of deliverables to build.
Weeks 1–2
Audit & Architecture
We analyze your existing app. Component by component. We identify inconsistencies, duplicates, and faulty patterns. We define the basic tokens (colors, typography, spacing). We validate the roadmap with you. Deliverable: System architecture + prioritized backlog.
List of sized tasks
Access to Dafolle OS
Weeks 3–4
Foundations (Tokens & Atoms)
We build the tokens (design variables) and atomic components (buttons, inputs, badges, etc.). We create the basic technical documentation. We test the implementation with your developers. Deliverable: Operational foundations.
List of sized tasks
Access to Dafolle OS
Weeks 5–6
Basic components
We develop essential components (cards, forms, navigation, modals). Comprehensive documentation with code examples and use cases. Integration tests. Deliverable: Ready-made basic component library.
List of sized tasks
Access to Dafolle OS
Weeks 7–8
Complex components
We tackle advanced patterns (data tables, dashboards, multi-step flows). We refine the documentation. We train your teams to use it. Deliverable: a complete, working design system.
List of sized tasks
Access to Dafolle OS
Month 3+
Evolution & Maintenance
Your product is evolving. Your design system is too. New components according to your needs. Adjustments on existing components. Maintenance of the documentation. Continuous support. Included in the subscription.
When we launched Dafolle, we had had enough of website redesigns that drag on for eight months, cost six months' worth of contract amendments, and end up with a site that no one dares touch anymore.
We built a model for the exact opposite: a subscription with no quotes, senior designers recruited for their business acumen, and an AI infrastructure that we enhance every month so your teams remain autonomous after we're done.
If you're hesitating about entrusting your redesign to us, let's take fifteen minutes. I'll tell you what we can do, and what we won't do.
Joffrey & Clara
Co-founders of Dafolle
The tools we use for app design systems
What exactly is a design system?
This is the library of all the visual components and design rules for your app. The tokens (colors, spacing, typography), the components (buttons, cards, inputs), the patterns (how they fit together), and the technical documentation. The goal: for every designer and developer to work with the same foundation, without reinventing the wheel.
Why not just a nice organized Figma file?
Because a Figma file, even if well organized, only resolves 30% of the problem. It lacks technical documentation (how to implement in code), usage rules (when to use which component), and above all, continuous evolution. Our design system is alive: it evolves with your product through the subscription.
How long does it take to set up?
8 weeks to have an operational design system with the essential components. But we deliver sprint by sprint: by weeks 3-4, you have the usable foundations. And we continue to enrich the system over the months according to your needs.
What tech stack do you work with?
We adapt to your stack. React, Vue, Angular, React Native, Flutter... We create the documentation and code examples in your technology. For documentation, we use Storybook (if you're on JS/React) or we integrate with your existing wiki (Notion, Confluence, etc.).
Can we modify/enrich the design system after delivery?
That's the whole point. With a subscription, the evolution of the design system is included. Need a new component? We create it. Need to adjust an existing component? We iterate. No change orders. It's included in the monthly package.
Do you train our teams to use it?
Yes. We don't just deliver a system and disappear. We train your designers to use it and to evolve it. We train your developers to implement it correctly. We document everything. The goal is for you to be autonomous, but with our ongoing support.
How much does it actually cost?
Initial setup (8 weeks of build): between €18K and €35K depending on your app's complexity. Then a monthly subscription (updates + maintenance + support): between €2,500 and €6,000/month. We define the exact scope together during the brief.
How is this different from an open-source design system (Material, Ant Design)?
Open-source design systems are solid but generic foundations. They don't reflect your brand identity and need heavy customization. We can start from an open-source base and tailor it to your brand, or build from scratch. We assess what makes the most sense for your case.
Do you guarantee a reduction in time-to-market?
We do not sell miracles. But the numbers speak for themselves: our clients reduce their average development time for new features by 2.5 times (from 8 days to 3 days for an average flow). The reason? The components are already created, documented, and tested. Developers assemble instead of recreating.
Can we start with an MVP of the design system?
Yes. We can start with a "Design System Core": tokens + 8-10 critical components + basic documentation. It takes 4 weeks. Then we gradually enrich it on a subscription basis according to your product priorities. Lean approach, quick results.