Baseball Super League now has separate public histories for Android mobile, Android TV and Apple devices. As of 14 August 2026, Google Play dates the mobile edition to 17 May 2026 and the television edition to 2 June 2026. Apple’s Baseball Super League 2026 listing shows a later version number and retains older notes that document a lineup option, leaderboard and gameplay work.
This journal anchors those records to the live Baseball Super League overview. It does not combine packages into one fictional release line, and it does not imply official league, team or player licensing.
Android mobile: 17 May 2026 maintenance snapshot
Google Play currently shows the mobile package updated on 17 May 2026. Its What’s New section says bug fixes and gameplay improvements. That wording supports a general maintenance statement but does not name a mode, control or measurable performance change.
The current description continues to present Quick, Full and Tournament modes, city-based team customization, star players and touch interaction across batting, pitching and fielding. Those are current description facts, not necessarily additions from the May update.
Android TV: 2 June 2026 maintenance snapshot
The separate Android TV package is dated 2 June 2026 and displays a bug-fix note. Its store description names remote or gamepad support, Quick games, tournaments, team-building actions and global competition language.
The package distinction is critical. A television maintenance date cannot be used as evidence that a mobile touch issue changed, and a mobile mode should not be inserted into television copy unless the TV listing or current build verifies it.
Apple version 2.5: current visible maintenance entry
Apple currently displays version 2.5 dated 24 June with a bug-fix description. The date and note should be rechecked on publication day because store views and displayed year context can change. The note itself does not support a claim about the specific bug, affected device or degree of improvement.
Apple lists iPhone, iPad, Mac and Apple TV compatibility and shows in-app purchases and subscription products. Those current commercial and device facts should remain separate from historical release notes.
Apple version 1.2.1: 31 May 2025
Apple’s public history dates version 1.2.1 to 31 May 2025 and describes gameplay improvements. No subsystem or measurement is named. A responsible journal records the maintenance direction without converting it into a promise of smoother frame rate, faster loading or revised timing.
If GameBee provides an approved internal release note later, this entry can be expanded with title, device scope and observable change. Until then, the public wording sets the limit.
Apple version 1.2: 11 March 2025
Version 1.2 is the most specific Apple entry in the checked history. It names a lineup option, a leaderboard and smoother gameplay. The lineup option adds a team-management decision, while the leaderboard creates a way to compare results. “Smoother gameplay” remains qualitative because the note publishes no metric or test condition.
These features should still be checked in the current build before a step-by-step guide is written. A historical addition can be renamed, relocated or revised in later versions even when the store keeps the old note visible.
Current modes are not a single cross-platform table
Mobile and Apple currently name Quick, Full and Tournament. Android TV names Quick games and tournaments in its public description. The omission of Full from the checked TV copy is not proof that the mode is absent, but it is a reason not to promise it editorially without direct verification.
The same principle applies to control language. Mobile and Apple descriptions discuss touch play, while Android TV identifies remote and gamepad input. Apple TV appears in Apple compatibility, but exact controller behavior belongs to the target device and current app.
Player feedback: mobile themes
Visible Google Play reviews for the mobile package include enthusiasm for the core game alongside reports involving bugs, lag, inning structure and player changes. Developer replies sometimes request more detail or indicate that improvements are being worked on.
These exchanges are useful for prioritizing a verification checklist: reproduce the sequence, note device and version, and check whether a current update changes the result. They do not prove that a particular May patch resolved any one review. A response expressing intent is not the same as a release note.
Player feedback: television themes
Android TV reviews include comments about subscription or time limits and device-specific behavior. Commercial experiences can depend on market, account, offer and version, so the current store detail and in-app terms must decide what a new player will encounter.
When a review describes a device problem, treat it as a test case rather than a universal condition. Record television or streaming-device model, operating-system version, package version, controller and exact action. That evidence is more useful to support than a broad statement that the TV edition is broken or unrestricted.
How feedback can enter this journal
Summarize a theme only when it is visible in a meaningful set of current public responses or when GameBee supplies approved support data. Attribute it as player-reported. Keep positive and critical context balanced, and avoid quoting personal information.
Connect feedback to an update only when a dated first-party source names the relationship. Acceptable evidence could be a detailed store note, a public GameBee release post or an approved product statement. Timing alone—complaint first, patch later—is not proof of causality.
A safe template for future entries
Record platform, package, version, displayed date and concise first-party change. Then state the direct player consequence only if it follows from the note. “Added lineup option” supports a new management choice. “Bug fixes” supports maintenance, not a named fix. Finally, recheck links, compatibility and commercial terms.
Keep old entries when they help explain a current feature, but label them historical. If a feature disappears from current evidence, do not silently repeat it as present; verify the build or revise the wording.
Version-history questions
Why do the mobile and Android TV editions have different update dates?
They are separate Google Play packages with different device targets and public histories. A shared title family does not require synchronized releases, modes or controls.
Did version 1.2 add lineup management on every platform?
The checked note belongs to Apple’s version 1.2. It supports an Apple historical statement, not a simultaneous Android or Android TV rollout. Other platforms need their own first-party evidence.
Have the reported lag or player-change issues been fixed?
The current generic maintenance notes do not verify a specific resolution. Test the latest package on the relevant device and look for a detailed first-party note before stating that an individual issue is fixed.
Does the Apple subscription apply to Android TV?
Do not transfer commercial terms between stores. Apple lists its own products, while Google Play presents terms for each Android package. Read the offer shown to the account and device before purchase.
Check the live release record
Start from Baseball Super League and open the exact mobile, Android TV or Apple listing for your installation. Use that first-party detail for the latest version, compatibility, controls and price terms.