Abstract: The subject disclosure is directed towards a technology by which background application code (e.g., provided by third-party developers) runs on a mobile device in a way that is constrained with respect to resource usage. A resource manager processes a resource reservation request for background code, to determine whether the requested resources meet constraint criteria for that type of background code. If the criteria are met and the resources are available, the resources are reserved, whereby the background code is ensured priority access to its reserved resources. As a result, a properly coded background application that executes within its constraints will not experience glitches or other problems (e.g., unexpected termination) and thereby provide a good user experience.

Abstract: Although a software developer writing software for a mobile device typically performs the development and some of the debugging of the application on a software development computer, the application also has to be debugged as it passes through the deactivate, terminate and reactivate states as it executes on the mobile device. To debug an application the developer can launch the debugger on the software development computer. The debugger can launch the application on the mobile device. If an event that terminates the application occurs, the debugger connection is terminated. In accordance with aspects of the subject matter disclosed herein, the debugger is automatically reattached to the restarted (activated) application. Reattaching the debugger automatically to the restarted application allows the developer to debug the mobile device application as an application passing through multiple states rather than debugging multiple instances of an application.

Abstract: The subject disclosure is directed towards a technology by which background application code (e.g., provided by third-party developers) runs on a mobile device in a way that is constrained with respect to resource usage. A resource manager processes a resource reservation request for background code, to determine whether the requested resources meet constraint criteria for that type of background code. If the criteria are met and the resources are available, the resources are reserved, whereby the background code is ensured priority access to its reserved resources. As a result, a properly coded background application that executes within its constraints will not experience glitches or other problems (e.g., unexpected termination) and thereby provide a good user experience.

Abstract: Although a software developer writing software for a mobile device typically performs the development and some of the debugging of the application on a software development computer, the application also has to be debugged as it passes through the deactivate, terminate and reactivate states as it executes on the mobile device. To debug an application the developer can launch the debugger on the software development computer. The debugger can launch the application on the mobile device. If an event that terminates the application occurs, the debugger connection is terminated. In accordance with aspects of the subject matter disclosed herein, the debugger is automatically reattached to the restarted (activated) application. Reattaching the debugger automatically to the restarted application allows the developer to debug the mobile device application as an application passing through multiple states rather than debugging multiple instances of an application.