Don’t Crash the Party: How to Ensure Your App’s Stability?
0 likes384 views
This document discusses how to prevent app crashes and ensure stability. It identifies crashes as a developer's worst nightmare and a major cause of uninstalls. The document then provides several solutions to minimize crashes, including careful management of memory, never blocking the main thread, using crash reporting tools to identify crashes, testing compatibility across different devices, and prioritizing features to reduce memory usage. The overall message is that acknowledging and addressing crashes is key to creating a stable app experience for users.
Don’t Crash the Party: How to Ensure Your App’s Stability?
- 1. Don’t Crash the Party: How to Ensure Your App’s Stability?
- 2. TABLE OF CONTENTS What's a developer worst nightmare? “My name is…And my app sometimes crash…” “The courage to change the things I can…” Crash solutions: Careful management of memory Crash solutions: Never block the main thread Crash solutions: Know the crashes Crash solutions: Compatibility Make a crashing app, not a crashing one!
- 3. WHAT’S A DEVELOPER WORST NIGHTMARE? That’s right, you guessed it: App Crashes Mobile apps’ quality and performance impact the bottom line. Crashes, especially of the repeated kind, drive the uninstall numbers high and drive your users to run away.
- 4. According to crittercism 32% of all apps have a crash rate of over 2% Source: crittercism research
- 5. So making your app crash-free (or at least crash-low) should be at top of your priority list
- 6. Check! What’s now? There’s plenty you can do to minimize this phenomenon: Making sure you’re aware of your own crashes Familiarizing yourself with the most known and common causes for mobile app crashes Make your app more stable with a relatively small investment
- 7. The first step, as with everything in life, is to acknowledge you have a problem “MY NAME IS… AND MY APP SOMETIMES CRASH…”
- 8. “THE COURAGE TO CHANGE THE THINGS I CAN…” The second step is to understand the possible cause of a crash: Is it low memory and processing issues Is it connectivity problems, poor connections Is it SDK Issues - 3rd party tools interfering with the app Is it device diversity- too many devices, not enough versions
- 9. What can you do to make sure your app stability is optimized and it functions correctly? The big question is:
- 10. Use Caching Group your network requests and fetches, make them small so they won’t overload the device, or make the size customable But be wise – Don’t overload with many context switching as well Prioritize – Dispense with some data or features to save memory CRASH SOLUTIONS: CAREFUL MANAGEMENT OF MEMORY
- 11. CRASH SOLUTIONS: NEVER BLOCK THE MAIN THREAD Mobile apps that block the main thread, are often declared “unresponsive” by the OS and often result in ANR (Application Not Responding) crashes. Move heavy processing (such as image loading, network fetches, filesystem accesses and so on) to run in background threads But be wise – no need to overload with many context switching as well. To avoid that:
- 12. CRASH SOLUTIONS: KNOW THY CRASHES! Use crash reporting tools such as Crashlytics, Crittercism, and Acra Use SafeDK In-App Protection that offers a “how when and why” regarding your crashes instantly as well as immediate action taking option.
- 13. Test your app on as many devices, platforms, manufactures, generations etc. as possible. Aim to be compatible with as many devices as possible, but know that you can’t be compatible with all of them. CRASH SOLUTIONS: COMPATIBILITY For affordable testing, you can use mobile app testing services and device farms Save your money elsewhere, not in testing.
- 14. While embarking is this journey to keep your crash sobriety, remember: MAKE A CRASHING APP, NOT A CRASHING ONE! Not all crashes can be foreseen ahead of time, but some can. You can learn of your crashes using crash reporting tools. Detect them, learn them and fix them. Not sure how to fix them? Well, try/catch should be your new best friend.
- 15. THANK YOU! contact@safedk.com Ask us anything over email or in the social. We are listening!