Sinh Vũ turns your identity into a single source of truth for designers and developers. Your team builds new screens from ready-made components, instead of every team doing it its own way.
5 steps · 5 approvals on your sidePick a step to see what Sinh Vũ does, what you decide and what you receive.
Step 01 · Discovery and alignment
Step 02 · System and usage rules
Step 03 · System and usage rules
Step 04 · System and usage rules
Step 05 · Rollout
Brand guidelines are written for people to read; a digital design system is the machine-readable version of the same identity. Once a brand has several digital products, each team builds its interface its own way, and colours and spacing slowly drift. A brand that looks great on paper still dilutes inside digital products, because nothing enforces it. Sinh Vũ builds one source of truth so the design team and the engineering team read the same table of values, instead of each side copying its own version.
A brand that looks great on paper still dilutes once it goes into digital products.
A system only lives if the engineers can use it. Sinh Vũ starts by taking stock of what is already running, builds the foundations, then has both teams review one sample component before rolling it out.
Part 1
Collect every component in use, note where it appears, then agree the colour, type and spacing scales and the grid.
Foundations approvedEvery component will read from it
Part 2
Build one sample component with all its states, review it together with someone from your engineering team, then roll out the rest.
Reviewed by both teamsDesign and engineering check it together
After handover
Hand over the system, train your team, and sign off once your engineers can rebuild a sample screen using only the system.
A sample screen rebuiltUsing only the system, no extra questions
Add the two figures together for the real time from kickoff to handover. Your part follows the approval window of each step, so approving early shortens the schedule.
Having these ready keeps the project on schedule. If something is missing, Sinh Vũ can still start, and the handover date moves back accordingly.
Each item comes with its format and the job it does for you; your engineering team turns the library into code.
Assemble new screens from ready-made buttons, inputs and cards, with every state.
Component library file
Bring colour, type and spacing into code without copying by hand.
Exportable to code
Know when to use each component, and when not to.
With every component
The library lives in your company's own workspace.
Transferred to your company
Your designers and engineers build new screens with the system on their own.
Handover session
The system is signed off by your team being able to use it, not by how good the drawings look. The four points below are written down from the start.
Every state covered
Each component has all the states stated in scope, with none missing when it is built for real.
Checked component by component
Usage documentation included
Each component comes with documentation on when to use it and when not to, clear to a newcomer.
Each entry read
Engineers rebuild a screen
Your engineers can rebuild a sample screen using only the system, without asking Sinh Vũ anything more.
A sample screen built
Source files that open
Source files open in the tools your team already uses, with no Sinh Vũ-specific software needed.
Opened in your team's tools
The tests Sinh Vũ runs before every design sign-off. Your files never leave your device.
The way of working on this page rests on principles from the Sinh Vũ craft doctrine. Open one to read the reasoning, its limits and when it fails.
Sinh Vũ quotes once it knows the number of components, the number of screens and the tools your team uses, as a fixed package. No surprise fees along the way.
Paid once
Quoted by the actual number of components and platforms, fixed as a package before building.
One or two digital products, standardising colour and type first.
4-7 weeks
Quoted by scope
Several products, shared design and engineering teams.
8-9 weeks
Quoted by scope
Many teams and partners share the digital identity.
10-12 weeks
Quoted by scope
Not sure which tier fits? Talk for 5 minutes and Sinh Vũ will suggest one →
Sinh Vũ talks to your technical team first to understand the platform in use, for example web or mobile app, before agreeing the design token table (standardised colours, spacing and type sizes) and the interface components reused in many places, such as buttons and inputs. The handover is a set of design files and a token table that exports to code, so engineers can follow it without guessing. Coding a working component library is not part of the service.
Yes, but the basics such as colour, type and spacing must be agreed before components are built; otherwise the system has nothing to anchor to, and changing the foundations later means rebuilding every component. That is why Sinh Vũ usually suggests tidying up the identity first, then building the digital system.
The point of a digital design system is that your team adds screens and uses existing components without asking Sinh Vũ about every small detail. Sinh Vũ hands over usage rules with it, and can run a quick training session for your in-house designers or engineers if you need.
They are not locked. Files are built in a widely used design tool, and tokens export in a standard format that ordinary web and app tooling can read. Your team can keep editing them without coming back to Sinh Vũ.
The digital design system is built with components and tokens in mind from the start, not drawn as nice screens and then worked out how to turn into code. That is why a conversation with your technical team always comes before building the system, so both sides speak the same language.
The number of components and screens and the complexity of digital products vary a great deal between businesses, so a single price list would not reflect the real workload. Sinh Vũ quotes once it clearly understands your product scope and technical platform.
It depends on the size of the product, the number of components to standardise and whether the business already has brand guidelines. The timeline is agreed with the quote, based on the real scope discussed.
The tokens and core design principles are not tied to any one technology, so they can be reused. Only the way components are implemented in the new technology needs redoing, which is usually much lighter than building the system from zero.
Send a few lines about what you need, and Sinh Vũ replies within the working day.