Mobile · Web · Interface · London SW20
Small screens,
cut with care
VAI Tech designs and builds mobile apps and web apps for the ordinary moments of a day: checking a timetable, booking a class, keeping a list, finding the thing you saved last week. We work like a gem cutter: remove everything that does not catch the light, then polish what remains until it feels effortless.

Illustrative generated photograph.
The four Cs, borrowed
How we judge an everyday app
Jewellers grade stones by cut, colour, clarity and carat. We grade small software with four qualities of our own, and we use them in every review.
Clarity
Each screen has one purpose you can state in a sentence. If we need two sentences, the screen is split or simplified.
Cut
Nothing is there for decoration alone. Every element, word and animation earns its place or is removed.
Colour
Colour is chosen for meaning and contrast first, mood second, and checked against accessibility ratios on real screens.
Calm
No nagging notifications, no manipulative prompts, no surprise permissions. The app is there when needed and quiet when not.
Five facets
What we make
Mobile apps for iOS and Android
Apps people open several times a week: lists, reminders, bookings, local information, small community tools. We usually build one shared codebase for both platforms and drop into native code for the moments that need it, such as widgets or camera work.
Web apps that feel like apps
Fast, installable web apps for tasks that do not justify a store download: booking forms, member areas, simple dashboards. They work on any phone with a browser and update instantly.
Interface and experience design
Research with real people, careful flows, then screens designed down to the spacing between a label and its value. Delivered as a small, well-documented design system.
Publishing support
Store accounts, listings, screenshots, privacy forms and review notes prepared with the same precision as the app itself, so the last step is not the stressful one.
Care after launch
Operating systems change every year. We keep apps current, fix what breaks and make small refinements, on response times agreed in writing.
Select a tab or a facet of the gem.
Everyday, illustrated
Three small moments, designed
These are illustrative concept screens, not client products. They show the kind of quiet, single-purpose interfaces we like to make.
Next bus
Thursday pilates
You have 5 of 8 classes left this month.
Library loans
Loupe 01 · Contrast
Is this text readable on that colour?
Pick two colours or type hex codes. The ratio is calculated with the WCAG 2.2 formula; the sample shows how it feels.
Your bus arrives in 4 minutes
Body text at ordinary size, the way most of an app is read.
Everyday mobile
Designed for a hand, a thumb and half a minute
Most everyday app use is brief and interrupted. Someone checks something while a kettle boils, then puts the phone away. We design for that rhythm: the answer appears first, actions sit within thumb reach, and if the person leaves halfway through a form, it is still there when they return.
We test with enlarged text, VoiceOver and TalkBack, dark mode, older phones and poor connections. We also test the boring states that most portfolios never show: empty lists, failed loads, expired sessions. Those are the moments when an app either feels trustworthy or does not.
Under the loupe
Our design method in five turns
Observe
Short conversations with people who will use the app, about the moment it serves.
Distil
One sentence per screen. A flow diagram that fits on a page.
Shape
Grey wireframes, then a clickable prototype on a real phone.
Test
Five people, a few tasks, careful notes on every hesitation.
Polish
Final visual design, states, motion and a documented system.
Loupe 02 · Store listing
Draft the three lines people see first
Character limits follow the current App Store fields: app name 30, subtitle 30, promotional text 170. Google Play's title limit is also 30. Check the store consoles before submitting, as limits can change.
Preview (illustrative)

Publishing support
The final setting
A beautiful app can still stumble at the store. We prepare listings, screenshots for the required device sizes, privacy declarations that match the real data flows, and reviewer notes with a working demo account. When reviewers ask questions, we answer them with you.
Every account is registered in your organisation's name. You hold the keys; we work with access you can remove at any time. We cannot promise approval or timing, which rest with Apple and Google, but careful preparation removes the most common reasons for delay.
Photograph: illustrative generated image.
Hallmarks
Standards stamped on every delivery
Fortnightly builds
You install and use the app as it grows.
Accessible by design
Towards WCAG 2.2 AA, with gaps listed openly.
Minimal data
Only what the app needs, described honestly.
Your ownership
Code, accounts and keys belong to you.
Real devices
Older phones, larger text, slow networks.
Clear change
New ideas weighed openly before they displace others.
Loupe 03 · Permission planner
When should your app ask?
Tick the permissions your app needs. The planner suggests an order and the moment for each request, following the guidance Apple and Google publish: ask in context, explain why, and keep working if someone says no.
Questions people ask
Before you write
Do we need a finished idea?
No. Many conversations start with a frustration rather than a plan: "booking our classes is a mess" is a perfectly good opening. Part of our work is turning that into a clear, small first version.
Can you work with our existing app?
Often, yes. We begin with a short review of the code, the store listings and the design, then tell you plainly whether it is better to refine what exists or rebuild parts of it.
How do we see progress?
Every fortnight you install the latest build on your own phone and receive a short note describing what changed. You never have to take our word for it.
Who owns the result?
You do: the code repository, store accounts, domains and design files are in your name from the start.
Begin
Tell us about the moment your app should improve
We read every message during working hours, Monday to Friday, 09:00 to 18:00 UK time, and reply by email. Existing clients can reach care directly.