5 minute version of my talk on tokenization and immersion. Given at PolyConf

1. @jna_sh
InsertToken
Tokenisation & Immersion

2. </speaker>
@jna_sh
@jna_sh

3. </content>
<content>
@jna_sh
Braintree

4. @jna_sh

5. </content>
<content>
@jna_sh
Video Games

6. </content>
<content>
@jna_sh
What makes video games
effective?

7. @jna_sh

8. @jna_sh

9. @jna_sh

10. @jna_sh
Immersion

11. @jna_sh

12. @jna_sh
Seamless

13. @jna_sh
Developers need
immersion

14. @jna_sh

15. @jna_sh

16. @jna_sh

17. @jna_sh

18. @jna_sh

19. @jna_sh

20. @jna_sh

21. @jna_sh

22. @jna_sh

23. @jna_sh

24. @jna_sh
30%

25. @jna_sh

26. @jna_sh
Maintain the Magic

27. @jna_sh
Immersion is Fragile

28. @jna_sh

29. @jna_sh
We’ve killed the magic.

30. </content>
<content>
@jna_sh
Is there something that
can help us?

31. Spoilers:
yes

32. </content>
<content>
@jna_sh
Tokenization

33. </content>
<content>
@jna_sh
Sensitive data

34. </content>
<content>
@jna_sh
Sensitive data

35. @jna_sh

36. @jna_sh

37. @jna_sh

38. @jna_sh

39. @jna_sh

40. @jna_sh

41. @jna_sh
Keep it out of
application state.

42. @jna_sh
Secure Transport

43. @jna_sh
Tokenization is magic.

44. @jna_sh
Tactical Immersion

45. @jna_sh

46. @jna_sh
Narrative Immersion

47. @jna_sh

48. @jna_sh
Spatial Immersion

49. @jna_sh

50. </content>
<content>
@jna_sh
…But there’s one more
thing.

51. </content>
<content>
@jna_sh
Immersion not by
developers.

52. </content>
<content>
@jna_sh
But for developers.

53. </content>
<content>
@jna_sh
v.zero

54. @jna_sh

55. </content>
<content>
@jna_sh
New payment methods?

56. </content>
<content>
@jna_sh
No new code.

57. </content>
<content>
@jna_sh
No new builds.

58. </content>
<content>
@jna_sh
No app updates.

59. </content>
<content>
@jna_sh
Braintree uses tokenization
to immerse developers.

60. @jna_sh

61. </speaker>
@jna_sh
@jna_sh

62. @jna_sh
Thanks_ @braintree_dev