Mobile apps

Mobile apps for iPhone and Android, built and looked after.

We design and build your app, the server and admin panel behind it, launch it on the App Store and Google Play in your company's name, and keep it updated for every new iOS and Android release.

9:41
Mobile apps

What we build for your app

One team for the screens, the code, the server and the stores, so nothing falls between two vendors.

iOS apps

Native iPhone and iPad apps written in Swift, following Apple's design guidelines so they feel at home on the device and pass App Store review.

Android apps

Native Android apps in Kotlin that run well on the wide range of phones your customers carry, from budget handsets to flagships.

Cross-platform apps

One codebase in Flutter or React Native that ships to both stores. Usually the faster route when the app is mostly screens, forms and data.

App architecture

The API, database, logins, push notifications and payments behind the app, planned before the first screen so the app can grow without a rewrite.

Backend and admin panel

A web admin panel where your team manages users, orders, content and notifications without calling a developer.

App care

Bug fixes, new features, crash reports and updates for each new iOS and Android version, so the app keeps working and keeps passing review.

9:41
How your app is builtApp architecture
Your appiOS and AndroidAPILogins, data, rules
DatabaseCloudBackups
PushPaymentsAnalytics
Architecture

How your app is put together

The phone is only the front of the app. What sits behind it decides whether the app stays fast, safe and easy to change.

  • Your app talks to one API. Logins, rules and data checks live on the server, not in the phone, so they cannot be bypassed.
  • A database designed around your records: customers, orders, bookings, whatever the app is for.
  • Push notifications through Apple's and Google's own services.
  • Payments through a gateway such as Razorpay for goods and services. Digital content sold inside the app usually has to use the store's own billing.
  • Analytics and crash reports, so we see problems before your reviews do.

Native or cross-platform?

Native iOS and AndroidCross-platform
Best whenThe app leans on the camera, Bluetooth, maps or heavy animationThe app is mostly screens, forms, lists and payments
CodebasesTwo: Swift for iOS, Kotlin for AndroidOne, in Flutter or React Native
Store launchThe same for both: accounts, testing, listings and reviewThe same for both: accounts, testing, listings and review
How we work

How we build your app

Short rounds, test builds on your own phone, and no surprises at the store.

  1. Scope on a callWe talk through who uses the app, what they need to do in it and what it must connect to. You get a written scope with the screens and features.
  2. Design the screensClickable designs for the key flows, so you can tap through the app before any code is written.
  3. Build in short roundsWe build the app and the server together and share test builds as we go, through TestFlight on iPhone and a testing track on Google Play.
  4. Launch on both storesStore listings, privacy answers and review, with every developer account in your company's name.
  5. Look after itFixes, new features and a check against each new iOS and Android version, so the app keeps working on new phones.
Integrations

What your app can connect to

Connections we set up as part of the build. See every integration.

WhatsApp

Order and booking updates on WhatsApp, next to the app.

Razorpay

Payments for goods and services inside the app.

Google Analytics

See which screens people use and where they drop off.

Google Calendar

Bookings made in the app land on your calendar.

Email

Sign-in, receipt and password emails.

Webhooks and API

An API and webhooks to talk to your own systems.

FAQ

Questions we get asked

Should we build native or cross-platform?

It depends on what the app does. If it leans on the camera, Bluetooth, maps or heavy animation, native Swift and Kotlin apps usually give the best result. If it is mostly screens, forms, lists and payments, one cross-platform codebase in Flutter or React Native ships to both stores faster and is simpler to maintain. We recommend one after the scoping call and explain why.

Do you build the backend and admin panel too?

Yes. Most apps need a server, a database and a place for your team to manage users, orders and content. We build all of it together, so the app and the server are designed for each other.

Whose name are the App Store and Google Play accounts in?

Yours. We set up the Apple Developer Program and Google Play Console in your company's name, with your D-U-N-S number, and work inside them as your developer. The app, the listings and the code stay yours.

Can you take over an app someone else built?

Often, yes. We first review the code, the server and the store accounts, then tell you plainly what is in good shape and what needs fixing before we change anything.

What happens after the app is live?

Apple and Google release new versions of iOS and Android every year and update their store rules. With app care we fix bugs, ship new features, watch crash reports and update the app so it keeps working on new phones and keeps passing review.

Can the app take payments?

Yes. For physical goods and services, such as orders, bookings and fees, the app can take payments through a gateway like Razorpay. Digital content or subscriptions used inside the app usually have to go through Apple's in-app purchase and Google Play billing, and we plan for that from the start.

How do we start?

Book a call or message us on WhatsApp. Tell us what the app is for and who will use it, and we will come back with a written scope.

Tell us about your app

Book a call or message us on WhatsApp with what the app should do and who will use it. One team designs it, builds it, launches it and looks after it. You can also write to support@duedoor.com.

What we buildApps, software, business systems and cloud, by one team you can call.
Chat on WhatsApp