Presented at FITC's Web Unleashed 2016 in Toronto by Jane Kim, BaubleBar FITC produces events for digital creators in Toronto, Amsterdam, NYC and beyond Save 10% off any of our events with discount code 'slideshare' Check out our events at http://fitc.ca or follow us at https://twitter.com/fitc Overview Personal data can be super useful, but usually keeping track of anything it involves a lot of unused mobile apps and expensive trackers. What if you could just… code your own? Using Hoodie, an awesome front end framework with a noBackend philosophy, Jane created a personal data tracking app that that helps her track anything and everything. With the magic of PouchDB she can access all her data points in real time and write tests for continuous integration that notify her if she’s adulting properly or not (TAP… literally everything) Of course, just because your tests fail doesn’t mean YOU are a failure. Jane will tell you how she uses this tool to track personal goals (meditate once a day, how often she drinks water) and how she’s feeling (how bad is her arm pain? How happy is she today?) to examine trends in her life. By the end of this talk you’ll be able to use or extend the same app for all the things you want to track and achieve. Target Audience Anyone who is interested in learning a new framework or new back-end technologies Assumed Audience Knowledge Javascript Five Things Audience Members Will Learn PouchDB Hoodie API’s Self care Testing

1. life-api
jane kim
@janecakemaster

4. being an adult is hard
😔

11. 😟😖😭

12. fitness trackers
and
apple watches

13. fitness trackers
and
apple watches
😒

15. personal data

16. personal data
+
code

17. personal api?

18. life-api
DIY personal tracking

19. what do you want to track?

20. 🍖->💩
🍣->☠
🚴->+

21. 😟😪💀😀

22. become a better
photographer
📸

24. good habits are built with
with incremental wins

25. i have the data
now what?

26. configurable goals
- incremental
- long term
- small wins
+ +

27. let's write a personal api

28. what's an API?

29. what's a RESTful API?

30. REpresentational
State
Transfer

31. Resource-based service

32. Constraints:
uniform interface
stateless
cacheable
client-server
layered system

33. REST isn't going away

34. server
routes
data store

36. logs are made up of inputs

37. every input is a time input
with an optional text field

38. Tips

39. Use plurals
/logs/time-bedtime
/inputs/

40. Short segments
Granular resources
/logs
/inputs

41. Mirror backend structure
PUT /logs/time-bedtime
_logs.put(log) //pouchdb

42. Tools

43. constant WIP

44. thx tronno!
@janecakemaster
https://github.com/janecakemaster/life-api