Pool Masters Pro has two verified public edition records and only a narrow update history. Google's Android TV package is Pool Masters 3D: Multiplayer and carries a dated 27 May 2026 checkpoint with a Bug Fixes note. Apple ID 6756917324 uses the Pool Masters Pro – Multiplayer name.
These sources can prove identity, current features, visible dates and the exact wording of maintenance notes. They cannot prove which defect changed, how performance moved or whether a particular review caused a release. This ledger keeps those boundaries visible so later evidence can be added without rewriting history.
The ledger begins with two exact identifiers
Google package com.gamebee.androidtv.pool identifies the Connected TV edition. Apple ID 6756917324 identifies the iPhone and iPad edition. The display names are related but not identical, so every evidence row needs the identifier before a date, feature or update statement.
This prevents an Apple version from being assigned to Android TV or a television control claim from appearing as a mobile change. The website product family can remain consistent while the ledger preserves the store-level records that make each statement testable.
Google provides a dated Android TV checkpoint
The Android TV listing was labeled updated on 27 May 2026 when checked. Its public description documents local two-player Pass & Play, online multiplayer, solo trick shots, remote-supported aim, spin and power, customization and realistic ball movement. These are current-state facts at that checkpoint.
The What's new field says Bug Fixes. That wording establishes maintenance activity but does not identify a repaired mode, controller, network path or television model. A dated entry should repeat the narrow note and keep the affected system and result marked unknown.
Apple shows versions without a complete public chronology
Apple's visible history lists version 1.0 at Jan 9 and version 1.1 at Jun 2. The captured presentation does not display a year beside those rows. Version 1.1 uses the wording Bug fixes to give you an improved gaming experience, while the earlier row also carries broad bug-fix language.
The ledger should not infer a year from the copyright line, current date or version order. It can record the labels exactly as seen and add a year only when Apple or another approved source exposes it. Accuracy is stronger than an apparently complete but guessed timeline.
Current features are not automatically recent additions
Apple documents 8-ball, real-time PvP, tournaments, touch controls, Pass & Play, trick shots, offline practice and cue customization. Google documents a closely related Connected TV set. A current description proves availability at observation time, not the version that introduced each feature.
A feature becomes a change only when a dated note, archived baseline or approved first-party statement connects it to a release. Until that evidence exists, the ledger should use observed in the current listing rather than added in version 1.1 or introduced in May.
Platform differences belong beside the update record
Apple explicitly describes offline solo practice and touch gestures. Android TV explicitly describes television remote support and a Connected TV interface. These distinctions help players understand why two editions can change on separate schedules and why one release note may not apply elsewhere.
When a future note mentions controls or compatibility, record the exact device class and package. Avoid summarizing it as a universal Pool Masters improvement unless both stores publish matching evidence or GameBee provides an explicit cross-edition release statement.
Ratings and reviews are observations, not release causes
Google displays a changeable rating overview and public comments for the TV package. Apple currently says there are not enough ratings or reviews to display an overview. Those presentations can describe the public feedback environment at a dated checkpoint, but they are not equivalent datasets.
A review may report a freeze, purchase concern or positive local-play experience, yet it cannot prove the issue exists on every device. It also cannot prove a later Bug Fixes note answered that report. Causality requires a GameBee response or changelog that makes the connection explicit.
Performance claims need a measured test condition
Phrases such as seamless performance, smooth controls or realistic physics appear in promotional descriptions. They describe intended experience, not a benchmark. A verified improvement would need the edition, build, device, test condition, metric and before-and-after result or a specific first-party statement.
Without those fields, the ledger can report that a store uses performance language and that maintenance notes exist. It should not invent frame-rate gains, reduced crashes, faster matchmaking or improved input latency. This keeps the authority asset credible when more detailed technical evidence becomes available.
Every future row needs the same evidence contract
Record store, identifier, visible date, version, exact note, current feature affected and evidence for the player-facing result. Preserve unknown values instead of filling them from another edition. Attach screenshots or approved changelog links when GameBee can publish them.
A consistent contract lets readers distinguish a store-maintenance marker from a meaningful gameplay milestone. Over time, it can show genuine progress across mobile and television without merging histories or turning a changeable rating into a permanent product claim.
Return to the Pool Masters review for the current 8-ball, multiplayer, Pass & Play, trick-shot and device-fit verdict.
Questions about the Pool Masters edition ledger
What is the latest dated Android TV checkpoint in this ledger?
Google labeled package com.gamebee.androidtv.pool updated on 27 May 2026. The public What's new field says only Bug Fixes, so the affected system and measured result remain unknown.
Which Apple versions are visible?
Apple's checked history displays versions 1.0 and 1.1 with Jan 9 and Jun 2 labels. The visible rows do not show years, so the ledger preserves the dates without inventing them.
Do current features prove what changed in the latest release?
No. A current store description establishes what is publicly documented at the observation date. A dated note or earlier baseline is required to attribute a feature to a particular release.
Did player feedback cause the published bug fixes?
No causal link is public. Reviews can be recorded as dated player reports, but only an attributed GameBee response or detailed changelog can connect a report to a specific change.