Midcore playable byte budget vs tutorial length tradeoff checklist

Editorial collage hero: checklist-midcore-playable-byte-budget-vs-tutorial

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

  1. Pick the export target first: Unity single HTML vs TikTok zip — do not assume one binary serves both without re-export.
  2. Budget assets: Allocate bytes to tutorial frames, audio and fonts before adding a second mechanic.
  3. One teachable verb: Midcore playables should teach one session-1 verb that exists in FTUE; cut lore cards that inflate base64.
  4. Measure raw HTML/zip size before gzip myths; vendors weigh the uploaded package.
  5. CTA early enough: If tutorial length pushes interaction past typical rewarded attention, shorten — size compliance alone is not enough.
  6. QA matrix: Portrait/landscape, MRAID viewableChange (Unity), TikTok safe zones.
  7. Kill criterion: Reject builds that only pass size by stripping the verb the UA brief promised.

Facts vs limits

FieldEvidence
Unity sizeUnder 5 MB, single HTML
TikTok sizeZip < 5 MB
Optimal tutorial secondsNot mandated by these docs

Download the evidence table.

Related posts

When midcore playables should stay out of a network: kill criteria

media buying

playable ads

·

1 min read

When midcore playables should stay out of a network: kill criteria

Rewarded placement map: session minute versus ad load

media buying

playable ads

·

1 min read

Rewarded placement map: session minute versus ad load

Midcore playable: one complete loop before CTA

creative strategy

playable ads

·

1 min read

Midcore playable: one complete loop before CTA