Google Inc.

Jessica Lynn Gray

Michael Noth

James Kason Keiger

Siyang Xie

Christopher Rohrs

Adam Sah

Dylan Parker

Steven L Goldberg

Carlos Valdivia

The subject matter of this specification can be implemented in, among other things, a computer-implemented method for application lifecycle management. The method includes receiving crash reports from a first version of an application at multiple initial computing devices. The first version of the application is from a first group of versions. The method further includes determining that the crash reports include more than a threshold amount of crash reports. The method further includes determining that a second version of the application from a second group of versions corrects a cause of the crash reports. The method further includes providing instructions to the initial computing devices to retrieve updates to the application from the second group of versions rather than the first group of versions.

Managing groups of application versions

The subject matter of this specification can be implemented in, among other things, a computer-implemented method for application lifecycle management including providing a first application version to initial computing devices. The method includes receiving first crash reports from the first application version. The method includes determining that the first crash reports include more than a first threshold of reports. The method includes preventing provision of the first application version to additional computing devices in response to determining that the first crash reports include more than the first threshold of reports. The method includes receiving second crash reports from the first application version. The method includes determining that the second crash reports include less than a second threshold of reports. The method includes providing the first application version to the additional computing devices in response to determining that the second crash reports include less than the second threshold of reports.

Application version deployment using crash reports

The subject matter of this specification can be implemented in, among other things, a computer-implemented method for identifying causes of application crashes. The method includes receiving crash reports from multiple computing devices resulting from a problem that occurs in an application in operation at the computing devices. The crash reports include sets of properties that describe system states of the computing devices where the problem occurred. The method further includes identifying similarities between one or more properties in the sets of properties from the crash reports. The method further includes identifying differences between one or more properties in the sets of properties from the crash reports. The method further includes identifying one or more candidates for a cause of the problem in the application based on a clustering of the similarities and the differences. The method further includes generating a report that includes the one or more candidates.

Identifying causes of application crashes

The subject matter of this specification can be implemented in, among other things, a method for crash reporting for resource-constrained devices. The method includes a step for accessing one or more rules for crash data management upon an application crash on a resource-constrained device. The one or more accessed rules take into account at least one resource constraint of the resource-constrained device. The method also includes a step for collecting crash data and communicating the crash data to a crash report management system. Either or both the collecting or the communicating of the crash data is based on the one or more accessed rules.

Collecting application crashes on resource-constrained devices

A system and method for incorporating message catalogs in remote modules. The system and method comprise a container server that identifies one or more modules for use with a container document, receives a module specification from a remote server, and serves the container document with module data based on the module specification, wherein the module data comprises a message reference that identifies a message catalog.

Message catalogs for remote modules

A system and method for serving content in a container document. The system comprises a container server that identifies one or more modules for use with a container document, receives a module specification from a remote server, and serves the container document including module data based on the module specification. The module specification comprises a content element and one or more optional preference elements that enable the container server to provide preferences to the module.

Growing community of inventors

Seattle, WA, United States of America

Jessica Lynn Gray