The mobile gaming platform reference.

The missing layer

Players discover games through a personalized feed that learns from what they browse, play, follow, and skip. From there they can enter a game's community, follow updates, play supported demos, challenge friends, and build a public gaming identity.

Developers get the connected infrastructure around that experience: game pages, visibility, devlogs, testing, feedback, behavioral analytics, communities, rankings, and campaigns. Games can join during development or after release.

Two sides of the same system

• Developers bring games, devlogs, Demo Builds, updates, and campaigns.
• Players bring discovery, attention, play, feedback, follows, and promotion.
• PixelPicked connects those actions into a persistent history and community around each game.

A continuous journey

• Idea: establish the concept and give people something to follow.
• Development: publish devlogs and make progress visible.
• Playable: share a Demo Build and let players experience the game.
• Learning: combine structured feedback with behavioral analytics.
• Momentum: run campaigns around milestones, updates, new demos, and release.
• Growth: keep the page, community, updates, and discovery presence active after release.

What stays connected

The game page, followers, devlogs, playable experiences, player responses, and campaigns belong to one history. Developers do not need to rebuild the audience and story for every new milestone.

What a game page brings together

• The game name, description, genre, development status, and visual identity.
• Screenshots, artwork, trailers, and playable Demo Builds.
• Devlogs, followers, feedback, campaigns, and release destinations.
• The developer or studio behind the game.

Human review

Submitted games are reviewed by people before entering curated discovery. Review protects the quality of the player experience and helps original, thoughtfully made work stand apart from clones, direct asset flips, and low-effort listings.

What to publish

• New mechanics, systems, levels, characters, and art direction.
• Design decisions, experiments, tradeoffs, and lessons learned.
• Screenshots, clips, prototypes, before-and-after comparisons, and milestones.
• Questions that invite players into a useful discussion.

How community compounds

Devlogs give followers a reason to return before the game is released. Over time, that repeated context makes Demo Build feedback more informed and gives important updates and campaigns an audience that already understands the game.

Followers can stay connected through development, release, and later updates. The relationship is not reset on launch day.

Full and focused experiences

• Publish a full browser-playable build when the complete experience is appropriate.
• Offer a focused 5-, 10-, or 15-minute experience when a shorter introduction serves the game better.
• Reach early game testers without adding install friction to the first experience.
• Use Demo Builds during development, alongside a campaign, or as an interactive preview near release.

More than a trailer

Screenshots and trailers show how a game looks. A Demo Build lets the mechanics, controls, pacing, and feel make the case directly. Players can try the experience before installing the final mobile game.

Demo Builds are browser-playable HTML exports hosted within the PixelPicked experience. The final released game can still be distributed through its normal app-store destinations.

How it works

Analytics operate around Demo Builds hosted on PixelPicked. This removes the need to integrate a separate analytics SDK or manually instrument the game simply to learn from a pre-launch demo.

Available signals

• Sessions: playtime, active time, session count, and session length.
• Retention: return behavior across Day 1, Day 3, and Day 7 windows.
• Performance: frame-rate context, device context, and crash information.
• Progression: level starts, completions, and funnel drop-off.
• Interaction: click and interface engagement patterns.
• Build comparison: understand how different Demo Build versions or variants perform.

When to use it

PixelPicked can detect many scores and end states through DOM or canvas recognition. Games without a visible game-over screen, games with unusual rendering, and games that already know their exact internal score should use the Game Events SDK instead.

The SDK is automatically available as window.PixelPicked inside builds hosted by PixelPicked. The game reports events; the player securely attaches the signed-in account or anonymous player identity before PixelPicked updates personal bests, leaderboards, and active challenges.

Core calls

• PixelPicked.score(1250) reports the current score without ending the run.
• PixelPicked.gameOver(1250) reports the final score and ends the run.
• PixelPicked.level(8), timer(seconds), moves(count), accuracy(percent), collection(count), and streak(count) report other supported metrics.
• PixelPicked.success(value) and PixelPicked.failure(value) finish success/failure objectives.
• PixelPicked.challengeComplete(value) completes an SDK-backed challenge objective.
• PixelPicked.event(name, value, options) sends a custom event configured in the admin challenge detector.

What feedback can cover

• Overall experience and gameplay quality.
• Visual presentation, clarity, controls, difficulty, and performance.
• What the player liked and what created friction.
• Bugs, crashes, and contextual notes from the play session.

Feedback plus behavior

What early game testers say and what they do answer different questions. Structured feedback explains perception; Demo Build analytics show behavior. Used together, they help validate the game and give developers a more complete view of what to improve and what to preserve.

What can become a campaign

• A meaningful development milestone or reveal.
• A major update, new version, or substantial content drop.
• A new or updated Demo Build players can experience.
• The release of the game on its final distribution platforms.

What a campaign connects

A campaign brings the update, game page, Demo Build, followers, notifications, community response, and discovery together. Players can support and promote the moments they believe deserve attention, helping them travel beyond the existing follower base.

After the campaign

The game keeps its followers, content, and discovery presence. Campaigns add to the game's history rather than replacing it, so later updates can build on earlier momentum.

Discover more than finished listings

Discovery can begin with a recommendation, a playable demo, a ranking, a devlog, or community activity. Players see the game alongside the people, updates, and conversations around it.

Signals used across discovery

• Player taste and behavior across browsing, plays, follows, and skips.
• Genres, development stages, and game status.
• Devlogs, new Demo Builds, updates, and campaigns.
• Community follows, feedback, support, and promotion.
• Editorial selections and The Weekly Pixel newsletter.

Play before installing

When a Demo Build is available, players can experience a full build or a focused time-limited version in the browser before installing the final game.

Follow the development story

• Follow games that look promising and return to their evolving pages.
• Read devlogs and see mechanics, visuals, and decisions change over time.
• Receive meaningful updates about games you care about.

Shape what gets made

Players can respond to devlogs and share structured feedback after playing. Thoughtful responses help developers understand what is working, where friction appears, and which parts of the game are worth pushing further.

Promotion is not limited to release

Players can support meaningful milestones, major updates, Demo Builds, and releases. This gives attention to the moments that move a game forward, even when the final release is still some distance away.

Community and editorial reach

• Community support helps surface games and campaigns within PixelPicked.
• Curated selections can introduce strong work to people outside its current followers.
• The Weekly Pixel can highlight games, updates, and developer stories worth knowing about.

Developer and player experiences

A developer can still discover, follow, and play games. A player experience emphasizes discovery and participation, while the developer experience adds tools for managing games, content, Demo Builds, insight, and campaigns.

Meaningful notifications

• Devlogs and important development updates.
• New Demo Builds and campaign activity.
• Milestones, major updates, and releases.
• Relevant community interactions and responses.

Community expectations

• Represent games, progress, identity, and player experience honestly.
• Keep feedback specific, constructive, and relevant to the game.
• Do not manipulate community signals, impersonate others, harass people, or post spam.
• Use reporting tools when a game, devlog, response, or account violates platform standards.

Current access and pricing

PixelPicked is currently available at no cost during early access. The long-term revenue model, plans, and prices are still being developed. Current availability is not a permanent pricing commitment.