TwitFitLog: Startup Weekend SF '09 Demo

551 views

Published on

Our team's demo from San Francisco Startup Weekend 2009, a Twitter-based fitness log.

Published in: Technology, Sports
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
551
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

TwitFitLog: Startup Weekend SF '09 Demo

  1. 2. team of five includes:
  2. 3. 1 with 1000+ Twitter followers,
  3. 4. 1 joined Twitter yesterday,
  4. 5. 3 marathon finishers,
  5. 6. 1 who lost 100 lbs.,
  6. 7. 2 triathletes…
  7. 8. ...and the inventor of the fitness donut.
  8. 9. (and fitness pizza)
  9. 10. (and fitness coconut cream pie)
  10. 11. Three MIT graduates,
  11. 12. an MD,
  12. 13. a CSCS,
  13. 14. a trading card entrepreneur,
  14. 15. a couple of startup veterans,
  15. 16. a researcher from a mobile think tank,
  16. 17. the author of a 1993 Internet book,
  17. 18. a product manager at Half.com and Amazon.com,
  18. 19. and a Ruby geek.
  19. 20. … but we didn't finish coding a demo for Sunday night.
  20. 21. So…what did we do?
  21. 22. “ I just worked out and am not near a computer, but I want to log it before I forget, and share my progress with friends….”
  22. 23. Use Twitter via text or web: @fitlog #run 3 miles @fitlog #bike 56 miles @fitlog #prostrate 108 @fitlog #pushup 23
  23. 24. records your tweets in a database and displays a web page of your workouts over time.
  24. 25. We brainstormed ideas, use cases, features, markets, monetization and more
  25. 26. Captured in a wiki http:// fitlog.pbwiki.com
  26. 27. Narrowed the scope to what we thought we could implement in a weekend...
  27. 28. Set up a domain, email, frameworks, and an equity agreement.
  28. 29. Created a logo and mockups, then started coding... (which you've heard the results of)
  29. 34. next …
  30. 35. We'll meet every two weeks, and contribute in the evenings and weekends as available
  31. 36. Release features frequently, use A/B testing (and the like) look to feedback from users to focus as we iterate.

×