Version Tracking
Upload multiple game versions to track how the codebase evolves over releases.
Overview
Upload 2 or more APK versions of the same game to automatically generate:
- Function delta — how many functions were added, removed, or changed
- Version trajectory — trend direction (growing / shrinking / stable)
- Rollback detection — versions where function count dropped significantly
- Anomaly alerts — string spikes, constant drops, zero annotation coverage
How to set up
Use Batch Upload to submit multiple versions in one workflow. The pipeline processes them in versionCode order and links them as a version series.
Reading version data
Once all jobs in a batch complete, the Analytics page shows:
| Metric | Description |
|--------|-------------|
| Δ Functions | Net change in function count vs previous version |
| Growth % | Percentage change |
| Call density | calls / functions — proxy for code complexity |
| String delta | Change in string constant count |
| Annotation rate | % of functions with AI annotations |
Example: Tile Pyramid
| Version | Δ Functions | Notes | |---------|------------|-------| | v1.0.0 | — | Baseline | | v1.0.8 | +1,185 | Major feature addition | | v1.0.10 | −931 | Rollback detected | | v1.0.11 | +695 | Recovery after rollback | | v1.0.13 | +544 | Incremental growth |
v1.0.10 also showed a string spike (+3,517 strings) and constant drop (−28,427) — indicating a large asset/config restructuring that accompanied the rollback.
Anomaly types
| Anomaly | Trigger | Severity |
|---------|---------|---------|
| rollback | Δ functions < −100 | high |
| string_spike | Δ strings > +500 | high if > 2,000 |
| constant_drop | Δ constants < −1,000 | high if < −5,000 |
| zero_annotation | annotation rate = 0% on game-core | medium |
API access
Version comparison data is available through the Compare API:
GET /api/compare/versions?binary_ids={id1},{id2}
X-SaaS-Email: you@example.com
X-API-Key: re_xxx
Returns function-level diff between two binaries of the same game.