Pro Yearly is on sale from $80 to $50! »

Google Cast, when one screen is not enough

D4be3ad792b57408b3ab6fe98caef08e?s=47 danybony
November 16, 2019

Google Cast, when one screen is not enough

When we develop mobile apps or websites, our users can interact with them using a large selection of displays, but there is one that is often ignored: the TV one.
In this talk I'll give and introduction to Google Cast, seeing how it can be used to to create a more central, prominent space for the most important content of your service.

D4be3ad792b57408b3ab6fe98caef08e?s=128

danybony

November 16, 2019
Tweet

Transcript

  1. Google Cast When one screen is not enough Daniele Bonaldo

  2. None
  3. None
  4. None
  5. Receiver Sender Sofa

  6. Receiver

  7. Receiver implementation Default Custom Styled

  8. Touch support

  9. Sender

  10. Cast button

  11. Cast button

  12. No receiver detected Receiver detected Connecting Connected

  13. Cast button

  14. Cast dialog

  15. Cast dialog

  16. Expanded controller

  17. Mini controller

  18. Notification

  19. Lock screen

  20. Volume control

  21. Playing intent

  22. Sender-receiver interaction

  23. Discovery

  24. Connect and play Play and Connect Vs

  25. Playback control

  26. Playback control

  27. Cast stop

  28. Custom messages { “author”: “…”, “views”: “…”, }

  29. Cast console

  30. Cast console https://cast.google.com/publish

  31. Cast console

  32. Cast console

  33. Unpublished apps and test devices

  34. Testing https://developers.google.com/cast/docs/testing

  35. Debugging https://developers.google.com/cast/docs/debugging

  36. Conclusions

  37. Conclusions • Cast Application Framework • Covers most common use

    cases • Highly customisable • Multiple options for receiver • Consider multiple senders • Custom messages for richer experiences • Manual testing checklist
  38. Daniele Bonaldo Thank You! @danybony_ danybony danielebonaldo.com