STAR-EATING GIRL
A released portrait arcade game with its own production Google Play package, 30-boss progression, comic connection, support context, and finished-game claims.
IN-HOUSE CASE STUDY // IDENTITY AND EVIDENCE
Two related games without one confusing store identity.
STAR-EATING GIRL and StarEatingGirl SpaceCleaner share a studio and part of a fictional universe. They do not share a package, release state, progression system, support route, or visual promise. This case study documents how those boundaries were kept visible.
The risk
Related titles can accidentally borrow each other's screenshots, icons, claims, test instructions, or support links. That creates avoidable customer confusion and weakens release evidence. The goal was not to make both pages look identical. The goal was to make the publisher recognizable while keeping each product truthful.
Identity boundary
StarEatingGirl SpaceCleaner
A separate testing-stage product with its own package, cleaner-focused play loop, tester route, privacy notice, support page, and release-state language.
Evidence-first workflow
- Product map: package, platform, release track, support URL, privacy URL, and primary action were recorded separately.
- Visual map: icon, palette, logo placement, crop zones, gameplay capture, and store role were checked against each actual product.
- Claim map: public statements were limited to behavior and release status supported by the candidate or published build.
- Link audit: game, test, support, privacy, and website routes were checked as customer-facing destinations.
- Boundary review: every asset and statement was checked for accidental crossover before publication.
What was verified
- Distinct official app icons are used on the website and product routes.
- Each game has a separate official page and browser-play route.
- STAR-EATING GIRL points to its production listing.
- SpaceCleaner points to testing instructions, product-specific privacy information, and product-specific support.
- The shared company emblem does not replace either game's product identity.
What this case does not claim
This in-house case study demonstrates identity separation, evidence mapping, and public-route verification. It does not claim that a store will approve every submission, that every device combination has been tested, or that visual consistency guarantees installs, retention, ratings, or revenue.
Apply the same method to your release
A small evidence review can identify mismatched claims, links, screenshots, and release-state language before full production begins. Larger packages can then use the approved evidence map for icons, feature graphics, screenshots, trailers, store copy, and launch pages.
View fixed-scope release services Use the free claim-ledger guide