Abstract: The case is directed to portable or client devices that are adapted to instantiate a client application that is communicably coupled to one or more remote host services. The client application is also adapted to cause a display of a graphical user interface having various regions. A first interface region of the graphical user interface may be associated with a first microfunction installed on the device and a second region may be associated with a second microfunction installed on the device. The various microfunctions may enable the client application to interface with one or more remote host services and may be shared across different client applications. In some cases, multiple microfunctions are used to define a custom, user-defined integrated application.

Abstract: The case is directed to portable or client devices that are adapted to instantiate a client application that is communicably coupled to one or more remote host services. The client application is also adapted to cause a display of a graphical user interface having various regions. A first interface region of the graphical user interface may be associated with a first microfunction installed on the device and a second region may be associated with a second microfunction installed on the device. The various microfunctions may enable the client application to interface with one or more remote host services and may be shared across different client applications. In some cases, multiple microfunctions are used to define a custom, user-defined integrated application.

Abstract: The case is directed to portable or client devices that are adapted to instantiate a client application that is communicably coupled to one or more remote host services. The client application is also adapted to cause a display of a graphical user interface having various regions. A first interface region of the graphical user interface may be associated with a first microfunction installed on the device and a second region may be associated with a second microfunction installed on the device. The various microfunctions may enable the client application to interface with one or more remote host services and may be shared across different client applications. In some cases, multiple microfunctions are used to define a custom, user-defined integrated application.

Abstract: The case is directed to portable or client devices that are adapted to instantiate a client application that is communicably coupled to one or more remote host services. The client application is also adapted to cause a display of a graphical user interface having various regions. A first interface region of the graphical user interface may be associated with a first microfunction installed on the device and a second region may be associated with a second microfunction installed on the device. The various microfunctions may enable the client application to interface with one or more remote host services and may be shared across different client applications. In some cases, multiple microfunctions are used to define a custom, user-defined integrated application.

Abstract: The case is directed to portable or client devices that are adapted to instantiate a client application that is communicably coupled to one or more remote host services. The client application is also adapted to cause a display of a graphical user interface having various regions. A first interface region of the graphical user interface may be associated with a first microfunction installed on the device and a second region may be associated with a second microfunction installed on the device. The various microfunctions may enable the client application to interface with one or more remote host services and may be shared across different client applications. In some cases, multiple microfunctions are used to define a custom, user-defined integrated application.

Abstract: A query gateway service for servicing API requests of software services, the query gateway service configured to monitor for, and execute, client-defined field resolvers so that client applications can define, at least in part, how data served to that client application in response to an API request is formatted, validated, mutated, or otherwise presented.

Abstract: An issue tracking system includes a host device executing an issue tracking service in communication with a client device executing at least one of an issue reporting application and/or an application under test. The issue reporting application generates a session identifier that defines a debugging session. The application under test can receive the identifier and tag logs or other data generated during the debugging session. The issue reporting application can thereafter receive the debugging data and can populate an issue report template based on that data.

Abstract: An issue tracking system includes a host device executing an issue tracking service in communication with a client device executing at least one of an issue reporting application and/or an application under test. The issue reporting application generates a session identifier that defines a debugging session. The application under test can receive the identifier and tag logs or other data generated during the debugging session. The issue reporting application can thereafter receive the debugging data and can populate an issue report template based on that data.

Abstract: Techniques herein include receiving, at a scripting language component, a request to execute one or more scripting language commands, and sending the commands from the scripting language component to a native execution component for determination, based at least in part on a security policy, whether to execute the one or more scripting language commands as corresponding native commands outside the scripting language component. In response to determining to execute the commands, the commands are translated into one or more native commands and are executed. In some embodiments, the scripting language component determines, based on a security policy, whether commands are permissible, and only if they are, forwards the commands to the native execution component for translation and execution.

Abstract: Techniques herein include receiving, at a scripting language component, a request to execute one or more scripting language commands, and sending the commands from the scripting language component to a native execution component for determination, based at least in part on a security policy, whether to execute the one or more scripting language commands as corresponding native commands outside the scripting language component. In response to determining to execute the commands, the commands are translated into one or more native commands and are executed. In some embodiments, the scripting language component determines, based on a security policy, whether commands are permissible, and only if they are, forwards the commands to the native execution component for translation and execution.

Abstract: Techniques herein include receiving, at a scripting language component of a native execution bridge, a request to execute one or more scripting language commands, and sending the commands from the scripting language component to a native execution component of the native execution bridge for determination, based at least in part on a security policy, whether to execute the one or more scripting language commands as corresponding native commands outside the scripting language component. In response to determining to execute the commands, the commands are translated into one or more natively executable commands and are executed. In some embodiments, the scripting language component determines, based on a security policy, whether commands are permissible, and only if they are, forwarding those commands to the native execution component for translation and execution.

Abstract: Techniques herein include receiving, at a scripting language component of a native execution bridge, a request to execute one or more scripting language commands, and sending the commands from the scripting language component to a native execution component of the native execution bridge for determination, based at least in part on a security policy, whether to execute the one or more scripting language commands as corresponding native commands outside the scripting language component. In response to determining to execute the commands, the commands are translated into one or more natively executable commands and are executed. In some embodiments, the scripting language component determines, based on a security policy, whether commands are permissible, and only if they are, forwarding those commands to the native execution component for translation and execution.