Users can't find the thing
Navigation grown by accretion. Every new feature added a menu item until nobody could find anything.
Service 04 / 14
UI/UX Design
Design that ignores engineering constraints produces beautiful files nobody can build. We design in the same room as the people writing the code, and ship a system rather than a set of screens.
- Typical duration
- 4–10 weeks
- Engagement
- Team of 1–3 · Fixed scope
- Right for you if
- Products where users need training to complete basic tasks
- Teams whose UI has drifted into twelve shades of grey
- Companies with high signup rates and low activation
- Anyone about to build — design before code is the cheapest fix there is
Problems
You're probably here because of one of these.
If more than one sounds familiar, that's normal — they usually share a root cause.
Signups don't become users
People arrive, sign up, and never return. The gap between registration and first real value is too wide.
Nothing looks related
Four button styles, inconsistent spacing, and components rebuilt from scratch in every feature.
Designs don't survive implementation
Handoff is a static file and a hopeful conversation. What ships resembles the mockup only from a distance.
Approach
How the work actually runs.
From first conversation to running in production. Typical end-to-end duration for ui/ux design is 4–10 weeks.
- 01
Research
1–2 weeksWe watch real users attempt real tasks before proposing anything. Opinions lose to recordings.
- Moderated usability sessions with current users
- Analytics and funnel analysis of where people drop
- Competitive and adjacent-product teardown
- Prioritized findings tied to business metrics
- 02
Structure
1–2 weeksInformation architecture and flows come before any visual decision.
- Sitemap and navigation model
- Task flows for every primary user journey
- Low-fidelity wireframes for critical screens
- Content model and terminology decisions
- 03
Design system
2–3 weeksWe build the vocabulary once — tokens, components, states — then compose screens from it.
- Color, type, spacing and motion tokens for light and dark
- Component library with every interactive state specified
- Accessibility rules baked into the components
- Usage documentation for designers and engineers
- 04
Interface design
2–4 weeksHigh-fidelity screens composed from the system, including the states everyone forgets.
- Every screen at mobile, tablet and desktop
- Empty, loading, error and permission-denied states
- Interactive prototype for stakeholder and user testing
- Motion specifications with timing and easing
- 05
Validation
1 weekWe test the prototype with users before engineering commits to it.
- Usability testing on the interactive prototype
- Revisions from observed failures, not opinions
- Accessibility review against WCAG 2.2 AA
- Sign-off on the final design system
- 06
Implementation support
OngoingWe stay available through the build and review the front end against the system.
- Coded component library, not just design files
- Design QA on staging builds
- Direct access to the designer during engineering
- System maintenance as new patterns emerge
Included
What you get, spelled out.
Every item here is part of the engagement, not an upsell discovered halfway through.
Usability research
Recorded sessions with real users attempting real tasks, before design starts.
Design tokens
Color, type, spacing and motion as code — a single source of truth for both themes.
Component library
Every component specified in every state, delivered as design files and working code.
Interactive prototype
A clickable build that can be user-tested before engineering commits.
Accessibility built in
Contrast, focus order and semantics designed rather than retrofitted.
Responsive at three breakpoints
Mobile, tablet and desktop designed deliberately — not scaled down.
Every state designed
Empty, loading, error, offline and permission states specified up front.
Motion specifications
Timing, easing and choreography documented so implementation matches intent.
Stack
What we typically build this with.
A default, not a rule. If your team already runs something else and it fits the requirement, we work in your stack.
React
The largest hiring pool in the industry, so you're never dependent on us.
Vue
Gentler learning curve for teams inheriting the codebase. Excellent where an in-house team will take over.
Svelte
Compiles away the framework. Our pick when bundle size is a hard constraint — embedded UIs, low-end devices.
TypeScript
Types across the whole stack. Most integration bugs stop being possible.
Tailwind CSS
Design tokens enforced in markup. Styles stop drifting across a large team.
Next.js
Server rendering, streaming and edge delivery without hand-rolling the infrastructure.
Why Devsock
The difference is in how the work is run.
Ten dimensions where engagements usually go wrong, and what we do instead. Every claim in the right-hand column is something you can verify in the first two weeks.
DimensionTypical agencyDevsock
Estimates
TypicalAn hourly rate and a range that grows once work starts.
DevsockFixed scope and fixed price after a paid discovery. Changes are quoted before they enter a sprint.
Communication
TypicalA weekly status email written by an account manager.
DevsockDirect access to the engineers building it, a shared board you can read any time, and a demo every second week.
Code ownership
TypicalDelivered at the end, sometimes with a proprietary framework attached.
DevsockYour repository, your cloud account, from commit one. No proprietary layer, no licensing.
Testing
TypicalManual clicking before launch, if the timeline allows.
DevsockAutomated suites in CI, load testing at projected peak, and a WCAG 2.2 AA audit before release.
Architecture
TypicalWhatever the available developer knows best.
DevsockA written architecture decision record explaining what we chose, what we rejected, and why.
Security
TypicalAddressed if the client raises it.
DevsockDependency scanning in CI, least-privilege access, secrets management and a pre-launch review as standard.
Accessibility
TypicalOut of scope unless legally forced.
DevsockWCAG 2.2 AA designed in and audited. Keyboard and screen-reader tested, not assumed.
Handover
TypicalA zip file and a phone number that stops answering.
DevsockDocumented architecture, runbooks, and a paid handover period so your team can genuinely take over.
After launch
TypicalA new quote for every bug.
DevsockDefect fixes covered for 90 days. Support retainers carry response-time SLAs in the contract.
Saying no
TypicalEvery request becomes a line item.
DevsockWe'll tell you when a feature isn't worth building, or when the answer isn't software at all.
Work
What we've built, and what it changed.
Live products you can open and use. Each one names the constraint, the approach and what shipped.
- Next.js
- TypeScript
- React Native
- PostgreSQL
- Redis
- Stripe
- AWS
Multi-tenant SaaS platform and driver apps for dumpster rental operators
Challenge
Dumpster rental operators run bookings, fleet position, driver assignments and invoicing across spreadsheets, whiteboards and phone calls. Nobody knows where a container actually is, proof of service arrives days after the job, and billing gets reconstructed from memory at month end.
Solution
A multi-tenant SaaS platform with self-serve signup, subscription billing and tiered plans, paired with native driver apps on iOS and Android. Operators get real-time container status, driver scheduling with route optimisation, customer and contract management, and automated invoicing. Drivers receive job assignments and upload proof of service from the field.
What shipped
- Native driver apps published to both the App Store and Google Play
- Multi-tenant architecture with per-operator data isolation
- Self-serve onboarding with a 15-day trial and three subscription tiers
- Real-time inventory and container status tracking
- Driver scheduling with route optimisation
- Automated invoicing and payment processing
- Next.js
- TypeScript
- Tailwind CSS
- Vercel
Corporate platform for an independent renewable-energy consultancy
Challenge
An independent monitoring and evaluation consultancy for renewable energy projects needed to establish credibility with government, industrial and hospital buyers — a sector where procurement turns on verifiable regulatory standing and a demonstrable track record, not on marketing copy.
Solution
A structured corporate platform built around proof rather than persuasion: service definitions for independent oversight and technical training, a credentials section surfacing regulatory compliance across SECP, FBR, PRA and PEC, team profiles establishing sector experience, and a documented track record of verified installations. Enquiries route directly to the consultancy team.
What shipped
- Structured service architecture across oversight and training lines
- Regulatory credentials surfaced as the primary trust signal
- Track record documented across government, industrial and public-health installations
- Team credibility profiles with sector experience
- Enquiry capture routed to the consultancy team
- Server-rendered and fully indexable
- Next.js
- TypeScript
- PostgreSQL
- Tailwind CSS
- AWS
Training platform with multi-country scheduling and certificate verification
Challenge
A QHSE training provider delivering internationally accredited certifications across Saudi Arabia, the UAE and Pakistan needed to publish a constantly moving multi-city schedule, take registrations online, and let employers independently verify that a certificate is genuine — the last of which is what makes an accreditation worth anything.
Solution
A training platform combining a published course schedule across multiple countries with online registration, a separate corporate training enquiry path, and a public certificate verification tool employers can use to authenticate credentials. Accreditation bodies and trainer profiles are presented as structured, checkable content rather than a logo wall.
What shipped
- Public certificate verification for employers
- Multi-country training schedule with online registration
- Separate paths for open-enrolment and corporate training
- Course catalogue spanning ISO, OSHA, IOSH, NVQ and Lean Six Sigma
- Accreditation bodies and trainer credentials as structured content
- Server-rendered and fully indexable
Further work sits behind NDAs. We can walk you through the architecture and measured outcomes of those engagements under mutual NDA.
Request a walkthroughFAQ
UI/UX Design — common questions.
Specific to this service. The general questions about pricing, ownership and process are answered on the home page.
Still unsure? hello@devsock.com
Yes. Plenty of clients bring their own engineering team. We deliver the system as working coded components alongside the design files, which removes most of the usual handoff loss.
Related
Usually paired with.
Most engagements combine two or three of these. We'll tell you which ones you actually need.
Next step
Let's scope your ui/ux design project.
Bring us the problem rather than a specification. Thirty minutes with an engineer will tell you whether this is the right service, what it would take, and roughly what it would cost.
30 minutes
No slide deck, no sales team
An engineer
You speak to someone who builds
A straight answer
Including when it's don't build it