Locations · Tokyo, TYO
OlDevs is a full-stack studio in Vancouver working with organisations across Tokyo. Mobile apps, web applications, AI development and performance marketing, delivered by one accountable team that shows a working demo every week.
Remote from Vancouver, on-site when useful Weekly working demos Reply within one business day
Attribution · this quarter
GA4 · server-side312
Booked calls
3.1x
ROAS
−31%
CPL
Yes. OlDevs works with Tokyo organisations remotely from the Vancouver studio, travelling to Japan when a project warrants time on the ground.Tokyo is sixteen hours ahead of Vancouver, so there is no shared business day. Your morning is our late afternoon of the day before, and that is where calls sit. The services on offer are iOS and Android development, web apps, AI development and performance marketing.
Key facts
Services
Seven services from one accountable team — delivered remotely in your working hours.
Built for Tokyo Metropolis
The local rules and realities we design for from the first call.
Projects for Tokyo are shaped by the Act on the Protection of Personal Information, overseen by the Personal Information Protection Commission. We keep collection minimal, make purposes explicit in the interface, and document retention and deletion so your compliance team can review it.
Japanese public bodies follow JIS X 8341-3 guidance, and WCAG 2.2 AA is our working standard on every build. Keyboard operation, focus visibility, contrast and labelling are tested during development, including Japanese text at the sizes people actually read.
Japanese interfaces need line breaking, vertical rhythm and font stacks that respect kanji, kana and mixed Latin text. We design layouts that hold in both Japanese and the English used for international business, rather than stretching a Latin design over Japanese copy.
Applications, databases, backups and logs can run in Japanese cloud regions, which keeps latency low for Tokyo users and keeps data in country when that is your preference. We agree the region up front, and record which service stores which data.
Sectors
Electronics companies need product sites, support portals and companion apps that keep pace with hardware release cycles. We build systems that handle large catalogues, firmware documentation and multiple markets without a rebuild each year.
Head office teams coordinate dealers, suppliers and regional sites, usually across several systems. We build internal web applications and dashboards that consolidate that view, with permissions granular enough for a large organisation.
Games and entertainment brands need campaign sites, community features and mobile apps that survive a launch day surge. We build for that spike, instrument it properly, and keep the release process calm enough to ship updates often.
Robotics companies collect a great deal of machine data and need interfaces that make it legible. We build web dashboards, monitoring tools and AI features around your telemetry, designed for engineers first and executives second.
Process
Discover
We meet in your morning, which is our late afternoon the day before, to agree goals, users and constraints. The output is a written plan in English, and in Japanese where your stakeholders need it, before any build starts.
Design
Prototypes go up at the close of our day, so they are waiting when Tokyo opens. Comments left through your day are picked up when our day starts, and answers are back before you return to your desk.
Build
Weekly cycles, each ending in a working demo on a staging link with a short recorded walkthrough. That recording matters here: your team can review at nine in the morning without waiting for us.
Launch
Deployment is timed for Tokyo, usually a quiet hour that still falls inside our shared window, with checks on accessibility, performance, Japanese rendering and analytics beforehand, and monitoring while traffic settles.
Grow
After launch we keep measuring and improving: analytics and CRO, search and content, paid channels and email, reported plainly. Accounts, code and designs stay in your name the whole way.
Nearby
FAQ
No. Our studio is in Vancouver, British Columbia, and has been since 2014. Tokyo clients are served remotely, with calls scheduled in your morning, written and recorded updates through the rest of your day, and a working demo every week. We travel to Japan when a project genuinely needs us there.
By designing the engagement around it rather than pretending it is small. Tokyo mornings meet Vancouver late afternoons of the day before, so live calls go there. Everything else is asynchronous: recorded demos, written decisions and a shared board, so progress continues while one side sleeps. Enquiries get an answer within one business day.
Yes. We can deploy applications, databases, file storage, backups and logs to Japanese cloud regions, which also cuts latency for users in Tokyo. The region is agreed before development starts, and we document which third party services touch personal information so your review has something concrete to check.
Yes, with the right partners. We build the product to handle Japanese properly, covering typography, line breaking, input methods, sorting and forms, and work with your team or a translation partner on the wording itself. English versions for international business are planned in the same content model.
We build to WCAG 2.2 AA as our working standard, and we are familiar with the JIS X 8341-3 guidance that Japanese public bodies follow. Testing covers keyboard operation, focus visibility, contrast and labelling in Japanese as well as English. Questions about your own obligations belong with your legal advisers.
Send an outline of the project and you will have a reply within one business day, which usually means it is waiting when you next open your inbox. We then book a discovery call in your morning, agree scope in writing, and you request a quote from there. Clients own all code, designs and accounts.
Let’s connect
We’ll reply within one business day, in your working hours, with next steps and a tailored quote — no obligation.