The Twitter service with the cutesy raccoon mascot is making a new home on BlackBerry and Google Android phones. The free Seesmic, like its proliferate rivals, lets you read, manage, and compose Twitter messages much more flexibly than you can do from Twitter's Web site. We crash-tested both mobile versions as soon as we heard the news.
Seesmic on Android
Seesmic 1.0 for Android is available from the Android Market app, which is located on the smartphone. It takes up just over 1MB. The interface spreads four tabs along the top in both landscape and portrait mode, one each for the timeline, replies, direct messages, and your profile. There's also a ribbon on the screen that you can tap to refresh the feed. Click to open a tweet and you can save it as a favorite, retweet, or reply as a public "@" message or as a private posting. From the menu button, you can refresh, compose, or tinker with the settings.
Although Seesmic's Android interface is much more stripped down than its desktop AIR app for Windows and Mac, the app manages to remain flexible by giving you a choice over the kinds of notifications you'd like to receive, and over the partner services you'd prefer to use to send a photo, video, or shorten a URL.
Sure, it's blurry (blaming the BlackBerry camera), but squint hard enough and you'll see that Seesmic associated a picture with my account that's not actually my face.
(Credit: Jessica Dolcourt/CNET)The biggest flaws we've noticed so far? ... Read more
Is Google really thinking about making a substantial change to its business model by releasing the fabled Gphone?
Would Google really consider derailing Droid momentum with its own phone?
(Credit: Josh Miller/CNET)TechCrunch sparked the latest round of Gphone rumors Wednesday, reporting that its sources indicate Google is working on releasing a Google-branded Android phone sometime in early 2010 that will be sold directly to consumers at retail, presumably bypassing wireless carriers. Such a phone is supposedly being built by a manufacturing partner with the intent that Google's brand will dominate the phone; TechCrunch compares the strategy to what Microsoft did with Toshiba and the Zune music player.
Well before Google unveiled its Android mobile operating system project two years ago, and almost ever since, persistent rumors have circulated that Google's mobile phone ambitions go beyond software development. Just as consistently, Google executives have downplayed such rumors with statements that the company is most interested in seeding Android far and wide across multiple carriers and hardware manufacturers, rather than following Apple's strategy of designing and building the entire product itself.
Just a few weeks ago, Google's Andy Rubin, vice president of engineering for Android and the head of the project, told CNET that Google had no interest in "competing with its customers" by releasing a Google-developed phone, echoing comments he made earlier in the year that "I'd much rather be the guy that does a platform that's capable of running on multiple companies' phones than just focusing on a single product."
Now, there was some wiggle room in Rubin's statements. Most smartphone hardware brands--even Apple--don't actually build their own phones, they contract with companies in China or Taiwan that assemble the parts. Therefore, Google's statement that "we're not making hardware" doesn't preclude the company from designing hardware.
On Wednesday, Google refused to comment on what it termed "market rumor or speculation." But why would Google build its own phone? What would it have to gain to offset what it could potentially lose?
Google just signed a multiyear collaboration deal with Verizon Wireless, pledging to help develop a family of Android-based products running on Verizon's network. Any attempt on Google's part to bypass Verizon and sell its own branded handset would likely raise a few eyebrows in New Jersey, no matter how close of friends Google CEO Eric Schmidt and Verizon Wireless CEO Lowell McAdam have supposedly become.
So maybe Google wants to completely bypass carrier networks and release the ultimate IP phone, with Google Voice and the technologies it just acquired from Gizmo5. Such a phone would be free of the two-year contracts imposed by the wireless industry, but would it really be compelling without some kind of wide-area networking technology?
Google's Andy Rubin, head of Android development
(Credit: Google)In the same conversation in which he denied Google was working on its own hardware, Rubin implied that Google doesn't think there's much of a future for WiMax, which Intel and others have long billed as a way around the wireless carriers. The company sat out a recent funding round for WiMax start-up Clearwire after investing around $500 million in the company in 2008, and Rubin said it was planning future Android development around the LTE standard, which is the path that AT&T, T-Mobile, and Verizon plan to take to 4G networks. LTE carriers will likely insist on the now-familiar two-year contract to offset the costs of building out that network, unless federal regulators tell them they can't.
But assuming Google really is planning on releasing a completely Google-branded phone at retail, such a plan could derail the momentum enjoyed by Google and its Android partners this year.
The Microsoft/Zune strategy alluded to by TechCrunch was a disaster for Microsoft's PlaysForSure hardware partners, who had been working with the company on MP3 players that hooked into Microsoft's media software. It effectively cut them out of that market, and almost certainly created distrust and outright resentment that could come back to hurt Microsoft one day.
Any Google-branded phone would immediately compete with phones that Google partners like Verizon and Motorola are placing huge bets around, namely the Droid. What incentive would those companies have to work with Google in the future should it throw a huge wrench into their product development strategy?
And even putting all that aside, smartphones in the U.S. are only attractive to consumers because no one actually pays what a smartphone is worth. Heavy carrier subsidies knock the price of the average smartphone from around $500 or $600 to around $200, because time and time again most people have shown that even if they will save money in the long run by avoiding a two-year contract, they get sticker shock at the sight of a $599 phone. Just ask Apple: the iPhone would not be the iPhone if it was still selling for $599.
If Google were to release its own phone at retail, would it have to subsidize it itself to get the price down to about $200? Would the federal government look favorably on such a plan, knowing that virtually no other company could afford to sell such a smartphone at a loss?
TechCrunch later reported that Google could be working on a "data-only" device that would ostensibly use AT&T's network for data services, with calls being placed using VoIP technology. That's a bit puzzling as well, since that would allow Google to annoy new best friend Verizon and AT&T to annoy longtime steady Apple, so at this point, it's hard to know exactly what's going on here.
Few businesspeople directly answer questions about major strategy shifts they might be planning, for the obvious reason that surprise is a competitive advantage. But it's hard to imagine why Google would risk stunting Android momentum just as the software is rounding into the best chance for hardware manufacturers and wireless carriers to compete with Apple and AT&T.
That is, unless somebody at Google has decided that they are the ones with the best chance of competing with Apple.
Google announced Tuesday that the Donuts are ready.
Those smartphone developers waiting for the next version of Android, code-named Donut, will not have to wait any longer now that the Android 1.6 software development kit is available for download. As expected, Donut is not a major release of Android but adds a few goodies that developers might want to consider.
For example, Android can now run on CDMA phones used by the likes of Verizon and Sprint, adding more potential partners to the Android world. The latest release also adds a text-to-speech API (application programming interface) for developers to use in building applications, as well as support for a newer version of the Android Market and an improved search box.
Developers can download the SDK here. Phones running Donut are expected to arrive around October, Google said, which lines up well with the expected launch time frame for phones like Motorola's Cliq. Google has said it wants to release two major updates to Android a year, with the first major release of 2009, code-named Cupcake, having arrived in May.
Scan your Facebook news feed with the new Android app.
(Credit: Facebook)While iPhone owners have long had a powerful Facebook app with a wide range of functionality, Google Android users have had to make do with the mobile version of the social networking site (called Facebook Lite). Not only does it offer limited features, but also it is clunky and rather difficult to navigate.
But that changed Tuesday when a new and long-awaited Facebook app hit the Android market. The free app offers many of the features that you've come to expect on the iPhone app and the full version of the site. You can scan your news feed, view your friends' walls and user information, comment on status updates, hit the "like" button, take and upload photos, add new friends and post status updates of your own. What's more, you can add a notification widget to your home screen and you even can shake to refresh your news feed.
Though we welcome the extra features, the interface and navigation appear a bit convoluted as of now. For example, it takes a lot of clicks to get to a friend's profile and list of friends. Also, you can't get Facebook chat or access to messaging for now. We assume those features will be added soon.
It's worth noting that while Facebook is listed as the developer in the Android Market, according to Facebook's official Web page for the app, it was not developed by the company. From what we hear, Google developed the app with Facebook's help.
We installed the app without incident on our T-Mobile MyTouch 3G. Check back soon for a full review.
Update: Article updated at 1:10pm PT with confirmation from Facebook.
Thanks to close collaborations with Apple, Microsoft, RIM (BlackBerry) engineers, and so on, Facebook-sponsored applications are available for a wide spectrum of mobile phones. An official Android app is in the works, Facebook has confirmed, with Facebook and Google working together on the software.
Some have scoffed that they'd never see the day when the two Silicon Valley titans pause the rivalry long enough to cooperate on a project. The truth is that they need each other, at least this time. Google needs to fill its Android application storefront with popular titles to stay relevant, and Facebook needs to ensure that mobile users can continue accessing core functionality from any device. It would be overstating the issue to suggest that, in one sense, they both need each other to beat each other, but in the case of this small victory, the brand win is important to both.
Facebook for Android is expected to launch with fewer features than its iPhone counterpart, TechCrunch reports. If their tip is correct, users may have to make do without the message in-box. However, Facebook for Android will center on the familiar activity feed and status updates, and is said to be powered by Facebook's Stream API.
We'll see what transpires when the application materializes, so stay tuned for an update and hands-on review in the near future. Neither Facebook nor Google would share a release date, but a Facebook representative told CNET that the app is coming "soon."
Android has the strong Fbook app from developer NextMobile Web (covered here), but with all due respect, it's akin to serving margarine instead of butter; margarine salts and fattens just fine, but we all know it's not the same thing.
Google's move to let software run natively on Android devices opens the door for a version of Firefox that can run on the operating system.
At present, Android applications are written in Java and run on Google's Dalvik Java virtual machine. Last week, though, Google announced the Android Native Development Kit version 1.0 that lets software run natively on the Linux layer below, though the company sees it as a way not to run full-fledged applications as much as to run components of ordinary Android applications.
"Android applications run in the Dalvik virtual machine. The NDK allows developers to implement parts of these applications using native-code languages such as C and C++," said Google's David Turner in a Native Developer Kit blog post.
That's enough to whet the appetite of Mozilla, the organization that oversees development of Firefox and its mobile incarnation, called Fennec though likely to sport the Firefox name when it arrives in product form.
"Developers are taking a look at the NDK to see if it provides the capabilities we need to bring Fennec to Android. If it's possible, I think our community would be interested in doing it, because Android will be appearing on more smartphones with the capabilities to provide a good browsing experience," said Jay Sullivan, Mozilla's vice president of mobile.
A year ago, Mike Schroepfer, then Mozilla's vice president of engineering before he moved to Facebook, said Mozilla wasn't focusing on Android because of the Java constraint and because Android already has a capable browser of its own.
"We've been concentrating on other platforms that don't have browser or didn't have a good one," Schroepfer said in May 2008. "I'm looking forward to (Google) opening up the entire platform. Today I can't get Firefox on Android because I don't have the API (application programming interface) support.
The browser that ships with Android is based on the open-source WebKit project. That's the same foundation for Google Chrome, Safari on Mac OS X and the iPhone, and the browser on the new Palm Pre, making it something of an incumbent power among high-end mobile phones.
It's not a simple choice to releasing software that uses the Native Development Kit. Using the higher-level Java foundation insulates programmers from worrying about what underlying hardware is in a phone or other device, but using native code means the software must be tailored for a specific processor. It also means that software won't have access to many system-level features that are part of Android.
And writing native code can help boost performance, always a problem on mobile phones with limited hardware and battery life. In a parallel situation on PCs, Google has released software called Native Client that lets browsers run software natively processors for better performance.
Mozilla is interested in a variety of sub-PC devices. "We're also very interested in Netbooks across the operating system and chip architecture spectrum," Sullivan added. "Firefox, Fennec, and other Mozilla-based browsers have been demonstrated on Netbooks running Windows CE, various Linux variants, and Moblin," a Linux-based operating system for mobile devices backed by Intel.
Firefox's core use is on personal computers, though. There, a new version is imminent.
"The Mozilla team is mobilizing to ship Firefox 3.5, and it's looking like Tuesday morning" will be the ship time, Mozilla said in a statement Friday.
However, Mozilla also has issued three candidates instead of the expected one, and in the bigger picture added many new features to 3.5 that kept its release back months compared to the earlier, smaller-scale Firefox 3.1 plan, so give the organization some wiggle room.
The HTC Hero phone will have Flash support built in.
(Credit: HTC)Marking a departure from the world of iPhone, HTC's new Android-based Hero phone will also come with the ability to handle Flash elements that adorn many Web sites and power YouTube video.
Adobe Systems announced on Wednesday that its Flash Player will be built into the HTC phone, an important step in the company's efforts to spread Flash to mobile phones. The phone, one of several from HTC to use Google's open-source operating system, is scheduled to ship in Europe starting in July and in Asia and North America later in the year.
However, the initial version won't match Flash Player 10, the current version for PCs, which can run programs written with ActionScript 3. Instead, the Android version will handle ActionScript 2 applications written for Flash Player 9 chores, Adobe said. HTC is participating in the Open Screen Project to bring Flash Player 10 to mobile phones through over-the-air updates, though, so Adobe expects fuller Flash support eventually.
"Flash Player 10 for mobile platforms that include Android is expected to be available in the first half of 2010. We are working on delivering a beta of Flash Player 10 in the fourth quarter of 2009," the company said in a statement.
The Flash support will be built into the phone and not available as a download for other Android phone users, Adobe said.
Just having a check mark in a feature list isn't enough to outflank a competitor, but Flash is a significant feature on the Web. It powers many games, streaming videos, and dynamic stock charts, and other elaborate features on Web pages. And Flash is also used for many more dynamic advertisements.
Adobe demonstrated Flash on Android in an online video Wednesday, showing off the technology for watching a trailer at Yahoo Movies, playing the Penguin Swing game, and selecting a region on travel site Expedia. Double-clicking on the Flash element on the Web page runs it full screen.
Apple's iPhone doesn't run Flash, though Adobe would like to see it there and has been developing a version.
"We are developing Flash player for the iPhone. To release software on the iPhone requires Apple's agreement. We have to make it work great, and need to get their agreement to have it released," said Adobe chief technology officer Kevin Lynch in a 2008 interview. "We would love to see Flash on the iPhone."
Correction at 8:05 a.m. PDT to reflect updated information from Bsquare that says it's porting Flash technology, not Adobe's player itself, to Android, and that it's ported Flash to 100 embedded devices in general, not 100 Android devices.
(Credit:
CNET)
Adobe wowed a crowd last November when it demoed a full-fledged version of Flash 10 on T-Mobile's Google Android phone, the G1. We've been waiting expectantly since then to see Flash 10 mobile materialize for Android.
On Wednesday, embedded devices company Bsquare hinted there could be some movement in that direction, though not necessarily from Adobe itself. Instead, the company will partner with "a global, tier-one carrier" to port Adobe's Flash technology to Android's operating system to the carrier's mystery device. Bsquare notes that it has already ported similar technology to roughly 100 devices. While Bsquare isn't quite ready to spill the beans on which international carrier has commissioned its services, we're speculating that it could be T-Mobile, which already won Google's contract to exclusively supply the Android G1 phone in the U.S.
In addition to keeping the carrier name in the dark, it's also unclear what the product's limitations will be, how the ported Flash technology compares to or competes with Adobe's forthcoming offering, and when the finished product will begin to benefit the fine Android owners out there.
Mobile VoIP service Truphone announced Monday that it has integrated AOL Instant Messenger into its iPhone app. Besides being able to place VoIP calls, users can now log in to AOL and instant message other AIM users through the Truephone app. The software already includes support for Google Talk, Skype, Windows Live Messenger, and Yahoo Messenger.
Netbiscuits, a company that provides a Web software platform for mobile development and advertising, announced Monday that it has partnered with AdMob, the world's largest mobile-advertising service, to provide users with the advertising firm's ad placement tools. According to Netbiscuits, its software will offer users the option to integrate ads in mobile video and other media. The terms of the deal were not disclosed.
Google announced Friday that mobile-phone users are now able to modify Google Spreadsheets. According to the company, users can view, edit, sort, and filter spreadsheets on a variety of mobile devices, including the T-Mobile G1 and iPhone.
The Android Market, Google's online repository of applications for the T-Mobile G1 and succeeding devices using the search giant's mobile-phone operating system, now lets organizations charge money for their software.
The T-Mobile G1 updating to firmware 1.1.
(Credit: Stephen Shankland/CNET News)"I'm pleased to announce that Android Market is now accepting priced applications from US and UK developers," said Eric Chu in a blog post Friday. "Initially, priced applications will be available to end users in the US starting mid next week."
Google gives programmers 70 percent of Android app revenue, with the remainder going to wireless service carriers, minus billing settlement fees. Buyers and sellers must use Google Checkout to make their purchases.
Apple has had strong success with its App Store for selling iPhone and iPod Touch applications. Google is taking a different approach with its market, though, relying on users to rate applications rather than screening each one before it's published.
Until now, Android Market had only offered free applications. But Google has been working to improve it from its initial incarnation. "Android Market is able to distinguish among different Android devices. As devices are released, Android Market will ensure that users only see applications that will work correctly on their devices," Google said.
Support in other countries will follow. "We will also enable developers in Germany, Austria, Netherlands, France, and Spain to offer priced applications later this quarter. By the end of Q1 2009, we will announce support for developers in additional countries," Chu said.
Chu also said free applications would be available through Android Market in Australia beginning Sunday and in Singapore "in coming weeks."










