US 11,860,717 B1
Graphical user interface for presenting crash data
Konstantinos Polychronis, San Francisco, CA (US)
Assigned to Splunk Inc., San Francisco, CA (US)
Filed by Splunk Inc., San Francisco, CA (US)
Filed on Oct. 11, 2022, as Appl. No. 17/963,637.
Application 17/963,637 is a continuation of application No. 17/459,163, filed on Aug. 27, 2021, granted, now 11,500,709, issued on Nov. 15, 2022.
Application 17/459,163 is a continuation in part of application No. 16/526,586, filed on Jul. 30, 2019, granted, now 11,194,647, issued on Dec. 7, 2021.
Application 16/526,586 is a continuation of application No. 15/663,513, filed on Jul. 28, 2017, granted, now 10,409,668, issued on Sep. 10, 2019.
Application 15/663,513 is a continuation of application No. 14/697,427, filed on Apr. 27, 2015, granted, now 9,747,152, issued on Aug. 29, 2017.
Int. Cl. G06F 11/07 (2006.01)
CPC G06F 11/0769 (2013.01) [G06F 11/079 (2013.01); G06F 11/0742 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computer-implemented method comprising:
providing, at a developer device, a graphical user interface configured to present crash data associated with crashes of a mobile application on mobile devices, the crashes having occurred during user transactions conducted with the mobile application, the crash data comprising:
a list of crash types of the crashes;
a first transaction attribute associated with the crashes and generated by aggregating application data of the mobile application provided from the mobile devices; and
a second transaction attribute indicating a transaction status, of one or more of the user transactions, determined to correlate with a first set of the crashes, wherein the second transaction attribute comprises a monetary amount associated with a set of one or more items determined to be abandoned in association with the first set of the crashes; and
modifying the mobile application, to reduce subsequent occurrences of an error, based on analysis of at least a portion of the crash data.