Mobile app development for iOS and Android, from one codebase

We build iOS and Android apps with React Native and Expo, from one TypeScript codebase. That's how we build the BrokLeads app, now in early access. It uses the same account, leads and WhatsApp chats as the web app, and agents get a push alert when a lead is assigned to them.

Two apps, twice the bugs

Building two separate native apps doubles the cost and the bugs. Putting a web page in a wrapper feels cheap to users. And apps get rejected from the stores for reasons nobody planned for.

React Native with Expo avoids the first two, because one codebase compiles to real native apps. We plan for the third from the start: privacy details, sign-in rules, in-app account deletion and review notes are ready before the first submission.

What we deliver

  • Customer apps

    Ordering, booking, account and loyalty apps, with sign-in and push notifications.

  • Field and staff apps

    For people who work away from a desk, like the sales agents who use BrokLeads on their phones.

  • Companion apps

    A mobile app for your existing web product, sharing its API and business rules.

  • Store release and updates

    Listings, test builds and submissions to the App Store and Google Play, under your own developer accounts.

How we build it

Every mobile app development project runs through our delivery process. These are the steps that are specific to this work. Teal steps are thinking, graphite steps are building, and orange ones keep it running.

  1. Key journeys

    The three or four things people must be able to do, mapped first.

  2. Prototype on a phone

    Tap through it on your own device before it's built.

  3. Build on a shared API

    One TypeScript codebase for iOS and Android.

  4. Device testing

    Test builds through TestFlight and Google Play testing tracks.

  5. Store release

    Submission, review notes, then updates as you learn.

What you get

  • iOS and Android builds from one codebase
  • Push notifications
  • Sign-in tokens kept in the phone's secure storage
  • Test builds through TestFlight and Google Play testing tracks
  • Store listings, privacy details and review notes
  • Source code and build set-up (Expo EAS) in your accounts

Typical timelines

Typical timelines for mobile app development work
ScopeRange
App for an existing web product6–12 weeks
New app, first release10–16 weeks
First store reviewallow 1–2 weeks

Planning ranges, not quotes. Your scope sets the real timeline, which we confirm in writing after discovery. See how engagements are priced.

Tools we use

  • React Native
  • Expo and EAS
  • TypeScript
  • Expo Notifications
  • TanStack Query
  • NativeWind

See it in our work

  • BrokLeads mobile app

    React Native and Expo, in early access for Android and iOS, with push alerts and the same API as the web app.

Read next

Questions about mobile app development

Why React Native instead of separate Swift and Kotlin apps?

For most business apps, one TypeScript codebase for both platforms means lower cost and faster changes, and it can share code with a React web app. If your app needs deep platform features, we'll say so during discovery.

Do you publish to the App Store and Google Play?

Yes. We prepare the listings, privacy details and review notes, and submit under your developer accounts, so the apps belong to you. For accounts in a company's name, Apple and Google both ask for a D-U-N-S number, which can take a while to get, so it's worth starting early.

Can the app work with our existing system?

Yes, through an API. If you don't have one, we build it. In BrokLeads, the web app and the mobile app are equal clients of the same API.

Can small fixes ship without a store release?

Expo supports over-the-air updates for JavaScript changes. Changes to native features still go through store review.

Tell us about your mobile app development project

A few lines is enough. We'll ask the right questions on the call.

  1. We reply within one working day

    By email or WhatsApp, whichever you prefer.

  2. A short call

    To understand the goal, the people who'll use it and any deadline.

  3. A written scope and estimate

    Before any work starts, so you know what you're agreeing to.

So we can reply on WhatsApp if you prefer.

What are you building, who is it for, and is there a deadline?

We reply within one working day. By sending this you agree that Teknoesis (Lahore, Pakistan) may contact you about your request and store your details as described in our Privacy Policy. We use analytics tools; see Your Privacy Choices in the footer.