As a consumer, we are mindful of which apps keep our phones running very hot. We've had our own suspicions... But this might be the first time we are seeing analytics on mobile apps' misbehavior -- in the form of rankings. It tells us which mobile apps are costing networks' bandwidth, consumers' battery and apps developers' chances to get bundled in the operators' packages.
Seriously, though, this report isn't just for consumers or for apps designers. It goes to the heart of the matter for those who are designig network gear, I believe. Take a look at those apps on the "watch list."
Those apps, once they catch on, could change what the next-gen communication equipment need to handle -- almost overnight.
But the network providers will be happy if some apps use lots of bandwidth...consumers wil pay for it eventually...it remind me of Intel-Microsoft strategy of selling bloated software so you have to buy next gen just to keep up
Not so fast, Kris. Network operators hate the growing capex. They are under a constant pressued to come up with a clever "data plan" package to sign up more subscribers, and yet they don't want caught flat footed by some surprise apps consuming lots of signaling in their network.
So in spite of Comcast's much-advertized worries, Netflix creates a little less data volume than YouTube, and is much better than most of the listed apps for signaling efficiency. Not bad, I'd say, for a service that streams HD movies.
I always pay attention to your articles, Junko! :)
It would be interesting to get a normalized listing of these different apps, so you get a better idea of how well they are written. Obviously, a very popular app will create a greater overall load, but an elegantly written app has its own appeal.
We need obsessively compulsive designers, who don't mind going back to work the next day and fix what they did yesterday, which has kept them on edge all night. And managers who understand why this is important. In the rush to get things out, there's a lot of half-*ssed work going un-optimized, I'm afraid.
A Book For All Reasons Bernard Cole1 Comment Robert Oshana's recent book "Software Engineering for Embedded Systems (Newnes/Elsevier)," written and edited with Mark Kraeling, is a 'book for all reasons.' At almost 1,200 pages, it ...