AT&ampT Labs: We Want More Energy-Efficient Apps (And Here’s The Way We Get It Done)


In This summer Mike authored in regards to a new AT&T Labs Research are convinced that required a glance at finish to finish data transmission pathways so that they can understand why some apps drain a lot battery existence or are slow. They “discovered the origin from the issue in the complex interactions between your application, tool and cellular network, searching into network architecture minimizing level protocols which are typically hidden from application developers.” Here’s the main from the issue as well as an example from AT&T’s report:

Particularly, application developers are often not aware of cellular specific characteristics that incur potentially complex interaction using the application behavior. For professional developers, they frequently don’t have visibility in to the resource-restricted mobile execution atmosphere.

Such situations potentially lead to smartphone applications that aren’t cellular-friendly, i.e., their radio funnel utilization or device energy consumption are inefficient due to a insufficient transparency within the lower-layer protocol behavior.

For instance, we learned that for Pandora, a well known music streaming application on smartphones, because of the poor interaction between your radio resource control policy and also the application’s bandwith scheduling mechanism, 46% of their radio energy is allocated to periodic audience measurements that take into account only .2% of received user data.

Within the most lately released highlight from the report, AT&T Labs Research identifies 11 methods to build efficient apps which will work regardless of what carrier you’re targeting (all of the recommendations are targeted at carrier-independent standards and protocols). Here’s their email list:

  • Understand Mobile Systems
  • Handle Multiple Synchronised TCP Connections
  • Reduce Inefficient Connections with Periodic Transfers
  • Cope with Connection Opening Problems
  • Close Connections As Quickly As Possible
  • Offload to Wi-Fi
  • Handle Duplicate Content and Caching
  • Utilize Pre-fetching
  • Manage Peripherals
  • Upgrade from HTTP 1.
  • Handle Screen Rotations

Now let’s break lower a couple of. Because the first couple of tips were pretty much covered in July’s initial publish, we’ll jump lower their email list a little.

Offload to Wi-Fi

Every single mobile network uses cell towers to transfer data to cellular devices, and utilizes a RRC condition machine to handle radio stations sources efficiently. This means that 3G, LTE and EVDO systems, whatever the carrier, all operate on a condition machine.

Wi-Fi connections, however, tend to be more effective from the battery and network perspective, because there’s no latency for connection setup, and for that reason no requirement for the condition machine. Like a developer, this can be used to your benefit. Sneaky, you.

All that you should do is offer your users the chance to connect with Wi-Fi when it’s available. And you will find a lot of benefits:

  • Lower data costs
  • Faster connections
  • Lower battery drain
  • Improved network traffic
  • Improved customer experience
  • And promotion delays (TCP handshake) drop from ~2 seconds towards the nanosecond time-frame – allowing happy to appear without just as much delay.

 Utilize Pre-Fetching

Installing files “as needed” can slow the consumer experience. If your user scrolls with the primary screen of the application and it has to hold back for images to load, the applying seems slow. And no-one likes slow applications.

There is a simple solution, “pre-fetch” your computer data.

Pre-fetching means grabbing chunks of information awaiting what your user may wish to see. For instance, in case your user is installing the score of the baseball game, it’s safe to visualize he (or she) might want the entire box score and game summary too.

Pre-fetching this data reduces the amount of connections-and also, since each connection takes two seconds to setup prior to the download may even start, the application can look considerably faster.

Now, we’d be remiss when we didn’t point out that pre-fetching data could be overdone. It comes down lower to some delicate balance.

Find out more >>>

Handle Screen Rotations

Many apps are written so the device pings the server every time the consumer rotates the screen, despite the fact that there’s no switch to the information the consumer is experiencing. These pages don’t need to be reloaded – Um, hello… Discuss a waste.

What in the event you do rather?

Do this on for size. Track the orientation alternation in the application and send the data at scheduled times along with other data, instead of at random opening separate connections. Bingo!

If you wish to begin to see the break outs of 11 tips, visit AT&T’s Build Efficient Apps article. “Handle Duplicate Content and Caching” is definitely an especially good point and also the researchers provide you with a number of ways to treat the problem from various angles (which is why we didn’t highlight it above – you will find a lot of recommendations for us to list out within this publish!).

For any more in-depth understanding of all of the research, browse the AT&T Labs Research official report.


The author admin

Leave a Response