Abstract: A method of installing an application on a mobile user device is disclosed. A request for the application is received. Information is received related to the mobile user device on which the application is to be installed. A version of an application is determined to send in response to the request for the application and the information related to the mobile user device. The application version is sent to the mobile user device. Information is received related to the performance of the application version. Adapted application determination information is stored related to at least a portion of the received information.

Abstract: A method of installing an application on a mobile user device is disclosed. A request for the application is received. Information is received related to the mobile user device on which the application is to be installed. A version of an application is determined to send in response to the request for the application and the information related to the mobile user device. The application version is sent to the mobile user device. Information is received related to the performance of the application version. Adapted application determination information is stored related to at least a portion of the received information.

Abstract: A method of installing an application on a mobile user device is disclosed. A request for the application is received. Information is received related to the mobile user device on which the application is to be installed. A version of an application is determined to send in response to the request for the application and the information related to the mobile user device. The application version is sent to the mobile user device. Information is received related to the performance of the application version. Adapted application determination information is stored related to at least a portion of the received information.

Abstract: A method of installing an application on a mobile user device is disclosed. A request for the application is received. Information is received related to the mobile user device on which the application is to be installed. A version of an application is determined to send in response to the request for the application and the information related to the mobile user device. The application version is sent to the mobile user device. Information is received related to the performance of the application version. Adapted application determination information is stored related to at least a portion of the received information.

Abstract: A method is disclosed for providing personal training services, at a portable electronic device having a touch screen display, comprising displaying a user interface comprising a first region and a second region, where the first region is configured to display still images or videos and the second region comprises one or more timers. The method further includes displaying, in the first region of the user interface, a plurality of synchronized video panels and conveying audible information in synchronicity with the one or more timers. The method further includes, in response to detecting a first gesture on the touch screen display, while displaying the plurality of synchronized video panels, displaying, in the first region of the user interface, a first video panel of the plurality of synchronized video panels.

Abstract: Data relating to execution flows at a computer system is aggregated across multiple execution flows by categorizing each execution flow into an execution flow shape. The execution flows may represent sequences of software components that are invoked or other computer system resources that are consumed. The execution flow shapes are developed by observing and recording the execution flows at the computer system and applying lossy compression rules. Execution flows are categorized into an execution flow shape which is a closest match. The execution flow data may be aggregated by an agent at the computer system, and communicated to a manager for subsequent use. The aggregation combines the information from all execution flows into a small enough data set that can be reported without consuming unduly large processing overhead while still preserving as many of the interesting aspects of the execution flows as possible.

Abstract: Data relating to execution flows at a computer system is aggregated across multiple execution flows by categorizing each execution flow into an execution flow shape. The execution flows may represent sequences of software components that are invoked or other computer system resources that are consumed. The execution flow shapes are developed by observing and recording the execution flows at the computer system and applying lossy compression rules. Execution flows are categorized into an execution flow shape which is a closest match. The execution flow data may be aggregated by an agent at the computer system, and communicated to a manager for subsequent use. The aggregation combines the information from all execution flows into a small enough data set that can be reported without consuming unduly large processing overhead while still preserving as many of the interesting aspects of the execution flows as possible.

Abstract: Data relating to execution flows at a computer system is compressed and aggregated across multiple execution flows by categorizing each execution flow into an execution flow shape. The execution flows may represent sequences of software components that are invoked. The execution flow shapes are developed by observing the execution flows at the computer system and applying lossy compression rules, such as representing multiple iterations of a loop as a single iteration, skipping certain types of software components, such as those having a specified call stack depth, treating some of the software components as being optional, and ignoring recursive calls by the software components. The aggregation and compression allow the information from all execution flows to be combined into a small enough data set that can be reported without consuming unduly large processing overhead while still preserving as many of the interesting aspects of the execution flows as possible.

Abstract: Data relating to execution flows running on different processes or threads at a computer system is correlated. The execution flows may represent sequences of software components that are invoked or other computer system resources that are consumed. A first execution flow fulfills a first request by transmitting a second request which initiates a second execution flow, such as at another computer system. The second request includes meta data which identifies a context of the first request, such as a URL, an agent which monitors the first execution flow, and the component in the first execution flow which initiated the second request. A manager receives information regarding the first execution flow from the first agent, and information regarding the second execution flow, along with the meta data, from a second agent, for correlating the first and second execution flows. The received information may include execution flow shape data.