What this covers
Responsive, accessible screens that match your designs down to the details.
Tools
Figma, GSAP, Framer, Animation. The exact stack depends on what you already use.
Where it helps
- Consistent components across the agreed screens and screen sizes.
- Controls that work with a keyboard and show clear states.
- Components your designers and developers can reuse.
We agree what “done” means before work starts.
What you get
- Screen, component, and state inventory
- Responsive interface implementation
- Keyboard and accessibility checks on the main flows
- Component guidance and developer handover
The final list depends on the agreed scope. The estimate and schedule follow from it.
Data and security
We agree on login and access rules, how long data is kept, where keys are stored, and who handles releases. Early reviews use sample data, not real records.
How I work on it
Discovery, then scope and what “done” means, then design, build, testing, release prep and any agreed support.
What helps me get started
- Design files and existing style or component guidance
- Screen list, target devices, and interactive states
- Your framework and repository constraints
A short outline is enough for a first call. Please send sample data, not real records or passwords.
Related services
Read the planning guideQuestions
Do you do branding or UX research?
No, this service is about building and refining interfaces. Research or brand work would be a separate project.
What if the designs are missing mobile or error screens?
I list the missing states during scoping, and we agree how they should look before I build them.