search
explore
subscribe
network
community
iTweet and 140 Proof
Setting up this application for future growth.
The steady increase in traffic means that we've had to spend extra time and money on iTweet's server in order to keep up with all the users. Hosting has graciously been sponsored by The Illusion Factory, but the monthly demand keeps increasing and it's clear that something needs to change. The growing nature of both the to-do list and the server cost has led me to think of ways in which iTweet can become self-sustaining. This app needs to start earning its keep, peoples! One thing that I've decided to try is the insertion of sponsored tweets by 140 Proof.
This company has a very unique system of advertising delivery, promising very targeted content in an unobtrusive format. How does that work? 140 Proof's system scans your (publicly available) tweets and delivers you an ad tailored to your location and/or favorite topics. This means that you'll see content that is interesting and relevant to you. And the ads come in tweet format so they fit right in with the flow of the app. Most of them are real tweets, from a real Twitter account, and behave pretty much like the other tweets in your stream - you can reply, favorite or retweet them too. (I'm giving these sponsored tweets a slightly different style so you can tell them from regular tweets.)
Since a lot of people have asked me what my plans for future development are, here's a nutshell version:
iTweet.net has no database behind it. It doesn't store any of your information, and only uses data from the Twitter (and TwitPic, bit.ly, etc) APIs. In order to do some more "interesting" stuff, such as multiple accounts, decent Lists and follower management, autocompleter, etc, I need to put a database behind the front end and rewrite a whole bunch of stuff. This will let me do a lot more *interesting* things with the app, as it currently operates within the exact constraints of the API.
My immediate goals for iTweet are this:
- Switch to OAuth - this will eliminate API limit hassles
- Database-driven back end
- Support for new APIs - RT, geolocation etc.
- Support for multiple accounts, other oft-requested features
- Support for internationalization (multiple languages)
Cheers, and thanks for helping to make my little project take off. As always the user community will directly influence the direction of future development. Please let me know your thoughts below or by contacting me directly - I'm interested in hearing what you have to say.
Reader Comments:
Although I usually hate ads, but I think this is a great idea. It doesn’t disguise and can easily be differentiated with a different “designed box”. As long as it doesn’t start coming in floods, I wouldn’t mind targeted ads in my stream.
However, it really should be a lot more targeted. I’m seeing like “spanish” or something in my stream which I can’t understand at all.
It’s a great effort on trying to monetize the system. You have made a quick step infront of Twitter founders. Good for you!
Colby, when I first saw an ad I thought it was Twitter. I went to Twitter.com and then I realized it was iTweet.net.
Not too intrusive, but I think not precisely targeted when you use Spanish.
Anyway, I think it´s a good move to get at least covered your expenses.
@ebrito
Hey Im all for it. One has to find a way to pay the bills. I like the idea how your are going to make them look a bit different so we know its from 140 Proof, so I won’t ban them. Keep up the great work Colby! Love your stuff!
I think there is a problem with some users when using itweet in firefox AND adblockplus. We are unable to see the timeline, just the loading image. I uninstall Adblock and it worked wonders. I tried with Opera and IE, and it worked as well. So, we firefox users who block ads can’t use our itweet anymore.
@Ankit - Just this week Twitter just added some new API error checking for too-long tweets. I will add this to iTweet.
@Belinda and @ebrito - Thanks for your feedback! I will talk to 140 Proof about their internationalization support.
@Captain Jack - thanks so much for your feedback and support!
@Lisa - thanks! I had become aware there were some people having problems with the site, but hadn’t been able to figure out what was causing it. I’ll find a way to fix that asap.
Hello I also liked your idea of monetization of the project. Maybe I would use your services, but if that will be involved Geolocation. For example displaying advertisements of Russian-speaking users from Belarus, Minsk.
Bye!
I have some problem with some users when using itweet in firefox AND adblockplus. We are unable to see the timeline, just the loading image. I uninstall Adblock and it worked wonders. I tried with Opera and IE, and it worked as well. So, we firefox users who block ads can’t use our itweet anymore.
We are unable to see the timeline, just the loading image. I uninstall Adblock and it worked wonders. I tried with Opera and IE, and it worked as well.
I’m seeing like turkish or something in my stream which I can’t understand at all.
For example displaying advertisements of Russian-speaking users from Belarus, Minsk.
Interesting way to monetize coby!! Itweet has been my preffered choice of using twitter from web and will continue to do so.the clear demarcation of sponsored tweets will make it un-obstrusive and given by the examples mentioned in the post, a few of them could be useful too
Wish you all the success for the future!!
PS:: Can you please try handling the 140 char extension part.Itweet ends up losing my tweet if it goes beyond 140 and i hit enter :-(