post

IBM’s mobility play: MobileFirst

by

Airplane mode on iPhone

One of the big talking points at this year’s IBM Pulse was IBM’s recent unveiling of its new platform for mobile, MobileFirst. My colleague James covers the announcement in details on his RedMonk blog, but I thought I’d talk a bit about the GreenMonk perspective, as we haven’t covered mobile here very much to-date, and it is becoming increasingly pervasive.

Mobile is now huge. I know this is self-evident, but it is totally game-changing. Now everyone is instrumented, interconnected, and intelligent, as IBM themselves might say.

What does this have to do with sustainability? Well, we here at GreenMonk take a broad view of Sustainability and as we noted in our write-up of the Pulse conference, IBM’s Smarter initiatives all play to a sustainable agenda. Sustainability is all about doing things more efficiently. Mobile definitely enables that.

You only have to think of the application IBM rolled out last year to help staff and students crowdsource cleaning up of the Los Angeles Unified School’s District. And, it is also making a big splash in the Enterprise space, as witnessed by SAP’s Operational Risk Management mobile app; the ESB and IBM mobile app to help finding and scheduling charging of electric vehicles in Ireland and many similar initiatives.

And there’s also social – I wrote a blog post last November about the intersection of big data, social and sustainability. What does this have to do with mobile? Well, in each of the examples outlined in the blog post, a significant amount of the data would have been entered via mobile. People as sensors. The internet of everything.

There are lots of other examples in healthcare, smarter cities (the Boston mobile app I mentioned in this post), education, etc.

The one place IBM may be missing a trick in mobile? Mobile endpoint energy management. IBM have an endpoint management app for mobile, but it’s focus is more on security than energy management, but, as we’ve noted here previously, battery life is a significant pain point for mobile users. A user whose device is out of battery, is a frustrated, disconnected, unproductive worker.

An Endpoint Management solution which manages mobile battery life (by having low power modes, or by automatically shutting down all but the frontmost app, or similar, for example) would be a definite win for any enterprise.

Full disclosure – IBM paid travel and accommodation for me to attend Pulse.

post

Smartphone energy management – when will there be an app for that?

by

Mobile energy saving app?

I wrote a post last week about mobile endpoint management applications and their potential to extend smartphone battery life. It seems it was a prescient piece given the emergence this week of a study from Purdue University and Microsoft Research showing how energy is used by some smartphone applications [PDF].

The study indicates that many free, ad-supported applications expend most of their energy on serving the ads, as opposed to on the application itself. As an example, the core part of the free version of Angry Birds on Android uses only 18% of the total app energy. Most of the rest of the energy is used in gathering location, and handset details for upload to the ad server, downloading the ad, and the 3G tail.

This behaviour was similar in other free apps, such as Free Chess, NYTimes which were tested on Android and an energy bug found in Facebook causing the app to drain power even after termination, was confirmed fixed in the next version released (v1.3.1).

The researchers also performed this testing on Windows Mobile 6.5 but in the published paper, only the Android results are discussed.

Inmobi’s Terence Egan pushed back against some of the findings noting that

In one case, the researchers only looked at the first 33 seconds of usage when playing a chess game.

Naturally, at start up, an app will open communications to download an ad. Once the ad has been received, the app shouldn?t poll for another ad for some time.

Hver the time it take to play a game of chess (the computer usually beats me in 10 minutes) a few ad calls are dwarfed by the energy consumption of the screen, the speakers, and the haptic feedback.

Although, in a tacit admission that this is a potential issue further down in his post he lists handy best practices for developers to make “ad calls as battery friendly as possible”

The iPhone iOS operating system wasn’t looked at in this study at all but it is not immune from these issues either. And, in fact, reports are emerging now that the new iPad is unable to charge when certain energy intensive apps are running.

While it is important to remind developers of the need for green coding, not all coders will heed the advice and there will always be rogue apps out there draining your smartphone’s battery.

And this is not just a consumer issue – for enterprises it is important to keep the organisation’s smartphone owners happy, connected, and above all, productive. A drained battery is ultimately a disconnected, unproductive and frustrated employee. Reducing a phone’s energy use is, obviously a sustainability win too.

Mobile endpoint management applications could use technology similar to the eprof software used in the study, to identify bugs or rogue applications on phones. This could be reported back to a central database to alert users (and app developers) of issues found.

With more and more apps coming on the market, this is an issue which is only going to become more pronounced. Someone is going to come out with a decent mobile energy management app sooner, rather than later. It will be interesting to see where it comes from.

Photo Credit Tom Raftery