It is, of course, possible to find niches here, and we can of course
come up with ideas that could work. I certainly am not debating that.

But you have to admit that this is a big, big bomb to drop in the
development community; bigger than anything since *maybe* the Summize
acquisition, and the whole shebang was a lot smaller then.  And
Summize was doing work that most developers couldn't do, because of
the technical issues involved.

And I might also suggest that choice and diversity is generally a good
thing, even in areas you personally find boring. But perhaps not in
the financial sense for Twitter, which is why stuff like this happens.

It's not really just what was done, but *how* it was done that was
most disappointing. And I bet you didn't have anything to do with
that, so not much to say there.

Actually, I suspect iTunes is a great analogy, even with the other
apps you suggest. iTunes did destroy any competition in the primary
music playback app market, and I believe (anecdotally though) that it
dominates the lowest common denominator market -- also the largest
part of the market. I'll be happy to buy you a drink when Spotify and
and combined hit 50% of iTunes usage. They are the niche apps
along the lines you suggest we should be making.

Ed Finkler
AIM: funka7ron / ICQ: 3922133 /

On Apr 10, 12:20 am, Raffi Krikorian <> wrote:
> the way that i usually explain (the web site) is that it
> embodies one particular experience of "twitter". 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 experience -- 3rd party
> developers have taken those, and mimicked the experience.  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, spotify, etc., all exist and are doing
> things that itunes can't do.
> On Fri, Apr 9, 2010 at 7:26 PM, funkatron <> 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:
> > Have fun in SF next week, everybody!
> > --
> > Ed Finkler
> >
> > @funkatron
> > AIM: funka7ron / ICQ: 3922133 / 
> ><>
> > On Apr 9, 10:18 pm, Dewald Pretorius <> 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 <> wrote:
> > > > Before anyone rants, let me say congratulations Loren, and
> > congratulations
> > > > Twitter.  Awesome!  Totally awesome!
> > > > :-)
> > > > Tim.
> --
> Raffi Krikorian
> Twitter Platform Team

Reply via email to