There Should Be a Service for That
summary
Uses small shared backend services to run mobile games, including a shared backend that wraps push notifications, payments and CDN; a tiny remote-config client and a client-side A/B testing transporter; and integration with third-party analytics and dashboards for DAU, cohorts and conversion metrics. Compares feature sets and enterprise pricing (noting some services are too expensive) and argues that this central toolkit speeds iteration and simplifies operations.
AI-written summary · about
chapters (8)
- 0:00Service-based solutions
- 1:12Implementing service models
- 3:05Real-time monitoring
- 6:16Testing service APIs
- 9:03User engagement metrics
- 11:45Pricing & enterprise features
- 13:32Service reliability
- 15:33Future of service systems
related talks
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
32mSoftware development reimagined
30mFinding New Audiences for Your Mobile Games
54mScaling Web Services for Free to Play
32mBuilding Apps with an API-based Backend
20mFirebase, Analytics, Google, and Understanding How They Work Together
30mFirebase: The Power of Google in the Palm of Your Hand
34mMicro-services for a Billion people