Patent Description:
In an effort to create specialized and independent products, developers have developed a multitude of unique applications for computer systems, configured to perform a vast array of functions quickly and effectively. However, in pressing for this isolated application development model, some of the advantages of monolithic products and applications have been abandoned-namely, seamless user experience, and data sharing. Applications of computer systems utilize a variety of different file and data types, to perform distinct functions which are often unique to a particular application or system. Additionally, the applications themselves have corresponding user interfaces, with interface elements unique to themselves, and specially configured to facilitate access to certain data types.

As a result, user experience between applications tends to be choppy and jarring, with little to no continuity. Furthermore, data types are often incompatible between applications. These issues lead to a disconnected and problematic user experience.

<CIT> discloses a method for creating componentized applications. A request to invoke a text-list definition of a componentized application is received. The text-list definition of the componentized application identifies a collection of different listed independent application sub-components specified by a user to be executed as a set. A componentized user interface is created with a different user interface component associated with each of the different listed independent application sub-components within the text-list definition of the componentized application. The different listed independent application sub-components are independently accessed based upon user inputs received in association with the respective different user interface component associated with each of the different listed independent application components within the text-list definition of the componentized application.

<CIT> discloses integrated macro-frameworks that can be called by object oriented software code to provide a consistent and efficient graphical presentation. The frameworks are macro-functions that can be utilized by various applications and are such that within each application and from application to application there is a consistency in the presentation of information and how information is entered and retrieved. The frameworks also provide for efficient operations of the application as well as efficient access of database tables. The frameworks can also provide an efficient and consistent means for developing a graphical user interface navigation function for navigating through various screens of a given application.

The invention is defined by the independent claims, taking due account of any element which is equivalent to an element specified in the claims.

Various ones of the appended drawings merely illustrate example embodiments of the present disclosure and are not intended to limit its scope to the illustrated embodiments. On the contrary, these examples are intended to cover alternatives, modifications, and equivalents as may be included within the scope of the disclosure.

Reference will now be made in detail to specific example embodiments for carrying out the inventive subject matter of the present disclosure. In the following description, specific details are set forth in order to provide a thorough understanding of the subject matter. It shall be appreciated that embodiments may be practiced without some or all of these specific details.

Example embodiments relate to a network-based composite interface system, employed for generating a composite graphical user interface (GUI) based on interface elements of referenced applications, to facilitate the sharing of data objects across those applications. A "data object" as used herein may include any item of data or code that can be used by one or more computer programs to execute operations. "Application data" refers to data associated with an application, including, for example, configuration files to configure the parameters and initial settings of applications, as well as application program interfaces (API) associated with the applications. In example embodiments, the data is stored in one or more network databases and are capable of being accessed by applications hosted by servers that share common access to the network database, through the composite graphical user interface. Additional details regarding data objects can be found in <CIT> entitled "NETWORK-BASED PERMISSIONING SYSTEM," assigned to the assignee of the instant application.

Aspects of the present disclosure involve receiving references to application data of applications hosted by the servers. As briefly stated above, the application data includes the set of routines, protocols, and tools for building an application, and the interface of the application. Additionally, the application data may also refer to specific data types associated with the application. Thus, the application data is essentially a description for a computer of how to build a particular application (including its functionality). As a part of the process for generating a composite GUI, the composite interface system receives references to application data of one or more applications at various memory locations (e.g., at both local and third-party servers, as well as cloud servers). In this way, the composite interface system may access the application data of any referenced application in order to configure a composite GUI which includes interface elements of the referenced application (e.g., interface elements and locations of the interface elements within a GUI).

Accordingly, having received the references to the application data, the composite interface system generates and presents a composite GUI at a client device. The composite GUI includes the interface elements of the referenced application, and thereby facilitates the execution of functions and operations performed by the application, without the client device necessarily having direct access or compatibility to the functions of the application itself. In some embodiments, the composite interface system is configured to cause one or more processors of the client device to generate the composite interface.

