Approach mobile development with all the tools you need—not with one hand tied behind your back. Continue reading “What Mobile App Developers Need to Know About Performance Tools”
“If a tree falls in a forest and no one is around to hear it, does it make a sound?” Virtually everyone has heard of this philosophical thought experiment, yet few developers realize how much it applies to their development efforts, especially when it comes to the realm of logging.
Continue reading “The Fallacy of Logging”
It’s estimated that only 16% of customers will give an app more than two opportunities if it fails to work the first time. Still, other research has shown that up to half of mobile users will delete an app if they encounter even a single bug. Further complicating the issue is the fact that there are some 2,100,000 apps on the Apple App Store and approximately 3,763,223 Android apps.
According to Andrew Chen (general partner at Andreessen Horowitz) and Ankit Jain(founder of Quettra and former head of search & discovery for Google Play), the average mobile app loses some 77% of its user base within the first three days after a user installs it. Even more shocking, within the first 90 days, the average app has lost over 95% of its user base. The evidence suggests that most users make up their mind about whether or not to keep using an app within the first three to seven days.
VCs and innovators need to wake up: A new wave of mobile growth is under way
Lately, there’s a growing consensus that innovation and growth in mobile is over. It’s said that investment money has dried up, ideas from entrepreneurs aren’t pouring in at the same velocity, the app economy has stalled, etc.
That perspective is short-sighted and incorrect. Mobile technologies and services are only becoming more pervasive in our lives and remain the engine that drives new innovation. In fact, VCs and innovators must wake up to the fact that a new wave of exponential growth is just getting started.
Every good mobile engineer has questions that they wish they could answer, if they only had the time. One of those questions, related to concurrent network calls, goes something like: “How many calls can my app do and not impact app performance?” Until recently, no one had actually measured to figure it out — then we did!
We are excited for our latest release focused on taking the first step towards live feedback and continuing to make our SDK have as small a footprint as possible.
Mobile teams are singularly focused on crashes. Understandably so — they are the simplest to identify and diagnose. BUT crashes account for less than 1% of your issues! You still find errors and your users are still complaining.
There are two categories of performance errors that engineers must worry about. The first are visceral issues: those that actually stop the experience altogether and abruptly. These include crashes, which are fairly easy to diagnose and stop, and things like memory issues, CPU pegging, and too many concurrent network calls, which are more difficult.