Skip to content

Decisions & TODOs

Applied Decisions

These items from the original draft have been integrated into the documentation:

DecisionApplied In
Like/dislike feature is included from day oneFrontend (player footer), Data Model (events + rating metric)
Developer portal will also use iframes (consistent architecture)Game Sourcing, Architecture
Documentation is written in EnglishAll files
10% exploration slots are available on Home, category, and game detail page recommendations, but not on author pagesExploration & Ranking
On mobile, games launch in fullscreen with an explicit Play button (no auto-play)Frontend (responsive behavior)
On desktop, games auto-play when visiting the game pageFrontend (responsive behavior)
Tag badges (New, Trendy) appear as small icons in the top-left corner of game cardsFrontend (game card component), Data Model (tags)
One backend service per domain from the startArchitecture
Only one build per game in MVP, but build structure supports multipleGame Sourcing

Open Questions

Items that need further discussion or are deferred:

ItemStatusNotes
GDPR complianceDeferredNot addressed in MVP. Needs review before launch (cookie consent, data retention, right to deletion)
Ranking algorithm weightsTo defineWhich metrics feed into ranking and with what weights? Needs data to calibrate
Pagination vs infinite scrollTo decideBoth mentioned as options. Need to pick one and define UX behavior
Crash Rate detectionDeferredDepends on whether GameDistribution fires gameplay_stop on page exit. Needs testing
Mean FPS measurementDeferredFeasibility depends on canvas/WebGL access within iframes. May not be possible with broker games
Updated tagDeferredPlanned but not enabled in MVP. Needs definition of “update” for broker-sourced games
Login / accounts systemDeferredPlaceholder in header. No spec yet
Ad integration detailsTo defineshow_ad event exists but ad provider, placement strategy, and revenue model are not specified
Search implementationPartially resolvedMVP: PostgreSQL ILIKE + tsvector. Growth: Meilisearch. See Architecture → Tech Stack and Scaling → Search. Still open: autocomplete UX details, fuzzy matching threshold
Language / i18nTo defineLanguage selector in footer but no specification of supported languages or translation workflow
Ranked game demotionTo decideCan a Ranked game be demoted back to Exploration if metrics drop? Options: no demotion (poor games sink in rankings), auto-demotion below threshold, manual admin-only demotion. See Exploration & Ranking → Demotion
Author URL formatResolvedAuthor pages use slug-based URLs (/authors/:slug). See API Reference