HTC’s CFO reiterated that their Android phones—previously slated to be released Q4 of this year—will be released Q4 of this year. Android handsets are still planning to be shipped to “ODM clients” in the fourth quarter, meaning that you might not actually see them until late, late 2008 or early 2009. Why? Because those ODM clients, like T-Mobile or various other companies who are using HTC to design the base phone but customize it even more, need time to work their own add-ons in. So yes, on time might not mean on time for you to play with unless HTC releases an Android phone with the HTC branding, without going through secondary companies.
Nokia (NYSE: NOK)-owned Symbian and Google (NSDQ: GOOG)-created Android are destined to be combined to provide a single open sourceoperating system for smartphones, an analyst firm said Thursday.The merger of the two operating systems will begin within three to six months, driven mostly by the fact that Nokia and Google are pursuing similar open source strategies with their respective technology, J. Gold Associates said in a research note.
Nokia and other users of Symbian, which has the largest share of smartphones in the market, do not want to compete in the OS market, the firm said. With Google, the search engine entered the OS market to push the industry toward openness and a level playing field in offering applications and services on the devices.
“We expect that within the next three-six months, Symbian and Android will combine to provide a single open source OS,” J. Gold said. “Many of the same sponsors are involved in both initiatives.”
Nokia recently acquired 100% ownership of Symbian and announced plans to turn it over to a new Symbian Foundation to create an open source OS, which would be offered to foundation members sometime in the first half of 2009.
In pursuing the same open source strategy, Google and supporters have formed the Open Handset Alliance for Android. Members include Motorola (NYSE: MOT) and Japan-based DoCoMo, which are also participants in the Symbian Foundation.
J. Gold said both sides have good reasons for joining. Google’s investment in Android is “diluting the potential for it [Google] to build compelling cross-device applications where it can generate substantial revenues,” the firm said. Symbian, on the other hand, could cement its position with the open source community by not appearing as just a Nokia public relations stunt.
For the market as a whole, the consolidation would reduce the number of major platforms, making it easier for developers to write applications, which means more software would hit the market, J. Gold said. In addition, consolidation means lower support costs.
Finally, it may help discourage carriers from creating their own unique user experiences on specifically altered and customized devices “in order to maintain customer control, but which is also suppressing the growth of apps,” the firm said.
“A combination of the Android and Symbian efforts would be good for the industry, good for Google and good for Symbian,” J. Gold said. “It would also help spur a growth in the availability of applications and services. The downside is minimal. Everyone wins.”
Google’s strict code of secrecy may work fine for protecting its internal operations. But the company isn’t ingratiating itself to software developers by keeping major updates to its Android mobile software platform locked away in a Mountain View dungeon. Now, even those developers once very committed to pushing Google’s technology forward are thinking about abandoning Android – the most closed open platform to not yet exist.
Over at Google’s official Android discussion group, independent coder Nicolas Gramlich recently posted an ad hoc online petition calling on Google to at least tell developers why they can’t get a new and improved SDK for the fledgling mobile platform. Google hasn’t publicly updated the Android software developer’s kit in more than five months.
“In order not to lose many highly encouraged developers, I think it’s time to release some news about the development process of the SDK. Maybe let us know why we have to live with these long cycles,” reads his open letter to Google’s Android overseers. “In my personal opinion it is not the right choice to keep developers in the dark. We, the developers, are the absolute base of success to the whole Android platform.”
Gramlich is the man behind AndDev.org, an online Android developer community that boasts 3,075 registered members. He began coding for the as-yet-unreleased platform in November, the very day Google first unveiled the SDK. And he sees himself as one of the platform’s “biggest fans.” But he fears that Google’s ongoing Android secrecy is alienating its biggest supporters.
“Developers are getting annoyed and some have moved and some are thinking of moving to another platform,” he tells The Reg. “I hope Google will think twice about how long it waits for the next public-release.”
Of course, there are other reasons to code for other platforms. Other platforms actually exist.
Google had promised a real live Android phone by the end of the year, and now, even that’s a stretch, with reported delays on the prowl. And, many developers argue, the company’s SDK silence has set the platform back even further.
“I lost patience long ago. will keep coding/waiting untill the end of july. then ill either switch to the iphone (if sells are good) or windows mobile,” reads a mostly intelligible post from one of the many developers voicing their support for the Gramlich petition. “i see absolutely no use in working with a barely finished SDK on an emulator without a piece of hardware in my hand. MOBILE phone development is no fun if you cant test it MOBILE.”
Google unleashed the last major update to the Android SDK on February 13. The last minor tweak arrived on March 3. And in the nine months since Android was first announced, the company hasn’t given developers even the slightest hint about when updates would arrive. “This is the biggest mistake that Google could have made: not to have small public-release-cycles,” Gramlich says.
He’s doubly ticked off because he knows that a new SDK exists. Google is sharing updates with certain VIP developers - the fifty finalists for the company’s Android Developer Challenge, a coding contest offering $10m in prize money. Finalist Zach Hobbs wouldn’t speak to us about the SDK because - like the other finalists - he signed a Google non-disclosure agreement before getting his hands on those updates.
Google has already annoyed countless developers by keeping the Android source code under wraps. Though the company calls Android an open platform, it won’t actually release the source code until the first Android phone arrives sometime in the unspecified future.
Over the weekend, a stream of rumors flowed from Sun Valley, Idaho, where Google ( NSDQ: GOOG) executives supposedly talked about a Google-branded phone. I’ll explain what happened, but first off, it doesn’t appear to be true, and second, what is more important than whether a gPhone is in the works or not, is that the Google Android developer community is starting to show signs of malcontent.
Here’s how the gPhone rumor mill got going: It all started when The Hollywood Reporter wrote that three Google execs, who held a press conference in Sun Valley, apparently said that they are making “its own branded mobile phone as a replacement for the iPhone.” The story never comes full circle to give more information on exactly what that means, and no other reporters at the press conference picked up those comments. Nonetheless, the rumor caught fire and ran rampant on the Internet. GigaOm linked to the story, so did TechCrunch and ReadWriteWeb to name just three. TechCrunch took it a step further and reported that “San Francisco-based Ammunition Design Group, which has designed computers, mobile phones, hardware, and other devices for companies like Palm ( NSDQ: PALM), Hewlett-Packard, Dell Computer, and Logitech, may be working with Google to create an Android-based, Google branded Gphone.” Despite this, all of it appears to be untrue and that the original reporter misunderstood what the executives said. Google said last year when it launched Android that a gPhone was not under development, and they have not changed course.
Here’s the real story:ReadWriteWeb reported that Google Android developers and even Google engineering employees are frustrated with how the Android platform is evolving. This is a real threat to Android. With iPhones flying off the shelves, and Windows Mobile devices already out there in droves, and the Symbian OS becoming open and free, Google has to build a healthy developer community in order to compete. A petition seeking more information about the SDK was posted late last month to the Android Discussion Group, complaining of delays and bugs that have yet to be worked out. It says: “I’m starting this petition, to express my personal frustration about the release cycles and the information policy of the Android SDK…In order not to lose many highly encouraged developers, I think its time to release some news about the development process of the SDK.” One of the 38 responses to the post is signed by someone claiming to be an Google Android engineer. He says have some frustrations, too. “There is some truth however in saying that we (the Google Android team) are very much focusing on playing our part in getting an Android device on the shelves as soon as we possibly can, and that focus comes at the expense of other tasks, like getting an SDK out.”
While the image above is a design originally conceived for Samsung, it represents the work of San Fransisco-based product design and development firm Ammunition Design Group. Why should you care? Well beyond the fact that their site is packed full of amazing designs done for huge companies including Panasonic, Dell, Nike, HP, Wells Fargo, Microsoft and more; Ammunition may be the team helping make the much-rumored Google Gphone a reality. Last year there was plenty of buzz surrounding the possibility of a Google-baranded handset, however most of it was squashed shortly after the announcement of Android. Even still, at no point did Google really deny the claim that it was working on its own handset. As of today, consider those rumors back in full force as Techcrunch reports state that a Gphone is most likely in the works. The article cites two main reasons for the claim:
Hollywood Reporter Dan Cox’s recent piece stating, “The trio of Google execs also used the opportunity to talk about the inroads the company is making with its own branded mobile phone as a replacement for the iPhone,” after an interview with Google’s top execs Brin, Page and Schmidt.
“A good source” that swears Ammunition is currently designing a “seriously beautiful” Gphone for Google.
If the rumors are true, this will definitely have a huge impact on the handset market as we know it. A few big handset manufacturers have run the game for quite a while now and Google could be the second “newcomer” to hit the market in just a few years and make a huge dent in the business.
Making good software for mobile phones is hard — even for a technically adept company like Google (Nasdaq: GOOG) .
Indeed, it’s so difficult that the fleet-footed champion of search advertising finds itself in the unaccustomed position of playing catch-up to normally slow-moving industry behemoths.
As Google scrambles to release its mobile phone code sometime later this year, a nonprofit consortium of some of the world’s biggest telecommunications companies and handset makers has quietly beaten the search giant.
The LiMo Foundation, created in 2007 by Vodafone (NYSE: VOD), NTT DoCoMo, Motorola (NYSE: MOT) and four other telecom giants, delivered its first phone in February. It now boasts 18, including the Motorola RAZR2 V8 and MOTO Z6w.
Rushing the Gate
LiMo’s early success illustrates the stiff competition Google will face as it seeks to conquer a whole new high-tech domain.
The wireless industry has embraced LiMo, which has attracted 40 companies as members and is rapidly growing. In contrast, telecommunications carriers were at first wary of Google.
Executives from around the industry said they want to ensure that mobile devices do not follow the path of personal computers and become dominated by one or two gatekeepers.
“In the PC world, it’s about what is Microsoft’s road map and what is Intel’s road map,” said Mary McDowell, executive vice president of Nokia (NYSE: NOK) . In the mobile world, “we are actively driving the technology we use in our products.”
A Tough Timetable to Meet
Feverish speculation about the “Gphone” contributed to industry unease, though much of the concern subsided after Android, Google’s name for its mobile efforts, was announced in the fall of 2007. Android wasn’t a phone, but a bundle of still-to-be finished software that anyone could use to create a phone.
Like LiMo, Android wanted to become an industry standard. However, first it needed marketing partners. Initially, 33 companies signed on to Google’s Open Handset Alliance.
Google promised the first phones carrying the code would be available sometime in the second half of the year — along with the code itself.
However, meeting that timetable has been tough. Despite widespread interest among carriers and handset makers, only one carrier, T-Mobile , has announced plans to distribute an Android phone before the end of the year.
Meanwhile, LiMo has sprung ahead by using existing software contributed by members. “This means you have a far lower level of bugs and defects that you need to deal with,” said Morgan Gillis, the executive director of the LiMo Foundation.
The blogs are saying that T-Mobile USA will launch an Google Android-powered handset in the autumn in support of its nationwide 3G network rollout on October 1st.
It all started last weekend when TmoNews speculated on the T-Mobile 3G dates and suggested the Android handset would be the HTC Dream.
Despite telling its own readers that the news should be treated with ‘a whole damn bucket of salt’ it set off a chain reaction of blogging and re-reporting (hey, we didn’t want to miss out) that four days later leaves us in no clearer position.
It’s all exciting stuff. But remember just two weeks ago all the talk was of Google reneging on its promise to have Android handsets in the market by the end of 2008.
In light of that, The Register speculates on ways that Google and T-Mobile could speed up Android phone development to meet that October 1st day of destiny.
T-Mobile could be one of the first mobile operators to launch a handset running Google’s upcoming Android smartphone operating system, according to various blogs in the US.
One report claims T-Mobile USA will release an Android smartphone when it rolls out its 3G wireless network across the US towards the end of 2008.
Android marks Google’s entry into the mobile phone operating system market, with the search giant hoping to go head-to-head with the likes of Windows Mobile, Symbian and Palm. It will have a complete set of components, including a Linux-based operating system, middleware stack, customisable user interface and applications.
Google announced Android last year, and prototype devices based on the platform were on show at the Mobile World Congress in Barcelona earlier this year. However, last month it was reported that the first handsets running Android won’t be available until the fourth quarter of this year.
Reports from the US seem to back up that prediction, with News.com suggesting T-Mobile will launch an Android phone – possibly the HTC Dream - in October.
Google Maps Mobile is probably Google’s most actively developed mobile application. It seems like there are new versions popping up for one platform or another every couple of weeks these days. In the past few months for example, Google has issued a native S60 version updated several times, various versions that can make use of internal GPS, versions that can integrate with device phonebooks and Nokia Maps, cell-based location, etc. For the most recent feature addition, Google has decided to implement a bit of voice recognition. Sweet! A new version of Google Maps Mobile has been made available for the US BlackBerry Pearl 8110, 8120 and 8130 that allows users to speak their search criteria rather than type it. Voice search uses the same voice recognition engine as GOOG-411, Google’s free information service, so we know the accuracy will be spot on. Using pretty much couldn’t be easier:
Press “0? to center the map view around your location
Press the left-side key and hold it while you say the name or type of business you’re looking for (for example, “pizza”)
When you’re done speaking, release the left-side key, and our voice recognition technology will figure out your request and find the business you’ve been looking for, no typing needed.
These days there’s a pretty good chance that the rest of your BlackBerry-toting friends make fun of you from time to time because you’re still carrying a Pearl. Opportunities might be few and far between, but here’s a good chance to show them a little something they can’t have quite yet. Hit http://www.google.com/gmm from your Pearl to snag the latest build.
Google has signed a deal with digital-map maker Tele Atlas which allows Google to use the firm’s map data on a host of devices including cellphones and gadgets based the much anticipated Android operating system. Under the terms of the 5-year deal Google will also continue to use Tele Atlas mapping data on a host of Google services such as Google Maps and Google Earth.
Tele Atlas owns GPS device maker TomTom which assures a cozy relationship between Google and TomTom. Under the terms of the deal Google has agreed to send end-user mapping data back to Tele Atlas when it concludes user edits to maps. This, one would hope, would be a very efficient way for end-users help both Google and Tele Atlas to more accurately update maps with road closures and other type of mapping information.
This Wiki style of map making by using user edits has already been a tremendous help to both Google maps and TomTom devises through the Map Share feature, however now edits made on one map system will be carried over to the other. It’s possible now that by sharing the edited maps between TomTom and Google maps it could create the most accurate road maps around. And Tele Atlas wouldn’t even need to do any additional research to create those maps.
Categories
