That's basically 99.99% crash free users every day.
DELTAGRAPH WINDOWS 10 CODE
The team I am on wrote a giant addition to on of our 4 apps recently, where we added basically 40% more code to the app after 16 months of effort, and so far this code, which is used by most of our customers though not all, contributes around 1 in 10,000 to the crash rate. Despite the rather sketchy iOS betas the new app started off at 1 in 700 and when Apple fixed a load after free in MapKit, it improved to 1 in 1400 and stayed there pretty much the entire 8 months it existed, before the brand was sold and all of our tech was furloughed. Even though those are quite acceptable for most people I still view them as not good enough.Īt the travel company we replaced our flagship iOS app with a brand new from scratch app that launched on iOS 7 launch day (Apple wanted us there). Right now 3 of the apps are seeing around 0.3% (1 in 300) and one is terrible at 2.5% (1 in 40). We typically ship 4 apps at once (2 apps for different business units on iOS and Android) about 7 or so times a year. Now I don't consider the average rate even remotely acceptable. At my well known employer the alerts appear whenever the crash rate hits 1.5% for 15 minutes. There hasn't been a comparable report since then, but due to improving tools and especially on iOS with ARC and Swift, I think it's likely more like 1.5% or lower.
DELTAGRAPH WINDOWS 10 ANDROID
So what is a good, bad, or average crash rate? A few years ago when Crittercism existed they released a report showing the average iOS and Android app's crashed at a 2% (or 1 in 50) rate. Since then I view crash reports almost every day, even for our apps I have nothing to do with. When Crashlytics first appeared (I think it was them) and I saw the first live reports from our iPad app, I was hooked.
DELTAGRAPH WINDOWS 10 DOWNLOAD
When I first started at the travel company (now sadly just a brand of our former competitor), during the iOS 5 timeframe, the only crash reporting was in Apple's iTunes Connect, and it sucked and often failed to download anything. Usually I like to use the 1 in 100 style. Whichever makes more sense to you it is a consistent and comparable way at looking at crashes between time periods, versions or apps. There are multiple ways to look at a crash rate, as how many launches resulted in a crash (as in 1 in 100) or the percentage resulting in a crash (1%) or as the percentage without a crash (99%). Usually I look at 24 hours worth-our mobile apps are used 24x7 but practically 16 hours a day.
The crash rate is typically calculated as a count of the number of app launches in a period divided by the number of crashes in the same period. Along with various analytics one of the most useful and objective stats you can use to tell how well you did and what your customers are seeing is the crash rate. Today the options for knowing what the end user is experiencing for desktop and particularly mobile apps is amazing. When I shipped my first app 30 years ago, once we put it on a floppy and in the box and sent it away we had basically no idea what the ultimate customer experienced-unless they called us. What Your App's Crash Rate Can Tell You August 26, 2017
0 kommentar(er)
