(this is page 46 of 121)





Latest

As the count of App Store applications climbs from 15,000 to 20,000, one of my favorite pass times has become going to look at the new types of applications being released. While all of the numbers are climbing in the right direction, there is one metric where we seem to be a little stuck: the types of innovation that new apps are introducing. And by innovation I mean new types of interactions, with Shazam being the perfect example of something so cool (and previously impossible) that people who see it are left with afterimages of the future bouncing in their vision.

Is this apparent lack of this type of innovation due to the straightjacket of what the SDK allows developers to do or is it just representative of the kinds of things that a mainstream market expects from a pocket computer?

Charles is keeping a good progress report on how the iPhone platform is growing over time, but looking at the big pie chart in the middle of his post, you'd think that the iPhone is all about games, entertainment, and various different kinds of verticalized todo lists. Where are the new Shazams? How about more applications that combine the GPS with the various sensors on the device to help people contextualize their activities with the net in a better way?

Another observation: as the platform attracts more developers, the overall quality and "snappiness" of the apps seems to be going down. This is to be expected, but the result is that I've seen a few native apps as of late that actually seem to take longer to get to functional than it does to load webpages in mobile Safari. If this trend continues, I'm sure that folks might get to the point where they become afraid of installing yet another gas tracking application.

Video capture. Background processing. Multi-tasking. API access to the Bluetooth radio. Notifications. I'm going to guess that opening up 50% or more of these avenues for interaction will unleash a new class of apps from developers. I just hope it happens soon.

Update: Now this is the kind of innovation I was thinking about (if it works).
Comments Permalink

This crazy silliness of Twitter taking over a realtime version of what Google has done for webpages has got to stop. Yes it is a great service that has created a valuable layer abstraction between people's extended and overlapping addressbooks that can sometimes deliver an awesome level of serendipitous shared context in close to realtime. Yes it further lowers the bar for "publishing" by continuing to blur the distinction between communication and content creation.

But at the end of the day, it's just a very thin little app with a medium number of people on it— still far from crossing into the mainstream.

And most important of all, as my friend Andy recently wrote, disruptive innovation does not happen in isolation of the incumbents, and in this case Google would be absolutely idiotic not to be paying attention to the value of realtime indexing of status updates. And unfortunately for Twitter, once they do I think it will be easy for them to add realtime to search (or any of their other products) and suck the unique power of Twitter right out from under them.

Finally, on the $50MM incremental investment as proof that Twitter is going to be "something huge." Venture guys are not stupid and in this new climate most of the ones in the consumer online space have turned into momentum investors where ever deal that shows any real adoption traction is still getting bid up too much. In this case though, I'd be willing to bet that one of the new investors has a real strong "feeling" that Twitter is going to be bought, either by Google or Microsoft in the next 12 months. It won't be a homerun investment for them— but it will not be bad and also help to garner their fund more street cred in the consumer online space.

Because one thing is clear to me— Twitter is not a billion dollar business about to happen. It is an interesting tweak that belongs inside one of the big information portals and at this very moment I am sure there are people at each of these big companies tweaking their "Twitter killer" strategies (or getting their M&A ducks in a row).

Comments Permalink

Yesterday I wrote about the need for a cron in the cloud and ended with the hope that someone builds a scalable way for periodic processes to run in much the same way that AppEngine allows for request-reponse interactions (turns out that it is already in the plan for AppEngine).

There are obvious reasons why a distributed scalable job manager is a great service, but today I want to pick up on why a common sandbox for all of the world's cron jobs might be a really interesting thing to develop.

My inspiration for my view of a cron in the cloud was really influenced by a recent talk I heard from my newest favorite author, Daniel Suarez (of Daemon fame) on "Bot Mediated Reality." Daniel is quickly coming to be regarded as someone who can pick out the faint outlines of the near future from existing technologies and in this talk he does not disappoint when he takes on the implications of the dangerous mix of society's ruthless quest for efficiency with automated programs deployed to take actions over a world whose interface is increasingly being standardized by web forms, APIs, and other such disinter-mediators of human judgment.

