A quick sitdown with Motorola co-CEO Sanjay Jha
We had a chance to catch up for a minute with the man tasked with turning around Moto's phone business, Mobile Devices CEO Sanjay Jha, just moments before he went on stage to introduce the Backflip this week at CES. With Android getting more attention than ever before, it's never been a better time to sit down with a guy who's gone all-in with the platform, right? He talks Nexus One, Google, firmware updates, Blur, and more, so don't be shy -- read on for the full transcript! CZ: So what is the, if you can talk a little bit about the justification for deciding whether a device gets Blur or whether it's a Google Experience Device? What influences that decision?
SJ: Really, I think if it's going to be a leading-edge Google product, then Google says, look, it's going to be my experience, and we will control the experience that you deliver, in which case we don't put our MOTOBLUR. But if we decide that it's our experience then it allows that. So it's really a matter of our relationship with Google on that one. And you'd find, for instance, that HTC... the Nexus doesn't have the Sense UI. It's the same kind of thing.
CZ: Exactly. So if we can compare this to the CLIQ, they're basically almost exactly the same size.
SJ: Yes, just slightly smaller, and as a result of which it kind of seems to be a little more gender-neutral. Women just love the keyboard. Men love the keyboard too. And you've got all of these symbols here. One other cool thing I didn't show you... it has a touch in the back. It has reverse touch, so you can control things and you can navigate here. When you're doing email and some of these things and you want to more precisely position the cursor. For instance I can enlarge the browser just by tapping the back. Sometimes that has an advantage and we actually think that when some of the developers have access to the API, they will do a bunch of cool things with reverse touch which will allow gaming and some other things to be done in a much better way.
CZ: Right. So there is a custom Motorola API for this device?
SJ: Well, in virtually every device we do, we stick with the standard API. But if we do things which are not standard, we publish the API.
CZ: Okay, so those are accessible to any developer that wants to develop for it?
SJ: To any developer, yeah.
CZ: Okay, great. I'm sure you've been getting this question a lot all day and I apologize, but what... give us your sense of what the Nexus One means for the market, because it's a fundamentally different way to approach the way that Android is sold and marketed. I think that this is something that Microsoft has been avoiding for years with Windows Mobile, right? They don't want to compete with their partners.
SJ: The way I think of it -- and I don't know if you were there yesterday or not...
CZ: We watched it.
SJ: I showed up quite late unfortunately, but this is a channel to the market that Google -- because they have so many visitors to the website -- can provide, and in some ways think about being able to introduce some innovation faster into the market. Now, the first device is HTC's device, the Nexus One, but I think that there will be multiple devices and I think that we said "yes" today that probably this next device is our device.
CZ: Okay.
SJ: So, I see no great difference than selling it to, say, Best Buy or through Amazon on amazon.com or through carriers. It's another channel into the marketplace and the dynamics, I suspect, will be very similar of delivering these devices into the marketplace. Obviously, the experience is different to buy it on the website, but we don't know how that will play out yet. And I think probably Google will tell you that they don't know how it will play out. We're hoping that, as a result of that, we can get our innovations into the marketplace faster. That's probably the most optimistic view that one could take of what that could do. The other view is that it, you know, people that are used to buying their phones the way they do or devices the way they do, and it makes a modest amount of difference to how many devices ship through that channel. We just don't know. I mean, I'm very happy to support it and participate because it's something new in the industry, but, you know, it's not Google doing the hardware, it's that they're working with partners to deliver the hardware, and in some sense, you can look at the Droid -- that device is 2.0, and this is 2.1. The day that launches, 2.1 will be available to us and we'll upgrade the Droid to 2.1. So the software feature sets will be available completely to us.
CZ: And that speed of upgrade -- that's largely because of the fact that it's a Google Experience device, right?
SJ: No, I think that --
CZ: Not having Blur on there.
SJ: That's a very good point. The more you put beyond what Google gives you -- every time there's a new release of software, you have to update all the other software. So that is the only difference. But of course, we're very motivated -- like HTC with Sense UI, us with MOTOBLUR, and others -- to add our software to meet different needs so we can differentiate ourselves. But yeah, you're right, I think that if all we do is use Google software... well, they have made that 2.0-to-2.1 a fairly simple transition, so we could do that very quickly. But if we had MOTOBLUR on it, we'll then have to migrate MOTOBLUR to 2.1, and it'll take a little longer. But we think that overall that's the right thing to do.
CZ: Okay. Yeah, it seems like Google is moving in the direction of having a hero device for every release of Android. Droid for 2.0, Nexus One for 2.1...
SJ: Yeah, that's right. I think that's... there's a very good reason for it, which is that it's really difficult to deliver software with that level of integration. You can go back a little bit and look at what Microsoft did with their model, and I think that if you don't work very closely with hardware and software manufacturers together to deliver that experience, it's really difficult to deliver an integrated experience. And I completely understand why that makes sense. And you can't do ten devices one fine day, you gotta do one device. So I think it makes sense to me.
CZ: Right. It seems with the CLIQ and also with this new device that they're coming very close to infringing on, if not already infringing on, what AT&T is calling the "quick messaging" segment, right? The feature phones with full QWERTY keyboards. Is that something that you're kind of infringing on on purpose? You want to get into that market with the smartphones? With an entry-level smartphone?
SJ: I don't know if you were at the AT&T meeting today. It's just the direction that the industry is headed, which is smartphones are coming down-tier, and it is happening all the time, and of course, we are very motivated. And I've said a number of times that a core part of our strategy is to bring smartphones lower down the tier. So if we can offer better capability, more features, better mobile internet integration at a price point that used to be quick mobile messaging devices then I think that tier will have to shift. And I don't know that I've sat down and said, "let's go infringe on it," but that's the kind of...
CZ: That's where it's going.
SJ: That's where it's going.
CZ: And it seems like Android is to the point now where it can very effectively run on these older 528MHz MSM7200-class processors, and those cores certainly in 2010 will be lower-end cores. You're not going to those in high-end devices, right?
SJ: It's true, it's true, but if you look at 2.1, it has much more 3D capability. So to deliver a good 2.1 experience, I think, you know, the Nexus One has a gigahertz processor. You will see us deliver those gigahertz processors in the marketplace. I think that the impatience that the users have with the response to their input is such that I think that you will see the latest softwares generally requiring more processing. And, you know, all the right trends in the industry will drive that to open. But, as a result of it, slightly lower-tier devices can go pretty low in terms of price point.
CZ: Right. And to your comments and to Andy Rubin's comments yesterday, I think 2.1 requires 3D acceleration, is that right?
SJ: I believe it does, yeah. To do it effectively... I mean, you can do anything, you can emulate any 3D action, but to do it in a responsive way, I think it probably does.
CZ: So, as a result of that, do you think that will keep Android not necessarily in the higher end of the market, but midrange and above?
SJ: Yeah, I think that it's all just a matter of time, because the 3D cores are shrinking. As you know, I was in the chipset business at one time. Those cores are shrinking and I don't see any great reason why, in a short period of time, that doesn't come down to more tiers.
CZ (holding an XT800): Do you see this kind of form factor coming to other markets? Because right now, these are basically China-exclusive.
SJ: When you say this kind of format, you mean a tablet?
CZ: Right.
SJ: Yeah, we will bring tablet to US. Definitely bring tablet to US.
CZ: Okay. But you don't have any timeframe on that?
SJ: Not today. All I would say is in short order.





















