How to build a Top 10 game on Facebook
•
10 likes•7,574 views
The document discusses best practices for building large-scale Facebook games at the company wooga. It begins by outlining some of the challenges of scaling games to millions of users, including complexity, the large scale, and features constantly changing. The company's philosophy is then discussed as being very agile, prioritizing individuals, working software, customer collaboration, and responding to changes. Teams at wooga work independently in small groups with clear responsibilities and close communication. Examples of practices discussed include unit testing, service-oriented architecture, and continuous integration. Unit testing is said to improve encapsulation, act as documentation, and provide a safety net. Mock objects are also mentioned as a way to simulate dependencies in tests.
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (19)
Similar to How to build a Top 10 game on Facebook
Similar to How to build a Top 10 game on Facebook (20)
More from Wooga
More from Wooga (20)
Recently uploaded
Recently uploaded (20)
How to build a Top 10 game on Facebook
- 1. + Scaling Massive Flash-‐Projects -‐How to build a Top 10 game on Facebook-‐ Philipp Moeser (Co-‐Founder & CTO) Ma8es Groeger (Senior Engineer)
- 2. n Teams & tools Teams and Tools you need to build a Top Game you need to build a big game 2
- 3. wooga – world of gaming About wooga Founded January 2009 Philipp Moeser Funding of $32m -‐Co-‐Founder & CTO-‐ InternaJonal team of 100 from over 20 countries in Berlin Ma8es Groeger -‐Senior Engineer-‐ Key stats 6 games on Facebook, 39 million acJve users 3rd biggest social game developer worldwide 70% of users are female (age 20-‐60) 3
- 4. Agenda I. Challenges II. Our philosophy III. Environment IV. Best pracJce examples V. Summary 4
- 5. Agenda I. Challenges 5
- 6. § Launched February 2010 § 12th Facebook game § 10 m monthly acJve user (MAU) § 800 engineering days invested
- 7. § Launched May 2010 § 14th biggest Facebook game § 8,7 m MAU § 1200 engineering days invested so far
- 8. § Launched August 2011 § Top 10 fastest growing game § 3 m MAU § 500 engineering days invested so far
- 9. How do games differ n Quick prototyping n Features get killed n High complexity 9
- 10. Challenges summary n Complex n Large n Moving target 10
- 11. Agenda I. Challenges II. Our philosophy 11
- 12. Agile! 12
- 13. Why agile? 13
- 14. development manifesto for agile soJware 14 http://10yearsagile.org/wp-content/uploads/2011/01/background.jpg/
- 15. Our philosophy: agile n Individuals and interacJons over processes and tools n Working socware over comprehensive documentaJon n Customer collaboraJon over contract negoJaJon n Responding to changes over following a plan 15
- 16. Our philosophy: agile n Individuals and interacJons over processes and tools n Working socware over comprehensive documentaJon n Customer collaboraJon over contract negoJaJon n Responding to changes over following a plan 16
- 17. talk 17
- 18. Our philosophy: agile n Individuals and interacJons over processes and tools n Working socware over comprehensive documentaJon n Customer collaboraJon over contract negoJaJon n Responding to changes over following a plan 18
- 19. prototypes 19
- 20. Our philosophy: agile n Individuals and interacJons over processes and tools n Working socware over comprehensive documentaJon n Customer collaboraJon over contract negoJaJon n Responding to changes over following a plan 20
- 22. Our philosophy: agile n Individuals and interacJons over processes and tools n Working socware over comprehensive documentaJon n Customer collaboraJon over contract negoJaJon n Responding to changes over following a plan 22
- 23. Collaborate. best soluPon 23 http://www.financialmeltdown.com/the_solution.html
- 24. Why agile? 24
- 25. Philosophy summary n Internal communicaJon (instead of processes) n Protoyping & iteraJng n External communicaJon (instead of contracts) n Flexibility 25
- 26. Agenda I. Challenges II. Our philosophy III. Environment 26
- 27. Independence 27
- 28. no frameworks 28
- 29. no processes 29
- 30. no manager 30
- 31. Responsibility 31
- 32. few roles 32
- 33. small team 33
- 34. CommunicaPon 34
- 35. one room one room 35
- 36. Team summary n Independence n Responsibility n CommunicaJon 36
- 37. Agenda I. Challenges II. Our philosophy III. Environment IV. Best pracJce examples 37
- 38. And now... 38
- 39. hands on 39
- 40. Agile rocks 40
- 41. danger 41
- 42. 42 http://www.lebensmittelfotos.com/2008/07/20/spaghetti-und-pesto/
- 43. 43
- 44. Examples n Unit tesJng n Service layer n ConJnuous integraJon 44
- 45. Examples n Unit tesJng n Service layer n ConJnuous integraJon 45
- 46. What is unit tesJng? A C B 46
- 47. One test per class A C B T T T 47
- 48. change of perspecPve 48
- 50. encapsulation safety net 50 http://cheejyg.deviantart.com/art/HortPark-Recycling-bin-174639710
- 51. acts as documentaPon encapsulation safety net 51 http://cheejyg.deviantart.com/art/HortPark-Recycling-bin-174639710
- 52. 52
- 53. 53
- 54. 54
- 55. 55
- 59. 59
- 60. Mock objects n Simulated objects with controlled behaviour n Same interface as the real object n SuggesJng: Mockito Flex h8ps://bitbucket.org/loomis/mockito-‐flex 60
- 61. Example A C B 61
- 62. Dependency A C B T 62
- 63. Mock dependency A M B T 63
- 64. 64
- 65. Example IUser A Energy Controller Reward Assigner T 65
- 71. Examples n Unit tesJng n Service layer n ConJnuous integraJon 71
- 72. Client communicaJon Client JS Backend Facebook 72
- 73. Keep your client independent Client Service Layer JS Backend Facebook 73
- 74. Now you can fake everything Client Service Layer Fake Fake Fake JS Backend Facebook 74
- 75. Benefits? 75
- 76. easier to test 76
- 77. target new platforms 77
- 78. work offline 78
- 79. How to implement? 79
- 80. 80
- 81. decoraPon 81
- 82. 82
- 86. Compiler Constants 86
- 87. Compiler Constants 87
- 88. Compiler Constants 88
- 89. Compiler Constants 89
- 90. Compiler Constants 90
- 91. Always build two versions??? 91
- 92. Examples n Unit tesJng n Service layer n ConJnuous integraJon 92
- 93. What it does n ConJnuously applies quality control n Runs on a server n AutomaJcally builds and deploys n Jobs: snapshot, nightly, release 93
- 94. 94
- 98. Test coverage 98
- 99. Benefits? 99
- 100. runnable version 100
- 101. run all tests runnable version 101
- 102. runs all tests arPsts see their changes 102
- 103. runs all tests perform heavy operaPons 103
- 104. Wrap-‐up: best pracJce n Special requirements for code n Keep up producJon speed n Keep your client independent n Automate as much as possible 104
- 105. Agenda I. Challenges II. Our philosophy III. Environment IV. Best pracJce examples V. Summary 105
- 106. I. Challenges II. Our philosophy Internal communication (instead of processes) Internal communication | Protoyping & iterating Large | complex Protoyping & iterating | External External communication (instead of contracts) | moving target communication | Flexibility Flexibility III. Environment! IV. Best pracPce examples Independence | responsibility | communication Unit testing | service layer | cont. integration
- 107. wooga.com/jobs 107
- 108. Thank you! Philipp Moeser CO-‐Founder & CTO wooga Ma^es Groeger Senior Engineer at wooga @Ma8esGroeger Twi^er: @wooga wooga.com/jobs 108