Abstract: A method for managing an application exchange platform includes receiving, from a developer, a service function, wherein the service function includes configuration details for an application available through an online application exchange. The method includes deploying the service function in the application exchange, identifying a first domain event requesting access to the service function from a user, and calling the service function in the online application exchange, in response to the first domain event. The method also includes recording a metric associate with the service function and a return parameter, emitting a second domain event indicative of a completion of the service function, and charging, with a billing tool, an appropriate party based on a usage metadata for the service function. A system and a non-transitory, computer-readable memory storing instructions to cause the system to perform the above method are also provided.

Abstract: A method for managing an application exchange platform includes receiving, from a developer, a service function, wherein the service function includes configuration details for an application available through an online application exchange. The method includes deploying the service function in the application exchange, identifying a first domain event requesting access to the service function from a user, and calling the service function in the online application exchange, in response to the first domain event. The method also includes recording a metric associate with the service function and a return parameter, emitting a second domain event indicative of a completion of the service function, and charging, with a billing tool, an appropriate party based on a usage metadata for the service function. A system and a non-transitory, computer-readable memory storing instructions to cause the system to perform the above method are also provided.

Abstract: One variation of a method for changing a state of a wearable device includes: in response to detected motion of the wearable device, transitioning from a low-power mode into a test mode; in the test mode, detecting a proximity of a surface to the wearable device, detecting a temperature of the surface, and based on a temperature of the surface correlated to a human skin temperature, transitioning from the test mode into an active mode; and, in the active mode sampling a heart rate sensor arranged within the wearable device and wirelessly broadcasting a value corresponding to an output of the heart rate sensor.

Abstract: One variation of a method for monitoring sleep of a user includes: assigning a collective wakefulness model—generated from sleep data collected from a set of other users—to the user for a first time period; storing a first set of vitals data collected by a wearable device worn by the user during first time period; extrapolating, from the collective wakefulness model, a first waking time of the user for a first sleep event during first time period based on data in the first set of vitals data; queuing the first waking time for transmission to a mobile computing device linked to the account for presentation to a guardian of the user; in response to expiration of the first time period, generating an individual wakefulness model specific to the user based on the first set of vitals data collected during the first time period.

Abstract: One variation of a method for changing a state of a wearable device includes: in response to detected motion of the wearable device, transitioning from a low-power mode into a test mode; in the test mode, detecting a proximity of a surface to the wearable device, detecting a temperature of the surface, and based on a temperature of the surface correlated to a human skin temperature, transitioning from the test mode into an active mode; and, in the active mode sampling a heart rate sensor arranged within the wearable device and wirelessly broadcasting a value corresponding to an output of the heart rate sensor.

Abstract: One variation of a method for monitoring sleep of a user includes: assigning a collective wakefulness model—generated from sleep data collected from a set of other users—to the user for a first time period; storing a first set of vitals data collected by a wearable device worn by the user during first time period; extrapolating, from the collective wakefulness model, a first waking time of the user for a first sleep event during first time period based on data in the first set of vitals data; queuing the first waking time for transmission to a mobile computing device linked to the account for presentation to a guardian of the user; in response to expiration of the first time period, generating an individual wakefulness model specific to the user based on the first set of vitals data collected during the first time period.

Abstract: Methods, apparatuses, and systems are presented for automating organization of multiple processes involving maintaining a uniform record of process threads using a server, each process thread comprising a representation of a collaborative process involving a plurality of users, enabling at least one of the plurality of users to carry out a user action while interacting with a different types of application program, and modifying at least one process thread in the uniform record of process threads in response to the user action. Modifying the process thread may comprise generating the process thread as a new process thread. Alternatively or in addition, modifying the process thread may comprise modifying the process thread as an existing process thread. At least one of the process threads may reflect user actions carried out by more than one of the plurality of users.

Abstract: Methods, apparatuses, and systems are presented for automating organization of multiple processes involving maintaining a uniform record of process threads using at least one server, each process thread comprising a representation of a collaborative process capable of involving a plurality of users, enabling at least one of the plurality of users to carry out a user action while interacting with one of a plurality of different types of application programs, and modifying at least one process thread in the uniform record of process threads in response to the user action carried out by the user. Modifying the at least one process thread may comprise generating the at least one process thread as a new process thread. Alternatively or in addition, modifying the at least one process thread may comprise modifying the at least one process thread as an existing process thread. At least one of the process threads may reflect user actions carried out by more than one of the plurality of users.

Abstract: Methods, apparatuses, and systems are presented for automating organization of multiple processes involving maintaining a uniform record of process threads using at least one server, each process thread comprising a representation of a collaborative process capable of involving a plurality of users, enabling at least one of the plurality of users to carry out a user action while interacting with one of a plurality of different types of application programs, and modifying at least one process thread in the uniform record of process threads in response to the user action carried out by the user. Modifying the at least one process thread may comprise generating the at least one process thread as a new process thread. Alternatively or in addition, modifying the at least one process thread may comprise modifying the at least one process thread as an existing process thread. At least one of the process threads may reflect user actions carried out by more than one of the plurality of users.