A portion of the composite GUI generated by the composite interface system includes a sidebar configured to display a graphical element (or elements) representative of the referenced applications. The composite GUI may receive inputs from a client device through the sidebar (e.g., a selection of a graphical element), to launch and cause display of interface elements associated with referenced applications.

Once the composite GUI has been generated and displayed at the client device, the composite interface system receives a selection of a data object from the client device. The data object may be located at a third party server, a local database, or at the client device itself. Having received a selection of the data object, the composite interface system identifies an object type of the data object in order to determine a compatible application to access. After determining the compatible application, the composite interface system access the application data of the compatible application to retrieve the information defining the interface of the application, and causes display of the interface elements of the application within the composite GUI. Thus, a user of the client device may have access to interfaces and functionality of multiple applications through a single composite GUI.

In some embodiments, in order to facilitate sharing of data objects between applications, the composite interface system employs a method of creating and storing artifacts which reference individual data objects of the application (or applications) referenced to the composite GUI. Artifacts are structured and accessed depending on what the base application specifies. An artifact is a reference to a particular data object (or instance of a data object). The referenced application has a data object associated with it, and the data object itself has a number of data attributes surrounding it. The data attributes include, for example, user permissions, a data type identifier, a search instance identifier, a source identifier, and a specific ID of the data object itself.

Having received a selection of a particular data object, the composite interface system creates an artifact referencing the data object. The artifact includes metadata associated with the data object, and formatted by the composite interface system. For example, the composite interface system may include an artifact repository for the discovery, organization, and collection of artifacts, to enable collaborative project development by facilitating the creation and sharing of projects comprising one or more artifacts.

In some example embodiments, the composite interface system provides a publish-subscribe type messaging service, where users may define projects within the composite graphical user interface by selecting one or more artifacts to include in a project, and automatically distribute the project to groups of subscribers. For example, a user of the client device may search the set of artifacts displayed at the client device via a search field within the composite GUI. The composite interface system may then remove at least a portion of artifacts from the set of artifacts based on the search, leaving a presentation of only relevant artifacts. The user may then select one or more artifacts from among the remaining artifacts to assign to a project. Having defined a project, the user may then distribute the project to a subscriber or group of subscribers.

<FIG> is a network diagram illustrating a network environment <NUM> suitable for operating a composite interface system <NUM>. A networked system <NUM> provides server-side functionality, via a network <NUM> (e.g., an intranet, the Internet or a Wide Area Network (WAN)), to one or more clients such as the client device <NUM>. <FIG> illustrates a web client <NUM>, client applications <NUM> executing on respective client device <NUM>.

An Application Program Interface (API) server <NUM> and a web server <NUM> are coupled to, and provide programmatic and web interfaces respectively to, one or more application servers <NUM>. The application servers <NUM> host the composite interface system <NUM>. The application servers <NUM> are, in turn, shown to be coupled to one or more database servers <NUM> that facilitate access to one or more databases <NUM>.

A composite interface system <NUM> facilitates the creation of composite GUI and sharable artifacts for the networked system <NUM>. For example, the composite interface system <NUM> is configured to receive references to application data from a client device <NUM>, and generate a composite GUI based on the referenced application data.

As shown, the network environment <NUM> includes the client device <NUM> in communication with the networked system <NUM> over the network <NUM>. The networked system <NUM> communicates and exchanges data with the client device <NUM> that pertains to various functions and aspects associated with the networked system <NUM> and its users. Likewise, the client device <NUM>, which may be any of a variety of types of devices that include at least a display, a processor, and communication capabilities that provide access to the network <NUM> (e.g., a smart phone, a tablet computer, a personal digital assistant (PDA), a personal navigation device (PND), a handheld computer, a desktop computer, a laptop or netbook, or a wearable computing device), may be operated by a user (e.g., a person) of the network system <NUM> to exchange data with the presentation platform <NUM> over the network <NUM>.

