A nice new update is headed for the Gmail for Android app today. The biggest change will be for those who are lucky enough to be on Android 4.1 Jelly Bean or higher. Expandable notifications coming from the app will now include the ability to reply to an email, delete an email, or archive an email straight from the notification without having to enter the app.

If you’re on Ice Cream Sandwich or higher, you’ll get a faster search experience, and some typical bug fixes and performance improvements. Finally, those on Android 2.2 and higher can all expect enhanced performance and a new Labels API for third-party developers. There’s not much more to it than that, so you’ll probably want to go ahead and grab the upgrade as soon as possible. You can do just that in the Google Play Store.

Windows Azure has added new support for a number of services including PhoneGap, Dropbox and Hadoop.

According to a blog post by Scott Guthrie, a corporate vice president in the Microsoft Tools and Servers group, developers can connect both HTML5 web-client apps, Apache Cordova/PhoneGap and Windows Phone 7.5 clients to use Windows Azure Mobile Services as a backend. The new mobile services web client library, he writes, supports Internet Explorer 8 and “current versions of Chrome, Firefox, and Safari, plus PhoneGap 2.3.0+.”

Windows Azure also now supports site and app deployment from Dropbox to any website.

Windows Azure is also supporting Mercurial repositories when setting up continuous deployment of websites from CodePlex or Bitbucket repositories. They have also made updates to the user interface.

HDInsight, a new service for Windows Azure, provides the capability to deploy, manage and use Hadoop clusters running on Windows Azure.

The Windows Azure user interface is a differentiator for Microsoft. It is consistent with the company’s user interface. That’s compared to Amazon Web Services, which is still most widely used to program from the command line.

After much fanfare the Pebble smartwatch made the leap from fanciful concept to full-fledged product earlier this year, but now that units have started to ship and people have started to wear them, what’s Pebble’s next step?

Why, enticing developers, of course. Pebble founder Eric Migicovsky noted in a backer update video released earlier this morning that an early version of the smartwatch’s watchface SDK would be made available to would-be Pebble developers during the second week of April.

And when I say “early version,” I mean early version. At this stage it’s being looked at as more a proof-of-concept release than anything else, and Migicovsky points out that there’s a “99% chance” that the team will revamp some of the underlying APIs involved. What’s more, anyone expecting the ability to use the SDK preview to tap into the Pebble’s sensors and radios (like the accelerometer for tracking movement) will come away disappointed — the release is geared strictly toward new watchfaces, though Migicovsky says that games are also fair game as they rely mostly on button inputs.

The early SDK has been in testing with “hacker” backers — a group of about 100 people who pledged $235 or more for the privilege of early tinkering rights — for the past few months, and some of the apps they’ve created will be released alongside the SDK. The most notable new app? A low-res (and therefore faithful) reproduction of Snake that hearkens back to Nokia’s feature phone glory days.

Granted, new watchfaces may not seem like the most crucial addition even to Pebble buffs, but the impending release marks a pretty dramatic shift in scope for the Pebble team. What once started as a company whose daily operations were completely dictated by the need to manufacture and ship over $10 million worth of gadgets is now a company gearing up to focus on the next stage of the Pebble’s life cycle: building up the app ecosystem so the value of owning a Pebble extends beyond the wow factor of wearing a tiny e-paper display on your wrist. Migicovsky concedes that Pebble hasn’t “done the best job so far of communicating with developers,” but the team looks very willing to change that — hopefully a full-blown version of the SDK shows up sooner rather than later.

Update 34 – Pebble Watchface SDK in April from Pebble Technology on Vimeo.

It’s not a huge surprise that Google is dropping Google Reader, the blog reader it operated since 2005. After all, they’d let it go for some time now (not that I’m complaining – it was after all, a free service, a fine product, and a boon for the overall ecosystem of blogging, podcasts and RSS).

The reality, though, is that Google operates at vast scale, and a niche consumer product like Reader just doesn’t move the needle. As crazy as it may sound, today even a billion-dollar business is simply a distraction to Google (unless, of course, it’s well on the way to becoming a five-billion-dollar business).

