Don't be "that guy"
As a developer, you understand the complexities involved in building good apps that customers will love. Do you build for Android or iOS, use Titanium or Ramp, sell on Android Market or Amazon's new App Store? Even after you've made all your choices and thrown everything you have into it, you could be disappointed to find that your app is slow to load, respond to input, and even drains battery life.
Nobody wants to be "that guy" whose app gets avoided like the plague — you've got unhappy app users, negative app reviews, and few app downloads as a result. AT&T has recent research that sheds light on why this can happen and how developers can avoid this issue by building better apps.
For the first time, researchers looked at end to end data transmission paths and discovered the source of the problem in the complex interactions between the application, device and the cellular network, looking into network architecture and lower level protocols that are typically hidden from application developers. Beyond just identifying the problem, the research offers best practices and solutions for developers to build responsive and energy efficient apps.
Analyzing PANDORA® internet radio, it was discovered that the streaming music, what the user wanted from the app, was delivered efficiently, but periodic audience measurements were draining battery life. Here is an excerpt of the PANDORA® Case Study:
"While the music itself was sent simply and efficiently as a single file, the periodic audience measurements—each constituting only 2KBs or so—were being transmitted at regular 62.5-second intervals. The constant cycle of ramping up to full power (2 seconds to ramp up, 1 second to download 2KB) and back to idle (17 seconds for the two tail times, the first down from full-power mode and the second down from half-power mode) was extremely wasteful. Of the total amount of device battery energy consumed, 46% was expended on these periodic measurements, less than .2% of the data transmitted.
Once the initial problem was diagnosed—a scatter-burst transmission of small packets—the solution was obvious: bundle the packets into a single transmission. Doing so would result in an easy 40% energy savings."
Mobile development offers unique challenges bringing Internet protocols and wireless protocols together with the utilization of radio resources. And radio is really at the crux of the difference. How does it affect your wireless data connections? Learn how in our new document: Top Radio Resource Issues in Mobile Application Development. Plus, on the other pages in this Best Practices for Building Efficient Apps section, we're passing on tips that will help improve your app on all carriers worldwide, not just on AT&T, because all of the recommendations are based on carrier-independent standards and protocols. And the really good news is that most of these optimization recommendations are easy to implement. In fact, many are simple configuration changes. You'll quickly see the benefits of optimization, including increased application responsiveness, improved efficiency of application code, improved battery life, and last, but certainly not least, hopefully more positive user reviews for your applications.
Read the Top Radio Resource Issues in Mobile Application Development document.
Read the full AT&T Labs Research article.
And, read these Best Practices to help you build more efficient apps: