There is a lot of merit in your point of view with regards to one's
But, what that also means is the death of the ecosystem as we know it.
The ecosystem as we know it used to develop "for" Twitter, enhancing
the Twitter offering.
What you're proposing is a radical change, where one does not develop
"for" Twitter to enhance their service, but where one simply exploits
their service to enhance your own core (it's a very good strategy, by
Coming back to the acquisition, if this strategy of Twitter runs its
course, innovation of Twitter is going to be greatly stifled. Most
developers will stop developing new things that enhance the Twitter
Apart from the initial 140-character service, Twitter has not yet
innovated anything. Everything they have, subsequent to the initial
base service, has been things others have innovated for them, or ideas
they got from somewhere else. And now they've stifled or at least
discouraged those innovators. Oh, look, is that a hole in Twitter's
On Apr 10, 12:44 pm, Jesse Stay <jesses...@gmail.com> wrote:
> In support of what Raffi is saying, I think too many apps are "supports" for
> Twitter (some call it "filling holes"). I think the more beneficial, and
> long-term advantageous approach is instead to make Twitter a "support" for
> your application. I hope this isn't seen as spam, but I wrote about this
> last night in where I suggest we re-evaluate what our "cores" are based
> The Twitter app ecosystem is far from dead, is still thriving - we just need
> to re-evaluate where our cores are based. I think Twitter has drawn the
> line in the sand on what their core is. It's time we adjust ours so we're
> using Twitter as a complement, rather than the other way around. Just my
> $.02 - see you at Chirp!
> On Fri, Apr 9, 2010 at 10:20 PM, Raffi Krikorian <ra...@twitter.com> wrote:
> > the way that i usually explain twitter.com (the web site) is that it
> > embodies one particular experience of "twitter". twitter.com needs to
> > implement almost every feature that twitter builds, and needs to implement
> > it in a way that is easy to use for the* lowest common denominator of user
> > *. this now also holds for the iphone. so, one possible answer for how
> > to innovate and do potentially interesting/lucrative/creative things is to
> > simply not target the lowest common denominator user anymore. find a
> > particular need, and not the generic need, and blow it out of the water.
> > what i am most interested in seeing is apps that break out of the mold and
> > do things differently. ever since i joined the twitter platform, our team
> > has built APIs that directly mirror the twitter.com experience -- 3rd
> > party developers have taken those, and mimicked the twitter.comexperience.
> > for example, countless apps simply fetch timelines from the API
> > and just render them. can we start to do more creative things?
> > i don't have any great potentials off the top of my head (its midnight
> > where i am now, and i flew in on a red-eye last night), but here are a few
> > potential ones. i'm sure more creative application developers can come up
> > with more. i want to see applications for people that:
> > - don't have time to sit and watch twitter 24/7/365. while i love to
> > scan through my timeline, frankly, that's a lot of content. can you
> > summarize it for me? can you do something better than chronological
> > sort?
> > - want to understand what's going on around them. how do i discover
> > people talking about the place i currently am? how do i know this
> > restaurant is good? this involves user discovery, place discovery,
> > content
> > analysis, etc.
> > - want to see what people are talking about a particular tv show, news
> > article, or any piece of live-real-world content in real time. how can
> > twitter be a "second/third/fourth screen" to the world?
> > perhaps the OS X music playback app market is a poor example? sure
> > itunes is a dominant app, but last.fm, spotify, etc., all exist and are
> > doing things that itunes can't do.
> > On Fri, Apr 9, 2010 at 7:26 PM, funkatron <funkat...@gmail.com> wrote:
> >> Twitter did this to BB clients too, today.
> >> You think this is the last platform they'll do an Official Client on?
> >> Take a look at the OS X music playback app market to see the future of
> >> Twitter clients.
> >> Here's the shirt for the Chirp keynote:http://spaz.spreadshirt.com/
> >> Have fun in SF next week, everybody!
> >> --
> >> Ed Finkler
> >> @funkatron
> >> AIM: funka7ron / ICQ: 3922133 /
> >> XMPP:funkat...@gmail.com<xmpp%3afunkat...@gmail.com>
> >> On Apr 9, 10:18 pm, Dewald Pretorius <dpr...@gmail.com> wrote:
> >> > It's great for Loren.
> >> > But, there's a problem, and I hope I'm not the only seeing it.
> >> > Twitter has just kicked all the other developers of Twitter iPhone
> >> > (and iPad) clients in the teeth. Big time. Now suddenly their products
> >> > compete with a free product that carries the Twitter brand name, and
> >> > that has potentially millions of dollars at its disposal for further
> >> > development.
> >> > It's really like they're saying, "We picked the winner. Thanks for
> >> > everything you've done in the past, but now, screw you."
> >> > This would not have been such a huge deal if the developer ecosystem
> >> > did not play such a huge role in propelling Twitter to where it is
> >> > today.
> >> > Please correct me if I'm wrong.
> >> > On Apr 9, 10:41 pm, Tim Haines <tmhai...@gmail.com> wrote:
> >> > > Before anyone rants, let me say congratulations Loren, and
> >> congratulations
> >> > > Twitter. Awesome! Totally awesome!
> >> > > :-)
> >> > > Tim.
> > --
> > Raffi Krikorian
> > Twitter Platform Team
> >http://twitter.com/raffi- Hide quoted text -
> - Show quoted text -
To unsubscribe, reply using "remove me" as the subject.