Kotlin, Jetpack Compose and Play
Android app development that survives real devices.
Kotlin and Jetpack Compose, tested on the mid-range phones your customers actually own rather than the flagship on a developer's desk. Play Console submission handled here.
30-min call with a senior lead · Reply within 1 business day · NDA on request
Projects shipped
Years of team experience
Countries served
Client score
01The approach
Our approach to Android app development.
Android is not one device.
What changes on the phone
- New users reach something useful fast90s to value
- They come back on day thirty+41% retention
- A cold start that feels instant-1.9s cold start
- It keeps working in lifts and dead zonesOffline-first
- Store review passed first time, handled here100% pass rate
- The same senior engineers, start to finish0 swaps
Read the full approach
It is a spread of screen sizes, chipsets, OS versions and manufacturer skins, and the phone your developer tests on is almost never the phone your customer is holding. An app that feels quick on a flagship can be unusable on a three-year-old mid-range handset, which in India is most of the market.
So we pick the test devices from your analytics, not from a wishlist. Cold start, scroll performance and memory are measured on the slowest device you have agreed to support, and that number goes in the spec rather than being discovered after launch.
The other half is Play policy. Target API level deadlines, the Data safety form, background execution limits and permission declarations all move, and each one can pull an app from the store if it is left until submission week. We handle those during the build.
What we settle before writing Kotlin
- Minimum SDK, chosen from your analytics
- The slowest device we commit to supporting
- Data safety form and permission declarations
- Kotlin native or React Native, scoped both ways
- Who owns the Play Console account
02Services
Native, hybrid or a web app. What the app has to do on the device decides which of these is right.
Android app development services we offer.
| Native apps Kotlin and Jetpack Compose against the current SDK. The right answer when the app leans on the camera, background location, offline sync or on-device processing. | Hybrid and cross-platform apps One React Native or Flutter codebase for both stores, with Kotlin written only where the hardware demands it. Usually the cheaper answer when iOS needs the same product. | Web apps and PWAs An installable progressive web app when a Play listing is not worth the overhead. One build that runs on any Android phone, updates without a release, and still works offline. | |
|---|---|---|---|
| Typical timeline | 12–16 weeks | 10–14 weeks | 8–12 weeks |
| Next stepQuoted per project after a free consultation. | Discuss this route | Explore hybrid app development | Explore web app development |
Native apps
Kotlin and Jetpack Compose against the current SDK. The right answer when the app leans on the camera, background location, offline sync or on-device processing.
- Timeline
- 12–16 weeks
Hybrid and cross-platform apps
One React Native or Flutter codebase for both stores, with Kotlin written only where the hardware demands it. Usually the cheaper answer when iOS needs the same product.
- Timeline
- 10–14 weeks
Web apps and PWAs
An installable progressive web app when a Play listing is not worth the overhead. One build that runs on any Android phone, updates without a release, and still works offline.
- Timeline
- 8–12 weeks
03Process
Our Android app development process.
Five stages, and your team installs builds from the Play internal track from week five.
01ShapeWeek 1–2
Scope cut, devices chosen. Interviews, a competitive read and one hard prioritisation session. Your analytics decide the minimum SDK and the slowest device we commit to, and Kotlin and React Native are both scoped and costed.
02DesignWeek 2–4
The first ninety seconds, drawn first. Onboarding and the first session before anything else, because that is where installs are lost. Material 3 where it fits your brand, and layouts drawn for a small mid-range screen before a large one.
03BuildWeek 4–12
Kotlin, in two-week slices. Working builds every fortnight on the internal testing track. Performance is measured on the agreed slowest device each cycle, so a regression is caught in the sprint that caused it.
04SubmitWeek 12–14
Through Play review, cleanly. Store listing, screenshots at every required size, the Data safety form and the permission declarations that stop an avoidable rejection. We submit and we answer review.
05WatchPost-launch
Two weeks of cover, then your call. Fourteen days included: ANR and crash triage in Android vitals, review responses, and the first read on where new users drop out. A retainer afterwards is optional.
Stage 02 · Design
04Included
What we deliver.
01Tested on the phones your users own
Test devices picked from your analytics, not from a wishlist. Cold start and scroll are measured on the slowest handset we have agreed to support.
02Play policy handled during the build
Target API level, the Data safety form, permission declarations and background limits. Left to submission week, any of them can pull an app from the store.
03Time to first value, specified
How fast a new user reaches something worth having. Written into the spec with a number against it, then measured.
04Internal testing track from week five
Your team installs real builds from Play while there is still time for the feedback to change something.
05Your Play Console account
Published under your organisation, not ours. If we part ways, the listing, the reviews and the install base stay where they are.
06Kotlin you can hand to anyone
Reviewed, documented and conventional. The next developer should not need us to explain the architecture.
05The work
Phone, tablet and large-screen work, described honestly. The published examples are in the portfolio.
What we build on Android.
Android work, end to end.
Consumer apps, internal tools, and the backends underneath them.
- Native Kotlin and Jetpack Compose apps
- Tablet, foldable and large-screen builds
- React Native with native Android modules
- APIs, integrations and data pipelines
Much of our product work sits under an NDA. Everything in the portfolio was built by the same engineers and is live right now, go and prod it.
06Why Syscodes
What clients say after comparing us with larger app agencies.
Why teams pick us for Android.
devices, not emulators
We test on the phones people own
Test devices come from your analytics. A mid-range handset that is three years old is the real target, not the flagship the developer happens to carry.
to first value
We design the first session
Time to first value is a spec item with a number against it. That is where installs are lost, long before anyone finds a bug.
policy items settled
Play policy is part of the build
Target API level, the Data safety form and permission declarations are settled early. Left late, any of them can pull a live app from the store.
routes always costed
We will talk you out of native
Kotlin is not always right. We scope and cost both routes, and a third of the apps we ship turn out not to be native at all.
years of team experience
Senior engineers, no bench
The person in your scoping call writes the Kotlin. Nothing is handed down to someone you have never spoken to.
ownership from day one
The account stays yours
Published under your Play Console account with the code in your repository. Leaving us costs you nothing but the notice period.
07Clients
130+ brands across 20+ countries, from pre-seed founders to national operators.
Teams whose apps we ship.
“I would absolutely hire Syscodes again. Their Shopify expertise, clear communication, and reliability made the entire project seamless. They brought valuable ideas and recommendations that genuinely improved the final result. Professional, responsive, and highly skilled, I couldn’t recommend them more highly.”
conversion rate
“Great experience working with Syscodes on our CRO-focused website redesign. They understood our goals, improved the user flow, and delivered a better design. Communication was smooth, deadlines were met, and the whole process was very professional. Would definitely work with them again.”
sales
Not sure where to start?
Ask us anything before committing to a call. Most questions get a real answer within a few hours.
or WhatsApp +91 70034 16634
9.9/10 client score · 150+ projects · 100% on time
08Engagements
What an Android app costs depends on its scope and on how many devices it has to behave on, not on a price list. Every engagement is scoped after a free consultation, and the written proposal carries the number.
What Android app development costs, and what shapes it.
Engagement
Android MVP
- One defined v1, phones only
- Kotlin or React Native, costed both ways
- Play submission handled by us
- Analytics wired before launch
Most chosen
Native Android build
- Kotlin and Jetpack Compose
- Phone, tablet and large screen
- Data safety and permissions handled
- Performance floor device agreed
Engagement
Android and iOS together
- One React Native codebase
- Native Kotlin where the hardware needs it
- Both stores, one release train
- Cheaper to run than two native apps
09FAQ
Frequently asked questions.
Scope, cost, device support, the platform decision and Play review.
Still unsure?
Ask us anything before committing to a call. Most questions get a real answer within a few hours.
hello@syscodes.in+91 70034 16634
Book a 30-min call
What do Android app development services cost in India?
There is no price list, because the number is set by scope rather than by platform. A single-purpose Android MVP and a native app with offline sync, background location and a backend behind it differ by an order of magnitude. We scope every engagement after a free consultation and put the figure in a written proposal, along with what would move it.
How long does it take to build an Android app?
Twelve to sixteen weeks is typical for a native Kotlin build, and ten to fourteen for React Native. Your team installs the first internal-track build in week five. Play review itself is usually three to seven days, which is faster than the App Store.
Which Android versions and devices will you support?
We set the minimum SDK from your own analytics rather than a default, and we name one slowest device that performance is measured against every sprint. Supporting one more version back costs testing time and constrains which APIs we can use, so it is worth deciding on data.
Should we build native Kotlin or use React Native?
It depends on what the app asks of the phone. Camera work, background location, offline sync, on-device processing and heavy animation point to native Kotlin. A product that is mostly screens, forms and data, and that needs iOS too, is usually better served by one React Native codebase with Kotlin written only where the hardware demands it. We scope and cost both before you decide.
Why does my app feel slow on cheaper phones?
Almost always because it was built and tested on a flagship. Cold start, scroll performance and memory behave completely differently on a three-year-old mid-range handset, which in India is most of the market. We pick that device up front and measure against it every sprint rather than discovering the problem in store reviews.
Who owns the code and the Play Console account?
You do, both, from the first commit. The app is published under your organisation's Play Console account rather than ours, and the repository is yours. If you leave us, the listing, the reviews and the install base stay exactly where they are.
Do you also publish to other Android stores?
We can. Most clients need Google Play alone, but if your market includes regions or devices where another store matters, we will say so during scoping rather than after. It changes the build less than people expect and the release process more.
What happens after the app is live?
Fourteen days of cover is included: ANR and crash triage in Android vitals, responses to store reviews, and the first read on where new users drop out. A retainer after that is optional and plenty of clients do not take one. If you do, it is the same engineers.
Where are you based, and can you work with us outside Kolkata?
Do you work with clients outside India?
Yes. We have delivered in 20+ countries across five continents, and we commit to four guaranteed overlap hours with US Eastern (18:30–22:30 IST), with a full overlap for the UK and Europe. The names are in the contract.
10Start a project
Let’s scope your Android app.
Tell us who the app is for and which phones they carry. Written proposal inside one business day.
- Within 1 business dayWe read it properly and reply with real questions, not a templated brochure.
- A 30-minute scoping callFree, no obligation. We tell you honestly if we are the wrong fit.
- A written proposalScope, timeline, deliverables and the success metric, all on one page.
You'll hear back from a senior lead, never a bot.