Mobile app development company in Kolkata

Cross-platform with React Native or Flutter is the right default for most business applications: one codebase, both stores, and near-native performance for list-driven, form-driven and content-driven products. It is where most Indian budgets get the best return.

Native Kotlin or Swift earns its extra cost when the product depends on the platform itself, such as heavy camera or sensor use, background location, tight hardware integration or demanding graphics.

A progressive web app is worth considering when the audience will not install anything, when you need instant updates without store review, or when the product is fundamentally a website with offline needs. We will tell you when that is the cheaper honest answer.

We test on mid-range Android hardware and throttled connections, not only on a recent flagship. Application size, cold start time and offline behaviour matter more here than any animation, and a queued-write offline mode is often the difference between an app that gets used in the field and one that does not.

Payments are integrated for how India actually pays: UPI intent flows, cards, netbanking and wallets through Razorpay or a comparable gateway, with correct handling of pending and failed states rather than an optimistic success screen.

Where an app serves multiple regions we plan language support at the design stage, including how Bengali and Devanagari text behaves in constrained layouts.

Getting into the stores is a project step, not an afterthought. We prepare store listings, screenshots, privacy policies and the Google Play data safety and Apple privacy nutrition declarations, and we keep the app aligned with the target API level Google Play requires each year, since falling behind blocks updates.

Rejections are usually predictable: a missing privacy policy, an account deletion route that does not exist, permissions that are requested without justification, or a login wall with no demo credentials for the reviewer. We clear those before submission.

Releases are staged, with a phased rollout and crash reporting watched closely for the first few days so a bad build reaches a small fraction of users rather than all of them.

Credentials go in the platform keystore or keychain, never in shared preferences. Traffic is TLS-only with certificate handling appropriate to the risk, and every authorisation decision is enforced on the server, because a client-side check is not a control.

Personal data collection is minimised and documented against the Digital Personal Data Protection Act 2023 and the DPDP Rules notified in November 2025, which set out consent notice, retention and breach notification duties. Getting this right at design time is far cheaper than retrofitting it.

After launch we handle store policy changes, operating system upgrades, dependency updates and crash triage on a support arrangement, because an unmaintained app quietly stops working within a year or two.