The client device <NUM> communicates with the network <NUM> via a wired or wireless connection. For example, one or more portions of the network <NUM> may comprises an ad hoc network, an intranet, an extranet, a Virtual Private Network (VPN), a Local Area Network (LAN), a wireless LAN (WLAN), a Wide Area Network (WAN), a wireless WAN (WWAN), a Metropolitan Area Network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular telephone network, a wireless network, a Wireless Fidelity (Wi-Fi®) network, a Worldwide Interoperability for Microwave Access (WiMax) network, another type of network, or any suitable combination thereof.

In various embodiments, the data exchanged between the client device <NUM> and the networked system <NUM> may involve user-selected functions available through one or more user interfaces (UIs). The UIs may be specifically associated with a web client <NUM> (e.g., a browser) or an application <NUM>, executing on the client device <NUM>, and in communication with the presentation platform <NUM>.

Turning specifically to the networked system <NUM>, a web server <NUM> is coupled to (e.g., via wired or wireless interfaces), and provides web interfaces to, an application server <NUM>. In some embodiments, the composite interface system <NUM> runs and executes on the application server <NUM>, while in other embodiments, the application server <NUM> provides the client device <NUM> with a set of instructions (e.g., computer-readable code) that causes the web client <NUM> and the client application <NUM> of the client device <NUM> to execute and run the composite interface system <NUM>.

<FIG> is a block diagram illustrating various components of the composite interface system <NUM>, which is provided as part of the network system <NUM>, consistent with some embodiments. To avoid obscuring the inventive subject matter with unnecessary detail, various functional components (e.g., modules and engines) that are not germane to conveying an understanding of the inventive subject matter have been omitted from <FIG>. However, a skilled artisan will readily recognize that various additional functional components may be supported by the composite interface system <NUM> to facilitate additional functionality that is not specifically described herein.

As is understood by skilled artisans in the relevant computer arts, each functional component (e.g., module) illustrated in <FIG> may be implemented using hardware (e.g., a processor of a machine) or a combination of logic (e.g., executable software instructions) and hardware (e.g., memory and processor of a machine) for executing the logic. Furthermore, one or more of the various functional components depicted in <FIG> may reside on a single computer (e.g., a laptop, client device <NUM>), or may be distributed across several computers in various arrangements such as cloud-based architectures. In some embodiments, modules of the composite interface system <NUM> may be distributed between the client device <NUM> and application server <NUM>. Moreover, it shall be appreciated that while the functional components (e.g., modules) of <FIG> are discussed in the singular sense, in other embodiments, multiple instances of one or more of the modules may be employed.

The composite interface system <NUM> is shown as including an artifact module <NUM>, a composite interface module <NUM>, a notification module <NUM>, and a permissions module <NUM>, all configured to communicate with each other (e.g., via a bus, shared memory, a switch, or application programming interfaces (APIs)).

The artifact module <NUM> facilitates discovery, organization and collection of artifacts and to enable collaborative project development. The artifact module <NUM> creates artifacts based on metadata of identified data objects (e.g., by the artifact module <NUM> itself, or via user selection). An artifact is a reference to a data object, crated based on metadata associated with the data object. For example, a data object may have metadata which includes data defining a source of the data object, user permissions of the data object, a unique identifier of the data object, a data type of the data object, and so on. Upon identifying the data object, the artifact module <NUM> creates an artifact for the data object with the metadata. Having created an artifact, the artifact module <NUM> may store the artifact within an artifact repository, along with a set of artifacts.

In some embodiments, the artifact module <NUM> facilitates the creation, editing, and exporting of projects. In the context of this specification, a project is a sharable object comprising one or more artifacts. The artifact module <NUM> may receive a selection of one or more artifacts through a composite GUI presented at a client device, and assign the selection of artifacts to a project. The artifact module <NUM> may additionally assign a project identifier (e.g., project ID) to the project.

The composite interface module <NUM> receives references to application data, extracts interface data defining interface elements from the application data, and generates a composite GUI based on the application data. The application data may include an identifier of the application, a network address of the application, and interface data defining an interface of the application. The composite interface module <NUM> may reside server side (e.g., within the application server <NUM>), or in some embodiments may reside client side (e.g., within the client device <NUM>), such that the generation of the composite GUI is accomplished by one or more processors of the client device <NUM>.

