Zegacode
ID

Mobile apps · Android & iOS

Android & iOS apps for Indonesian businesses

A Flutter MVP for both stores — not two native teams on day one. From Rp49.000.000 — 8–12 screens, 6–10 weeks, source code in the handover, published on store accounts you own.

Chat on WhatsAppCompare with custom web
Flutter, Android + iOSStore accounts in your nameSource code at handover60-day bugfix after live

01 / Mobile apps · Android & iOS

Flutter first. Native only when it is mandatory.

One codebase for Android and iOS keeps an MVP on a single timeline and stops the two stores from forking. Kotlin plus Swift is a separate quote — only when in-OS performance is a real requirement, not because it sounds more “enterprise”.

02 / Mobile apps · Android & iOS

The store accounts are yours

Google Play and Apple Developer are not held as studio property. Play Store submit is in the package. App Store follows once the Apple account is active. Apple’s USD 99/year is not our margin — it is Apple’s fee, paid by the client.

03 / Mobile apps · Android & iOS

What ships in v1, what waits for v2

Eight to twelve screens people will use every day. Production in-app payments, realtime chat, or AI features are above this floor. We would rather cut a feature than ship a brittle foundation.

04 / Mobile apps · Android & iOS

After live

Sixty days of bugfix. OS updates and further fixes can sit on an annual retainer (typically 15–20% of build value). It is optional; you already have the source.

6–10 weeks

Android & iOS app · From Rp49.000.000

3 revision rounds

Included

  • Flutter MVP: 8–12 screens, Android and iOS from one codebase
  • A small admin web for basic operations
  • Store listing assets and Play Store submit on the client’s account
  • App Store accompaniment once the client’s Apple Developer account is active
  • Source code and handover notes under contract
  • 60-day bugfix after live

Not included

  • Apple Developer programme fee (USD 99/year) — paid by the client
  • Production in-app payments, realtime chat, or AI features at this floor
  • Native Kotlin + Swift (separate quote, only when OS-level performance is mandatory)
  • User-acquisition ads or social account management
  • An OS-update retainer (optional; typically 15–20% of build value per year)

Process

How we work

  1. 01

    WhatsApp + MVP cut

    Eight to twelve screens that must ship in v1. Production payments, realtime chat, or on-device AI sit above the Rp49 million floor.

  2. 02

    Screen list and store accounts

    Google Play and Apple Developer accounts stay yours. Apple’s USD 99/year fee is on the client.

  3. 03

    Design + Flutter

    One codebase for Android and iOS, plus a small admin web for basic content and operations.

  4. 04

    Internal testing

    TestFlight / internal testing before store listing. Three revision rounds inside the agreed screens.

  5. 05

    Store submit

    We prepare listing assets. Google and Apple review are outside any studio’s control — we stay on the thread until live.

  6. 06

    Handover + 60-day bugfix

    Source code, handover notes, and post-launch bugfix. An annual OS retainer is optional.

FAQ

What people ask before they pay a deposit.

What does an Android and iOS app cost at Zegacode?

From Rp49,000,000 for a Flutter MVP: 8–12 screens, Android plus iOS, a simple admin web, and Play Store submit on your account.

Flutter or native?

Flutter (one codebase) for a two-store MVP. Native Kotlin plus Swift only if deep OS performance is required — that is a separate quote.

Do you publish to Play Store and App Store?

Yes, including listing assets. Developer accounts stay yours. The Apple Developer fee (USD 99/year) is on the client.

Do I get the source code?

Yes, handed over under the contract, with handover notes.

How long until launch?

6–10 weeks for an MVP at this floor. Payments, realtime chat, or AI sit outside it.

How does maintenance work?

Bugfix for 60 days after go-live. A yearly retainer can be 15–20% of build cost for OS updates and further fixes.

Contact

Have a brief, an old PDF, or just “we need a website”?