The strongest public scale statement currently available from GameBee is dated, not live: its five-year milestone article says the studio had published more than 50 games, reached more than 10 platforms and passed 20 million downloads. The article was published on 26 August 2024 and shows a 20 May 2025 update date.
That source does not verify a current portfolio of 70 or more unique published games. As of 27 August 2026, the public evidence supports the dated 50+ milestone and current examples across the GameBee website, Google Play and Apple, including iPhone/iPad, Mac and Apple TV groupings. A responsible portfolio report keeps those evidence periods separate.
The 2024 milestone establishes a historical baseline
GameBee's anniversary article attaches three scale claims to the studio's first five years: availability on more than 10 platforms, more than 50 games published and more than 20 million downloads. Because the source is first-party and dated, those figures can support a historical milestone. They should not be silently relabelled as a live count for August 2026.
The distinction is important for readers and structured data. A dated statement answers what GameBee reported at that milestone. A current total would require a newer, equally explicit first-party inventory or corporate statement with a clear counting method. Without that source, the older figures remain useful precisely because their time boundary is visible.
The public record does not currently prove 70 or more titles
A claim of 70 or more titles needs a public source and a clear counting rule, but the checked records supply neither. The live GameBee catalogue shows selected titles, Google Play displays a current developer portfolio and Apple groups current listings by platform. None identifies 70 or more unique published games or explains whether separate editions, renamed products and removed listings would count once or several times.
The evidence-safe conclusion is to retain the dated 50+ milestone and describe current platform examples without assigning a newer total. A 70+ statement should appear only after GameBee publishes a dated count or an auditable inventory. Until then, the larger number remains unverified and should not be presented as a current portfolio fact.
A website catalogue is not automatically a portfolio census
The current GameBee games catalogue is valuable because it lets visitors discover named products and reach their public destinations. It is not labelled as a complete record of every released, regional, retired or store-specific edition. Counting the visible cards would therefore answer how many items appeared on that page at one moment, not how many unique games the studio has published.
Catalogue maintenance also creates identity questions. A game can be renamed, refreshed on a legacy URL, released under separate mobile and television packages or presented differently by Apple and Google. A trustworthy count needs a stable product identifier and an explicit rule for editions. Artwork or title similarity alone cannot decide whether two listings represent one game, one port or distinct products.
Current store portfolios prove platform presence, not total scale
Google Play publicly identifies Gamebee Studio and currently shows Adventure Runner with additional developer examples such as Baseball Super League, Fruit Cutter TV, World Sports Games, Rolling Ball Adventure, football, Dino Hunter, Stunt Extreme, Jet Force, Bowling Master and Office Rush. Those visible records demonstrate an active Android portfolio, while each package retains its own availability and mutable store fields.
Apple's Game Bee Studio developer page currently groups listings under iPhone/iPad, Mac and Apple TV. That verifies public presence across those Apple categories in the selected storefront. It does not prove that every title supports all three, that purchases transfer or that the same gameplay and controls are present in each edition.
Smart TV is a stated business focus with edition-level proof
The GameBee homepage describes the company as specializing in CTV or Smart TV publishing and production. Current Apple TV groupings and television-oriented Google Play records give product-level examples consistent with that focus. The combination supports a broad television presence, but the exact supported hardware must still come from each current listing.
A Smart TV claim should not become a universal device promise. Apple TV, Google TV and Android TV are distinct environments, and other television platforms require their own public evidence. The anniversary article's 10+ platform milestone is historical aggregate context; it does not provide a current matrix showing which title appears on which platform.
Desktop evidence must distinguish capability from release
Apple currently exposes a Mac portfolio group, so public Mac availability can be supported for the listed records. GameBee's services page also describes development experience across PC, Mac, Linux, iOS, Android, WebGL and Nintendo Switch. That statement demonstrates capability, not a current released-game inventory for every platform in the list.
A claim that the current GameBee portfolio spans PC therefore needs title-specific public release evidence, not only a service capability statement. Until a verified PC release is available, the supported conclusion is that desktop capability is public and Mac listings are visible, while broader PC availability remains product-specific and unresolved.
Update history belongs to individual editions
Update history, performance and player feedback cannot be generalized across a studio portfolio. Google Play packages and Apple IDs carry their own version dates and notes. A bug-fix entry for one edition does not prove a shared engine change, improved performance elsewhere or a studio-wide release cadence.
Use version notes as narrow evidence: record the title, identifier, version or update date, platform and exact wording. If the note says only bug fixes, do not assign a feature, cause or performance result. A portfolio report can explain this method without converting several unrelated notes into a single development history.
Player feedback and performance need attributed evidence
Store ratings and reviews are mutable, territory-dependent and uneven across games. They can help a reader inspect one edition at publication time, but combining them would hide differences in audience size, version, platform and age. No checked first-party source links a portfolio-wide change to a defined player-feedback programme or publishes a common performance benchmark.
Any future improvement claim should be attributed to a named release note, developer statement or documented feedback theme. Claims about frame rate, stability, loading or control response need the exact device and build. Without that detail, the evidence-safe statement is that each edition has a separate public record whose current feedback and performance must be evaluated independently.
A durable evidence ledger can support future count updates
A future 70+ claim becomes publishable when GameBee provides a dated first-party statement or a reconciled inventory. The ledger should assign one canonical product identity, list distinct packages or Apple IDs beneath it, record platform and region, mark active or historical status and cite the public destination checked on a specific date. That prevents ports and renames from inflating the total.
The same ledger can preserve milestones without erasing history. Keep the 2024 50+ games, 10+ platforms and 20 million+ downloads statement as a dated snapshot. Add a later total only with its own source and date. Readers can then see genuine growth rather than a moving number whose definition changed between reports.
Verdict: the public portfolio is broad, but the count must stay dated
The first-party record clearly supports a multi-platform GameBee portfolio, a Smart TV publishing focus and a meaningful five-year milestone. Current Google Play and Apple developer pages show active examples across Android, iPhone/iPad, Mac and Apple TV, while the GameBee catalogue provides a direct first-party discovery path.
What the record does not yet support is equally clear: a current 70+ unique-game total, universal PC availability, shared features or portfolio-wide performance and feedback results. Publishing the verified milestone with its date is stronger than repeating an unsupported larger number. Update the count only when GameBee releases a newer auditable source.
Return to the GameBee platform and play-style guide to use the verified portfolio as a practical game-selection starting point.
Questions about GameBee portfolio evidence
Does GameBee publicly verify more than 70 published games?
Not in the first-party sources checked on 27 August 2026. The dated five-year article verifies more than 50 games published, more than 10 platforms and more than 20 million downloads at that milestone.
Why not count every visible website and store listing?
A visible entry can be a separate edition, port, renamed product, regional listing or selective catalogue card. A unique-game total needs stable product identities and an explicit counting method.
Which GameBee platforms are currently visible in official records?
The checked Google Play portfolio supports Android examples, while Apple's developer page groups current listings under iPhone/iPad, Mac and Apple TV. The GameBee homepage also states a CTV or Smart TV publishing focus.
What evidence would make a future portfolio count publishable?
Use a newer dated GameBee statement or a reconciled first-party inventory that identifies unique products, editions, platforms, public destinations and active or historical status without double-counting ports or renames.