In some example embodiments, the composite interface module <NUM> receives a set of references to multiple sets of application data, and in response to receiving an instruction to generate a composite GUI, generates a composite GUI based on the referenced application data. The composite GUI includes a presentation of interface elements from each of the applications associated with the set of application data received. For example, in response to receiving a reference to application data, the composite interface module <NUM> may generate and cause display of a graphical icon representative of the application data at a location within the composite GUI, such that selection of the graphical icon causes the composite interface module <NUM> to display the interface elements associated with the selected graphical element.

In further example embodiments, a portion of the composite GUI created by the composite interface module <NUM> includes a sidebar containing a presentation of the graphical icons associated with each of the referenced applications. For example, the sidebar may include an application icon, such that selection of the application icon results in display of a window which includes an arrangement of the graphical icons. A user may select one or more of the graphical icons from the display window in order to cause display of the corresponding interface elements associated with each referenced application. In some embodiments, the composite interface module <NUM> communicates the selection of the graphical icon to the artifact module <NUM>, and in response to receiving the selection, the artifact module <NUM> causes display of an assortment of artifacts referencing data objects associated with the selected graphical icon. The assortment of graphical icons may be presented as a sortable list within the composite GUI.

The notification module <NUM> provides publish-subscribe type messaging capability, to automatically distribute projects defined by a user within the composite graphical user interface (e.g., by selecting one or more artifacts to include in a project) to a group of subscribers. For example, upon receiving a project definition (i.e., a set of artifacts selected and assigned to the project), the notification module <NUM> identifies a subscription request from a referenced application. The subscription request may include one or more user identifiers with various network addresses to receive the project (and corresponding artifacts).

The notification module <NUM> distributes the project to the application. Upon receipt of the project, the application may access the data objects associated the project through the associated artifacts. For example, upon receipt of the projects, the applications may extract the artifacts, and access the data objects associated with the artifacts through the composite interface system <NUM>. In this way, an application itself doesn't have to know how to read a particular data type itself, but can instead rely on the composite interface system <NUM> to retrieve and access the data based on the artifact.

The permissions module <NUM> is configured to evaluate and determine user access permissions with respect to data objects referenced by artifacts in the composite interface system <NUM>. The evaluation of user access permissions, in most instances, is triggered by receipt of an access request received via an API from a referenced application supported by the composite interface system <NUM>. The access request includes a data resource identifier corresponding to the data object for which access is being requested, and a user identifier corresponding to the requesting user. In some instances, the access request may further include one or more filters identifying one or more particular operations or sets of operations that are of interest.

<FIG> is a flow-chart illustrating a method <NUM> for generating and causing display of a composite GUI at a client device, according to some example embodiments. The method <NUM> is embodied in computer-readable instructions for execution by one or more processors such that the operations of the method <NUM> are performed in part or in whole by the network-based composite interface system <NUM>; accordingly, the method <NUM> is described below by way of example with reference thereto. However, it shall be appreciated that at least some of the operations of the method <NUM> may be deployed on various other hardware configurations, and the method <NUM> is not intended to be limited to the network-based composite interface system <NUM>.

At operation <NUM>, the composite interface module <NUM> receives a reference to application data of an application. For example, the composite interface module <NUM> may provide a set of computer-readable instructions to the client device <NUM> that causes the client device <NUM> to display an application reference interface. The user <NUM> may thereby provide references to application data of applications to be included within the composite GUI generated by the composite interface system <NUM>. In some embodiments, in response to receiving the reference to the application data, the artifact module <NUM> identifies data objects associated with the referenced application and creates one or more artifacts based on the metadata of the data objects.

