In the past 6 months, I’ve seen more and more infrastructure companies focused on network data optimization (and why shouldn’t they be with video consumption continuing to explode and now representing 40% of all data load). On the other hand, from an operator perspective, the introduction of data caps in creates the downside protection they need (eg if someone is being data abusive, they are paying a significant premium for it) – not a bad situation for the operator.
That being said, what I haven’t found much focus on is the shift of data consumption responsibility to the developer. Developers need to build network-efficient applications and unfortunately, I still haven’t found a best practices / guidelines for developers to adhere to.
I’m definitely not a network expert but certainly developers should keep in mind the following:
1. Chatty vs queued (I’ve heard that the opening/closing of network connections causes unnecessary pain; developers can design around this?)
2. WiFi vs 3G (It’s not difficult to determine network speed and then determine whether to do the “large” or “small” download. This is similar to how in prepaid days, apps may wait until nighttime to download data because of the cheaper tariffs)
3. Roaming or not (This would require network APIs to be available but assuming it is, this would absolutely impact when the application should be transmitting data)
4. Load on the network (Again, this would require network APIs, but knowing load can be used to a developers advantage)
5. Compressed vs uncompressed (Many argue that the PC resulted in inefficient app development and mobile made you efficient again with limited storage/memory/CPU etc. Now that mobile is the new PC, that may be happening again. If you have a server-based application, why not compress?)
And the list goes on…
Operators need to put more pressure on developers in writing network-efficient apps rather than pushing data caps, IMO. Let me know if anyone finds a list of best practices?
Follow This Blog Via Email
- SXSW 2016: Messaging Bots
- Reflecting on the Productivity Category
- Tech Discrimination
- Daily Active Users Don’t Matter!
- IOT: The Competition for Attention
- How Google and Others Are Using Data Science to Speed Up Productivity
- Why I’m Excited About Google Glass?
- Context Is a Layer and Not a Category
- Sales 2.0: The Bottoms-Up Sales Model
- Is UX Going to be Commoditized Next?
- To Win Enterprise, Target the Consumer
- Using a Chromebook for a Week
- Android (and the Tab!) in the Enterprise
- Ad Learnings from Recipe Search
- CPA Advertising on Mobile
- Enterprise Mobile Is Hot!
- Network Responsibility
- In-Door Mapping
- The Social Network
- Using a Mobile Phone to Drive Behavior Change
- Apps vs. Web Apps
- Understanding Developer Psychology
- Are Batteries Improving?
- Over the Air and Emerging Markets
- Are Platform Game Lobbies the Next Social Graph?
- Are Plugins (and Flash) Going Away?
- Lessons Learned in Monetization
- Understanding the Emerging Market
- OEMs, Please Choose
- Understanding PDE (Positional Determining Entity)
- Has the Power Shifted Back to Operators?
- Is the Killer App the App Store?
- Navigating the Mobile Content Landscape
- Wholesale Application Community
- Sharing Overload?
- The Ad Ballot
- Device Patent Wars
- Is Apple Making a Mobile Wallet Play?
- Top 6 Reasons Why Nokia Doesn’t Have a Capacitive Touch Screen
- Mobile Trends 2020
- Mobile Taking a Cue From the Travel Industry
- CTIA Party Analysis
- Measuring AT&Ts Network
- Mobile Cloud Computing
- Mobile Beyond & NARIP
- Mobile 2.0 Advertising Notes
- Carnival of the Mobilists #193
- The Broken Subscription Model
- The Mobile Reserve
- The Fragmented Web
- Got to Love the Music Industry
- What Platforms Should I Build For?
- To Operator or to Not to Operator
- What Do Bankers Do?
- My Older Posts