Product Design Case Study · Design SystemsMerger: car2go → SHARE NOW · car sharing · 2019 – 2021
A system built to survive a rebrand
car2go built its app, web and B2B tools in separate teams. I built and led Camelot, with the brand as its bottom layer. That carried the rebrand to SHARE NOW. When we rebuilt the web, I reorganised it by purpose, so app and web stayed one.
- Role in the project
- Built and ledProduct designer, leading the founding group from 2019
- Platforms
- iOS, Android and webplus B2B tools, websites and print
- Responsibility
- Architecture and rulesLayers, naming scheme, principles and icon library; with brand, marketing and engineering
- Status
- and 2 more states
Shipped+2
As of September 2026
Shipped
Carried on after the rebrand as SHARE NOW Design System 2.0
Continued
After I left in 2021, by a design colleague in Stuttgart
Open
Impact figures are not documented
Shipped+2
As of September 2026
Shipped
Carried on after the rebrand as SHARE NOW Design System 2.0
Continued
After I left in 2021, by a design colleague in Stuttgart
Open
Impact figures are not documented
I did not build a system for one brand. I put the brand underneath the system so it could carry a change.
Camelot Design System
At a glance
4 layers
from the brand up to the interface
4 layersfrom the brand up to the interfaceScope of the system, not a measured outcome2,239
components in 68 sets, one naming scheme
2,239components in 68 sets, one naming schemeSize of the design library3 platforms
iOS, Android and web from one system
3 platformsiOS, Android and web from one systemPlus B2B tools, websites and print
Problem
Organised by purpose
Four layers from brand to interface instead of one library per platform.
Intervention
The brand at the bottom
When the brand changes, the change runs up through every layer.
Outcome
Carried the rebrand
Camelot became SHARE NOW Design System 2.0.
- Role in the project
- Built and ledProduct designer, leading the founding group from 2019
- Platforms
- iOS, Android and webplus B2B tools, websites and print
- Responsibility
- Architecture and rulesLayers, naming scheme, principles and icon library; with brand, marketing and engineering
Every team built its own components
At car2go, teams and products grew fast: the customer app, webviews, B2B, registration, later SHARE NOW Pass. A shared system existed only on the design side; engineering teams had no common source for components, patterns or templates and built much of it themselves.
01
Duplicate code
The same building blocks in several codebases.
02
Slow delivery
Every feature started from scratch.
03
Inconsistent brand
Users experienced every product a little differently.
04
No single source of truth
Nobody knew which component was the real one.
Before: one library per platform
App styleguide
Customer app with its own components.
Web styleguide
Website and webviews, maintained separately.
B2B styleguide
Tools for business customers.
BA styleguide
Yet another world of its own.
Splitting by platform made ownership easy and collaboration hard. Every team worked in its own silo, new components were hard to contribute, and we kept rebuilding the same building blocks.
The Camelot scope named three job stories, and the product teams add a fourth. What they all share: nobody should have to build the same building blocks twice:
CompanyJob story
- When
- new products and teams come in,
- I want
- one consistent experience across all products,
- so
- users reach their goals the easiest way.
DesignJob story
- When
- I design a solution for a new feature,
- I want
- a scalable design system,
- so
- I can build solutions and experiences faster.
EngineeringJob story
- When
- I build a feature,
- I want
- a scalable component system,
- so
- I don't have to rewrite every component each time.
Product teamsJob story
- When
- I build a feature for the app, a webview or the web,
- I want
- to use the same building blocks,
- so
- the brand looks the same everywhere, even when it changes.
Organised by purpose, not by platform
The order of the layers is the real decision. The brand sits at the very bottom, then the foundations, then the interactive UI and the public-facing pages.
A big influence was Brad Frost and his Atomic Design: small building blocks that combine into larger ones.
Brand
Colours, illustrations, vehicles and imagery as the foundation.
Foundations
Palette, typography, grid, breakpoints, buttons, input fields.
Interactive UI
For devices and desktop: map pins, sheets, navigation, tables, forms.
Public-facing UI
Website and landing pages, responsive, built from the same foundations.
Foundation: the pill buttons
The names follow the same order: category, subcategory, type, component. “Interactive UI / Device / Messaging / ToastBar” tells you where a building block lives and what it is for before you open it.
This order came later. When we rebuilt the website and the web products for private and business customers, web app elements also found their way into the native apps. There they could not feel different from everything around them, or they would have confused people. So I developed the system further and proposed this order as the new structure in April 2021: for consistency, for flexibility and as the link between app and web. Deliberately not as a hard switch, but as a transition out of the existing libraries.
Native in shape, consistent in behaviour
Because the foundations are shared, platforms only differ where the platform demands it. The toggle follows one form on iOS and the web and another on Android; colours, states and spacing stay the same. Typography comes in dedicated sets for web, iOS and Android.
The same toggle, true to each platform
A whole screen, two platforms
The library grew to 68 component sets and 2,239 components, all following one naming scheme, with a dedicated area for native iOS patterns.
The library mirrors the code
A system only stays shared if everyone knows how to extend it. New components had to follow six principles, and every change to a typeface, a colour or an existing component had to be agreed with engineering, because it takes effect everywhere at once.
Search first
Check the library first. The solution probably exists already.
Scalability
Don't build just for the task at hand; build so others can reuse it.
Consistency
Don't reinvent the wheel. Bring it in and make it better.
Snowflakes
Avoid one-off components, or have the facts to justify them.
Styleguide
Use the defined palettes and type; agree anything new with brand, marketing and design.
Collaboration
The library mirrors the components in code. Changes only happen together with engineering.
A justified one-off
The pin where it lives
Later, Storybook became the documentation in code, synced automatically into the native apps. We also had our own icon library and worked with marketing to carry the system all the way into print. In 2021 the library moved to Figma.
Who decides
At Camelot, the design team made the decisions, and made them together. The final sign-off was mine, as gatekeeper. The developers came to me with systems of their own, since iOS was built in Swift and Android natively. That became one shared route: we kept developing Camelot together, tested it pixel-perfect and connected the platforms through the global foundations.
Together in the design team
The design team decides; the work is done together
Sign-off
Me as gatekeeper, at the end of the review
Native build
The developers build in their own systems, in Swift and for Android
Pixel-perfect test
Checked together against the design, connected through the global foundations
Accessibility
Accessibility was a focus of the customer-app work at car2go and SHARE NOW. In Camelot's six principles, though, it was not a rule of its own. The rebuild now measures against WCAG: white on the primary action blue reaches only about 2.9:1, less than the 4.5:1 that AA requires for normal text.
Learning
Libraries split by platform make ownership comfortable and the system lonely.
Camelot became SHARE NOW Design System 2.0
The move from car2go to SHARE NOW was the stress test for the bottom layer: a new brand met a system that had deliberately put the brand underneath everything else. Camelot shipped and carried on as SHARE NOW Design System 2.0. After I left, a design colleague in Stuttgart took it forward.
The decision came with the 2019 merger: the app had to be rebuilt so it looked like neither car2go nor DriveNow, and the entire design library was to be rebranded. That is where the decision came from to put the brand in its own layer underneath the system. The order by purpose only followed later, when we rebuilt the web products.
See also:Compass Design System
What came of it
We never measured the goals from the scope. What is documented: Camelot shipped, carried the rebrand and was continued after I left.
In daily work
Storybook as documentation in code, synced into the native apps
Part of how design and engineering work
Rebrand
Carried on as SHARE NOW Design System 2.0
Rebrand the entire design library
Library
68 component sets, 2,239 components, one naming scheme
One source for every platform
Platforms
Native shapes and type sets per platform, the same colours and states
iOS, Android and web from the same foundations
In the guildopen
not documented
Part of the frontend guild, with at least one vocal advocate
At scaleopen
not measured
Replace duplicated foundation components in 80% of teams
What I learned and would do differently today
Caveats
I built and led Camelot; design and engineering implemented it together, and after I left in 2021 a design colleague in Stuttgart took it forward. What is documented is its structure, scope and course; there are no figures on its impact. As of April 2021.
Learnings
The brand belongs at the bottom
A system survives a rebrand when the brand is a layer of its own, not something baked into every component.
Organising by purpose means spreading ownership
Libraries split by platform are comfortable but lonely. Organised by purpose, teams work on the same building block instead of copies.
Clarify what exists, then build
During the merger we rushed into one feature and threw it away months later. Since then I start with the roadmap and what already exists.
A system only stays shared if people can extend it
Clear principles for new components mattered more than any single component.
What I would do differently today
Make the goals measurable
We had clear success criteria but no measurement. Today I would count the duplicated foundation components before starting, so a goal like 80% of teams can actually be proven.
Spread ownership earlier
Ordering by purpose and shared ownership only came with the 2021 proposal. Today I would decide from the start who maintains which layer.
Accessibility as a principle of its own
Contrast, focus and keyboard to WCAG AA belong next to the six as a seventh rule, with values in the tokens instead of in review.
A design system doesn't prove itself at its first release. It proves itself at the first rebrand.
fin (for now)