In his world, left unchecked, these bots will continue ruthlessly running on schedule taking first order actions that will cause the continued centralization of power in the hands of the few people capable of maintaining a semblance of control over the vast bot nets currently working for bad (DDOS style) and good (automated trading systems). Suarez's answer to avoiding the coming Judgement Day where the machines take over revolves around using richer interfaces to distinguish human from machine and forming committees of humans to control the types of bots we allow into a more secure and verifiable Internet (the "Dark Net" as he calls it).

But what if instead of doing that (or before getting there), someone like Google (or Amazon or anyone else who is credible in the cloud computing ecosystem) launches a platform for running bots that has built into it clear lines for distinguishing identity and (where appropriate) intent? I'm thinking of something a lot richer than "* * * * * run_me_every_minute.bin > email_errors—" something that encompasses identity, context, inter-job communication (with something a little richer than publish/subscribe), and maybe even some sort of a transaction system, just for starters.

Think about it. As the Web 2.0 lovefest melts down for real, one its true legacies is the legitimazation of the XML over HTTP API for inter application communication. At some conference last year I remember someone talking about how the inefficiency of the high volume polling that takes place to determine for instance whether a information source has been updated has a real and measurable impact on the carbon footprint of some of our largest web services. It might be worth doing Cloud Cron for just its green impact alone.

What I'm thinking is something like Second Life for processes with server farms partitioned and dedicated to all sorts of collaboration across processes. In Suarez's talk, he mentioned how deployed bots sometimes start working at cross purposes when one company acquires a competitor and the IT guys forget to turn off the competitive intelligence scrapers that have been looking at prices (or worse yet trading against) a former competitor.
I have no doubt this more reality than fiction even today, and no matter how brittle these jobs may be enough of them running unchecked may bite us in the butt someday soon.

So who wants to go out and build this cron for the cloud already?

Comments Permalink

Where is cron for the cloud?

This week Google lifted a number of annoying limits on my favorite project, AppEngine. With each release they are getting closer to providing something really interesting for developers truly interested in migrating their apps to the cloud.

I love the way AppEngine is giving developers the ability to start from a better point for apps that need to be designed to scale infinitely and don't think that asking folks to a) learn a new language, b) forget about the the SQL tier, and c) limit things like native code for the sake of sandboxing and scaling are big prices to pay in return— especially as it is clear that the team at Google continues to improve the offering. And though most of the attention goes to Amazon's EC2, from a "cloud perspective" most of their innovation came in changing the underlying startup economics for apps and not in fundamentally rewiring the way these apps are built.

That said, there is still something sorely missing from AppEngine's toolset: a way to run periodic tasks that are not tied to the request/response lifecycle. Anyone who has ever worked on any meaningful web application knows that 20-30% of the code runs in this mode: processing orders, generating static versions of things, vacuuming up email queues, parsing RSS feeds, or just doing general cleanup. Unfortunately, as of this writing, any of the methods used to get these periodic tasks to run on Google's compute cloud are kludgey at best.

I do hope AppEngine adds some sort of cron-like functionality soon as this seems to me to be the last major element required to write a real production application on it (for instance, between AppEngine+periodic and S3, we could rewrite all of Tabblo at a fraction of the startup cost and hopefully with a better performance profile).

But even if they don't, it strikes me as a good opportunity for Google to build another building block service like S3, EC2, SQS, etc. Except in doing it the "Google way" we might end up with something much more interesting than a scalable cron— a sort of metaverse for all of the bots now confined to the crontabs on individual virtual hosts everywhere. But more on that tomorrow...

Comments Permalink

James Dyson (of "sucks like a Dyson" vacuum cleaner fame) has a great piece in the Guardian calling on engineers to make Britain great again. In it he talks about how we all need to start making stuff again. Or as he puts it:

We need to rediscover that fascination with that train set of our childhood. We've built our modern economy on the service sector, loans, banking and the dotcom bubble. Now that's collapsed, we should seek to base it on something long term with solid foundations. If we don't, we risk losing an already weakened position for good. Making money from money should be replaced with making money from making.

As I've been looking at the profile of a number of different businesses inside of HP lately, I've been struck by how much profitability in almost always directly correlated with how much product invention the business happens to do. A long list of IP assignments in a given market is almost always a predictor of a very profitable business while all the PR, transactions, and buzz in the world can't keep a business very far from "banana handler" profits.

A great compliment to the new president's insistence that we need to bring the makers back to the center of this story.

Comments Permalink