8 janvier 2026
finding the perfect version naming strategy
Version names are tiny release contracts: they should reflect change clearly without asking developers to think too much.
Now in closed testing
Synton
Know exactly what you are shipping to Google Play.
Synton is an Android release cockpit for small teams. Connect GitHub and Google Play, get versioned builds and git-aware changelogs, then promote known releases across Play Store tracks.
Track dashboard
app.synton.demo
Latest known build
v1.8.4code 184
main
Version policy
feat: minor bump
Generated notes
4 commits since beta
Play sync
2 min ago
Google Play tracks
Internal
v1.8.4code 184
Alpha
v1.8.3code 183
Beta
v1.8.2code 182
Production
v1.8.1code 181
Internal
v1.8.4
code 184
Alpha
v1.8.3
code 183
Beta
v1.8.2
code 182
Production
v1.8.1
code 181
Promote v1.8.2 to production
Uses the existing Google Play version code, then syncs the track state back into Synton.
Release clarity, not another CI platform
Your build may come from CI, but the release truth lives across commits, version codes, generated notes, Google Play tracks, and the occasional manual promotion. Synton keeps that trail readable.
Version as a service
Ask the API for the next Android version and get a predictable version name, version code, commits, and notes.
Google Play track sync
Sync internal, alpha, beta, and production tracks so Synton reflects what is actually active in Google Play.
Controlled promotion
Promote a known version code from Synton, then reconcile Google Play back into the release trail.
What Synton actually does
A release ledger between your CI and Google Play.
Synton does not replace your Android build system. It keeps the release metadata that usually gets lost around it: version decisions, commit ranges, generated notes, Play Store tracks, and promotion history.
01
Your CI asks for a version
Send Synton the current commit, branch, and Android package name. Synton compares it with the previous known version, reads the commit logs, applies your version bump policy, and returns the next Android version name. For example: fix: bumps the patch, feat: bumps the minor, and breaking changes bump the major.
02
Synton records the build
Each generated version stays linked to the source commit, bump type, changelog, and app configuration. It becomes a known build that can later be matched with Google Play state.
03
Google Play remains the runtime authority
Synton syncs Play tracks from Google Play, stores the current track state, and reconciles local releases when it observes a version code that matches a known build.
04
Promotion uses known version codes
When you promote from Synton, it updates the target Play track with an existing version code, commits the Google Play edit, and immediately syncs the track state back.
Coming next
The missing release workflow around the version API.
The version service is the first brick. The next useful pieces are the ones that make publishing easier to understand: release notes and track movement.
Release note assistant
Compile the commit logs since the last release on the same Play track, then help draft a clearer release note. A later version can use AI to turn technical commits into more human text.
Interactive Play track dashboard
Show where each version currently lives across internal, alpha, beta, and production, with arrows for promotion paths and sync state when Google Play changes outside Synton.
From the blog
Read more →
1 janvier 2026
Finding the Perfect Name for the App
Naming a developer tool is never just branding — it is deciding what the product promises in a single word.
27 décembre 2025
From Code to Play Store: The Long Journey of an Android App
Why Android releases still feel fragmented, and why Synton starts by tightening the path from commit to Play Store.