BookWell
Appointment Booking App
BookWell is a booking product held to one standard: choosing a time must take less effort than calling the clinic — and the appointment it books must actually be kept.
Designed & developed by Entrovix
- Year
- 2025
- Discipline
- Consumer MobileUX/UI DesignEngineering
- Services
- Product StrategyMobile UX/UI DesignMobile EngineeringNotification Design
- Built with
- React NativeTypeScriptNode.jsPostgreSQLTwilio
The Challenge
Losing to the telephone
Most clinic booking flows lose to the telephone. A receptionist answers in seconds, knows what is actually free, and confirms on the spot — while the app asks for an account, presents a calendar that is really an enquiry form, and replies a day later to say the slot was never available.
The brief set the bar exactly there: if choosing a time takes longer than calling, or the calendar shows anything other than the truth, the product has no reason to exist.
The Approach
How we worked
The calendar is the diary
Every slot on screen is a slot the practice can honour. If the grid shows a time, tapping it books it — there is no request pending behind a hopeful interface.
Value before identity
Practitioners, days and times are all browsable without an account. Details are asked for once, at confirmation, when giving them buys something.
The reminder is the product
A booking kept is the job the app exists to do, so the reminder is created by the booking itself rather than offered afterwards as a setting.
One thumb, within reach
Selection and confirmation sit within thumb reach of each other, and no step in the flow demands a second hand or a second screen.
The Solution
A calendar that tells the truth
The booking screen holds the whole decision. The practitioner sits at the top — name and specialism — the week runs as a strip beneath, and the chosen day's six slots fill a grid below that, every one of them live availability. Picking a slot lights the confirm bar at the foot of the screen, and the tap that follows is the booking.
Confirmation answers the question that decides whether the product worked: will the appointment be kept? The card that floats up says “Booked, reminder set” as a single fact, because the reminder was scheduled by the same action as the booking. The clinic card keeps who and where in view, so nothing has to be looked up on the way out the door.
Inside the product
What it actually does
Every Screen
One product, whatever it is opened on
The phone layout is not the desktop one squeezed down. Density, hit areas and reading order are decided per screen, and the interface keeps its meaning at both ends.
Capability
What we brought to BookWell
The same services are available on their own — each one links to what it involves, how it runs and what you get.
Built with
- React Native
- TypeScript
- Node.js
- PostgreSQL
- Twilio
Disciplines
Consumer Mobile · UX/UI Design · Engineering
The Outcome
What it settled
- Every slot shown is a slot the practice can honour
- Browsing asks for no account; identity arrives at confirmation
- The reminder is created by the booking, not offered after it
- The whole flow fits one screen and one thumb
That was some of our work
Now let’s talk about yours.
Tell us what you’re building. You’ll get a written plan, a clear proposal, and a team that shows its work every week.