At operation <NUM>, the composite interface module <NUM> receives an instruction to generate a composite GUI, and in response, generates a composite GUI which includes the interface elements of the referenced application. A portion of the composite GUI includes a sidebar in which a graphical icon representing the referenced application data is displayed. The sidebar includes an application icon, which a user may select, and in response to receiving a selection of the application icon, the composite interface module <NUM> may cause display of a window which includes one or more graphical icons associated with referenced applications. According to the present invention, the selection of the graphical icon results in display of interface elements of a referenced application.

In further example embodiments, the composite GUI includes a presentation of a listing of artifacts associated with the referenced application data. For example, responsive to receiving the reference to the application data, the artifact module <NUM> creates one or more artifacts based on the referenced application data, and stores the artifacts within an artifact repository (e.g., database <NUM>). Thus, at operation <NUM>, when the composite interface module <NUM> generates the composite GUI based on the application data, the composite interface module <NUM> may access the artifact repository to retrieve the set of artifacts associated with the application.

At operation <NUM>, the composite interface module <NUM> causes display of the composite GUI at a client device (e.g., client device <NUM>). In some embodiments, the permissions module <NUM> may identify user access permissions associated with a user identifier associated with the client device <NUM>, and cause display of the composite GUI based on the determined user permissions. For example, a user may not have access to an entire set of artifacts based on their user permissions. Upon determining the user permissions of the user identifier, the permissions module <NUM> removes artifacts which are inaccessible to the user identifier, and presents only those artifacts which the user permissions allow.

<FIG> is a flow-chart illustrating a method <NUM> for causing display of a set of interface elements associated with a referenced application based on a selection of an artifact, according to some example embodiments. The method <NUM> is embodied in computer-readable instructions for execution by one or more processors such that the operations of the method <NUM> are performed in part or in whole by the network-based composite interface system <NUM>; accordingly, the method <NUM> is described below by way of example with reference thereto. However, it shall be appreciated that at least some of the operations of the method <NUM> may be deployed on various other hardware configurations, and the method <NUM> is not intended to be limited to the network-based composite interface system <NUM>.

At operation <NUM>, the composite interface module <NUM> receives a selection of an artifact from a client device <NUM>. For example, the composite GUI may include a set of artifacts associated with referenced applications. The set of artifacts may be presented in a user defined sort order (e.g., through a selection of an attribute), based on metadata associated with the artifact.

At operation <NUM>, in response to receiving a selection of the artifact at the client device <NUM>, the composite interface module <NUM> identifies the referenced application associated with the artifact and causes display of the interface elements of the identified application.

<FIG> is a flow-chart illustrating a method <NUM> for distributing a project based on a subscription request, according to some example embodiments. The method <NUM> is embodied in computer-readable instructions for execution by one or more processors such that the operations of the method <NUM> are performed in part or in whole by the network-based composite interface system <NUM>; accordingly, the method <NUM> is described below by way of example with reference thereto. However, it shall be appreciated that at least some of the operations of the method <NUM> may be deployed on various other hardware configurations, and the method <NUM> is not intended to be limited to the network-based composite interface system <NUM>.

Many applications or services need long-running calls and a scheme for pushing data to the front-end, and in some cases, backend services may need to communicate with unrelated or incompatible front-ends (e.g. pushing data from one referenced application to another referenced application). The front-end refers to the portion of an application which users interact with, while the back-end refers to the resources of the application configured to service and provide functionality to the front-end. The front-end of one application may not necessarily be compatible with the back-end of another application. The composite GUI generated by the composite interface system <NUM> therefore provides a general communications channel between the back-end of a referenced application and a front-end of another referenced application, and as such provides a way to address messages to reach the front-end via the use of projects (e.g., sets of artifacts).

At operation <NUM>, the notification module <NUM> receives a subscription request from a referenced application. The subscription request includes an application identifier of the subscribing application, and a user identifier of a subscribing user. The subscription request may also include a data type.

At operation <NUM>, the artifact module <NUM> receives a selection of one or more artifacts at the client device <NUM>. For example, a user <NUM> may select one or more artifacts among a set of artifacts displayed in the composite GUI at the client device <NUM>.

