Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Email Interfaces
    for your
Ruby Applications
About Me
Why an Email
 Interface?
Everyone has it.
Everyone gets it.
Inherent attention.
Gradual
engagement.
Embedded identity.
Resurrect dead data.
Other people’s
programming.
The actual mobile web.
Asynchronicity.
The need for speed.
It’s brutally productive.
Make the internet
  work for us.
The Downside
Poor fit
Power-users only
Support
headaches
Spam
No feedback
(Potentially)
   Slow
Styles of Interaction
Links
NetFlix
CraigsList
gCal
Reply
Google
Groups
Basecamp
Lighthouse
Command Line
Remember
 the Milk
I Want
 Sandy
3mindMe
Forwarding
TripIt
TrackMyShipments
Highrise
User-Generated
   Content
Posterous
Flickr
Rate It All
Elements of the
   Interface
The TO: address
TripIt
Tumblr
Posterous
3mindMe
The Subject
Hiveminder
Flickr
Posterous
The Body
Remember
 the Milk
TripIt
I Want Sandy
The Attachments
Backpack
Flickr
Posterous
This is how
 we do it
Receiving
Postfix
POP/IMAP
Lamson
Fetching
Postfix Filter
TMail::MailDir
Fetcher
Long-Running Process
Monit
Cron
Lockfile
Processing
TMail
mms2r
RESTfully
Astrotrain
Testing
Fixtures
Thanks!
• http://speakerrate.com/talks/1539
• http://delicious.com/deisinger/emailtalk
• Twitter: @deisinger
Upcoming SlideShare
Loading in …5
×

Email Interfaces for your Ruby Applications

1,541 views

Published on

  • Be the first to comment

Email Interfaces for your Ruby Applications

  1. 1. Email Interfaces for your Ruby Applications
  2. 2. About Me
  3. 3. Why an Email Interface?
  4. 4. Everyone has it.
  5. 5. Everyone gets it.
  6. 6. Inherent attention.
  7. 7. Gradual engagement.
  8. 8. Embedded identity.
  9. 9. Resurrect dead data.
  10. 10. Other people’s programming.
  11. 11. The actual mobile web.
  12. 12. Asynchronicity.
  13. 13. The need for speed.
  14. 14. It’s brutally productive.
  15. 15. Make the internet work for us.
  16. 16. The Downside
  17. 17. Poor fit
  18. 18. Power-users only
  19. 19. Support headaches
  20. 20. Spam
  21. 21. No feedback
  22. 22. (Potentially) Slow
  23. 23. Styles of Interaction
  24. 24. Links
  25. 25. NetFlix
  26. 26. CraigsList
  27. 27. gCal
  28. 28. Reply
  29. 29. Google Groups
  30. 30. Basecamp
  31. 31. Lighthouse
  32. 32. Command Line
  33. 33. Remember the Milk
  34. 34. I Want Sandy
  35. 35. 3mindMe
  36. 36. Forwarding
  37. 37. TripIt
  38. 38. TrackMyShipments
  39. 39. Highrise
  40. 40. User-Generated Content
  41. 41. Posterous
  42. 42. Flickr
  43. 43. Rate It All
  44. 44. Elements of the Interface
  45. 45. The TO: address
  46. 46. TripIt
  47. 47. Tumblr
  48. 48. Posterous
  49. 49. 3mindMe
  50. 50. The Subject
  51. 51. Hiveminder
  52. 52. Flickr
  53. 53. Posterous
  54. 54. The Body
  55. 55. Remember the Milk
  56. 56. TripIt
  57. 57. I Want Sandy
  58. 58. The Attachments
  59. 59. Backpack
  60. 60. Flickr
  61. 61. Posterous
  62. 62. This is how we do it
  63. 63. Receiving
  64. 64. Postfix
  65. 65. POP/IMAP
  66. 66. Lamson
  67. 67. Fetching
  68. 68. Postfix Filter
  69. 69. TMail::MailDir
  70. 70. Fetcher
  71. 71. Long-Running Process
  72. 72. Monit
  73. 73. Cron
  74. 74. Lockfile
  75. 75. Processing
  76. 76. TMail
  77. 77. mms2r
  78. 78. RESTfully
  79. 79. Astrotrain
  80. 80. Testing
  81. 81. Fixtures
  82. 82. Thanks! • http://speakerrate.com/talks/1539 • http://delicious.com/deisinger/emailtalk • Twitter: @deisinger

×