So all those who are signingpetitions to Google(and even one to The White House!) are missing the bigger point: that this is a victim of the company’s DNA, one that’s accelerated under Larry Page’s management. Some companies specialize in keeping the status quo, others specialize in moving forward. Google is the latter. If the company maintained every niche product with N thousand fans, even paying ones, it’d become the very bungling bureaucracy we love to hate. For a company with Google’s ethos and standing, any such dead-end, non-revenue-producing product that’s retained is holding others back, and prevents the company from moving forward and making true innovations instead of incremental improvements.

Open standards just a means to an end

While Google is giving up on Reader, I believe the company will still embrace subscriptions in a big way, just without RSS (by which I mean RSS, Atom, PubSubHubbub, etc.) Sure, they may continue to lean on RSS as part of their technical infrastructure – e.g. Googlebot will still be crawling external RSS feeds to identify fresh content – but users won’t see those three letters or the shiny feed icon that accompanies them.

To understand why Google’s walking away from RSS, look at Google’s relationship with open standards over the past decade. Google has experimented with various open technologies and found it difficult to win over Google-scale audiences and developers. The list of casualties would include OpenSocial (present in Orkut but not Plus), Activity Streams (present in Buzz, but not Plus, though certainly an inspiration), Social Graph API (no longer available) and RSS (not just Reader, but Feedburner is fading out and podcast app Listen was killed months ago).

Furthermore, Android has been a stonking success for the company, and while it may be open source, with a relatively open store policy, it’s not particularly based on open standards in the way that ChromeOS, WebOS, and now Firefox OS are.

So overall, Google’s lesson has been to lead with a compelling user experience first and then build an API from there, an API which may be based on open standards, but only if it’s a means to an end. Developers are much more attracted to a big market than a glorious proclamation of Open. It’s this philosophy that explains why Google has been so cautious with the Google Plus API.

Doubling down on media

Google isn’t giving up on blogs and media. Far from it. They already have Google News, Google Currents, and Google Now. And on Plus, they have vibrant product pages and communities. The Economist, Time, and ESPN all have over 2 million followers, for example.

This comes at a time when Facebook has been facing a backlash from journalists, with people saying that unless you’re paying for sponsored posts, it doesn’t show up in streams. Facebook’s recent design aims to fix this with a separate Subscriptions area, but as discussed on this week’s TWIT, it’s looking more like they experimented with subscriptions, that it wasn’t core to their business of connecting individuals, and now it’s off to the side.

So Google has an opportunity to win over media brands right now, and I believe they’ll be placing an emphasis on this in their own apps like Currents, as well as on Google Plus proper. In many respects, Currents is exactly what you’d expect from Google in 2013. It’s pretty, mobile-native, and “just works” without anyone having to learn the details of RSS.

Looking further ahead, Google has a vision heavily influenced by machine learning. The company has long known that the best search is the one you didn’t have to make, and this always-on attitude is now coming to fruition with Google Now. Google Now anticipates what users might be interested in at any time, and that includes the kind of articles people might presently be discovering on Google Plus.

Reader’s demise is understandably a sad moment for many, but I believe in time, it will be a positive for the overall ecosystem. Google simply wasn’t innovating on Reader, and as people shift over to services like Feedly or Newsblur (and new ones are popping up as I write), those companies will have extra incentive to innovate and extra resources to do so. Meanwhile, Google will continue to work on what it does best: boiling oceans and shooting for the moon.

Michael Mahemoff previously worked at Google and is founder of cloud podcasting serviceplayer.fm. Follow him on Twitter @mahemoff.

Have an idea for a post you’d like to contribute to GigaOm? Clickhere for our guidelinesand contact info.

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

• The 2013 task management tools market
• How consumer media will change in 2013
• Social 2013: The enterprise strikes back

The impending demise of Google Reader has major implications for the app development community; Google's RSS service had become the de facto standard for third-party clients, and users and developers alike will need to find an alternative. Popular news aggregation app Feedly thinks it has a solution, though — it's been working on a project that clones the Google Reader API, and says that users will see a "seamless transition" once Reader shuts down.

It sounds like other clients will have the option of Feedly's solution, too; a statement provided to GigaOm says that since the Feedly-created API is supposed to be identical to Google's, other clients should be able to plug into the service in the same way. However, Feedly notes that...

Continue reading…