At operation <NUM>, the artifact module <NUM> receives a request from the client device <NUM> to assign the selected artifacts to a project. In response to receiving the request to assign the selected artifacts to a project, the artifact module <NUM> generates a project which includes the selected artifacts.

At operation <NUM>, the notification module <NUM> distributes the project based on the subscription request, to the referenced application. The referenced application may then notify the subscribing user (e.g., based on the user identifier) of the project. The requesting application may then access then artifacts through the project, and cause display of the data objects associated with the artifacts through the composite GUI.

As an example of the composite GUI generated by the composite interface module <NUM>, <FIG> is an interface diagram illustrating a composite GUI <NUM> for displaying interface elements of a referenced application, according to some example embodiments. As shown, the composite GUI <NUM> includes a sidebar <NUM>, an application window <NUM>, the application window <NUM> including a set of graphical icons representing referenced applications (e.g., graphical icon <NUM>), a cursor <NUM> to make selections within the composite GUI <NUM>, a referenced application interface <NUM>, and a set of interface elements <NUM>, of the referenced application.

For example, in response to receiving the reference to the application data, as in operation <NUM> of <FIG>, the composite interface module <NUM> creates a graphical icon <NUM> to display within the sidebar <NUM>. As shown in <FIG>, the sidebar may also include an application icon <NUM>, which a user <NUM> may select with the cursor <NUM> to display the application window <NUM>, which includes a set of graphical icons, such as graphical icon <NUM>, representative of referenced applications. Upon receiving a selection of the graphical icon <NUM>, the composite interface module <NUM> causes display of the associated interface (e.g., interface <NUM>), and its interface elements <NUM>.

As an example of the composite GUI generated by the composite interface module <NUM>, <FIG> is an interface diagram illustrating the composite GUI <NUM> for displaying a set of artifacts to create a sharable project, according to some example embodiments. As shown, the composite GUI <NUM> is shown to include a set of artifacts <NUM>, a graphical icon identifying an application type <NUM>, a search field <NUM>, a project creation window <NUM>, and the cursor <NUM>.

In some embodiments, the composite GUI <NUM> displays a set of artifacts associated with the referenced applications (e.g., set of artifacts <NUM>). A user <NUM> may select an artifact (e.g., artifact <NUM>) with the cursor <NUM>. In response to receiving the selection of the artifact <NUM>, the composite GUI <NUM> causes display of a project creation window <NUM>. The project creation window <NUM> includes a set of options to share the artifact in a project or to an individual or group of individuals based on a user identifier or set of user identifiers provided by the user <NUM>, or to duplicate, rename, or convert the artifact into another format or data type. For example, as in operation <NUM> of <FIG>, a user <NUM> may select the artifact <NUM> to assign the artifact <NUM> to a project, which may then be distributed to a subscriber or subscriber list.

The composite GUI <NUM> is also shown to include a search field <NUM>. A user <NUM> may enter a search term into the search field <NUM>, and in response to receiving the search term, the artifact module <NUM> may present relevant artifacts within the composite GUI <NUM>.

<FIG> is an illustration of the composite interface system <NUM>, a set of applications <NUM>, and a composite user interface <NUM>, generated by the composite interface system <NUM>, based on the applications <NUM>. The applications <NUM> may be located at both local (e.g., databases <NUM>) and third-party servers, as well as cloud servers. The composite interface system <NUM> receives references to the applications <NUM> (e.g., App. <NUM>, App. <NUM>, App. <NUM>, App. <NUM>), and generate the composite user interface <NUM>, based on interface elements from the set of applications <NUM>.

<FIG> is a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions for causing the machine to perform any one or more of the methodologies discussed herein may be executed. Specifically, <FIG> shows a diagrammatic representation of the machine <NUM> in the example form of a system, within which instructions <NUM> (e.g., software, a program, an application, an applet, an app, a driver, or other executable code) for causing the machine <NUM> to perform any one or more of the methodologies discussed herein may be executed. For example, the instructions <NUM> include executable code that causes the machine <NUM> to execute the methods <NUM> and <NUM>. In this way, these instructions <NUM> transform the general, non-programmed machine into a particular machine programmed to carry out the described and illustrated functions in the manner described herein. The machine <NUM> may operate as a standalone device or may be coupled (e.g., networked) to other machines.

