sample screen, example widths
344 dp
115%
window size classCompactunder 600 dp
layout problems3
  • Cards are fixed at 180 dp, sized on a 412 dp phone: the second column runs 40 dp past the edge of this 344 dp screen.
  • Card text area is fixed at 68 dp: at 115% font size, 4 lines of title or price are cut off.
  • Add buttons are 40 dp tall, under the 48 dp minimum touch target.

Android apps that work on every phone your customers carry

Kotlin and Jetpack Compose apps tested across screen sizes, foldables and Android versions, with Google Play testing tracks and target-API updates handled for you. One platform from €16,900.

from€16,900one native platform, excl. VATproposed, owner to confirm

Written fixed price within one working day. The Play Console account and the code are yours.

The Google Play launch path

Four testing tracks stand between a finished build and the store. For newer personal developer accounts, one of them has a fixed waiting period. Play with the numbers to see how it affects your launch date.

Developer account
8
day 6
  1. Internal testing

    Done

    Up to 100 testers you invite by email. Builds reach them quickly, so it is the track for every sprint build.

  2. Closed testing

    Day 6, not counting

    Testers join by email list or Google Group. New personal accounts need at least 12 testers opted in for the last 14 days in a row.

  3. Open testing

    Optional

    Anyone can join from your store listing. Useful for a public beta; many apps skip it.

  4. Production

    Locked

    Apply for production access in Play Console and answer questions about the test. Google reviews the application, then you release with a staged rollout.

14-day clock0 / 14

Only 8 testers opted in: the 14-day clock needs at least 12. Day 6 does not count yet; invite 4 more.

Assumes the same testers stay opted in throughout. Based on Google Play policy for personal accounts created after November 2023; the rule has changed before, so check the current policy in Play Console. Target API: each year, usually in late August, Google Play raises the minimum target API level for new apps and app updates to roughly one year behind the latest Android release. Apps that miss it cannot ship updates. Check the current deadline in Play Console.

Prices for Android work

Fixed prices from a written scope, excluding VAT. A clickable prototype from €1,900 can come first and is credited against the build.

Cross-platform MVP

Android and iOS from one codebase.

from€14,900excl. VAT
  • Flutter or React Native
  • Both stores, one budget
  • Native code only where needed
About cross-platform
Recommended

Native Android app

Kotlin and Compose, built to adapt.

from€16,900estimate, excl. VAT
  • Compact, medium and expanded layouts
  • Font scaling up to 200% tested
  • Connected to your store or server
  • Closed test and Play release run for you
Get an Android app quote

Android and iOS

Two native apps, one contract.

from€29,000excl. VAT
  • Native on both platforms
  • Shared backend and API
  • One point of contact
About the iOS side

All prices are proposed. owner to confirm Publishing an existing app from €690; care after launch from €290 a month, see app maintenance. Google Play developer registration: a one-off $25, paid by you; check the current fee on Google's own pages.

Know which phones your customers use? Get a fixed Android price tomorrow.

Get an Android app quote

What a native Android build includes

Scoped in writing before any code, with the device and Android version list agreed up front so testing has a clear finish line.

Kotlin and Compose

Screens in Jetpack Compose with Material components, Kotlin coroutines for network work, and a minimum Android version chosen from your own audience data.

Layouts that adapt

Window size classes drive the layout: one column on compact phones, cards and a navigation rail on medium windows, list and detail side by side on expanded ones.

Big text that still fits

Android 14 and later scale text up to 200%, with headings growing less than body text. Every screen is checked at the largest setting.

Connected to what you run

Your Shopify or WooCommerce store, your site or your own server API, with Stripe or your provider for payments. That web and server side is where I am strongest.

Push and background work

Firebase Cloud Messaging for notifications and WorkManager for sync, tested against manufacturer battery savers that stop background tasks.

Yours on day one

Play Console account in your company's name, Play App Signing with an upload key you hold, and the Git repository.

From device list to yearly update

