Keith’s Training HubAll learning folders

REAL-LIFE LEARNINGS · 24 October 2026

G9: games & devices

Keep platforms distinct and test controls as people actually use them.

LESSON 1

Web, tablet and TV are separate products

A browser pass does not establish that a native tablet or television build behaves correctly.

What worked

Keeping platform-specific source, artifact and acceptance records avoids accidental substitutions.

What to avoid

Do not replace a legacy game or use a different port just because it builds.

Next time

  1. Confirm the intended platform and source lineage.
  2. Preserve existing games and device-specific behaviour.
  3. Record the exact artifact and build configuration.
  4. Run acceptance on the intended physical device.

Evidence & status: Platform boundaries documented; physical acceptance remains separate.

Back to folder contents ↑

LESSON 2

Test repeated Select, Help and Back

Controls can behave correctly once but fail when repeated or interrupted.

What worked

Regression checks for repeated input and overlay dismissal protect realistic play.

What to avoid

A local test count does not prove an APK was built, installed or accepted on hardware.

Next time

  1. Open Help during the relevant game state.
  2. Repeat Select and navigation inputs.
  3. Dismiss, resume and check focus and state.
  4. Repeat on the actual controller/device before sign-off.

Evidence & status: Local regression work completed; no new APK publication or physical pass is claimed.

Back to folder contents ↑

LESSON 3

Recover source before rebuilding

A recovered archive is useful only when it matches the intended candidate.

What worked

Exact hashes and a pinned compiler make the build provenance auditable.

What to avoid

Do not patch a convenient but unrelated port or silently change toolchains.

Next time

  1. Verify source and artifact hashes.
  2. Record the matching compiler and configuration.
  3. Keep the recovered baseline unchanged for comparison.
  4. Separate source tests, build success and installation evidence.

Evidence & status: Source-recovery lessons captured; each future build needs its own evidence.

Back to folder contents ↑