Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Playing With WatchConnectivity for ~24 hours

Playing With WatchConnectivity for ~24 hours

This is ~5 minutes pitch on which I share a few thoughts about playing with WatchConnectivity APIs - and other cool stuff - for the first 24 hours in order to make an unofficial app for the CocoaHeads Conference.

829e745fc00d15823f96bffb92577d51?s=128

Matheus Albuquerque

November 10, 2016
Tweet

More Decks by Matheus Albuquerque

Other Decks in Programming

Transcript

  1. @ ythecombinator #BEPiD playing with Watch Connectivity for ~24 hours

  2. None
  3. OUR GOAL an app where you access all of the

    most awaited event of the year: the COCOAHEADS CONFERENCE 2016; with information about the venue, speakers, schedule, sponsors, partners... (and during the event, you can even tweet about the talks!)
  4. None
  5. OUR GOAL an app where you access all of the

    most awaited event of the year: the COCOAHEADS CONFERENCE 2016; with information about the venue, speakers, programming, sponsors, partners... (and during the event, you can even tweet about the talks!) ~24 hours
  6. OUR STACK JSON Watch Connectivity

  7. DIFFICULTIES & LESSONS LEARNT

  8. None
  9. SERVER JSON Watch Connectivity

  10. #1 we all must have a quick back-end for prototyping

  11. https:// github.com/ typicode/ json- server

  12. https:// www.get post man .com

  13. iOS JSON Watch Connectivity

  14. #1 Alamofire + SwiftyJSON =

  15. #2 you must keep as much processing as possible here

  16. #3 you must keep as much depende ncies as possible

    here
  17. watchOS JSON Watch Connectivity

  18. #1 the simulator makes you forget that you can rely

    on an awful connecti on
  19. the simulator adds some latency to the requests but response

    times on-device can sometimes be quite slower !
  20. #2 optimize your design for a constrai ned as f*ck

    screen
  21. #3 I can just update my views as often as

    I want
  22. #1 the simulator makes you forget that you can rely

    on an awful connecti on DON’T YOU FORGET THIS
  23. #4 keep all session data in a single class

  24. #5 think very well about message -passing strategy

  25. #6 think very well about devices states handling

  26. None
  27. THINK ABOUT & EXPERIMENT

  28. Activity Rings

  29. PROMISES

  30. Functional- Reactive- Programming

  31. NSURLSession

  32. AND SO…

  33. None
  34. None
  35. None
  36. None
  37. ✓ Watch Connectivity × Complications

  38. 'Que Deus tenha misericórdia deste App'

  39. SORRY! (not that sorry)