Testing is planned from the first week, not squeezed in before launch.

  1. 1

    Device list

    Your analytics show which Android versions and screen sizes your customers use. That becomes the test list.

  2. 2

    Prototype

    A clickable prototype on your own phone, tested with customers before the build is priced.

  3. 3

    Build

    Kotlin and Compose, with an internal test build on your phone every two weeks.

  4. 4

    Test and launch

    Closed test with real testers, store listing, then a staged rollout to a small share of users first.

  5. 5

    Yearly update

    The app moves to the new target API level before Google Play's deadline, tested on the new Android release.

Questions about Android apps

Why does Android testing take longer?

Because there are far more combinations to cover. Android runs on phones from many manufacturers, foldables and tablets, across several OS versions, and some manufacturers add battery savers that stop background work. I test window size classes and font scales on emulators, then a short list of real devices picked from your own analytics.

What is the Google Play closed test requirement?

Personal developer accounts created after November 2023 must run a closed test with at least 12 testers opted in for the last 14 days before they can apply for production access. Organisation accounts are not bound by it. The rule has changed before, so check the current policy in Play Console before planning a launch date.

Can you add an Android app to my existing iOS app?

Yes. I start by reviewing your iOS app, its backend and its store accounts, then build the Android version in Kotlin against the same server and data. Screens follow Android conventions such as the back gesture and Material components. If both apps need heavy rework, I will compare that with one cross-platform rebuild.

When I would not recommend a native Android app

Who builds your app

I am a web and store specialist who builds apps that connect to your store, site and server. Larger native builds are delivered with a vetted partner developer, under one contract and one point of contact. owner to confirm

If the prototype shows the app is not worth building, you stop there and keep the prototype and the test notes.

  • 01You will need the same app on iOS within a year and the budget is tight. One cross-platform app avoids paying for the screens twice.
  • 02The app would mostly show your store's catalogue. On Android, an installable web app can sit on the home screen and send notifications without a Play listing.
  • 03You need managed devices for a whole workforce or custom hardware drivers. That is specialist enterprise work, and I will point you to someone who does it daily.

Get an Android app quote

A new app, an Android version of your iOS app, or one stuck before production access. Tell me what it should do; you get a written fixed price within one working day.

Prefer email? Write to [email protected]

Pikselipolku is an independent studio and is not affiliated with Apple, Google or any other company named here.

EnquiryReply within one working day
What do you need?

Two lines are enough: what you do and what you want to achieve.

About 2 minutes. Helps me send a firmer price.

Reply within one working day

Or email me: [email protected]

Made in Tampere. The path ends here.61.4978° N, 23.7610° E

Tell me what you need. I reply within one working day.

About these landmarks
  • Näsinneula tower, Tampere, 1971. Opened in 1971, with an observation deck and a revolving restaurant at the top.
  • Finlayson mill, Tampere, 1820. Cotton mill founded in 1820 by James Finlayson; the red-brick mill and chimney still stand by the Tammerkoski rapids.
  • Tampere Cathedral, 1907. National Romantic granite church by Lars Sonck, with frescoes by Hugo Simberg.
  • Helsinki Cathedral, 1852. White neoclassical church with green domes above the Senate Square steps, designed by Carl Ludvig Engel.
  • Parliament House, Helsinki, 1931. Eduskuntatalo, built of red granite behind a front row of tall columns.
  • Temppeliaukio Church, Helsinki, 1969. The Rock Church: cut into solid bedrock and roofed with a copper dome.
  • Suomenlinna sea fortress, Helsinki, 1748. Island fortress begun in 1748 at the entrance to Helsinki harbour; a UNESCO World Heritage Site.
  • Olavinlinna castle, Savonlinna, 1475. Medieval castle with three round towers, built on a rock island between two lakes.
  • Sauna by a frozen lake, UNESCO 2020. Finnish sauna culture is on UNESCO’s list of the intangible cultural heritage of humanity.
  • Lapland: spruce, reindeer and a fell, North. The northern end of the journey: spruce forest, a reindeer and a snow-capped fell.
© 2026 Pikselipolku, Tampere, FinlandBusiness ID [Y-tunnus]Built to WCAG 2.2 AABack to top