TechTensteinColour contrast checker
Compare foreground and background colours against WCAG 2.2 AA thresholds. No colour values are sent to TechTenstein.
UI/UX & product design
UI/UX design services for websites and apps
UI/UX design that makes the important tasks understandable before you commit to a full build. We can map user journeys and create screens and prototypes for a defined website or application.
Discuss this project ↗Who this is for
Teams planning a new product or improving a specific journey in an existing one.
What we can scope
- A focused review of the target user and task
- Page or screen flows with content priorities
- Responsive interface designs and a reviewable prototype
- Design handover with reusable components and interaction notes
How the project runs
Six checkpoints from brief to handover.
Design work uses the same six checkpoints, with the emphasis on the review stage: page or screen flows are reviewed before anyone commits to implementation, and concepts are labelled as concepts, not live products.
- Define the outcome. Start with the users, the task, constraints and how you will judge success.
- Agree scope and fees. The proposal defines deliverables, milestones, review rounds, dependencies, ownership and ongoing costs.
- Review the design. Review the page or screen flow before committing to implementation.
- Build and test. Implementation proceeds through reviewable milestones, with agreed functionality, accessibility, security and performance checks.
- Approve and launch. You approve the release. Domain, hosting and app-store access are handled through scoped access, and store reviews remain external decisions.
- Handover and care. Receive the agreed source, access and operation notes. Any maintenance plan is optional and defines its tasks, limits and third-party costs.
What you own at handover
- Design deliverables, research activities and revision rounds are agreed before work begins.
- The handover includes reusable components and interaction notes for whoever builds the product.
- Ownership of the finished design and any third-party licences are defined in the proposal.
What is agreed, and what is not promised.
Design deliverables, research activities and revision rounds are agreed before work begins. Prototypes are not production applications, and conversion improvements require measurement.
We confirm scope, fees, timelines and ownership in the project agreement. A brief is an enquiry, not a purchase or a promise of delivery.
How the project process works →Free · no email required
Free tools to prepare
your brief.
Use these before you request a proposal. They organise the decisions; they are not quotes or proof of results.
Accessibility quick review
Combine preliminary HTML checks, contrast guidance and the human tests still required.
Landing page review
Inspect content structure, calls to action and form-label foundations on an existing page.
Combine in one reviewed scope
Related services
Related work can be combined in one reviewed scope. We do not bundle unrelated deliverables merely to make a project larger.
Before you start
Frequently asked questions
What is the difference between UI and UX design?
User interface design shapes the controls, content hierarchy and visual states through which a person operates a product. User experience covers the wider journey: whether the product solves the right problem, works reliably and respects the person’s context. A strong product needs both.
What does a UI/UX design deliverable include?
A focused review of the target user and task, page or screen flows with content priorities, responsive interface designs and a reviewable prototype, and a design handover with reusable components and interaction notes. Research activities and revision rounds are agreed before work begins.
Is a prototype the same as a working app?
No. Prototypes are not production applications. A prototype lets you review the journey before committing to implementation, and concepts are labelled as concepts, not live products.
Will a redesign increase conversions?
Not automatically. Conversion improvements require measurement. Design can make a journey clearer, and the success measures to check after release should be named in the scope.
Can our own developers build from your designs?
Yes. Who will build and maintain the final product is decided in the brief. The design handover includes reusable components and interaction notes so the build team can implement it, and a TechTenstein build can be scoped separately.
Your next step
Tell us what
you have in mind.
You don’t need a perfect specification to start. You can also email contact@techtenstein.com.