Twitter’s Crashlytics has iOS developer’s backs with a new out of memory (OOM) reporting feature, a first for any crash reporting platform. For users, OOM crashes are just like any other app crash, and most reporting platforms file them as a basic crash. The problem is developers don’t get granular details on why an app crashed, leaving them to fret over the scariest question any developer faces: what happened? On iOS, developers who have Crashlytics and Answers Kits enabled on their apps will now see OOM events broken into their own categories. It tells a developer the overall sessions affected by…

This story continues at The Next Web