Midcore playable byte budget vs tutorial length tradeoff checklist

Checklist for midcore playable tutorial length under Unity and TikTok documented 5 MB packaging caps.
Tutorial length fights byte budgets on midcore more than casual. Unity requires playables under 5 MB in a single inlined HTML (Unity playable specs). TikTok requires a playable .zip smaller than 5 MB (TikTok playable ads). Those caps are hard packaging limits, not creative taste.
Operator checklist
- Pick the export target first: Unity single HTML vs TikTok zip — do not assume one binary serves both without re-export.
- Budget assets: Allocate bytes to tutorial frames, audio and fonts before adding a second mechanic.
- One teachable verb: Midcore playables should teach one session-1 verb that exists in FTUE; cut lore cards that inflate base64.
- Measure raw HTML/zip size before gzip myths; vendors weigh the uploaded package.
- CTA early enough: If tutorial length pushes interaction past typical rewarded attention, shorten — size compliance alone is not enough.
- QA matrix: Portrait/landscape, MRAID viewableChange (Unity), TikTok safe zones.
- Kill criterion: Reject builds that only pass size by stripping the verb the UA brief promised.
Facts vs limits
| Field | Evidence |
|---|---|
| Unity size | Under 5 MB, single HTML |
| TikTok size | Zip < 5 MB |
| Optimal tutorial seconds | Not mandated by these docs |


