Project description
Our interface has been put together over three years by different people, and you can see every handover in it. The button on the billing page is two pixels taller than the button in settings, paddings are picked by eye, and I counted six greys in the mockups that nobody can tell apart or explain. Every new screen starts with an argument about what a primary button looks like and ends with one more slightly different input field.
I want to close this question once. I am ordering a design system in Figma that becomes the single source of truth for the product: colour and size tokens, a type scale, a grid, and a component library where every element carries all of its states — default, hover, pressed, disabled, error and loading. Forms and tables deserve the most attention, because that is where our users actually work and where the inconsistency hurts most today.
Light and dark themes must be built from the same tokens, so switching a theme is a swap of values and not a second set of screens. Each component needs a short documentation page: when to use it, when not to, which variants exist, how it behaves on a narrow screen. The acceptance test is simple — a developer opens the library and assembles a screen without asking me a single question.
What I expect in the work:
— tokens for colour, spacing, radius and typography, light and dark themes from one shared set;
— a component library with all six states on every interactive element;
— forms and tables in detail: fields, validation, sorting, pagination, empty states;
— spacing rules and a grid that let a screen be assembled without improvisation;
— a documentation page for each component, written for developers, not for a portfolio;
— templates of typical screens: list, record card, settings, step form, empty and error states;
— contrast of text and interface elements is checked against commonly accepted accessibility norms, not by eye;
— fonts are chosen with a licence that covers web use;
— the library is handed over with rights to the file and is not tied to the contractor's account.
Two weeks is the timeline I am counting on, and I am happy to split the work into stages with a review after each one.
I want to close this question once. I am ordering a design system in Figma that becomes the single source of truth for the product: colour and size tokens, a type scale, a grid, and a component library where every element carries all of its states — default, hover, pressed, disabled, error and loading. Forms and tables deserve the most attention, because that is where our users actually work and where the inconsistency hurts most today.
Light and dark themes must be built from the same tokens, so switching a theme is a swap of values and not a second set of screens. Each component needs a short documentation page: when to use it, when not to, which variants exist, how it behaves on a narrow screen. The acceptance test is simple — a developer opens the library and assembles a screen without asking me a single question.
What I expect in the work:
— tokens for colour, spacing, radius and typography, light and dark themes from one shared set;
— a component library with all six states on every interactive element;
— forms and tables in detail: fields, validation, sorting, pagination, empty states;
— spacing rules and a grid that let a screen be assembled without improvisation;
— a documentation page for each component, written for developers, not for a portfolio;
— templates of typical screens: list, record card, settings, step form, empty and error states;
— contrast of text and interface elements is checked against commonly accepted accessibility norms, not by eye;
— fonts are chosen with a licence that covers web use;
— the library is handed over with rights to the file and is not tied to the contractor's account.
Two weeks is the timeline I am counting on, and I am happy to split the work into stages with a review after each one.
Design and multimedia Cash, Bank transfer
