Skip to content
ANB Codes

Websites and apps

iPhone and Android apps

We build iPhone and Android apps from a single codebase, so both stay in step and cost less to maintain. We handle store listings, reviews and release management for you.

Overview

Apps for iPhone and Android, published on the App Store and Google Play.

Customers increasingly expect to book, order and track from their phone, and a slow or crash-prone app reflects on the whole business. Building separately for iPhone and Android doubles the work and lets the two versions drift apart. This service delivers both from a single codebase, together with the server and admin panel the app depends on.

Design comes first: the key screens, and an honest look at which phone features are genuinely needed, such as camera, maps, payments or offline use. Test builds reach your phones every two weeks, so feedback arrives early. Store rules are followed from the start, and we prepare listings, screenshots and privacy forms, then answer reviewer questions until both stores approve.

Your apps are published under developer accounts in your company's name, and the source code passes to you once paid. A patient app and a rider app for a healthcare platform were built and released this way. After release, a care plan covers new iOS and Android versions, certificates, store policy changes and the next set of features.

What you receive
App Store and Google Play releases · Admin panel · Source code · Store accounts
Typical technology
React Native · Expo · Swift · Kotlin · Firebase

Who it's for

Is this right for you?

If people only need the app now and then, an app that opens in the browser is often quicker and simpler.

  • A business that needs both iPhone and Android on one budget
  • A company whose current app crashes or collects poor reviews
  • A service whose customers expect to book, order or track from their phone

Scope

What goes into it

Every engagement is scoped to your goal. These are the parts most projects include.

  • App designiPhone, iPad and Android layouts.
  • Native featuresPush notifications, camera, maps, payments and offline use.
  • Back end and adminThe server, database and admin panel behind the app.
  • Store submissionListings, screenshots, privacy forms and review.
  • Analytics and crash reportingKnow how the app is used and fix issues fast.
  • Over-the-air updatesShip fixes without waiting for store review, where allowed.

Timeline

How a typical project runs

Usual length: usually 10 to 20 weeks, plus store review time. Your written scope gives the exact plan.

  1. 01Weeks 1–3

    App screens and phone features

    We design the key screens and agree the phone features needed, such as camera, maps, payments or offline use.

  2. 02Weeks 3–14

    App and server sprints

    We build the app and the server behind it, sending test builds to your phones every two weeks.

  3. 03Weeks 14–17

    Store listings and beta testers

    We prepare screenshots, privacy forms and store text while a wider group tests the app.

  4. 04Weeks 17–20

    Store review and release

    We submit under your developer accounts, answer reviewer questions and release when both stores approve.

One-time project

A fixed quote for an agreed scope, paid in milestones. You own the code and accounts once it's paid.

Monthly care plan

A monthly subscription that keeps your software secure, monitored and improving, with response times in writing.

Industries we have built this for

Getting started

What happens after you get in touch

Discuss your project
  1. 01Tell us the problemA short form or a call. A senior lead replies within one working day.
  2. 02One callWe sign an NDA first if you need one, then go through your goals, users and current systems.
  3. 03Written scope and fixed quoteWithin 48 hours of the call, with milestones and a timeline.
  4. 04Build in milestonesYou see working software at every milestone, and you own what we build.

Questions

Before you ask

What changes the size of the job

  • How many screens and user types the app has
  • Phone features like payments, maps, offline use or Bluetooth devices
  • Whether the server and admin panel already exist or are built new
Do we own the app store accounts?

Yes. Apps are published under your own developer accounts.

What if Apple or Google reject the app?

We read the reason, fix it and resubmit, which usually takes days rather than weeks. We follow the store rules from the start to keep rejections rare.

Do we need developer accounts of our own?

Yes. You need Apple and Google developer accounts in your company's name, and we guide you through opening them.

How is this priced?

As a one-time project with a fixed quote, agreed after a short call and paid in milestones. After launch you can add a monthly care plan for hosting, updates and support.

Previous work

Projects in this area

The first two projects used this directly; the others are related work from websites and apps.

Tell us what you need built.

Share the problem in a few lines. After one call you'll get a written scope and a fixed quote within 48 hours.