Solutions · Kiosk & Self-Service Software
A kiosk runs unattended, in public, all day. We build check in, ordering, ticketing and wayfinding software that stays locked to its task, reaches every user, keeps working when the network drops, and updates from a dashboard you control.
You own the code and IP Weekly demos Reply within one business day
Good morning
Your account at a glance
Balance
12,480
OlDevs is a full-stack technology studio in Vancouver, British Columbia that builds kiosk and self-service software: check in, ordering, ticketing, wayfinding and information terminals.Every build covers the whole picture, including a touch interface sized for real reach and lighting, kiosk mode and device lockdown, offline handling so a dropped connection does not stop a queue, and remote management for updates and device health. We work with the hardware and payment terminals you already have, or help you shortlist them before a line of code is written. When an off the shelf kiosk product already fits your workflow, we will say so.
Key facts
Kiosk and self-service systems
Self serve arrival for clinics, offices, events and service counters. Visitors identify themselves, confirm details, print a badge or take a number, and staff watch the queue update in real time on the screens they already use.
Menu and catalogue browsing, modifiers, upsells and order review, all built for thumbs and gloved hands. We integrate the payment terminal you choose so card data stays inside that device and never passes through your kiosk app.
Sell, collect and scan tickets, memberships and day passes at the door. Barcode and NFC reading, printed and wallet passes, group entries, and a sensible fallback for the moments when a scanner or a network link gives out.
Interactive maps, directories, schedules and self serve lookups for lobbies, campuses, malls and transit spaces. Content comes from a CMS your own team edits, so a moved office or a changed schedule never waits on a software release.
One app, one task, no way out. We configure single app modes, hide system UI and gestures, block navigation away from your screens, handle idle timeouts and session resets, and clear personal data between users so nothing carries over.
A dashboard for the whole fleet: push a new build, change content or configuration per site, watch device health and printer or paper status, and get alerted when a terminal goes quiet instead of hearing about it from a customer.
Process
Fit check
We map the journey a person takes at the terminal, the systems behind it and the constraints of the space. If an off the shelf product covers it, we say so early and help you compare, rather than quoting a build you do not need.
Flow and interface prototype
A clickable prototype at real kiosk dimensions, walked through with staff and tested by people who have never seen it. This is where reach, wording, target sizes and the number of taps to finish get settled, before code.
Working demo every week
One accountable team builds in weekly increments, and every week you get a working build to open and try. Integrations, payment terminal, printer and scanner behaviour land as running software, not as status reports.
Pilot on the real hardware
We install on the chosen device in the actual location: lighting, glare, network, mounting height and peripherals included. We run soak tests, power cuts and dropped connections, then fix what real use exposes.
Rollout and remote care
Staged deployment across sites with a way back to the previous version, attendant documentation and training, then remote updates, monitoring and support. You own the code, the accounts and the dashboard throughout.
How we work
People use a kiosk standing up, in a hurry, sometimes with a bag in one hand. Large targets, short steps, obvious progress, no hover states and no tiny close buttons. Every screen answers what happens next without anyone reading instructions.
We build to WCAG 2.2 AA and treat the physical device as part of the interface: controls within seated reach, readable type at kiosk viewing distance, audio and screen reader support, and flows that finish without fine motor precision or perfect eyesight.
Content, prices and configuration cache on the device. Orders, check ins and scans queue locally and sync when the link returns. Where an action truly needs the network, the screen says so plainly instead of hanging, and staff get a way to carry on.
Single app mode, hidden system UI, blocked gestures and external links, an attendant exit behind a code, automatic recovery after power loss, and a session reset that clears personal data between users so nothing lingers on a public screen.
Card entry, encryption and authorisation stay on the payment terminal hardware. Your kiosk app requests an amount and reads a result, which keeps the sensitive scope narrow. We confirm current requirements with your acquirer before designing the flow.
Fleet visibility is part of the build, not an afterthought: staged rollouts with a route back, per site configuration, remote reboot, and health reporting for connectivity, printers, scanners and paper so faults surface before a customer reports them.
Who it's for
Lobby check in, meeting room and visitor management, internal service points and information terminals across many sites, with single sign on, fleet visibility and IT policies your security team can actually approve.
Public counters, service centres and event registration, where accessibility, bilingual EN and FR interfaces, privacy and procurement documentation matter as much as the interface itself. Nothing here is legal advice on your obligations.
Ordering and self serve terminals rolled out across locations with shared code and per site configuration: local menus, hours and content, one management dashboard, and updates you can stage rather than send everywhere at once.
A first kiosk product taken from concept to something you can put in front of real users on real hardware, scoped so the pilot proves the idea before the fleet is ordered. You own the code, designs, accounts and IP.
Since 2014
Studio founded
WCAG 2.2 AA
Accessibility target on every build
1 business day
Reply to every enquiry
FAQ
Often buying wins, and we will tell you when. If your workflow matches a mainstream product for restaurant ordering, visitor sign in or ticketing, buying is usually faster to get running and simpler to maintain. Building makes sense when the workflow is unusual, when the kiosk must speak to systems no product supports, when the interface has to carry your brand precisely, or when licence terms would lock up data you need.
We help you shortlist rather than resell. The choices that matter are screen size and mounting height, indoor or outdoor rating, glare and glove performance on the touch layer, the peripherals you actually need such as printer, scanner, camera or card reader, and how the device will be powered, locked and serviced. We then build against the exact model you pick and test on it, not on a desk tablet.
Card data should never touch your kiosk app. We integrate a payment terminal that handles entry, encryption and authorisation on its own hardware, and your application only asks for an amount and receives a result. That keeps the sensitive scope with the terminal and its provider. Requirements change over time, so we confirm the current rules with your acquirer before we design the flow.
The kiosk keeps working. We design an offline mode up front: content and prices cached locally, transactions and check ins queued on the device, clear messaging about what is available while the link is down, and a sync that reconciles cleanly when it returns. Some actions genuinely need the network, and for those we say so on screen rather than failing silently or spinning forever.
We build to WCAG 2.2 AA, and physical reach matters as much as code. That means every control reachable from a seated position, generous target sizes, real contrast under bright lobby lighting, no colour only cues, audio output with a headphone jack where it fits, and screen reader support on the platform the kiosk runs. We test with a screen reader on the real device.
Kiosk mode is the foundation, and it is more than a setting. We use the single app lockdown each platform provides, then close the gaps: disabled system gestures and status bars, blocked external links and downloads, an attendant exit behind a code, automatic restart after power loss, and an idle timeout that resets the session and wipes anything the last person entered.
Remotely, on your schedule. Builds and content roll out from a management dashboard, usually to a pilot group first, with staged deployment and a way back to the previous version. You choose the window so updates land overnight or between shifts. The same dashboard reports version, uptime, connectivity and peripheral status per device, so you know a rollout finished everywhere.
Let’s connect
Tell us what you’re building. We’ll reply within one business day with next steps and a tailored quote — no obligation.