Skip to content
cirlume.
Menu

Mobile / 3 technologies

Apps that work in a pocket, on a bad connection.

Mobile apps run on devices you don’t control, often without signal, and every release goes through app store review. We usually build one cross-platform codebase with React Native and Expo. We go fully native when an app depends on platform features, or when a team already has native code.

Start a project

What we use

Mobile technologies we know well.

Why us

What we bring to mobile work.

  • Three platforms, one app

    SimRhythm runs on iOS and iPad, Android and the web from a single Expo and React Native codebase.

  • Apps for different roles

    SoulCare has a carer app and a family app on iOS and Android, each built for the job its users do.

  • Honest about native

    When a feature needs Swift or Kotlin, or a cross-platform tool adds more cost than it saves, we say so.

What you get

What a well-chosen stack gives you.

  • One codebase, two stores

    iOS and Android from shared code, with platform-specific parts only where they matter.

  • Offline by design

    Local storage and sync, so people can keep working without a connection.

  • Fixes without a full release

    Over-the-air updates for JavaScript changes, within each store’s rules.

  • Store releases handled

    Signing, listings, review and staged rollouts managed as part of the work.

Where AI fits

AI in mobile work.

  • On-device models

    Apple’s Foundation Models framework and Android’s Gemini Nano APIs run smaller models on the phone, for features that must work offline or keep data local.

    AI workflow automation ↗

  • Reading photos of documents

    Capture a form or label with the camera and pull out the fields, with the image kept for checking.

    Document data extraction ↗

Where it stops: On-device models are only on newer phones and are less capable than cloud models, so features need a fallback.

Choosing between them

Which one, and when.

React Native with Expo for most products, especially alongside a React web app. Flutter when a team already writes Dart or wants identical rendering on every device. Swift and Kotlin for apps built around deep platform features.

What’s changing

Shifts to plan for.

Dates that affect mobile technologies, checked against the official sources.

  1. August 2026

    Google Play targets Android 16

    New apps and updates for phones and tablets must target API level 36. Extensions can be requested until 1 November 2026.

  2. April 2026

    App Store requires the iOS 26 SDK

    Since 28 April 2026, uploads must be built with Xcode 26. Apps can still support older iOS versions; only the build tools changed.

  3. October 2025

    React Native drops the old architecture

    React Native 0.82 runs only on the New Architecture, so libraries that never moved over block upgrades.

Common questions

Mobile questions.

Will a cross-platform app feel native?

React Native draws real platform components, so lists, inputs and navigation behave the way people expect. We write native modules where a feature needs them.

Do you publish to the app stores for us?

Yes, under your own developer accounts. We prepare builds, listings and review notes, and stay involved until each release is approved.