1. Scalability
   1. Access twitter API from web browser, where possible
   2. Celery instances
      1. types
         1. CPU-intense
            1. boilerpipe
            2. text algorithms
            3. TTS
         2. traffic-intense
            1. RSS/twitter scraping
            2. HTML downloading
            3. images downloading & checking
   3. Mailing, spam filters issue
      1. Some research needed
         1. set up mailing properly
         2. get to google/etc whitelists
            1. ???
         3. keep track of quality
2. Better UI (MVC)
   1. Technologies
      1. Backbone.js
      2. templates on client
         1. dust.js
      3. modular JS
         1. browserify
      4. socket.io
         1. server
            1. Tornado?
            2. native socket.io (node.js)?
         2. client
      5. REST API
         1. for web app
         2. for iOS app
   2. Architecture
      1. Views, models on client
      2. templates on client
      3. modular JS
      4. REST resources
   3. Challenge
      1. Really good UI is not so easy to implement
3. Quality & complexity
   1. Keep track of technical debt
   2. Maintain some conceptual documentation
4. Twitter functions
   1. State I
      1. View
      2. Trends
      3. Retweet
      4. Edit & retweet
      5. New
      6. Delete
      7. Unfollow
      8. Error handling
         1. fav/unfav conflict
            1. custom twitter app won't specify errors http://joxi.ru/BLmGplKtwk1v2l
            2. tweetdeck: updates statuses in real time
   2. Stage II
      1. Direct messages