As ever a bang upto date follow up on Andriod (i.e. about a week late). See the previous post for disclosure and background (if you’ve been living under a rock).
First up; one of my concerns is that, given the non-reciprocal nature of the licence, it would require extreme discipline from all parties to not fragment the platform. Well fear not, ZDNet reports that everyone in the OHA has signed a non-fragmentation agreement
“All of the partners have signed a non-fragmentation agreement saying they won’t modify [the code] in non-compatible ways,” said the spokesperson. “That is not to say that a company that is not part of the OHA could not do so.”
Without seeing the agreement and not being a lawyer I have no idea how enforceable such an agreement would be. As ever the devil would be in the details – defining fragmentation, or ‘modifying code in non-compatible ways’.
Also on ZDNet is an interesting interview with Andy Rubin, director of mobile platforms at Google,
“The platform is completely open in a variety of ways. Of course it has open APIs, but it’s also open source, and it being open source means it’s (open to inspection).
So expect to have the entire industry crawling all over the source base, trying to make sure that there aren’t security issues, and there aren’t inefficiencies in how the platform is designed.”
But when exactly will we get to do that? Before or after the first phones ship?
The alliance is completely open. It’s not a closed thing; it’s not a club. We welcome anybody. Members who wish to join the alliance actually have to contribute something, so I encourage people to join and contribute.
So it’s a little unclear but it seems you have to contribute first and then get to be a member. Who decides? Google? Some percentage of the existing OHA members?
As ever with these kind of interviews it’s always easy to pick out something to poke at but this was too tempting;
Apple has a great business in building really, really high-quality consumer products, and the platform that we’re building can go into a lot of different products.
Including really, really low-quality products presumably.
The source won’t be available until the phones ship in late 2008: http://robilad.livejournal.com/23498.html
— James Nov 28, 10:46 am #
There are some fragmentation points lined out in the Android API docs, for example the OpenGL stuff is optional.
More interestingly, there are three trends that may team up to whack Google over the head:
* it’s mostly a US-centric play, along with their 700 spectrum bid, and the US consumer market shows signs of smashing itself right into a good old fashioned recession by the time the phones are actually out.
* intel will increasingly start pushing x86 down to the phone sets in the coming years, so the value of controlling a proprietary Linux distro for ARM is questionable in the long term, as X86 always wins.
* Low priced sub notebooks a la eee pc will be bundled in France this winter and subsidized by a mobile telco, and they offer an order of magnitude better experience to the ‘web’ user than iphone or android could. Rumor has it that the next eee pc gen will have 3G on board, and between a Skype connection over WiFi, and your regular cell/data rate for everywhere else, the kind of low priced x86 devices that Google will be effectively competing with expensive high end phones for the lucrative mobile data flat rates is nothing they can really hope to win, afaict.
— Dalibor Topic Nov 28, 07:25 pm #