Cross-Platform Game Development With Rails

Transcript

1. Cross-Platform Game Development With Rails Insights from the trenches
2. @caueguerra caue@uken.com cauê guerra
6. [demo]
8. 25 million installs
9. 2 engines
10. 8 titles
11. top 25
12. why HTML5?
13. Facebook Blackberry Android iPhone iPad 1. reaches more people
14. 2. easy to add new features
15. 3. easier to maintain
16. before we get started...
17. myths
18. [demo]
20. front-end tricks
21. 1. loading screen
22. 2. sprites
25. 3. adapt
29. 4. creating maps
30. http://www.mapeditor.org/
32. architecture
33. game SDKs payments auth ads notifications ...
34. game payments auth ads notifications ... game game REST Services API calls
35. game payments auth ads notifications ... game game REST Services
36. game engine assets engine API calls game engine assets game engine assets game engine assets game engine assets
38. let’s dig in...
39. Payments device user makes a purchase provider game validation
40. Payments device user makes a purchase provider service validation game
41. user auth user does not need username/password device has udid/uuid/android_id Game users devices auth
42. what if I want to know which users play more than one game?
43. what if I want to change the auth logic?
44. auth system game credentials user_id
45. user device account identifier device identifier device account identifier identifier
46. use as few SDKs as possible
47. prefer server-to-server integrations
48. backend tricks
49. 1. retry silently
50. 2. features on/off
51. 3. roll-out plan
52. final tips
53. 1. make it social
54. 2. engage your users in the first minutes
55. 3. A/B test as much as you can
56. 4. have an awesome support team
57. in conclusion
58. 1. it is just a webapp
59. 2. it doesn’t need to be too fancy
60. 3. a good idea is better than good graphics
61. 4. you can do it
62. Thank you!
63. Questions?
64. uken.com/jobs