Games Ducky

Games Ducky began as a place to play. A catalogue of browser titles, a search box, categories down the side — the kind of site people open for ten minutes between other things. That part still works, and it still gets most of the traffic.

how it started

So we started writing them ourselves.

The news desk came later, and it came from a specific annoyance. We were watching what our own visitors played, week after week, and none of it appeared anywhere in games coverage. A browser title would pull enormous numbers and the entire industry press would ignore it, while the same fourteen console announcements got rewritten across forty sites. Meanwhile the actual industry stories that changed things — a storefront quietly adjusting its refund window, a studio going silent for eight months before the layoff announcement — got a single paragraph each, if that.

Editorial desk for video game industry reporting
A catalogue of browser titles, a search box, categories down the side
Who Runs This

Small operation, three people, no pretence otherwise.

Video game news editor Daniel Reeve
Daniel Reeve

Daniel Reeve edits the site and writes most of the industry coverage — release dates, publisher moves, platform policy. He decides what runs and takes the blame when something’s wrong.

Source verification for video game industry reporting
Priya Raghavan

Priya Raghavan covers mobile and browser games, which means she spends a lot of time reading store policy updates that nobody else reads. Most of what we publish about monetisation and app store rules comes from her.

Correction and timestamp process for Games Ducky articles
Tomas Lindqvist

Tomas Lindqvist handles research and corrections. Before a story goes up, he’s the one checking whether the source actually says what we think it says, and he’s the one who processes it when a reader tells us we got something wrong.

What We Cover

Release dates, policy, studios, browser games

Map of video game platforms covered by Games Ducky

Release dates and the delays that move them. Console and handheld hardware. Storefront and subscription policy, which is dull to write and matters more than most trailers. Studio news — acquisitions, closures, leadership changes, layoffs. Patch notes when a patch genuinely changes how a game plays. And browser and HTML5 games as a real sector with real studios behind it, not as a novelty item.

We don’t do previews written from a publisher’s B-roll. We don’t run “top 10 games you must play” pieces assembled from other people’s reviews. We don’t cover leaks from anonymous accounts with no track record, and we don’t chase every rumour that clears 10,000 reposts.

What We Won’t Publish

audience first

Worth being direct about this. A large share of our audience is young — the games library skews heavily towards kids and teenagers, and we know it from the traffic. So Games Ducky doesn’t carry real-money gambling content, casino affiliate material, or promotion for apps distributed outside official stores. That rules out a category of revenue that plenty of games sites accept, and we’ve turned it down more than once. It isn’t a moral posture; it’s just the obvious call when you know who’s reading.

How We Check Things

sources, labels, corrections

Every factual claim traces back

Every factual claim traces back to something a reader could open themselves: a publisher newswire post, an earnings call transcript, a regulatory filing, a store listing. Where a story rests on a single outlet’s reporting, we name that outlet in the sentence rather than absorbing it into our own voice.

Unconfirmed material gets flagged

Unconfirmed material gets flagged as unconfirmed, in the headline where it matters. Dates that come from a rumour and dates that come from a publisher never sit in the same column of our release calendar without a label separating them.

Corrections go at the top

Corrections go at the top of the affected article with a timestamp and a plain description of what was wrong. Nothing gets fixed quietly. If we’ve published something incorrect for six hours, the record should show that we published something incorrect for six hours.

Where This Goes Next

The release calendar is the piece we’re most focused on, because it’s the thing readers actually return to. Longer-term, we want proper reporting on the browser games sector — who makes these games, how they get distributed, what the economics look like — since nobody else is doing it and we’re sitting on the audience data that makes it interesting.

Reader tips have already produced several stories that we wouldn’t have found otherwise. If you spot something before we do, [email protected] is the address, and it reaches the three of us directly.