Pages

Showing posts with label Google. Show all posts
Showing posts with label Google. Show all posts

Tuesday, 30 April 2013

Google to Abandon more Services


Google announced today that it's taking the ax to a handful of services, including Google Reader, in its latest round of spring cleaning.Google said it will retire the RSS reader on July 1, giving users and developers a little more than three months to export their data with Google Takeout to alternative RSS readers. The Web giant said in a company blog post today that its decision was based on declining usage of the RSS reader, which Google launched in 2005.The company also revealed a half dozen other services or features to be eliminated this year, bringing the total number of closures to 70 since it started its spring cleaning campaign in 2011. Google cited the dramatic shift to mobile devices as the impetus behind the latest round of cuts."It's been a long time since we have had this rate of change -- it probably hasn't happened since the birth of personal computing 40 years ago," Urs Hölzle, senior vice president of Technical Infrastructure, wrote in the blog. "To make the most of these opportunities, we need to focus -- otherwise we spread ourselves too thin and lack impact." The company announced today that it will immediately cease sales and updates for photo-editing software Snapseed Desktop for Macintosh and Windows, though it will continue to offer the related mobile app on iOS and Android for free. Next week, Google with end support for Google Voice App for BlackBerry and recommends that BlackBerry users wishing to continue using the app switch to its HTML5 app.For developers, Google is shutting down its Search API for Shopping, GUI Builder and five UiApp widgets, and CalDAV API, which will still be available only to white-listed developers. These tools will close on September 16.Other closures announced today include Google Building Maker, which allowed people to make 3D building models for Google Earth and Maps, and the Google Cloud Connect plug-in, which automatically saved Microsoft Office files from Windows PCs in Google Drive.

Sunday, 28 April 2013

Facebook Home And The Promise Of Android

Facebook Home And The Promise Of Android

If you’re an iPhone user, you might be feeling a little left behind, because Facebook launched an application called Facebook Home, touted by CEO Mark Zuckerberg as the “next version of Facebook.” In fact, you might be feeling this way if you’re an Android user, too. For now, only a handful of select devices can even run Home (officially) — notably missing from the lineup is Google’s Nexus 4, the latest in the lineup of Nexus-branded flagship Android phones — devices that users adopt in particular to stay ahead of the curve when it comes to new app releases.
But Facebook promised that more handsets will be supported in time, as will tablets. Well, only Android ones, that is.
It’s too soon to say whether Facebook Home will live up to the company’s claims and expectations of becoming the new way people interact with the social network, or whether it will go down only as a notable experiment on the social network’s part. If the latter, it won’t be a major loss to the company, as Facebook will continue to have access to data from a core group of heavy Facebook enthusiasts. It will learn what keeps users engaged, what posts and images catch their eye and their clicks, and, eventually, which advertisements do, too. But to those who can’t download Facebook Home today because they’re using the “wrong” smartphone, it’s of small comfort to think that perhaps the product won’t ever really be as successful as Facebook promises. Because for users, what matters is not whether this grand roll of the dice pays off for Facebook itself – it’s whether you have the ability to participate in the game in the first place.
This is the challenge of the new mobile landscape.
Unlike the web, where the worst thing developers encountered was IE compatibility – and yes, that was bad – it was only a matter of time (and hair pulling and screaming) and energy to bring a new idea to everyone who had Internet access and a web browser. Because the web is built on open standards, this sort of thing is possible.
Facebook wouldn’t even be Facebook had this not been the case.
But mobile is a different story, and a potentially dangerous one in terms of progress and innovation, as Facebook Home today proves.
On the one side, you have an Android ecosystem that’s fragmented by operating system version. In fact, Google quietly changed the way it discloses that fragmentation. Now, instead of telling the developer community how many phones run Jelly Bean or Gingerbread, for instance, it tells them how many of those devices are used by people who download apps. It’s an attempt to paint a rosier picture of OS distribution patterns by focusing on the app-haves instead of the app have-nots. (Spoiler: there are a lot of people running old versions of Android out there.)
Then on the other side, there’s Apple. Because of its restrictions, Facebook Home will never be able to run as intended on iOS operating systems. That’s not necessarily a bad thing, to be clear. It’s just a statement. Apple deserves plenty of credit for helping technology become an interest of the mainstream – a group that felt its former interfaces, configurations, and command lines too complicated and confusing. Or worse, simply not fun. The iPhone wasn’t the first smartphone, but it radically altered the way that people interact with – and learned to love and care about – technology.
But if we’re giving Apple credit for sparking this trend, lets give them credit for potentially stalling progress here, too.
It’s only a few years into this new paradigm of computing, and things are already starting to feel a little dated. We’ve become accustomed to, bored with, and finally overrun by mobile applications. So the shift ahead of us is enabling new experiences – possibly those that put an app-centric interface secondary. Android is well on its way to enabling this, with its potential for customizations and widgets, as well as the deep hooks that apps can sink into the underlying operating system.
Apps like Facebook Home.
Facebook Home, however, is but the first high-profile example. A niche group Android users have been doing this for years on their own with third-party widgets, launchers, and replacements for core applications.
Android is not an ideal landscape overall. (See: fragmentation issues above. See also: app quality, developer revenue potential, etc.) In other words, this is a not a statement about who wins the larger war, it’s about who wins on this particular battlefront. That said, in terms of enabling a new mobile experience, Android is now more promising than iOS. Of course, you may think that Facebook Home itself is a terrible, horrible thing that you would never consider installing on your own phone, and that’s just fine.
The point is, it’s a different idea. It’s not really an Android launcher, it’s only inspired by them. And even if you have no particular affinity for Facebook itself, you might for the next company that follows it. Because someone will. In fact, one already has: Korean messaging giant KakaoTalk just announced plans for a Facebook Home competitor of its own.
More will come.
And later, it won’t be just about direct copycats like KakaoTalk, or the third-party developers promising DIY “Home-like” experiences, either. Facebook Home’s existence speaks to a world where developers will be prompted to think beyond applications and the isolated experiences they deliver. With the layering, and overall well-designed nature of the Facebook Home feature called “Chat Heads,” we’ve been shown the potential to build entirely different ways of interacting with our devices. Period.
This is the path of innovation. Someone takes a bold step forward with a new idea. Eyebrows are raised, pundits opine, testers review, but ultimately a thing dies or lives in the hands of the everyday users. You.
Facebook Home itself might not make it. It challenges the status quo by making other applications less important than Facebook. That’s a radical enough idea that it could easily fail.
But the damage – whether Facebook Home succeeds or not – is already done. Facebook Home is something else. Wired called it an apperating system. That’s perfect. It exists somewhere between apps and phones. It dug out a whole new space, now begging to be exploited, experimented upon, and filled with new ideas.

