Skip to content
2good.dev

What we build

Mobile apps

Android and iOS apps for customers, dealers and field teams. Cross platform and native apps with the backend they need, through to store submission. Built to a signed specification and paid for after you accept the work.

Talk to usEstimate the hours
A developer coding on a laptop while checking a phone

The situation

Your customers and staff live on their phones

A dealer in a small town rarely logs in to a desktop portal, though they will happily open an app to check a price list and place a repeat order. A field engineer needs the job details offline in a basement plant room. A clinic patient wants to book from a phone. The trouble is that apps carry costs a website does not: two app stores, phone models of every age, notifications, offline data and updates that users must install. A good mobile project decides early what really needs an app and keeps the rest on the web.

2goodDealer ordersAK

Dealer orders

New2

  • Order 2291, 40 pcs
  • Order 2292, 12 pcs

Packed1

  • Order 2287

Dispatched2

  • Order 2280, Indore
  • Order 2283, Jaipur
Representative screen with sample data. Client screens stay private.

What we build

Mobile apps, in practice.

  1. Cross platform apps

    One codebase in React Native or Flutter for Android and iOS, which suits most business apps and keeps maintenance costs down.

  2. Native Android and iOS

    Kotlin and Swift where the app needs close access to the device, such as heavy camera use, Bluetooth hardware or background tracking.

  3. Dealer and sales apps

    Catalogues, price lists, order taking, outstanding balances and scheme details for dealers and sales staff on the road.

  4. Field service apps

    Job lists, checklists, photos, signatures and offline use for technicians, with everything syncing back when the signal returns.

  5. App backends and APIs

    The server, database, login, notifications and admin panel behind the app, shared with your web app where that makes sense.

  6. Store release and updates

    Play Store and App Store submission, review responses, and planned updates as Android and iOS versions change.

Typical sizes

Roughly how many hours.

Planning sizes only. The real number comes from a signed scope after the first conversation.

  1. 150TO180HOURS

    A simple companion app

    A few screens on top of an existing backend, such as order status or a catalogue. Roughly INR 29,850 to INR 35,820 before tax at INR 199 an hour.

  2. 200TO450HOURS

    A business app with its own backend

    Login, the core workflow, notifications, an admin panel and store release on both platforms. Roughly INR 39,800 to INR 89,550 before tax.

  3. 500TO1,000HOURS

    A larger app with offline use or payments

    Offline sync, payments, several user roles and integrations. Roughly INR 99,500 to INR 1,99,000 before tax.

Turn hours into a total

An example

Illustrative: a Surat textile trader's dealer app

Consider a textile trader in Surat who takes most dealer orders over WhatsApp and phone, with prices sent as forwarded images. The specification describes a cross platform app where approved dealers see the current catalogue with their own price list, place orders, and check outstanding balances pulled from the trader's accounts. A small admin panel lets the office update designs and approve new dealers. Store submission is part of the specification.

Technology we often use

  • React Native
  • Flutter
  • Kotlin
  • Swift
  • TypeScript
  • Node.js
  • Firebase
  • PostgreSQL
  • Razorpay

Chosen to fit the project and your team, and written into the specification.

Questions

About mobile apps.

Should we build native or cross platform?

For most business apps, cross platform with React Native or Flutter is the sensible default: one codebase, two stores. Native makes sense when the app depends heavily on device hardware. The choice is made during scoping and written into the specification.

Do you publish the app to the stores?

Store submission can be part of the specification. It is usually best for the developer accounts to be in your name, and store fees are agreed in writing before work starts.

How do you test on different phones?

Testing is included at no extra charge. The specification lists the Android and iOS versions and the kinds of device the app must support, and acceptance is tested against that list.

Related

Related work and reading

What we buildWeb applicationsWeb apps, portals and sites that your customers and staff use daily.What we buildCustom softwareBusiness software built around how your team already works.What we buildMaintenance and supportFixes, updates and steady improvements for software you already run.
GuideWhat to check before you accept delivered softwareAccepting work is the moment you agree it meets the specification. A Surat trader's dealer app shows how to test a delivery properly.GuideEstimating hours for an MVPA first version is easier to estimate feature by feature, as a range. A Pune founder's booking app is worked through from hours to cost to cutting scope.GuideHanding over code, credentials and documentationA system is fully yours when you can run, change and move it without asking anyone. An Ahmedabad clinic chain shows what a handover should contain, with a checklist to work from.

Start with a conversation

Tell us what you want built. We will tell you plainly whether it fits.

The first conversation is free. You get a rough size in hours, the tier that suits the work, and what a first 150 hour block would cover.

Talk to usBook a 30 minute call
Or get a ballpark proposal in two minutes
Two young Indian colleagues working together on a tablet in a modern workspace
Chat with 2good.dev on WhatsApp