Locations · El Paso, TX
OlDevs builds bilingual English and Spanish products for El Paso companies in manufacturing, logistics, health care and defence. You get one accountable team, weekly working demos, and full ownership of everything we make.
Remote from Vancouver, on-site when useful Weekly working demos Reply within one business day
Illustrative product interface — not client data.
Yes. El Paso clients are served from the OlDevs studio in Vancouver, with video calls in your hours and travel to the city when a project benefits from being in the room.El Paso keeps Mountain Time, an hour ahead of Vancouver, which leaves the working day shared almost end to end. The work covers web development, web apps, Android and iOS apps, full-stack builds, AI development and performance marketing.
Key facts
Services
Seven services from one accountable team — delivered remotely in your working hours.
Built for Texas
The local rules and realities we design for from the first call.
The Texas Data Privacy and Security Act shapes how we set up consent, analytics and marketing tags on an El Paso site. We record what is collected and who receives it, so your advisors have a clear picture rather than guesswork.
ADA Title III litigation risk applies to public-facing sites across the United States, and the 2024 ADA Title II rule holds state and local government web content to WCAG 2.1 AA. Our builds target WCAG 2.2 AA, with screen reader checks in English and in Spanish.
Bilingual work is standard in El Paso, so it is standard in our builds. Language switching sits in the navigation, each language gets its own URLs and metadata, and Spanish copy is given the extra room it needs in the layout.
When records must stay in the country, United States hosting regions hold the application, its backups, its logs and its analytics. Where a system spans the border with Ciudad Juarez, we agree what crosses and what does not before we build it.
Sectors
Operations spanning El Paso and Ciudad Juarez run on paperwork, schedules and units that differ by side. We build systems that hold both realities honestly and report on them together, in English and in Spanish.
Freight and warehousing teams need screens that work on a handheld in a yard, not a polished desktop dashboard nobody opens. We design for gloves, glare and patchy signal, then integrate with whatever dispatch already uses.
Clinics and health systems need appointment flows, patient information and forms that read clearly in both languages and pass an accessibility check. We build to WCAG 2.2 AA and document every tag placed on the page.
Contact centres live or die on their internal tools. We build agent-facing applications, reporting and integrations with the phone and CRM systems already in place, keeping the interface fast enough to use all day.
Process
Discover
We start with a video call in your hours, mapping who the site serves on each side of the border and which parts have to exist in both English and Spanish.
Design
Layouts are drawn for both languages at once, because Spanish copy runs longer than English. You review the designs live and we adjust them while you are still on the call.
Build
Development runs in weekly cycles with a working demo each Friday, built against your real content rather than placeholder text nobody will ever read.
Launch
Before release we test forms, translations, tracking and consent behaviour, then publish and watch the first days of traffic together with your team.
Grow
Once live, we look at search demand in both languages, tune the pages carrying the load, and plan the next release around what the numbers actually show.
FAQ
There is not. The studio sits in Vancouver, British Columbia, and El Paso engagements run remotely, with visits to the city when a project genuinely needs someone on the floor or in front of a room. Nothing about ownership changes: your code, designs, accounts and IP belong to you.
Yes. Bilingual work is part of what we do, and we plan for it from the first wireframe rather than bolting a translation layer on later. That means language switching in the navigation, correct URLs and metadata per language, and forms, error messages and email templates written in both.
They can. We model the flow as it actually runs, with separate sites, currencies, units and approval steps wherever they differ, and one reporting view over the top. Where records need to stay in the United States, the hosting region, backups and logs are all placed there.
We set up consent, analytics and marketing tags so choices are recorded and honoured, and we give you a written list of what is collected, why, and which third parties receive it. Your legal advisors can then work from that documentation when judging your position under the TDPSA.
It does. ADA Title III litigation risk attaches to public-facing sites, and beyond the risk, an accessible site simply works for more customers. We build to WCAG 2.2 AA, check keyboard use and colour contrast, and test with a screen reader in both languages.
El Paso is on Mountain Time, one hour ahead of Vancouver, which leaves nearly the whole working day shared. We book calls in your hours, reply to every enquiry within one business day, and show a working demo each week, so you never wait long to see progress.
Let’s connect
We’ll reply within one business day, in your working hours, with next steps and a tailored quote — no obligation.