By way of non-limiting example, the machine <NUM> may comprise or correspond to a television, a computer (e.g., a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, or a netbook), a set-top box (STB), a personal digital assistant (PDA), an entertainment media system (e.g., an audio/video receiver), a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a portable media player, or any machine capable of outputting audio signals and capable of executing the instructions <NUM>, sequentially or otherwise, that specify actions to be taken by machine <NUM>. Further, while only a single machine <NUM> is illustrated, the term "machine" shall also be taken to include a collection of machines <NUM> that individually or jointly execute the instructions <NUM> to perform any one or more of the methodologies discussed herein.

The machine <NUM> may include processors <NUM>, memory <NUM>, storage unit <NUM> and I/O components <NUM>, which may be configured to communicate with each other such as via a bus <NUM>. In an example embodiment, the processors <NUM> (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor <NUM> and processor <NUM> that may execute instructions <NUM>. The term "processor" is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as "cores") that may execute instructions contemporaneously. Although <FIG> shows multiple processors, the machine <NUM> may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiples cores, or any combination thereof.

The memory <NUM> (e.g., a main memory or other memory storage) and the storage unit <NUM> are both accessible to the processors <NUM> such as via the bus <NUM>. The memory <NUM> and the storage unit <NUM> store the instructions <NUM> embodying any one or more of the methodologies or functions described herein. In some embodiments, the databases <NUM> resides on the storage unit <NUM>. The instructions <NUM> may also reside, completely or partially, within the memory <NUM>, within the storage unit <NUM>, within at least one of the processors <NUM> (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine <NUM>. Accordingly, the memory <NUM>, the storage unit <NUM>, and the memory of processors <NUM> are examples of machine-readable media.

As used herein, "machine-readable medium" means a device able to store instructions and data temporarily or permanently and may include, but is not be limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage (e.g., erasable programmable read-only memory (EEPROM)), or any suitable combination thereof. The term "machine-readable medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store instructions <NUM>. The term "machine-readable medium" shall also be taken to include any medium, or combination of multiple media, that is capable of storing instructions (e.g., instructions <NUM>) for execution by a machine (e.g., machine <NUM>), such that the instructions, when executed by one or more processors of the machine <NUM> (e.g., processors <NUM>), cause the machine <NUM> to perform any one or more of the methodologies described herein (e.g., methods <NUM> and <NUM>). Accordingly, a "machine-readable medium" refers to a single storage apparatus or device, as well as "cloud-based" storage systems or storage networks that include multiple storage apparatus or devices. The term "machine-readable medium" excludes signals per se.

Furthermore, the "machine-readable medium" is non-transitory in that it does not embody a propagating signal. However, labeling the tangible machine-readable medium as "non-transitory" should not be construed to mean that the medium is incapable of movement - the medium should be considered as being transportable from one real-world location to another. Additionally, since the machine-readable medium is tangible, the medium may be considered to be a machine-readable device.

The I/O components <NUM> may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific I/O components <NUM> that are included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components <NUM> may include many other components that are not specifically shown in <FIG>. The I/O components <NUM> are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. In various example embodiments, the I/O components <NUM> may include input components <NUM> and output components <NUM>. The input components <NUM> may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components, and the like. The output components <NUM> may include visual components (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth.

Communication may be implemented using a wide variety of technologies. The I/O components <NUM> may include communication components <NUM> operable to couple the machine <NUM> to a network <NUM> or devices <NUM> via coupling <NUM> and coupling <NUM>, respectively. For example, the communication components <NUM> may include a network interface component or other suitable device to interface with the network <NUM>. In further examples, communication components <NUM> may include wired communication components, wireless communication components, cellular communication components, near field communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices <NUM> may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a Universal Serial Bus (USB)).

Certain embodiments are described herein as including logic or a number of components, modules, or mechanisms. Modules may constitute either software modules (e.g., code embodied on a machine-readable medium e.g. a storage medium or a transmission signal) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. In example embodiments, one or more computer systems (e.g., a standalone, client, or server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.

For example, a hardware module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations.

Accordingly, the term "hardware module" should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in a certain manner and/or to perform certain operations described herein. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each of the hardware modules need not be configured or instantiated at any one instance in time. For example, where the hardware modules comprise a general-purpose processor configured using software, the general-purpose processor may be configured as respective different hardware modules at different times. Software may accordingly configure a processor, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.

Where multiple of such hardware modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses that connect the hardware modules).

Similarly, the methods described herein may be at least partially processor-implemented. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment, or a server farm), while in other embodiments the processors may be distributed across a number of locations.