Chrome and Android’s Excellent Collision Course



Andy Rubin left Android, and Chrome and Apps boss Sundar Pichai is taking over. Desktop melts into mobile. It's a familiar dance, following iOS and OS X and the whole Windows 8 philosophy down the same convergence rabbit hole. But this one is a little different.It's clear by now that the merging of desktop and mobile is the endgame for tech's major players. Apple has been moving iOS and OS X closer together for years; bits like Reminders and Notes and iMessages traverse seamlessly from one OS to the other. Microsoft went in even harder with Windows 8, tying Windows desktop to a whole new interface aimed at bringing mobile and desktop experiences closer together. Both approaches worked, mostly. Windows 8 tablets and hybrids and Windows Phone 8 handsets are great in conjunction with Windows 8 computers. iPhones and iPads work quantifiably better with OS X.
But what if Android were brought under Chrome's umbrella wholesale? If its reminders and syncing and everything else were all handled natively in the Chrome browser? By converging on Chrome, Google can give Android the same level of integration that Apple and Microsoft strain to provide within their own OS gardens, except on any computer that runs Chrome. Just plug your Android phone or tablet into any laptop, and it's as at home in Chrome as an iPhone would be on a MacBook. After a Chrome convergence, Android could work perfectly with anything. That would be huge.
At the very least it would be an improvement over Android's current relationship to most desktops, which is basically nonexistent. Syncing files requires cumbersome and anachronistic syncing apps, and even more fluid cloud solutions like Drive and Play Music require apps that are less than seamless to get things done. Which makes no sense, really. It can feel like you're using third party hacks to get your stuff onto your phone or the cloud, where it exists wonderfully thereafter. All you can really do with a Chrome/Android pairing is fling web pages and bookmarks back and forth.
A merger with the Chrome ethos would offer welcome short-term benefits for Android as well. For a company that has such wide-reaching capabilities, Google's parts haven't really worked in harmony. For years, Search was its own app. The Android Gmail app is wonderful, but closed off from deeper integration like BlackBerry 10's Hub idea. And only recently has Google Now started to synthesize the power of having all this data, spitting out useful cards keyed into your searches, calendar events, and email alerts. A tighter integration would go a long way to breaking down some of these walls between services, like not being able to pull a Google Drive photo into your Google+ account. It's probably not a coincidence that Google Now coming to Chrome, iOS, and Windows 8 was announced just a few days ago in the latest Chrome beta build.
And then there's this: mixing Chrome with Android puts Google in perfect position to build a Surface-like hybrid that beats Microsoft to finding the sweet spot of desktop and tablet. The Pixel is flawed in a lot of ways—specifically its insane price tag—but it's a drop-dead gorgeous piece of hardware. And it's easy to see how its tall screen could pull double duty as a tablet—just tap and swipe the screen. It's already got a tablet-ready resolution on it, unlike other laptop/tablet hybrids. Google's also gotten pretty good at building kits to export Android apps, like you saw with the droves of BB10 apps made from converted Android versions. The benefit to a desktop OS like Chrome OS might be limited, but could help get some butts in the seat.
But that's getting ahead of ourselves. Big picture? Services like Search and Gmail are more popular than Android. Bringing everything under the same tent makes Android vaguely more pleasant to use if you're already an established user, but more importantly would go a long way to dispelling the image of Android as an overly complicated pain in the ass to anyone who hasn't used it, or even subverting the entire "Android" brand. Oh, you got an Android? Just plug it into Chrome and you'll be fine.
It will be a slow process, of course. There will probably be additions made here and there, features added as they're needed. Getting Android's messy notifications under control with a push to a Chrome-based notification center would be a great start. But the future of Android is clearly Chrome, and Chrome's is Android. That's welcome news for Google, and even better for you.