Brian Gerkey

They might do one job in the morning, one job in the afternoon.

Automating those kinds of tasks has not historically been economical.

And that's the type of problem that we think we can solve.

So we think the demand is there.

We think the hardware is there.

What has been missing is a software layer.

You mentioned earlier Android for robotics.

One of the ways that we think about ourselves is...

you know, if we can provide that Android-like layer that gives you access to many different types of hardware, so you treat the different robot brands similarly, which gives you that freedom of choice when you're going to go deploy your application.

You can say, you know, for this application, robot brand A is probably the best

fit because it has strengths in these areas.

And then for this application over here, robot brand B is best because, well, that end customer is already invested in their facility and robot brand B. And so I can take my application.

I just have it run on brand B and that meets their needs.

If you can give that hardware abstraction layer and then that's a starting point.

That's not enough.

You also need to give

The application developers, those developer tools that I mentioned earlier, so being able to visualize the data, log it, play it back, debug systems, understand what's happening.

And then increasingly, you need to give them the capabilities or the algorithms.

And so you don't want people to be building everything from the ground up.

So just like if you were going to build an Android application, there's a huge toolkit that's already available to you.