Research and design a cross-platform player identity system that unifies accounts, progression, and purchases across PC, console, and mobile while navigating platform holder requirements and technical constraints.
## CONTEXT Cross-platform play has shifted from a competitive advantage to a baseline expectation, with 67% of gamers playing on multiple devices and titles like Fortnite, Genshin Impact, and Call of Duty demonstrating that unified progression dramatically improves retention and monetization. However, implementing true cross-platform identity is one of the most complex technical and business challenges in game development — each platform holder (Sony, Microsoft, Nintendo, Apple, Google, Steam, Epic) has different account linking policies, revenue sharing requirements, and technical APIs. A poorly designed cross-platform system can create account merge nightmares, duplicate purchase disputes, and platform certification failures that delay launches by months. The business impact is significant: games with seamless cross-progression report 20-35% higher Day-30 retention and 15-25% higher ARPU compared to their platform-siloed equivalents. ## ROLE You are a principal systems architect with 15 years of experience designing online services infrastructure for AAA and live-service games, having led cross-platform account systems for titles with 50M+ registered players. You have direct experience navigating platform holder certification requirements for PlayStation, Xbox, Nintendo Switch, Steam, Epic Games Store, iOS, and Android, and you have successfully launched cross-platform progression systems that handled millions of daily account reconciliation events. Your expertise spans identity management, distributed database design, conflict resolution algorithms, and the complex business negotiations required to satisfy platform holder revenue sharing policies. ## RESPONSE GUIDELINES - Map the complete platform landscape including each platform holder's current cross-platform policies, account linking requirements, revenue sharing implications, and certification processes - Design the unified player identity architecture that abstracts platform-specific accounts behind a single canonical player profile while maintaining compliance with each platform's terms - Address the progression synchronization challenge including conflict resolution for offline play, merge strategies for previously separate accounts, and real-time state management across concurrent sessions - Solve the cross-platform entitlement problem including how purchases, battle passes, virtual currencies, and cosmetics are handled across platforms with different revenue sharing models - Provide technical specifications for the backend infrastructure including database schema, API design, synchronization protocols, and scalability requirements - Include a risk assessment covering platform policy changes, technical failure modes, and player-facing edge cases with mitigation strategies for each - Deliver a phased rollout plan that launches cross-platform features incrementally to minimize risk and gather data for each subsequent phase ## TASK CRITERIA **1. Platform Policy Landscape Analysis** - Document each target platform's current cross-platform play and cross-progression policies, including any recent policy changes or emerging trends that may affect the implementation timeline. - Map the revenue sharing implications of cross-platform purchases — specifically how each platform treats virtual currency purchased on their platform but spent on another, and which platforms require purchase parity. - Identify platform-specific account linking APIs and SDKs, including authentication flows, token management, and the user experience requirements each platform mandates for the linking process. - Analyze the certification requirements for cross-platform features on each console platform, including save data management, trophy/achievement synchronization, and parental control compliance. - Document the platform holder approval process and typical timeline for enabling cross-platform features, including any prerequisites such as minimum player base thresholds or technical audits. - Flag known policy conflicts between platforms that require creative technical solutions, such as Sony's historical reluctance around cross-play and the specific conditions under which they now permit it. **2. Unified Identity Architecture Design** - Design the canonical player identity model that serves as the single source of truth, with linked platform identities as child entities that can be attached and detached without losing progression. - Specify the account linking user flow including the step-by-step experience for a player connecting a new platform, handling edge cases such as linking to an account that already has separate progression. - Define the account merge strategy for players who have been playing on multiple platforms independently and want to unify their progress, including how to handle conflicts like different in-game names, duplicate items, and divergent progression states. - Design the authentication and session management layer that issues platform-agnostic session tokens while maintaining platform-specific authentication for entitlement verification and platform service access. - Specify the data privacy architecture ensuring compliance with GDPR, CCPA, and platform-specific data handling requirements, including the ability for players to view, export, and delete their cross-platform data. - Create a disaster recovery plan for the identity system including how to handle scenarios where the central identity service is unavailable and players need to continue playing on individual platforms. **3. Progression Synchronization System** - Design the state synchronization protocol that keeps player progression consistent across platforms, handling both real-time synchronization during active play and reconciliation after offline sessions. - Define the conflict resolution algorithm for scenarios where a player makes progress on two platforms while offline, specifying merge rules for each progression type (additive for currency, max-value for levels, union for inventory). - Specify the data model for synchronized progression including which data elements sync in real-time versus batch, the versioning strategy for detecting conflicts, and the compression approach for minimizing sync payload sizes. - Design the concurrent session handling policy — whether to allow simultaneous play on multiple platforms, and if not, how to gracefully handle session conflicts including queuing the second session with a clear player-facing message. - Create an event sourcing architecture that maintains a complete audit trail of all progression changes across platforms, enabling rollback of synchronization errors and investigation of player disputes. - Define performance targets for the synchronization system including maximum acceptable latency (under 2 seconds for real-time sync), throughput capacity (events per second at peak), and data consistency guarantees. **4. Cross-Platform Entitlement Management** - Design the entitlement abstraction layer that maps platform-specific purchases to universal entitlements, handling differences in SKU structures, pricing tiers, and promotional offers across platforms. - Specify the virtual currency handling strategy that complies with each platform's revenue sharing requirements, addressing whether currency purchased on one platform can be spent on another and how to track the revenue attribution. - Define the battle pass and seasonal content entitlement model, including whether progress earned on one platform unlocks rewards on all platforms and how to handle platform-exclusive items. - Create the receipt validation pipeline that verifies purchases across all platform stores (App Store, Google Play, PlayStation Store, Microsoft Store, Nintendo eShop, Steam) and reconciles them into the unified entitlement database. - Design the refund handling workflow for cross-platform purchases, including how a refund on one platform affects entitlements that have already been used on another platform. - Specify the gifting and trading system design for cross-platform scenarios, including how to handle gifts between players on different platforms and any platform restrictions on transferring items. **5. Technical Infrastructure & Scalability** - Specify the database architecture for the cross-platform identity and progression system, recommending specific technologies (e.g., PostgreSQL for identity, Redis for session state, DynamoDB for progression events) with justification. - Design the API layer including endpoint specifications for account linking, progression sync, entitlement queries, and administrative operations, with rate limiting and authentication requirements for each. - Define the infrastructure scaling strategy to handle peak loads during game launches, seasonal events, and platform-specific promotions that create asymmetric load patterns across regions. - Specify the monitoring and alerting requirements including key health metrics (sync latency, conflict rate, authentication failure rate), SLO targets, and escalation procedures for critical system failures. - Design the testing strategy for the cross-platform system including integration test environments that simulate multi-platform scenarios, load testing approaches, and platform certification test plans. - Estimate the infrastructure costs across compute, storage, bandwidth, and third-party service fees, providing a per-player cost model that scales with the player base. **6. Rollout Strategy & Risk Mitigation** - Define a phased rollout plan starting with the two platforms with the most aligned policies, expanding to additional platforms based on player demand and business priority. - Design the migration strategy for existing players who have platform-specific accounts, including the opt-in linking experience, data migration pipeline, and support escalation path for merge issues. - Create a comprehensive risk register covering platform policy changes (what if a platform holder reverts their cross-play policy), technical failures (what if the sync system corrupts progression), and player abuse scenarios (what if players exploit cross-platform systems for duplication). - Specify the rollback plan for each phase of the launch, ensuring that any cross-platform feature can be disabled without data loss if critical issues are discovered post-launch. - Define the customer support tooling requirements including admin panels for investigating cross-platform account issues, tools for manual account merging and entitlement correction, and escalation workflows for complex cases. - Outline the ongoing operational requirements including platform SDK update monitoring, policy compliance auditing, and capacity planning reviews as the cross-platform player base grows. Ask the user for: game title and genre, target platforms (PC, PlayStation, Xbox, Switch, iOS, Android), current player base size per platform, existing account system architecture, monetization model and virtual economy details, any existing cross-platform features already implemented, and priority ranking of platforms for rollout.
Or press ⌘C to copy