Skip to content

Locations · Detroit, MI

Digital products for Detroit, built to last.

Web, mobile, AI and marketing for Detroit companies in automotive, manufacturing, health care and finance. One accountable team in Vancouver, working your Eastern hours by video, with on-site visits when the work calls for it.

Remote from Vancouver, on-site when useful Weekly working demos Reply within one business day

build-orchestrator

main

src/

queue.ts

pool.ts

retry.ts

types.ts

index.ts

export interface BuildJob {

repo: string;

region: "ca-west-1";

}

export async function queue(

job: BuildJob,

): Promise<Run> {

return await pool.add(job);

212

Tests passed

0

Type errors

1.4s

Build time

Watching src/ — optimised rebuild on save

Detroit, in short

Yes. OlDevs works with Detroit businesses remotely from our Vancouver studio, with on-site visits when a project needs them.Detroit is three hours ahead of us, so your afternoon lines up with our morning and we schedule calls and demos inside your working day. We deliver web apps, Android and iOS apps, AI development and performance marketing, and you own all the code and accounts.

Key facts

01Location
Detroit, Michigan, United States
02Time zone
Eastern Time, 3 hours ahead of our studio
03Working hours overlap
Your 12:00–17:30 = our 9:00–14:30
04Privacy law
No comprehensive Michigan consumer-privacy statute as of our last review; federal sector rules apply (HIPAA, COPPA, GLBA, CAN-SPAM, FTC Act)
05Accessibility
ADA; WCAG 2.1 AA for state and local government under the 2024 Title II rule; we build to WCAG 2.2 AA
06Languages
English; Arabic and Spanish-speaking communities

Built for Michigan

What Detroit projects need us to get right.

The local rules and realities we design for from the first call.

01

Privacy under federal sector rules

Michigan has no comprehensive consumer-privacy statute as of our last review, so a Detroit product is bound by federal sector law: HIPAA for health data, COPPA for children, GLBA for finance, CAN-SPAM for email and the FTC Act. We map which of these touch your data before designing the schema.

HIPAA · GLBA · FTC Act

02

Accessibility to WCAG 2.2 AA

Public-facing Detroit sites carry ADA Title III litigation risk, and the 2024 Title II rule holds Michigan state and local government content to WCAG 2.1 AA, with April 2026 and April 2027 deadlines by population. Section 508 governs federal work. We build to WCAG 2.2 AA, which covers all three.

ADA · WCAG 2.2 AA · Section 508

03

English, Arabic and Spanish

English is the working language, and Detroit's Arabic and Spanish-speaking communities mean many local services want content in those languages too. We build language switching, right-to-left layouts for Arabic and translation workflows in from the start rather than bolting them on.

Arabic · Spanish · RTL layouts

04

US hosting and data residency

For Detroit clients we host on US regions, typically AWS us-east-2 in Ohio or the nearest Azure and Google Cloud regions, so data stays in the United States and latency stays low. Companies trading with Ontario can add a Canadian region for cross-border data if their contracts require it.

US hosting · AWS us-east-2 · Data residency

Sectors

Who we work with in Detroit.

Automotive and mobility

Suppliers, mobility start-ups and dealer groups need connected-vehicle dashboards, fleet and telematics apps, and computer vision for inspection lines. We build the front ends and the data pipelines behind them, then instrument everything so the numbers hold.

Advanced manufacturing

Plants want production tracking, quality-control tooling and predictive maintenance models that run on real sensor data. We start with the workflow on the floor, build the web app operators will use, and add machine learning only where it earns its keep.

Health care

Hospitals, clinics and health-tech companies need patient portals, scheduling apps and integrations that respect HIPAA. We design the data model around consent and access control, then add AI such as intake summarisation or triage support where clinicians ask.

Financial services

Banks, credit unions and lenders ask for online account tools, loan-origination web apps and analytics that satisfy GLBA. We build with audit trails and role-based access from day one and pair the product with marketing that brings in qualified applicants.

Process

Working with OlDevs from Detroit.

  1. Discover

    We kick off by video in your Eastern hours, usually mid-afternoon Detroit time, to map goals, users, integrations and constraints. You get a written scope and a plan before any code is written.

  2. Design

    Wireframes and clickable prototypes are reviewed on shared calls each week. We test the flows with your team and, where useful, with Detroit users, so the design settles before development starts.

  3. Build

    A working demo lands every week and you have staging access throughout, so you can click through real features between calls. One accountable team handles front end, back end, mobile and AI.

  4. Launch

    We schedule go-live inside your working day, watch the first hours together and hand over documentation, credentials and the repository. You own all the code, designs and accounts.

  5. Grow

    After launch we keep improving the product with analytics, CRO and paid or organic campaigns as you need them. We visit Detroit on site when a workshop or rollout calls for it.

FAQ

Detroit — questions we hear first.

No. OlDevs is a Vancouver studio and we serve Detroit remotely. Video calls run in your Eastern hours, every project has a weekly demo you can watch live or on recording, and when a discovery workshop or launch benefits from being in the room, we travel to Detroit for it.

Yes. Detroit is three hours ahead of Vancouver, so your afternoon from about noon to 5:30 pm matches our 9:00 am to 2:30 pm. We book kickoffs, reviews and demos in that window and answer messages sent in your morning by the start of ours. Every enquiry gets a reply within one business day.

Michigan has no comprehensive consumer-privacy statute as of our last review, so we work from the federal sector rules that apply to your data: HIPAA for health information, COPPA for children, GLBA for financial services, CAN-SPAM for email and the FTC Act for fair practice. We confirm the exact obligations with your counsel during discovery and build controls to match.

Yes. We deploy Detroit projects to US cloud regions on AWS, Azure or Google Cloud, with your organisation holding the account and the billing relationship. If your work with Ontario partners requires a Canadian copy of certain data, we can add a Canadian region alongside it.

Web app development, computer vision and predictive analytics for automotive and manufacturing, patient-facing mobile apps for health care, and performance marketing for financial services and technology companies. Full-stack builds that combine a web app, a mobile app and an AI feature are common.

Request a quote through the form on this page and tell us what you are trying to build or fix. We reply within one business day, set a video call in your Eastern hours, and follow up with a written scope and quote. There is no obligation at that stage.

Still have a question? Ask us when you request a quote

Let’s connect

Tell us about your Detroit project.

We’ll reply within one business day, in your working hours, with next steps and a tailored quote — no obligation.

We’ll only use your details to prepare your quote. No lists, no spam.

Call us Request a quote