The one or more processors may also operate to support performance of the relevant operations in a "cloud computing" environment or as a "software as a service" (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs).

Example embodiments may be implemented in digital electronic circuitry, or in computer hardware, firmware, or software, or in combinations of them. Example embodiments may be implemented using a computer program product, for example, a computer program tangibly embodied in an information carrier, for example, in a machine-readable medium for execution by, or to control the operation of, data processing apparatus, for example, a programmable processor, a computer, or multiple computers.

A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a standalone program or as a module, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site, or distributed across multiple sites and interconnected by a communication network.

In example embodiments, operations may be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output. Method operations can also be performed by, and apparatus of example embodiments may be implemented as, special purpose logic circuitry (e.g., an FPGA or an ASIC).

In embodiments deploying a programmable computing system, it will be appreciated that both hardware and software architectures merit consideration. Specifically, it will be appreciated that the choice of whether to implement certain functionality in permanently configured hardware (e.g., an ASIC), in temporarily configured hardware (e.g., a combination of software and a programmable processor), or in a combination of permanently and temporarily configured hardware may be a design choice. Below are set out hardware (e.g., machine) and software architectures that may be deployed, in various example embodiments.

Although the embodiments of the present invention have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the inventive subject matter. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term "invention" merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent, to those of skill in the art, upon reviewing the above description.

Claim 1:
A method (<NUM>) for generating a composite graphical user interface (GUI) based on interface elements of a referenced application, comprising:
receiving (<NUM>), at one or more processors (<NUM>), a reference to application data of an application (<NUM>), wherein the application data includes interface elements (<NUM>) of the application (<NUM>) and a set of instructions to execute a function of the application (<NUM>);
causing (<NUM>) display of a composite graphical user interface (<NUM>), GUI, at a display of a client device (<NUM>), the composite GUI (<NUM>) including a sidebar element (<NUM>) displayed at a portion of the display of the client device (<NUM>), the sidebar element (<NUM>) including a presentation of a graphical icon representative of the application (<NUM>);
receiving, at the one or more processors (<NUM>), a selection of the graphical icon (<NUM>) from the client device (<NUM>);
updating the display of the composite GUI (<NUM>) at the client device (<NUM>) to display the interface elements (<NUM>) of the application (<NUM>) associated with the selected graphical icon (<NUM>);
accessing a data repository associated with the application (<NUM>), the data repository including a data object that comprises data attributes;
generating, by the one or more processors (<NUM>), an artifact (<NUM>) that includes metadata associated with the data object presented at the client device (<NUM>), the artifact (<NUM>) being a reference to the data object; and
causing display of the artifact (<NUM>) with the composite GUI (<NUM>);
wherein the data attributes include a data type identifier of the data object, and wherein the method (<NUM>) further comprises:
receiving a request to assign the artifact (<NUM>) to a project from the client device (<NUM>), the project being a sharable object comprising one or more artifacts (<NUM>) and enabling collaborative project development;
receiving a distribution list that includes a set of network addresses of a set of client devices (<NUM>); and
distributing the project to the set of client devices (<NUM>).