Software For The OnePlus One
TH: Another interesting feature of the OnePlus One was using CyanogenMod for the operating system. Why did you choose to partner with another company for the OS rather than just doing your own skin like most other OEMs, and what led you to CyanogenMod?
CP: A lot of companies—when they start a mobile phone company—will start by making their own OEM skin or own ROM. They might spend eight months or a year on this and then start developing the hardware. Then one-and-a-half or two years later, they release the first phone. We thought about this, and we thought, ‘Why did people do this?’ Back in the day when we were still on Gingerbread or on Donut, it made sense, because the Android experience wasn’t that polished and OEMs needed to polish up the experience for the end consumer. Nowadays, since KitKat, Android is already pretty mature and a lot more users actually prefer stock Android to something more customized. So we thought, ‘What are we good at?’ Well, our experience is all in hardware, so let’s just make really good hardware first. And because the differentiation between OEM ROMs and stock Android is slowly disappearing anyway, why not do something very close to stock? Instead of waiting an extra year to release a phone, let’s release a phone in six months instead while working with the best people in the industry who can do this. At that time, Cyanogen had just formed a company. We were friends, so we said, ‘Hey, let’s try this out. You’re a new company. We’re a new company. Let’s just try this and see what happens.’ And so we started working together. We actually had a lot of feedback on the software, and they had feedback on the hardware, so it’s kind of a co-developed product. Looking back, it was a pretty good idea to work with Cyanogen, because I think a lot of our success comes from the fact that we actually worked with them. They already had this pretty good product, and they had this core community of users who really trusted them as a new brand. It really meant a lot to us—this trust.
TH: Are you planning to upgrade the One to Lollipop?
CP: We’re actually still working with CM on the Lollipop build. There are three stages of QC for software for us: one is Cyanogen’s own QC, one is our own QC, and then we have to pass the Google tests. It’s in this process now, and it can take some time, especially if one of these finds a bug or a problem.
TH: So you don’t have a hard release date yet?
CP: It’s really hard to commit to release dates within software. I think Steve [Kondik, Cyanogen Inc. CTO] has commented on Google+ saying it’s going to be released in early February, but I’m not sure when it’s going to be exactly.