Vewy interesting.....
You didn't ask them if they were done with winmo or about winmo7....
@astrocramp Motorola has already stated that they are moving away from WinMo. All smart phones will have Android.
@BH In October Motorola basically siad they were skipping 6.5 and waiting for WM7. Have you heard something more recent?
http://www.itproportal.com/portal/news/article/2009/10/8/motorola-wait-windows-mobile-7-concentrates-android/
@BH That's not entirely true - he said awhile back (I can't remember when) that they had a team working on winmo7 stuff. But it isn't really clear, that's why I would have liked to see him answer the question directly.
@astrocramp : I agree. I don't know why Engadget really didn't try to push him to say something about Moto's outlook for WinMo devices. We could have heard something more definite,
XT800 Coming to the states? Nice.
"SJ: Yeah, we will bring tablet to US. Definitely bring tablet to US."
Rain man?
An enjoyable read Chris. Thank you.
sholes tablet is the next google phone... i give it two to three months.
@ECH
And on Sprint. I hope.
@HardToBelieve Not going to happen, sorry dude! Have you seen the Droids numbers, lets be real.
@1ofdakoolkidz
Is 1.2 Million in 2 months good or bad?
http://www.chicagotribune.com/business/chi-biz-motorola-ces-sanjay-jha-jan07,0,3802572.story
interesting short interview.....always been a great admirer of Sanjay Jha and what he is doing @Motorola
Def a great read. The guy sounded like he was genuine in his responses--whereas most of the big timers for these companies give BS PR answers which is kind of crappy.
Although I would've asked why their press conference was so damn short. Not to mention I would've bothered him about why the euro droid has multitouch and the US droid does not...
@Rick James Rick James, you wrote two paragraphs in your coment, and I agree with them both, bitch.
@JakeMG
In that case, do you want to go smoke the stickiest of the icky?
@Rick James
Lack of Multitouch on Droid is Google's call not Motorola's, you would be barking up the wrong tree.
@ECH
Really? Why didn't Google tell Moto not to put multi-touch on the euro-droid/milestone then? Valid question either way.
@Rick James
I think is was Google (not Motorola) who put multitouch in their OS for the Milestone.
Engadget tried to pin Google down on this at the N1 press event and got no where. Google is clearly dragging their feet on Multitouch out of legal concerns regarding Apple. Once the lawyers are done milking every last drop of legal fees out of Google and give them the go ahead, Google will flip the switch and enable multitouch with an android updated for all hardware that can support it.
@ECH
The way I understand it, Android 2.0 supports multitouch. Its just that none of the native apps support it. You may be correct that Google said they didn't have a problem with multitouch in the euro-droid, however posing the question to motorola may have offered more insight as to if google gave the decision.
No matter what, its kind of crazy, especially considering there is multitouch on the Hero. Its really confusing as to exactly what is going on here.
@Rick James
Seeing as how the US N1 lacks multitouch, I am extremely confident that Google is calling the shots on who gets it and who doesn't. It seems that apple's patent claims are stronger in the US than europe, but even their US claims are weak according to many which is why some devices here have it. I think google is just being more cautious than others, since they would make such an attractive target for apples lawyers.
@Rick James You guys having a go about the lack of multitouch on the DROID as opposed to the Milestone, I can tell you it's definitely a catch-22 as, being a non-Google experience phone we still haven't seen 2.0.1 update (so we're still stuck with all the initial camera, random restart and other issues) or any official word even on when we can expect it. Honestly I'd almost trade the multitouch for some responsiveness from Motorola or anyone about what's happening. It's effectively abandonware.
The response stating as to when the Droid would get 2.1 was a little vague to me. It seems as if once the Nexus One is released, Motorola will be pushing the same 3D goodness out to the Droid.
However, what confuses me is the N1 is already out, so 2.1 is coming next week some time? Why push out a 2.0.2 update then?
I guess I'm just going to have to be patient and let the updates happen when they do.
@herki
2.0.2 for Droid? Is this officially coming out before 2.1? What's your source?
@ECH At the Motorola press event yesterday, they said besides 2.1 for Droid coming out, they would also push out a small maintenance update. Why bother if 2.1 is happening really soon?
@herki
http://www.engadget.com/2010/01/06/live-from-motorolas-ces-2010-press-event/
5:40PM He's talking about the Droid. He says they'll be pushing out a second maintenance update pretty soon -- no solid date, though.
Sure enough. They can push out as many updates as they want, the more the merrier, so long as we get the big ones like 2.1 as well. Good to see that was definately confirmed as well (yes a date would be nice).
@ECH I love updates a ton too. Especially if they have nifty new features like Android updates always seem to have. I'm just afraid that if they put time into making another update for 2.0, that means they don't plan on having 2.1 make it obsolete in a week.
Yeah, not asking about multitouch on the Droid was fail, as was not trying to get a specific date for Android 2.1 on the Droid, but other than that a good interview. Sanjay seems very down to earth and real for a CEO.
Moto might finally be on a good track....... Having been team Winmo as far back as the hitachi G1000 I used an android moto phone recently and it was a far better experience than others I have used....... Its good for them to stick with android and make google a bigger machine than it already is.
@(Unverified): That's because they actually have tried harder to make a better experience with Android. When they were doing WinMo phones, they didn't do much to improve the experience, but bogged it down with crap and cruddy specs.
I hope Moto does a great WinMo 7 phone, and hopefully launches a new line of Moto Q's.
I can't believe you didn't ask about the multitouch reasoning behind Droid and Milestone....
Of course he's a down to earth CEO, he's an engineer by trade. He tells it how it is.
should have asked what they fuck were they smoking when thinking up the backflip? the STUPIDEST design i've seen yet...
Ok, maybe I am overlooking it but did you ask about the keyboard-less droid or what? Um...that's kind of important(to me), and it seems as though he would have given you some sorta hint.
It will be interesting to see what they use their super bowl ad for. Will it be focused on a specific device (current droid, the next google phone, something else), or just a general overall company spot.
http://www.engadget.com/2009/12/30/motorola-buys-super-bowl-ad-spot/
Chris,
Can't believe you didn't ask why the American version of the Droid doesn't have multitouch (unless you install a 3rd party app that uses it). Some on here say that question should go to Google not Motorolla. I think both companies owe their US customers an honest explanation for why they are aren't getting the same base functionality the rest of the world enjoys.