Why we wrote this down
Most "review sites" don't tell you how a review actually gets made, and the reader is supposed to just trust the score. We don't think that's good enough — especially in the browser-game space, where the line between an editorial site and a thinly disguised content farm has gotten very blurry over the last two years.
So this article is the public version of our internal review playbook. If you ever land on a game review on Spinappy and wonder "is this a real editorial page or just partner marketing copy?" — what follows is the answer.
The first impression pass
Every game we cover starts with a browser-page check. The point is not to be overly technical — it is to catch the things a player would feel quickly:
- How long does the splash screen take? (Anything over 8 seconds with no progress indicator, we flag.)
- Is there a "click to play" gate, and does it actually do something or is it ad-injection bait?
- Are the controls discoverable in the first thirty seconds, or do you have to read a tutorial wall of text?
- On the third-party iframe, are the assets loading from a licensed distributor or are there third-party trackers piggy-backing on the page?
This pass alone is enough to flag a surprising number of titles for later cleanup, noindexing, or deeper review. We keep the full catalogue playable, while giving the highest-traffic and most representative games deeper documented coverage.
The core loop pass
For featured reviews and high-traffic catalogue pages, we spend extra time identifying the game's core loop — the 30-to-90-second cycle that, if it is good, will keep a player engaged for hours. For an idle game, that is "tap → spend → upgrade → wait." For a runner, it is "spawn → dodge three obstacles → die or chain a power-up." For an .io game, it is "engage → win or lose → respawn smarter."
We write the core loop down. In one sentence. If we can't articulate it in one sentence, the game is incoherent — and that's a useful thing to say in the review. (Some of our hardest-hitting verdicts are about games that have too many loops competing for attention.)
We also note the first moment the game tries to monetise — not because monetisation is bad, but because where it appears is a strong signal of design intent. A game that asks for $2.99 in the first five minutes is built around the cash register. A game that doesn't show an upgrade store until level four trusts its own loop.
The deeper "where does this break" pass
This is the pass where most marketing copy falls apart and most editorial reviews actually get made.
In deeper reviews, the page has to move past summary. The editorial pass should identify repeated obstacles, early upgrade decisions, device fit, input friction and the moments where the game starts to wear thin. This is where we find the cons that we put in the published "What doesn't work" section of a review — because every game has them.
We have a hard internal rule: if a review cannot name at least one honest limitation, it does not publish as final editorial copy. A page without a single criticism is marketing copy, and we do not want Spinappy to read like marketing copy.
The pros / cons / tips structure
Every published review on Spinappy has the same basic structure: an intro, body prose, a pros list, a cons list, a tips list, a verdict, and a short FAQ. Featured reviews may add extra hands-on notes. We picked that structure deliberately:
- Pros and cons in dedicated lists force editors to commit to specific claims. "Generally fun" doesn't survive being typed into a bullet — you have to write something concrete or delete the bullet.
- Tips reference specific in-game systems. "Have fun!" is not a tip. "Upgrade the floatie before the pet — slide speed compounds" is a tip. We will reject a draft if the tips section reads like a fortune cookie.
- The verdict ends with who the game is for and who it isn't for. A review that recommends a game to "everyone" is useless to anyone trying to make a decision.
Conflict-of-interest rules
Spinappy embeds games through licensed content partnerships. Our editors are paid by Spinappy, not by the game developers. We do not accept advance copies, premium keys, gift codes, or cosmetic giveaways from any developer or publisher. We also do not write reviews for games we have a personal financial relationship with — if an editor knows the developer, they recuse from that title and another editor on the team takes the review.
These rules are written down on our public Editorial Standards page, and any reader who spots a violation can email us at [email protected].
The byline matters
Featured reviews on Spinappy use a visible byline and a reviewed date. Maya Lin, Jordan Reyes, Priya Shah, Theo Park and Lena Vasquez represent the beats we use to organize coverage, from puzzle logic to mobile-first arcade play. If a page is presented as a full review without a name or date, that is a bug — please email us.
We also publish the date the review was last checked or re-tested. Browser games change. A title we liked in February might be unrecognisable after a content drop in May. The date on the byline is our promise that what you are reading reflects the latest editorial pass we have made on that page.
Why this matters for you
You don't owe us your trust just because we wrote a transparency post. But the next time you're deciding whether a "best browser games of 2026" listicle is worth reading, ask the simple questions: who is accountable for the page, what did they test, and what did they criticise? If the answer is "anonymous, who knows, and nothing" — close the tab. There are better-spent ten minutes out there.