Skip to content

Mobile application development

Mobile apps in .NET MAUI, Xamarin and Flutter — built with a bilingual team.

iOS and Android apps for enterprise and consumer products, from new builds to Xamarin → .NET MAUI upgrades. Our engineers work with your team in Japanese and English, with daily updates and Japanese QA sign-off.

  • 30 JLPT-certified engineers
  • iOS & Android from one codebase
  • Since 2000 in software delivery
One codebase iOS · Android
Shared logic
native reach
Request a callback
See mobile projects

Platforms

Pick the stack that fits the app

We recommend a stack during planning and document the decision in the architecture document, before development starts.

  • Microsoft · C#

    .NET MAUI

    Microsoft’s current cross-platform framework. One C# codebase for iOS and Android that shares business logic with your .NET backend.

  • Maintain · upgrade

    Xamarin

    Existing Xamarin apps kept running, and upgraded to .NET MAUI. We are running that upgrade today on a long-term client app.

  • Google · Dart

    Flutter

    Google’s cross-platform toolkit, for apps that need one custom interface on both iOS and Android.

  • Hybrid web-mobile

    Monaca / Cordova

    Web technology packaged as a mobile app — the stack behind our hospital questionnaire app for a Japanese client.

  • Low-code

    PowerApps

    Microsoft’s low-code platform for internal and companion apps, such as a parent download portal we built for a childcare client.

Backends and sign-in: Azure Functions, .NET and VB.NET web services, and OAuth.

Xamarin → .NET MAUI

Still on Xamarin? Plan the move to .NET MAUI.

Microsoft ended support for Xamarin on 1 May 2024, so Xamarin apps no longer get updates for new iOS and Android versions. We are upgrading a Xamarin app to .NET MAUI right now for a client we have worked with for more than three years.

  1. Map what must keep working

    Screens, saved data, sync, sign-in and every integration users rely on — including unusual workflows, not just the main screens.

  2. Upgrade in bounded releases

    Start with one workflow that has clear acceptance criteria, so you can evaluate a working build before the scope grows.

  3. Verify on real devices, then sign off

    Touch, text size and orientation are tested on the devices your users carry. Nothing is released without your UAT sign-off.

Mobile · delivered projects

Apps that run where the work happens.

Clients are described by type and country, matching how the work is documented.

01

Mobile · North American client

Automated Electrical Design System

Stack

Xamarin/MAUI + VB.NET web service — pinch-zoom blueprint storage with real-time sync. Xamarin → .NET MAUI upgrade in progress.

Duration

3+ years, ongoing.

Xamarin .NET MAUI VB.NET

02

Mobile · Japan client

Smart Room Meeting Management System

Stack

Xamarin + iOS iPads + OAuth — multilingual room booking, asset management and real-time availability across the organisation.

Scale

24 man-months.

Xamarin iOS OAuth

03

Mobile · Japan client

Aichimonshin — Patient Records System

Stack

Monaca + Azure Functions + Android — dynamic health questionnaires for hospital staff workflows.

Duration

4 months.

Monaca Azure Functions Android

Japan bilingual delivery

Work with us in Japanese, from kickoff to release.

30 JLPT-certified engineers (N1–N5), 3 bilingual project managers and 2 bilingual QA managers — built through our own language and technical training programme.

How we work
  • A daily team stand-up at 10:00 IST, with progress shared in Japanese
  • End-of-day status and progress reports
  • Detailed weekly reports in Japanese and English
  • UI/UX reviews aligned to Japanese design sensibility
  • Japanese QA sign-off before every release

FAQ

Questions we hear first

Can you upgrade our Xamarin app to .NET MAUI?

Yes. We are doing it now for a long-term client. We start by mapping what the app must keep doing, then upgrade in bounded releases that you test and sign off.

Should we choose .NET MAUI or Flutter?

.NET MAUI suits teams whose backend and skills are already .NET and C#. Flutter suits apps that need one custom interface on both platforms. We recommend one during planning and record the reasoning in the architecture document.

Can we work with your team in Japanese?

Yes. Status reports, documentation and QA sign-off can all run in Japanese, with weekly reports in both Japanese and English.

How will we see progress?

You get an end-of-day status every day and a detailed report every week. Every change goes through a reviewed pull request, and you sign off each release after user acceptance testing.

Do you build the backend too?

Yes — for example Azure Functions or .NET web services behind the app, with OAuth sign-in where needed.