# myCarConnect on Google Play: what it takes

Checked on 28 Oct 2026 against the apps as they are now (phone app, car app 0.175) and Google Play's current rules.

## 1. Decisions for you

| # | Question | My recommendation |
|---|----------|-------------------|
| A | Some features are not allowed on Play (YouTube audio, touch control from the car, the car app updating itself). Make a separate **Play edition** without them, and keep today's full apps for sideloading? | **Yes.** You keep everything on your own devices; Play users get the rest. |
| B | Put **one car app** on Play instead of 2GB and 3GB, choosing the light or full settings by itself from the device's memory? | **Yes.** Play wants one listing per app; two near-identical apps confuse users and may be flagged as duplicates. |
| C | The phone app also has an **Android Auto** part (navigation drawn by the car's Android Auto). Keep it on Play? | **Drop it for now.** Android Auto navigation apps get a separate, strict car review; our car screen app does the job instead. |
| D | Package names are permanent once published: `com.abdul.myandroidauto` (phone) and `com.abdul.kalaamscar.screen` (car). Keep them or pick new ones (for example `com.mycarconnect.phone` / `.car`)? | **New names** that match the app name, since nothing is published yet. Your installed apps would need one reinstall. |

## 2. Blockers I would fix in code (no decision needed)

1. **Target Android 16 (API 36).** Play requires it for every new app since 31 Aug 2026. Today the apps target API 34. This also means updating the build tools and making every screen draw edge to edge (Android 15+ forces it).
2. **Delete my account.** Play requires apps that create accounts to let users delete the account and its data, in the app and from a web page. Needs a "Delete account" button and a delete action in account.php, plus a small web page.
3. **Release builds signed with an upload key** as Android App Bundles (.aab). The phone app is a debug build today, and the car app's key and password sit in the project folder.
4. **Prominent disclosures** before asking for sensitive permissions (Play shows these in review):
   - Background location (trips without the car)
   - Physical activity (trips without the car)
   - Phone state (call banner on the car)
   - Notification access (messages on the car)
   - Microphone and screen capture (phone sound and Mirror Screen on the car)
5. **No secrets in the Play build:** the stream server key would be left out with YouTube (A); the Dropbox app key is allowed (Dropbox treats it as public).
6. **Remove `REQUEST_INSTALL_PACKAGES`** from the Play car app (Play does the updates).

## 3. Things only you can do

1. **Google Play Console developer account:** US$25 once, with ID verification. New personal accounts must run a **closed test with at least 12 testers for 14 days** before the first public release.
2. **Privacy policy page** on a public link. I can write it and you put it on host4data.cloud.
3. **Store listing:** short and full description, app icon 512x512, feature graphic 1024x500, at least 2 phone screenshots (and tablet ones for the car app). I can draft the text and make the graphics.
4. **Play Console forms:** Data safety (the app collects email, name, mobile, location, trips), content rating questionnaire, target audience, ads (none). I can give you the answers to fill in.
5. **Permission declarations** in Play Console for background location, and videos showing why it's needed. I can script what to record.

## 4. Order of work once you answer

1. Play edition flavours (A, B, C, D) and target API 36.
2. Account deletion (app, server, web page).
3. Permission disclosures.
4. Release signing and .aab builds.
5. Privacy policy, store text and graphics, Data safety answers.
6. You: developer account, closed test with 12 testers, then production.