Skip to main content

Build · Capacitor

Your existing web app on the App Store and Google Play. No rebuild.

We turn your web app into iOS and Android apps with Capacitor, add the native features app review expects, make your Laravel API ready for them, and submit both apps under your own store accounts, at a fixed price.

Both apps from $3,500, after a three-day review that sets the fixed quote.

Is your web app a good fit?

Capacitor reuses the front-end you already have. That is its strength, and it decides who should use it.

A good fit

  • A Laravel API with an Inertia, Vue or React front-end
  • A React or Vue web app on another backend, including apps built with AI tools
  • Customers asking for an app, push notifications or a place on the stores
  • A Cordova or React Native app that has become hard to keep releasing

Better served another way

  • Blade, Livewire or Filament screens only: they need a thin app front-end or NativePHP, and the review says which
  • Games, AR or heavy animation: that is a native or Flutter job
  • A brand-new app with nothing on the web yet: see Flutter app development

New app from scratch? Flutter app development.

More than a wrapper

Apple asks for features that lift an app beyond a repackaged website. These are the parts that do it, and the Laravel work they need behind them.

Push notifications

Sent from your Laravel API through Firebase and Apple’s push service, queued, with the device registered on sign-in and removed on sign-out.

Device features that earn their place

Camera, share sheet, haptics, offline storage, biometrics or Sign in with Apple, chosen for what your users actually do.

Sign-in that works in an app

Sanctum API tokens with an expiry, not the cookie login a browser uses, plus universal links and Android App Links so emailed links open the app.

Your Laravel API made ready

CORS and Reverb allow the app’s own origins, rate limits and token revocation are in place, and the API changes ship with tests.

Review, build, stores, pipeline

You can stop after the review and keep everything it produced.

1

Readiness review

Three working days. Stack fit, the Apple 4.2 risk, the API changes and the store checklist, then a fixed quote. The fee is credited against the build.

2

Build

Capacitor apps for iOS and Android around your front-end, the native features from the review, and the Laravel API changes behind them. Code in your repository from the first commit.

3

Stores

TestFlight and Play testing first, then both submissions from inside your App Store Connect and Play Console accounts. You keep the accounts, the signing keys and the code.

4

Release pipeline

A fastlane pipeline in your repository builds and uploads both apps, so the next release is one command, whoever makes it.

Two prices, both fixed

The review sets the build quote, and the quote does not move afterwards. If we underestimated, that is our cost.

App-store readiness review

$750

£570 · €690

3 working days

Whether your web app can ship as a Capacitor app, what Apple will want to see, and a fixed quote.

  • Stack-fit check: Inertia, Vue or React front-ends fit; Blade and Livewire need a plan
  • Apple 4.2 risk read and the native features that answer it
  • Login, CORS, push and deep-link plan for your Laravel API
  • Store-account and signing checklist, then a fixed quote; fee credited against the build
Book the review

Web app to App Store and Google Play

from $3,500

from £2,650 · from €3,200

3–5 weeks, plus store review

Your existing front-end as iOS and Android apps, with the native features review expects, submitted under your accounts.

  • Capacitor 8 apps for iOS and Android built from your front-end, bundled in the app rather than loading your live site
  • Push notifications through your Laravel API, and one more native feature (camera, share, offline, biometrics or Sign in with Apple)
  • Sanctum token login with an expiry, CORS for the app origins, universal and App Links
  • Both submissions under your accounts, with the privacy forms and account deletion the stores require
  • A rejection for minimum functionality or a technical fault in our scope fixed and resubmitted at no extra cost
  • A fastlane release pipeline in your repository, and a 30-day warranty
  • In-app subscriptions (quoted after the review)
  • Building a separate app front-end for Inertia, Blade or Livewire screens (quoted after the review)
  • Rejections over content, payments or business model (quoted separately)
Book the review first

Store fees are yours and paid to Apple and Google directly. After launch, the Mobile module on a care plan (+$300/month) keeps both apps through each year’s store deadlines.

Questions buyers ask first

Will Apple reject an app built from our web app?

It can. Apple’s guideline 4.2 asks for features that lift an app "beyond a repackaged website". That is why the build includes push notifications and at least one more native feature chosen in the review. We cannot promise approval, because Apple and Google decide. If either store rejects the app for minimum functionality or a technical fault in our scope, we fix it and resubmit at no extra cost; rejections over content, payments or your business model are quoted separately.

Does the app just load our website?

No. Capacitor’s own documentation says pointing the app at a live website is not intended for production. Your front-end is built into the app, and it talks to your Laravel API. That is also why the stack-fit check matters: Inertia, Vue and React front-ends bundle well; Blade and Livewire screens need a plan.

Can we ship fixes without going through the stores?

Changes to the web layer (HTML, CSS and JavaScript) can go out as live updates, for example with Capgo, as long as they do not change the app’s primary purpose, which is Apple’s rule. Anything native, such as a new plugin or permission, needs a new store build. Ionic stopped selling Appflow in February 2025 and its customers lose access after 31 December 2027, so we do not set it up for new apps.

Why can Android take two weeks longer?

Google Play requires personal developer accounts created after 13 November 2023 to run a closed test with at least 12 testers for 14 days before the app can go to production. Organisation accounts are not affected. The review tells you which applies and plans the test into the timeline.

Capacitor, NativePHP or Flutter?

Capacitor when you already have a JavaScript front-end worth keeping. NativePHP for Mobile, now free and MIT-licensed, runs PHP on the phone with native views, and suits a team that wants to stay in PHP and is starting the mobile screens fresh. Flutter when the app is new, needs heavy native UI, or should not depend on the web front-end at all.

Who owns the accounts, keys and code?

You do. Apple asks that apps go out under the client’s own developer account rather than an agency’s, and we work that way on both stores. The repository, the signing keys and the release pipeline stay with you.

Which phones does it support?

Capacitor 8 supports iOS 15 and later and Android 7.0 (API 24) and later, and builds against Android API 36, which Google Play requires for new apps and updates from 31 August 2026.

What you are actually buying

The answer to "why an agency in India?", in writing.

Who you contract with

Jigomit LLP, Ahmedabad, India. The company name on the contract and on every invoice.

UK/EU working hours

Working hours overlap the UK and EU day in full; the US East Coast morning in part.

NDA before requirements

We sign your NDA, or send ours, before you share a repository or a brief.

You own every line

You own every line. Code lives in your repository from day one. All IP in the work transfers to you on payment.

Named engineer

The same engineer stays on your account. No junior substitution.

Fixed means fixed

Fixed means fixed: if we underestimated, that is our cost, not yours.

Data-processing terms published

UK GDPR Article 28 processing terms are published and signed as a schedule to the engagement letter. Read the data-processing terms

Written SLAs

Response times in the contract, not on a slide.

Start with the readiness review

Send the web app’s address and a line on what your users should be able to do from their phone. Three working days later you have the fit, the risks and a fixed quote.