Improved computer-implemented systems and methods for creation, distribution and / or deployment of software elements

Abstract

The invention provides methods and systems that enable an owner (e.g. a service provider) to design and create an application, and then provide the execution of that application to end users via one or more deployers. The owner uses a platform, formed in accordance with an embodiment of the disclosure, to design the application. The application may comprise one or more of: logic code that provides the application's functionality, variables for storing data items used by the logic code. The platform may also enable the specification, provision and / or storage of one or more of: API config files to define and govern connectivity between the application and any data sources / recipients; a User Interface (Ul) to facilitate presentation of the application data to the end user via software on the end user device e.g. a browser; and an execution environment e.g. SDK to enable full and customised execution of the application by the deployers' respective systems.

Description

[0001]IMPROVED COMPUTER-IMPLEMENTED SYSTEMS AND METHODS FOR CREATION, DISTRIBUTION AND / OR DEPLOYMENT OF SOFTWARE ELEMENTS TECHNICAL FIELD This disclosure relates generally to computer-implemented solutions for the creation and / or deployment of software elements, such as applications. Embodiments are particularly suited for embedding applications within other applications. Advantageously, this enables the functionality of applications that derive from, belong to and / or are controlled or executed by different sources to be integrated and provided to end users in a seamless but secure manner. BACKGROUND There are many conceivable situations in which a service provider needs to provide their services to end users via a collaborating party. In respect of computing-based technologies, this can be achieved very simply by the collaborator providing a link to the service provider’s system e.g. by adding a hyperlink in the collaborator’s web page that takes the user to a resource that is available on the service provider’s system. In more sophisticated examples, service providers may embed their services into the technical solutions that are offered by collaborator(s) to the collaborators’ end users. This is typically achieved through the use of one or more Application Programming Interfaces (APIs) that define and govern the inter-communication between the parties’ respective systems. However, when using this embedded approach, service providers typically offer only a limited range of functionalities rather than a complete solution because of technical, security, legal / privacy implications that often arise from the embedding arrangement. Thus, the end user does not receive the service provider’s full suite of functionalities unless they take the time and effort to seek them out as part of a separate exercise. Moreover, service providers typically offer only a limited number of APIs, which means that the embedded service may only be suitable for use with a certain number and type of end user devices. Further still, such solutions often do not address the need to easily customise the embedded services according to the needs or specific attributes of particular collaborators, or to address security concerns that may arise by sharing connectivity, encryption, or authentication data between the systems of collaborating but potentially distinct organisations. While some prior art arrangements enable direct communication between a first application and a second application e.g. via the use of a container, this is less than desirable for the reasons mentioned above. In yet other situations, parties that have a desire to collaborate often struggle to reach a workable consensus on the technical and operational requirements to do so, and so the technical collaboration fails to materialise. Therefore, there is a need for a technical solution which addresses at least these concerns and enables the generation, deployment and execution of computer-implemented services from / by one party via another. Such a solution would preferably enable application creators / owners to easily and quickly build complex yet customisable UI-based applications for deployment to end users via a collaborating party, while allowing connectivity to, and integration with, a wide range of data sources / destination and preserving security. Such a solution has now been devised. SUMMARY Embodiments of the disclosure provide technical solutions for the secure distribution and / or delegation of software element(s) by an owning / generating / controlling party to at least one end user via at least one software element that is executed by a computing system of at least one collaborating / deploying / providing party. Additionally, or alternatively, the disclosure provides improved technical solutions for the generation of said software element(s). Hereafter, we may use the term ‘application’ for convenience instead of ‘software element’. In a preferred embodiment, a computing platform is provided that is arranged and operative to enable or facilitate an application owner / controller to: • design, create and implement software applications, each application being designed to provide at least one specified function and / or perform at least one specified task; the at least one function and / or task is specified by the application owner via a dashboard component of the platform; • provide, to at least one application deployer, an execution activation mechanism (trigger) for execution of the owner’s application, such that activation of the trigger initiates execution of the owner’s application; • provide an executable form of the owner’s application to the at least one deployer, such that the owner’s application can be run by the deployer party on behalf of the owner; the executable form of the application may be, comprise or form part of an execution environment that provides, to the deploying system, the technical elements required to run the application on behalf of the owner; for example, the environment may be or comprise a software development toolkit (SDK), a virtual machine, an interpreter, code libraries, binary files etc; the execution environment may comprise tools / functionality that enables the generation of an executable software unit (e.g. container) for execution of the owner’s application on the deployer’s system; • pre-determine, specify and store connectivity (config) rules and then establish, at run time, any secure connections that are required between the owner’s application and any interacting parties; interacting parties may comprise one or more of: third party software that provides data to, or receives data from, the owner’s application; the deployer’s system and / or deployer’s application; software executing on the end user’s computing device; • specify and provide a user interface (UI) and its necessary UI elements, for presentation of the owner’s application and its data to the end user on their device, via the deployer; • take advantage of data passporting and secure authentication processes that have been implemented by the deployer e.g. using Single Sign-On (SSO) authentication technologies that allow the end user to authenticate swiftly, securely and conveniently. Thus, embodiments provide improved technical solutions for the generation, provision, delegation and execution of software. Advantages include, but are not limited to: • the ability to keep sensitive aspects of the software separate from the execution / deployment processes and thus hidden, as the sensitive aspects are not provided to, or accessible by, the deployer, third parties or end user; • the owner can specify the logic and other aspects of the application once, but allow for customisation of the executable to a plurality of deployers in accordance with the owner’s specified rules (for example, by incorporation of each individual deployer’s logo, or use of a deployer specified font size / colour etc) • the disclosure provides for secure communication between any number or type of interacting parties, by allowing the owner to specify the rules and requirements for connection of their application to any API that a given implementation may interact with. In one form of wording, the disclosure may be described as providing technical solutions for the delivery of fully customisable and embeddable applications that interface with first and / or third-party APIs in a safe, secure and controlled environment. Additionally, or alternatively, embodiments may be described as providing a universal and flexible API adapter because they enable a one-to-many deployment arrangement to be constructed, in which a given owner can deploy their software to as many deployers as required. In a preferred embodiment, this is achieved by the use of a standardised SDK which the deployer provides to many end users. By contrast, prior art solutions comprise arrangements that are tailor made and designed for interaction with only specific deployers or groups of deployers. Instead of enabling a one-to- many arrangement, the prior art arrangements comprise only a customised solution for use within a particular system. Whereas embodiments of the disclosure involve provision of a standardised SDK, prior art solutions need the construction of custom-built software solutions. Therefore, the prior art arrangements are less versatile than embodiments of the present disclosure, and require significantly more time, resources and costs to be adapted for use across different deployment systems. Further technical advantages provided by embodiments of the disclosure include, but are not limited to: • the ability to execute an application on a deployer’s system in an isolated manner. This avoids technical issues such as security, authentication and privacy concerns that may arise in prior art solutions which work by establishing direct communications between two applications that are provided by collaborating but potentially distinct organisations. By direct contrast to such prior art arrangements, embodiments of the disclosure eliminate such potentially insecure and cumbersome communications, and enables the application to be executed on a deployer’s system in an isolated environment. Thus, embodiments provide a technically distinct architecture and data flow relative to the prior art, and enable construction of more secure, improved computing arrangements; • the ability to execute an owner’s software of a 3rdparty’s system without the 3rdparty’s intervention; thus, embodiments of the disclosure provide improved deployment arrangements that are easier and simpler to use; • reduction or elimination of the need for middleware, as the owner is able to provide the application to the deployer and run it directly on the deployer’s system. Thus, an improved solution that is more efficient, cost effective and requires fewer processing and memory resources relative to the prior art. LIST OF FIGURES Aspects and embodiments of the present disclosure will now be described, by way of example only, and with reference to the accompany drawings, in which: Figure 1 provides an illustration of at least some of the system components and their relationships, in accordance with an example embodiment of the disclosure; Figures 2 and 3 provide high-level illustrations of alternative system configurations in accordance with example embodiments of the disclosure; Figure 4 is a flowchart illustrating the steps taken in accordance with an example embodiment of the disclosure in use; Figure 5 shows a different perspective of the example embodiments of Figures 1, 2 and 3; Figure 6 provides an alternative view of the example embodiments of Figures 1, 2, 3 and 5; Figure 7 is a schematic diagram that illustrates a computing environment in which various embodiments of the disclosure can be implemented. DETAILED DESCRIPTION & ILLUSTRATIVE EMBODIMENTS We now describe, without limitation and with reference to the accompanying Figures, various aspects and features of the present disclosure for the purpose of illustrating at least one example embodiment. Turning to Figures 1 and 6 in particular, an embodiment of the disclosure comprises a computing platform 3 that facilitates and enables the creation of a first software element 4 by a first entity, and its subsequent provision to a second entity 2, such that the second entity can embed the first entity’s software element 4 within a second software element 12 that is arranged for execution on the second entity’s computing system. End users 5 of the second entity’s software element 12 can trigger or initiate execution of the first entity’s software element from within the second entity’s software element. Hereafter, for ease of reference only, we will refer to: • a ‘software element’ as an ‘application’; • the first entity 1 as the ‘owner’, ‘source’ or ‘controller’ of the first application. This is because the first application is determined, specified / or generated by the owner. The owner creates the first application such that it is arranged to provide, upon execution by at least one processor, one or more predetermined services, functionalities and / or outputs to an end user 5 operating a computing device 11; • the second entity 2 as the ‘deployer’, ‘collaborator’ or the ‘provider’ as the deployer 2 is the party which provides the owner’s application 4 to one or more end users 5 from within the deployer’s own (i.e. the second) application 12. • the first software element 4 as the ‘owner’s application’ 4, and the second software element 12 as the ‘deployer’s application’ 12. Embodiments of the disclosure enable the owner’s application 4 to be executed from the deployer’s application 12 to provide the functionality of the owner’s application to the deployer’s end user(s) 5. Thus, in accordance with a preferred embodiment, the deployer 2 provides execution of the owner’s application 4 to the end user 5 on behalf of the owner 1. As shown in Figure 2, the owner may distribute the owner’s application 4 to one or a plurality of deployers. Each deployer 2 may provide (i.e. deploy) the owner’s application 4 to the one or more end users 50 to 55via the deployer’s (second) application 12. It could be said that the deployer’s application 12 hosts the execution of the owner’s application. In some embodiments, as shown in Figures 1, 2 and 6, the owner and the deployer are separate entities. For example, they could comprise separate, unrelated companies or other types of organisation, or separate sub-entities (e.g. departments or companies) within the same organisational structure. In other embodiments, however, the owner and controller could be, comprise or belong to the same entity. Advantageously, as described in more detail below, this is achieved without disclosure or exposure of the back end functions of the owner’s application 4 to unauthorised entities, enables customisation of the owner’s application by the deployer 2 in accordance with rules and / or criteria that are specified by the owner 1, and also enables secure communication between the owner’s application 4, the end user device 11, and any third party technologies that connect with the owner’s application 4. As shown in Figures 2, 3, 5 and 6, the platform 3 comprises a plurality of components and features. These may include functionality to enable provision of the application 4 to the deployer 2 after it has been created by the owner 1. The platform may also comprise a tool or component that we will call a dashboard 15, that enables the owner 1 to generate the desired application 4. The dashboard enables the owner 1 to specify the features and functionality that will make up the application 4 in order to perform the task(s) and provide the service that the owner wishes to provide to the deployer’s end users. In some embodiments, the application 4 features include criteria, rules and attributes relating various aspects such as security, end-user authentication, how communications will be conducted between the application and other entities, and the data that will be stored in the variables 9 and used by the application 4 during execution. The platform may facilitate generation and specification of the application features using any suitable computing tool or collection of tools, such as the dashboard 15. In some embodiments, this may comprise the use of a mark-up language that enables definition of the application’s visual and functional features. The application 4 that is designed and generated by the owner 1 using the dashboard 15 may comprise at least one or more of the following features: • Application functionality The functions to be performed upon execution of the owner’s application 4 are encoded in machine-executable instructions; this may be referred to as the ‘program logic’, ‘logic code’ or simply ‘logic’ of the application 4; • Variables the data items / valuesthat the program logic operates on during execution are stored in, and accessed via, respective variables 9 that are declared (specified) within the application’s code; the lifetime (which may alternatively be referred to as the ‘scope’ or ‘persistence’) of the variables may vary depending on the nature or purpose of the data that they store; thus, it is the owner 1 that specifies, at the platform, the purpose, use and scope of the application’s data; for example, some data items may persist from one execution session to another e.g. deployer IDs etc; persistent data items may be stored in the owner’s database 8 for future access therefrom; the database 8 may be provided on a computing resource e.g. server at the platform 3, or within the owner’s wider system (network) 14, or in the cloud, or via any other suitable location / computing infrastructure appropriate to the particular implementation; however, other data items may be ephemeral or temporary, such as values that are only relevant to a particular execution session but not required for future access, or are used only during execution of a particular operation or calculation, or are not allowed to persist e.g. for regulatory or privacy reasons etc. Such data items may be inputted by an end user, or provided by the deployer, or calculated by the program logic, or (pseudo) randomly generated as required by the particular implementation; • API Configuration files 7 configuration files 7 (which may be referred to as ‘config files’ or simply ‘API configs’) specify and control how the application will communicate with first or third party computing entities. The dashboard 15 is operative to enable the owner 1 to create and / or edit machine executable rules (which we may call ‘scripts’) that define the configurations which will control how the application 4 communicates with other parties via one or more APIs 6. For example, the owner can, via the platform’s dashboard, specify which encryption layers must be used during an execution session, and how they must be set up. Advantageously, the owner 1 needs only specify an API config for a given entity once. However, subsequent alteration or update of config files 7 can be achieved via the dashboard as and when required by the owner. In a preferred embodiment, the API configs 7 are stored only within a resource that is owned or controlled by the owner 1; the storage facility 8 may be located within the platform and / or owner’s computing system 14 advantageously, the owner is able to specify, via the platform, configuration files for any chosen API, and any number of APIs; in effect, the disclosure provides a universal API adapter or solution; this provides a significant technical benefit relative to the prior art arrangements which are arranged for operation with only specific, predetermined API; therefore, the disclosure provides improvements in the generation and implementation of complex computing technologies; additionally, or alternatively, the disclosure provides improved computing architectures and arrangements • User Interface (UI) 16 UI 16 comprises the necessary definitions and data that is required for correctly formatting and processing the application 4 data for presentation to the user on the user’s device 11. The owner’s application 4 data may be formatted and presented in any appropriate manner, such as, for example, using visual, audio or tactile (e.g. vibration) output or a combination thereof. The UI comprises the necessary configurations and data for this to be handled correctly; Advantageously, the deployer may provide values for the variables defined by the owner during a set-up or initialisation stage; during the set-up phase, the owner and deployer agree to collaborate and the deployer agrees to deploy the owner’s application to the end user(s) on behalf of the owner. The deployer may provide data items such as logo, address etc to the owner so that the application 4 can be customised to the specific deployer 2 at runtime. • Software Development Toolkit (SDK) In one or more preferred embodiments, the owner’s application 4 is provided to the deployer’s system 17 from the platform 3 by means of an SDK; the SDK provides the complete environment that is needed for the owner’s application to execute when initiated by an end user 50to 55. In an example embodiment, the SDK (and / or the UI 16) may be provided as a service via an API that facilitates connectivity between the owner’s application 4 and the deployer’s application 12 that is executing on the deployer’s system 17. In some embodiments, the SDK may be used as follows: - The application deployer includes at least one trigger (snippet) in the deployer’s application 12. The SDK is provided to the deployer’s system by the platform; - When user activates the trigger, the code in the snippet calls (activates) the SDK and causes it to send a signal to the platform (this may be called a boot action). In response to receipt of the boot signal, the platform issues a new session and the owner application 4 starts executing; this includes: initialisation of variables, establishment of API connectivity, confirmation of authentication of end user and deployer etc. - the SDK opens a container within the deployer’s application 12 that is executing on the deployer’s system, platform engine begins to execute the logic code via the container, which means that the actions and data are made available (presented) to the end user 5 via the UI 16 because software on the end user’s device is connected to (interacting with) the deployer’s application 12. In some embodiments, the SDK may be provided, along with the configuration data, when the deployer receives a deployment from the application owner i.e. when the owner and employer have agreed to collaborate and the necessary set-up steps are performed. For web-based implementations, the SDK may be loaded into memory and executed at the start of each session. For implementations where the user’s electronic device is a mobile device, such as a device using the iOS or Android operating system, the SDK may be provided as part of a mobile app that is provided by the deployer to the end user who then installs it on their electronic device; in such implementations, the SDK may run when the user initiates a session. In some embodiments, the SDK performs functions relating to user authentication and data passporting. ‘Data passporting’ refers to the technology that allows collaborating parties to make user data available for service providers. It is a secure and encrypted way of sharing data between two entities, and subject to strong consent from the user before any data is passed over. As shown in Figure 5, the platform 3 may comprise an ‘engine’ or ‘execution’ component that is provided on the owner’s system 14 e.g. server. In one or more embodiments, the engine comprises a node package that is arranged to perform the necessary operations during execution of the application e.g. execution of the program logic and provision of necessary data to the end user 5. The engine may be used by both the owner’s system 14 and the end- user’s computing device 11 to process the mark-up documents generated by the owner via the dashboard and convert them into the correct format. For example, in a preferred embodiment the engine: • creates, renders and provides the UI 16 to the end user’s 5 presentation software e.g. browser running on the end user’s device 11 • handles connection to APIs 6 in accordance with the config files 7 • is used by the owner’s system 14 e.g. server to process the variables’ data 9 to execute the program logic (note: when the application 4 executes, one or more actions may be performed by software on the end user’s device 11 or at the owner’s system 14, depending on the nature / purpose of the action) With reference to Figures 3, 5 and 6, the platform 3 can be arranged for interaction with one or more owners. Figures 5 and 6 show an embodiment wherein the platform 3 is provided at the owner’s system 14. In such a scenario, an owner 1 hosts the platform 3 themselves. An alternative arrangement is shown in Figure 3, in which multiple owners 10and 11have access to the platform 3. Each owner registers with the platform such that a separate account is created for Owner 1 and Owner 2, each having their own identifier (ID) registered in association with their account at the platform 3. Storage of data relating to the owners’ applications can be stored in separate storage resources (or separate partitions of storage location(s)) at the platform as shown in figure 3 or may be stored off-platform in storage resources hosted or accessed independently by the respective owner. Advantageously, such an arrangement enables deployment of the owner’s application across multiple deployer systems such that the application executes in a secure, isolated environment that does not involve interaction with the deployer’s system. Moreover, the communication channel can be established between the owner’s SDK that has been provided on the deployer’s host system and the end user’s device. This is an entirely different technical approach relative to prior art that provides a customised container from the owner to the deployer, wherein the container is arranged to establish application-to-application communication between the owner’s application and the third party host system. Thus, the disclosed arrangement avoids several disadvantages associated with the prior art, and provides a technically improved solution that is more secure, efficient and versatile. IN-USE EXAMPLE With reference to the accompanying Figures, in particular Figure 4, we now provide a step- through of how an example embodiment could be used in practice. The person skilled in the art will readily appreciate that this is provided as an illustration only, and the disclosure can be put into practice in a variety of ways according to the needs of a particular implementation. Consider a scenario in which an owner wishes to provide a service or provide the output(s) of at least one predetermined function to an end user 5. In our current scenario, the end user 5 has a relationship with the deployer 2 and / or is able to execute an application 12 provided by the deployer 2 on the user’s device 11. Recall, however, that in some embodiments the deployer 2 and the owner 1 may be the same entity. The owner 1 uses the platform 3 as described above to generate an application 4 that will provide the desired service / output(s) to the end user 5 via the deployer’s application 12. The owner and the deployer perform the agreement and set up phase as discussed above. As shown in Figure 6, the deployer’s application may be arranged for communication and presentation at the user’s device 11 via any suitable arrangement comprising software arranged for execution on the necessary hardware and / or firmware. For example, the deployer’s application 12 may be arranged to execute on or within the user’s device 11 via a browser, or a software client or app installed on the user’s device 11, or some other suitably arranged software / hardware that enables presentation of the deployer’s application 12 to the end user 5. In our example, we will assume that the deployer’s application 12 is provided on the user’s device using a browser. The user 5 runs the deployer’s application 12 on their device 11. The deployer’s application 12 comprises an activation mechanism (which may be called an ‘application activator’, or ‘trigger’) 13 arranged to initiate execution of the owner’s application 4. The owner provides the trigger to the deployer so that the deployer can incorporate it into the code of the deployer application. In a preferred embodiment, the trigger 13 is provided within the deployer’s application 12 by inclusion of at least one portion of code, which may be referred to as a ‘snippet’. The deployer’s application 12 may comprise means for operating / activating the trigger 13. This may take any suitable form depending on the implementation. For example, it may comprise a UI component such as button, a hyperlink, drop-down menu, a keyboard input, a voice command received via a microphone, a mouse or pointer selection on a screen, an input to a touch screen etc. The UI component may be arranged to take an input (e.g. from the screen, microphone, mouse etc) and pass that on to the deployer’s application as a signal which activates the trigger i.e. begins execution of the snippet of code. Essentially, the trigger activator is any suitable means that enables the user 5 to indicate that (s)he wishes to initiate execution of the owner’s application 4. When the user 5 activates a trigger 13 in the deployer’s application 12, the instructions contained within the snippet may send a request to the platform 3 to execute the owner’s application 4. The platform 3 then initialises, on the owner’s system, an execution session that is specific to the new execution of the owner’s application 4. This may comprise steps being taken such as initialisation of certain variables, accessing persistent data from storage 8 and loading into run-time memory, generation of one or more security tokens for establishing secure communications between the owner’s application 4 and the deployer’s system 17 etc. As explained, the trigger is embedded in the deployer’s application 12 which is running on the deployer’s system 17. Suppose that the user 5 has authenticated with the deployer’s application 12 so that the user’s identity has been validated via any suitable authentication technique(s) e.g. via the use of cryptographic techniques comprising the use of key(s) or signatures, face recognition, other biometric verification, password / PIN verification etc. Thus, when the user activates the owner’s application, authentication techniques such as SSO can be utilised to avoid the time, resources and inconvenience associated with requiring the user 5 to authenticate again (this is shown on the left-hand side of Figure 5). Turning now to Figure 4 in combination with Figure 6: Step 1: the user 5 wishes to execute the owner’s application 4 and clicks on a button (trigger) to indicate this desire; Step 2: upon receipt of the signal generated by the trigger activation, a boot request is sent to the platform 3 which generates a session token; the end user's (5) identity is verified at the platform (3) via any suitable mechanism e.g. the use of one or more cryptographic digital signatures; Step 3: the SDK (10), which has been provided from the platform to the deployer's system (17), establishes a secure communication channel with the end user's device (11); Step 4: the SDK (10) generates an embedded container; the container comprises variables (9) for data that is required by the application logic and by the UI for presentation of the application data to the end user (5) via their device (11); Step 5: secure connections, as defined by the rules in the API config files (7), are established using API's (6) as required between the owner's application (4) and 3rd Party system(s) and / or 1st Party system(s); Step 6: The owner’s application (4) variables 9 are populated with data retrieved from various sources e.g. inputted by end user (5), supplied by the deployer (2), obtained from the owner's database (8), provided via API(s) (6), obtained from system-level functions (11), pseudo-randomly generated data, etc. Step 7: presentation software (e.g. browser) running on user device (11) displays the owner’s application UI (16) and its populated data for the end user (5) to view (or otherwise consume e.g. via audio or vibration etc); Step 8: The owner application (4) terminates: - persistent data can be stored e.g. in owner database (8); and / or - ephemeral data (e.g. memory allocated to session-only or time-based lifetime is released, data erased) EXAMPLE APPLICATIONS: Embodiments of the present disclosure may be used to advantage in a variety of application areas, technical and / or industrial contexts. The disclosure is not tied to any particular use- case scenario or application domain, and is agnostic with regard to the type or purpose of the application(s) that are generated by the owner. Embodiments of the disclosure may be used to advantage in any scenario where an application owner wishes to deploy their application to one or more end users via another (host) application. Purely for illustration, we provide the following as examples for which embodiments of the disclosure may be used: • a webpage on an airport website 12, hosted on the airport’s computing network 17 and viewable by travellers 5 visiting the airport web site, the web page containing one or more triggers 13, each trigger 13 causing execution of a respective owner application 4 provided by a respective owner 10 … nthat provides parking, accommodation, flight, insurance or other functions that may be of use to the traveller 5; • a telehealth system, such as a telesurgery system for delivering surgical services to a patient who is geographically remote from the surgical team; the owner 1 may be a telehealth specialist company having an account at the platform 3 as illustrated in Figure 3, and having multiple owner applications 4 at the platform, each owner application 4 being designed to facilitate delivery of a specific type of telesurgery and using data from different data sources (APIs 6), and being deployed to a variety of health trusts (deployers 20 … n) who allow surgeons (i.e. end users 5) to participate in a telesurgery session by secure connection via a trigger embedded in a client application 12 on the hospital’s network 17; an arrangement provided by such an embodiment can be beneficial in such situations where security, authenticity and sharing of sensitive data is of great importance; isolation of the execution of the owner’s application from the host system promotes protection of data and privacy, as well as protection from exploits and threats such as viruses and malware that might otherwise compromise the integrity of the devices involved; • a financial services solution (e.g. open banking service for secure connectivity between separate financial organisations) wherein the application owner 1 is a payment card services provider and the deployer(s) 2 are individual banks, and the end users are the banks’ customers 5; for example, the card provider 1 may use the platform to generate an application 4 that is deployed to end customers 5 via their respective, individual banks 2; • a system for enabling end users to select / vote for one or more options from a plurality of options, each option being provided by a separate and distinct owner 1. For example, a web site 12 operated by a sporting event organiser may have triggers for a plurality of charity applications (1) embedded in it, so that end users are able to choose which charity they wish to donate their sponsorship funds to; in this example, the individual charities are the owners 1 of their respective applications 4, and the sporting event web site 12 that the triggers are embedded in is provided by the deploying event organiser 2. Variations could include applications that offer service switching functionalities such as broadband or mobile phone services from different providers. VARIATIONS, OPTIONS AND DEFINITIONS Embodiments of the disclosure may provide computer implemented systems, methods and suitably arranged computing apparatus (hardware and / or software) for one or more of the embodiments substantially as described, illustrated in the Figures or claimed herein. The term ‘application’ may be used interchangeably with ‘software element’ or ‘program’. The term ‘operative’ may be used interchangeably with, or comprise, one or both of ‘arranged’ and ‘configured’. The terms ‘deploy / deployment’ may be used interchangeably with ‘provide / provision’ or ‘distribute / distribution’ • Deployment of the owner’s application may comprise provision of all necessary application data, including logic and state, in order for the application to be executed in the deployer’s system • Deployment of the owner’s application to the end user may comprise presentation of the visual / audio / tactile aspects (outputs) of the application on the end user’s electronic device • Deployment of the first and / or second applications may be performed by transmitting the necessary data over at least one computing network such as the internet, a WAN, a wireless network, a telecommunications network etc.; • when the first application is provided from the owner to the deployer, the necessary data may comprise the application logic and data items and / or a runtime environment; • when the second application is provided by the deployer’s computing system to the user’s device, the necessary data may comprise the UI features and data items. The first / second applications may be referred to as first / second programs or first / second software elements. The term ‘owner’ may be used interchangeably with ‘controller’, ‘creator’. The controller may be the party that controls / defines / specifies the application state (i.e. the variables and their declared types) and the program logic, via / using the tools provided within the (dashboard of) the platform. In accordance with one possible form of wording, the first application may be or comprise an embeddable UI that is able to connect to any API and is distributed to one or a plurality of application deployers for execution on any form of computing architecture / digital channel e.g. web, IOS, Android etc. The API(s) may be 3rdparty or 1stparty API(s). The application owner may have access to the platform and its components while an application deployer may be prohibited from seeing, access or using the platform or its components. The platform may enable the owner to generate and deploy (i.e. distribute) a plurality of different applications. In accordance with one or more embodiments, the disclosure may provide a method that may be described as any one or more of the following: • a method for generating or designing a computer-implemented application; • a method for embedding a first application within a second application; • a method for executing a first application that is provided by an application owner / controller, from within a second application that is provided and / or executed by an application deployer. A method according to any embodiment of the disclosure may comprise one or more of the following steps: • Executing the first application on a computing system / network of the deployer; • Executing the first application by the deployer and / or on behalf of the application owner; • Executing the first application upon determining that a user of the second application has activated a trigger arranged to cause the execution of the first application; • providing a platform substantially as described, claimed or illustrated in the figures provided herein; • providing a platform comprising one or more of: a dashboard, an engine, a storage facility; • providing a platform that is operative to enable or facilitate the generation, storage and / or modification by an application owner of one or more API configuration files; • providing a platform that is operative to enable or facilitate the generation, definition, specification, storage and / or modification by an application owner of one or more of: o at least one User Interface (UI) o machine executable logic (code / instructions) to perform one or more specific functions / tasks o a plurality of variables, each arranged for storing a respective data item required for the execution of the first application; • providing a platform that is operative to provide an execution environment (e.g. SDK) to at least one application deployer for the execution of the first application on the application deployer’s system and / or by (or on behalf of) the application deployer. According to another aspect of the disclosure, there is provided a computer implemented system arranged to perform any method step or combination of method steps described or claimed herein. Thus, there may be provided a computing resource which may be described as one or more of: a toolkit, system or platform, comprising suitably arranged hardware and / or software for the implementation of any method(s) or steps substantially as described, claimed or illustrated herein. We will use the term ‘platform’ for ease of reference. The platform may comprise one or more of a dashboard, an engine, a storage facility. The storage facility may allow storage of and access to data items that are used by the first application. The first application may use variables, defined by an application owner, to store the data items during initialisation and / or execution of the application. The variables may store session or persistent data. The data items may be provided from the application owner, the application deployer or the end user. The UI may be described as the visual / audio / tactile or other representation of the first application. It may be described as the interface that enables the first application and its data to be presented to the end user, and / or enables the end user to input data to the first application. The UI may be generated, at last in part, by a no-code-tool and / or a flow composer. These may be provided as part of the platform’s dashboard. The no-code tool may be operative to facilitate generation of the first application by the owner without the need to write source code. It may be operative to enable creation of the ‘look and feel’ i.e. user experience of the first application. The no code tool may comprise a graphical user interface that is arranged to allow the owner to create user interface of the first application. The flow composer may comprise a tool that allows the creation of the flow of the application. This may be used by at least one project manager at the owner’s organisation to build logic, navigation and or data flow of the first application. The flow composer may comprise a graphical user interface that allows or facilitates the creation / specification of one or more of: variables (data items), actions (logic), API connections and API configurations for the first application. The platform’s dashboard may be accessed by the owner via any suitable computing arrangement e.g. a web browser or an application installed on a computing resource of the owner. The SDK (or other type of runtime environment) may be utilised by the second application to open an embedded container within the deployer’s application 12. Upon establishment by the SDK of a secure connection, the SDK may open an embedded container with a representation of the owner application i.e. a UI (e.g. View) in the application 12. The container may comprise an executable software unit that includes all necessary executables for the entire runtime environment – this may include an executable version of the first application, one or more code libraries and / or one or more configuration files for execution of the first application by / on the deployer’s system. In accordance with one or more embodiments, interactive views may dynamically adapt and / or respond to user behaviour. This provides the advantage of being able to build complex and functionally sophisticated applications. Views may retrieve data from storage to provide the most relevant data to the first application. Data may be retrieved from a plurality of resources, and may be merged by the first application to create at least one customised data structure that is appropriate and / or necessary for the first application to perform its function(s) / task(s). Data may be obtained by the first application from one or more external data sources, and / or may be processed to standardise and or sanitise the obtained data item(s) to conform with the required functionality of the first application. A view may define an instance or part of the UI for the first application. A view may provide a representation of an entire page or section of the first application, or a part of a page / section thereof. A view may comprise any type of UI structure. The owner, when generating the first application, may navigate between different views as if they are web pages, and multiple views from an application may be displayed simultaneously. Secure connection to APIs may be made from the deployer’s network / system to any first- party network. Additionally, or alternatively, secure connection to APIs may be made from the deployer’s network / system to any third-party systems or domains across an electronic network such as, for example, the internet. The platform may comprise a data viewer. The data may be operative to enable the application owner to inspect or monitor the status of the platform, and / or may comprise functionality for generating an API connection report and custom events. In some embodiments, the platform may comprise a Content Delivery Network (CDN) to provide static assets and enhancement of connection speeds. Additionally, or alternatively, the platform may enable or facilitate selection, by one or more application owners, at least one data back-up arrangement. The platform may be described as one or more of: a computer-implemented system or toolkit. It may be arranged and / or configured for: • generating or designing a computer-implemented application; • embedding a first application within a second application; • executing a first application by an owner / controller of the first application such that: i) the execution of the first application is provided and / or made available to an end user who is using and / or interacting with a second application that is executing on a deployer’s computing system; the user may be using and / or interacting with the second application on or via an electronic device that is associated with, owned by, used by and / or controlled by the end user ; and ii) the execution, output of the execution and / or representation of the execution of first application is made available to the end user / the end user’s electronic device) from within the second application and / or the deployer’s computing system; the deployer’s computing system cay comprise hardware, firmware and / or software apparatus that is associated with or controlled by the deployer, and arranged to execute the second application by or on behalf of the deployer. The system may be operative to enable or facilitate: o execution of the first application on a computing system / network of the deployer; o execution of the first application by the deployer and / or on behalf of the application owner; o execution of the first application upon determination that the user of the second application has activated a trigger (provided within the second application) that is arranged to cause the execution of the first application; o generation, storage, definition, specification and / or modification by an application owner of one or more API configuration files; the generation, storage, definition, specification and / or modification of the API configuration file(s) may be performed at a platform of the system; o providing a platform that is operative to enable or facilitate the generation, definition, specification, storage and / or modification by an application owner of one or more of: o at least one User Interface (UI) o machine executable logic (code / instructions) to perform one or more specific functions / tasks o a plurality of variables, each arranged for storing a respective data item required for the execution of the first application; and / or o provision of an execution environment (e.g. SDK) to at least one application deployer for the execution of the first application on the application deployer’s system and / or by (or on behalf of) the application deployer.; provision of the run-time environment may comprise making the run time environment available to the deployer’s computing system and / or providing access to the SDK by the deployer. The first application may be arranged to connect, send requests to and receive responses from any number of APIs as needed for performance of the owner-specified service(s) / task(s) that are implemented by the program logic. The API configurations may identify or specify a URL and / or one or more authentication methods. In some embodiments, one or more of the following actions may be performed by or at the platform, optionally by an engine of the platform: • generation of the SDK and provision of access to it by the deployer; in some embodiments, the SDK may be provided to the deployer’s system; • execution of the logic code (Actions) • declaration, initialisation of data items (variables) • connection to 1st / 3rdparty APIs in accordance with the rules, instructions and / or criteria specified in the config files; preferably the config files are stored at the platform or in a storage facility that is accessible by one or more components of the platform; the API config file(s) may be specific to a particular owner application 4; • the platform issues a token in response to a request (which may be referred to as a “boot request”, and may be sent in response to activation of the trigger by the user); the boot request may perform some identity checks, and may (or may not) comprise one or more digital cryptography signatures; the signature(s) may be provided from / by the deployer’s system; One or more of the following actions may be performed by the deployer’s system: • the deployer includes at least one trigger (snippet) in their own (deployer / second) application, the deployer executes the deployer application on the deployer’s computing system for use / consumption / interaction by an end user who is operating an electronic computing device; • upon determination that the user has activated one of the at least one triggers, instructions / code provided within, in association with or by the trigger causes a signal to be transmitted, over at least one electronic / digital / computer-implemented network, to the platform; this may comprise the code in the snippet calling the SDK which then sends the signal to the platform; the platform may then initiate a session and begin execution of the owner application; the initiation and / or subsequent execution of the owner application may be performed, influenced and / or controlled, at least in part, by an engine component and / or other component(s) of the platform; • initiation of the execution may comprise one or more of: initialisation of variables, establishment of connectivity to one or more data sources and / or destinations via the API(s) and in accordance with their associated API configurations specified by the application owner, authentication of the end user and / or deployer (or confirmation of the deployer’s authentication of the end user); • enable or facilitate generation, by the SDK, of an executable software unit / element (e.g. container) on the deployer’s system; the executable unit / element may be generated (opened) from within or by the deployer’s application that is running on the deployer’s system; from the perspective of the platform, the engine and / or other platform component(s) may begin to execute the logic code of the owner’s application via the container; Thus, the owner application’s data items and the outputs / results of actions performed by the owner’s system as a result of executing the owner application can be made available to the end user via the end user’s device, because the end user’s device is connected to / interacting with / communicating with the deployer’s application that is running on the deployer’s computing system. Thus, embodiments may be described as enabling or facilitating execution of the owner application: • on or at the owner’s system (and / or a platform as disclosed herein provided, at least in part, on the owner’s system); in one or more embodiments, execution may be performed at the platform, optionally by an engine component of the platform; execution of the owner application may comprise one or more of: manipulation of data items stored in variables by the platform, enforcement of rules specified by the owner at the platform, possibly by use of a dashboard or dashboard component, establishment and / or control of connectivity between the owner application and at last one data source / destination, authentication of any relevant parties such as the deployer’s system, end user or end user’s device, performance of actions et); • such that the execution of the owner’s application is provided / deployed / presented to the user’s device by / via the deployer’s system; • by the deployer’s system on behalf of the owner; • by the deployer’s system via / by use or execution of an executable software unit that is provided and / or made available to the deployer’s system by the application owner, ENUMERATED CLAUSES The disclosure may provide embodiments as recited in any one or more of the following enumerated clauses, for the purpose of illustration only and without limitation. Any feature(s) recited in respect of a platform or system may be incorporated into a corresponding method clause / claim and vice versa. Any feature(s) recited in respect of one clause set may be incorporated in the one or more clauses of any other clause set. Enumerated clause set 1: Clause 1,1. A computer-implemented platform that is arranged to enable or facilitate, by an application controller: i) specification of the logic and associated data items for a first application that is arranged to perform, when executed, one or more tasks specified by the application controller; and ii) deployment (or provision / distribution) of the first application to at least one electronic device associated with a user via a second application that is arranged for execution / executed / executing on a computing system associated with an application deployer. Clause 1.2. The computer-implemented platform of Clause 1.1, wherein the platform is further arranged to enable or facilitate, by the application controller: the creation and / or specification of at least one Application Programming Interface (API) configuration file for defining, influencing or controlling connectivity between the first application and an API. Clause 1.3. The computer-implemented platform of Clause 1.1 or 1.2, wherein the platform comprises one or more of: i) a dashboard component to enable or facilitate generation of the first application by the application controller; ii) at least one data storage resource for storage or retrieval of data items required for execution of the first application; iii) a no code tool comprising a graphical user interface that is operative to facilitate or enable generation of the first application, and or a User Interface of the first application, by the application controller without writing source code; iv) a flow composer component comprising a graphical user interface that enables or facilitates the creation and / or specification of one or more of the following elements of the first application : at least one action to be performed during execution of the first application, a plurality of data items required for performance of the at least one action, at least one API connection and at least one API configuration. Clause 1.4. The computer-implemented platform of any preceding Clause, wherein deployment of the first application is performed in response to activation by the user of a trigger provided within the second application. Clause 1.5. The computer-implemented platform of Clause 1.4, wherein the trigger comprises a portion of code provided in the second application, wherein execution of the portion of code causes a signal to be sent from the computing system associated with the application deployer to the platform. Clause 1.6. The computer-implemented platform of any preceding Clause, wherein deployment of the first application comprises: i) provision of, or provision of access to, an execution environment by the platform to the computing system associated with the application deployer; and / or ii) presentation of a representation of the execution of the first application, preferably wherein the representation is or comprises a user interface defined by the application controller and / or specified using the platform. Clause 1.7. The computer-implemented platform of any preceding Clause, wherein: i) access to the platform is restricted the application controller; and / or ii) access to the platform is prohibited to the application deployer; ii) the first application is arranged to authenticate the user using the second application. Clause 1.8. The computer-implemented platform of any preceding Clause, wherein the platform is provided on a computing system that is associated with: i) the application controller; or ii) a platform provider. Clause 1.9. The computer-implemented platform of any preceding Clause, wherein deployment of the first application to the at least one electronic device associated with the user comprises presentation of the first application and its associated data items to the at least one electronic device by the second application. Clause 1.10. The computer-implemented platform of any preceding Clause, wherein the platform comprising one or a plurality of computer-implemented resources, and at least one of the computer-implemented resources comprises: a processor; and memory including executable instructions that, as a result of execution by the processor, causes the platform to perform or provide the feature(s) of any preceding Clause. Clause 1.11. A non-transitory computer-readable storage medium having stored thereon executable instructions that, as a result of being executed by a processor of a computer system comprising one or more computers, cause the computer system to provide the computer-implemented platform of any one of Clauses 1.1 to 1.10. Enumerated clause set 2: Clause 2.1. A computer-implemented method for embedding a first software element (e.g. first application) provided by a first party (e.g. application owner) within or into a second software element (e.g. second application) that is provided to an electronic device of a user, the method comprising the steps of: specifying, at a computing platform, the logic and associated data items of the first software element; and / or enabling or facilitating execution of the first software element on a computing system of a second party for presentation of the first application to the electronic device of the end user. Clause 2.2. The computer-implemented method of Clause 2.1, and comprising the step of: creating and / or specifying at least one Application Programming Interface (API) configuration file for defining, influencing or controlling connectivity between the first software element and at least one API. Clause 2.3. The computer-implemented method of Clause 2.1 or 2.2, wherein: i) one, some or all of the steps of Clause 2.1 or Clause 2.2 are performed by the first user; and / or ii) the step of enabling or facilitating execution of the first software element comprises provision of a runtime environment for the first software element by the first party to the computing system of the second party; and / or iii) the step of enabling or facilitating execution of the first software element is performed in response to activation by the user of at least one trigger provided within the second application. Clause 2.4. The computer-implemented method of any of Clauses 2.1 to 2.3, wherein one, some or all of the steps are performed by the first party using a platform as defined in any of Clauses 1.1 to 1.11, or described or illustrated herein. Enumerated clause set 3: Clause 3.1. A computer-implemented method, performed by an application owner, comprising the step: using a computer-implemented platform to enable or facilitate: i) specification of the logic and associated data items for a first application that is arranged to perform, when executed, one or more tasks specified by the application controller; and ii) provision of the first application to at least one electronic device associated with a user via a second application that is arranged for execution on a computing system associated with an application deployer. Clause 3.2. The computer-implemented platform of Clause 3.1, and further comprising the step of using the platform, by the application owner, to enable or facilitate: the creation and / or specification of at least one Application Programming Interface (API) configuration file for defining, influencing or controlling connectivity between the first application and a one or more APIs. Enumerated clause set 4: Clause 4.1. A computer-implemented method, performed by an application deployer having a computing system, comprising the step: using the computing system to deploy a first application to at least one electronic device associated with a user of a second application that is executing on the computing system, wherein: logic and associated data items for the first application are specified by the application controller at a platform provided in accordance with any Clause of clause set 1. Clause 4.2. The computer-implemented method of Clause 4.1, and further comprising the step of receiving, by the computing system of the application deployer and from the platform, an execution environment arranged to enable or facilitate execution of the first application by the computing system for presentation to the at last one electronic device associated with the user. Enumerated clause set 5: Clause 5.1. A computer-implemented method, preferably performed by an application deployer having a computing system, comprising the step: providing or presenting, by the computing system of the application deployer and to an electronic device of a user, execution of a first application on behalf of an application controller of the first application. Preferably, execution of the first application is performed, at least in part, at a computing system of the application controller. Additionally, or alternatively, execution of the first application may be provided or presented by the application deployer’s computing system to the user’s electronic device via, by or using the execution of an executable software unit. The executable software unit may be a container and / or may be provided to or made accessible to the deployer’s system by a computing platform controlled by the application controller. Clause 5.2. The computer-implemented method of Clause 5.1, wherein: i) the computing platform is arranged and configured in accordance with any embodiment of the platform / system disclosed herein, or operative to provide any functionality of an embodiment disclosed herein; and / or ii) connectivity or communication between the first application and at least one data source and / or data destination is controlled by at least one API configuration file that: - is stored at the platform or the owner’s system; and / or - comprises at least one rule, criteria or attribute specified by the controller to control or influence how the connectivity or communication is established or performed during execution of the first application; and / or iii) the execution of the first application is initiated upon determination that the user has activated a trigger provided within a second application that is executing on the deployer’s system; preferably wherein: activation of the trigger by the user causes a signal to be sent from the deployer’s system to the platform to initiate the execution of the first application; and / or iv) provision or presentation of the execution of the first application, by the computing system of the application deployer to the electronic device of the user, comprises presentation of a representation of the execution of the first application to the electronic device, preferably wherein the representation is or comprises a user interface defined by the application controller and / or specified using the platform. According to another aspect of the disclosure, there is provided a computer implemented system arranged to perform any method step or combination of method steps substantially as disclosed herein. There is provided a computer-implemented apparatus (e.g. system, network, one or more devices) comprising one or a plurality of computer-implemented resources (e.g. network node, user device, terminal, etc), wherein at least one computer-implemented node comprises: a processor; and memory including executable instructions that, as a result of execution by the processor, causes the system to perform any variation of the computer- implemented method disclosed herein. According to another aspect, there is provided a non-transitory computer-readable storage medium having stored thereon executable instructions that, as a result of being executed by a processor of at least one computer system, cause the computer system(s) to perform any embodiment of the computer-implemented method(s) disclosed herein. ILLUSTRATIVE COMPUTING ENVIRONMENT FIG.7 illustrates an example device 2500, with a processor 2502 and memory 2504 that can be configured to implement various embodiments of the methods and processes as discussed in the present application. In some embodiments, computing device 2500 may be a standalone device, or may form part of system. It may be a node on a network, and / or form part of a wider computing system comprised of interconnected devices arranged for communication with one another. Thus, the hardware and / or software of computing device 2600 may take any suitable known form to enable a chosen embodiment to be implemented on it. The skilled person will readily appreciate that many other forms and arrangements of hardware, software and / or firmware can be used, and that this is just an illustrative example. Memory 2504 can also host one or more databases and can include one or more forms of volatile data storage media such as random-access memory (RAM), and / or one or more forms of nonvolatile storage media (such as read-only memory (ROM), flash memory, and so forth). Device 2500 is one example of a computing device or programmable device and is not intended to suggest any limitation as to scope of use or functionality of device 2500 and / or its possible architectures. For example, device 2500 can comprise one or more computing devices, programmable logic controllers (PLCs), etc. Further, device 2500 should not be interpreted as having any dependency relating to one or a combination of components illustrated in device 2500. For example, device 2500 may include one or more of computers, such as a mobile / portable / handheld device, mobile phone or tablet, laptop computer, a desktop computer, a server, a mainframe computer, etc., or any combination or accumulation thereof. Device 2500 can also include a bus 2508 configured to allow various components and devices, such as processors 2502, memory 2504, and local data storage 2510, among other components, to communicate with each other. Bus 2508 can include one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. Bus 2508 can also include wired and / or wireless buses. Local data storage 2510 can include fixed media (e.g., RAM, ROM, a fixed hard drive, etc.) as well as removable media (e.g., a flash memory drive, a removable hard drive, optical disks, magnetic disks, and so forth). One or more input / output (I / O) device(s) 2512 may also communicate via a user interface (UI) controller 2514, which may connect with I / O device(s) 2512 either directly or through bus 2508. In one possible implementation, a network interface 2516 may communicate outside of device 2500 via a connected network. In some embodiments, the computing device 2500 may include software and / or hardware for connection of the computing device 2500 to at least one other device via wireless means such as Bluetooth, NFC or other wireless communication protocols or techniques. Additionally, or alternatively, the computing device 2500 may include or communicate with at least one other device that may be connected to the computing device 2500 through one or more ports (e.g., USB, a headphone jack, Lightning connector, HDMI, ethernet port, serial port, PS2 pinout, parallel port etc.). A media drive / interface 2518 can accept removable tangible media 2520, such as flash drives, optical disks, removable hard drives, software products, etc. In one possible implementation, logic, computing instructions, and / or software programs comprising elements of module 2506 may reside on removable media 2520 readable by media drive / interface 2518. In one possible embodiment, input / output device(s) 2512 can allow a user (such as a human annotator) to enter commands and information to device 2500, and also allow information to be presented to the user and / or other components or devices. Examples of input device(s) 2512 include, for example, sensors, a keyboard, a cursor control device (e.g., a mouse), a microphone, a scanner, and any other input devices known in the art. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, and so on. Various systems and processes of present disclosure may be described herein in the general context of software or program modules, or the techniques and modules may be implemented in pure computing hardware. Software generally includes routines, programs, objects, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. An implementation of these modules and techniques may be stored on or transmitted across some form of tangible computer- readable media. Computer-readable media can be any available data storage medium or media that is tangible and can be accessed by a computing device. Computer readable media may thus comprise computer storage media. “Computer storage media” designates tangible media, and includes volatile and non-volatile, removable, and non-removable tangible media implemented for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible medium which can be used to store the desired information, and which can be accessed by a computer. Some of the methods and processes described above, can be performed by one or more processors. The term “processor” should not be construed to limit the embodiments disclosed herein to any particular device type or system. The processor may include or form part of a computer system. Multiple processors may be used, and these may be running in parallel. The computer system may also include at least one computer processor (e.g., a microprocessor, microcontroller, digital signal processor, general-purpose computer, special-purpose machine, virtual machine, software container, and / or appliance) for executing any of the methods and processes described above. The system may be or comprise a decentralized, peer-to-peer or distributed computing architecture. The computer system may further include a memory such as a semiconductor memory device (e.g., a RAM, ROM, PROM, EEPROM, or Flash-Programmable RAM), a magnetic memory device (e.g., a diskette or fixed disk), an optical memory device (e.g., a CD-ROM), a PC card (e.g., PCMCIA card), or other memory device. Alternatively, or additionally, the processor(s) may include discrete electronic components coupled to a printed circuit board, integrated circuitry (e.g., Application Specific Integrated Circuits (ASIC)), and / or programmable logic devices (e.g., a Field Programmable Gate Arrays (FPGA)). Any of the methods and processes described above can be implemented using such logic devices. Some of the methods and processes described above, can be implemented as computer program logic for use with the computer processor. The computer program logic may be embodied in various forms, including a source code form or a computer executable form. Source code may include a series of computer program instructions in a variety of programming languages (e.g., an object code, an assembly language, or a high- level language such as C, C++, or JAVA). Such computer instructions can be stored in a non- transitory computer readable medium (e.g., memory) and executed by the computer processor. The computer instructions may be distributed in any form as a removable storage medium with accompanying printed or electronic documentation (e.g., shrink wrapped software), preloaded with a computer system (e.g., on system ROM or fixed disk), or distributed from a server or electronic bulletin board over a communication system (e.g., the Internet or World Wide Web). Although only a few example embodiments have been described in detail above, those skilled in the art will readily appreciate that many modifications are possible in the example embodiments without materially departing from this invention. Accordingly, all such modifications are intended to be included within the scope of this disclosure as defined in the following claims. In the claims, means-plus-function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents, but also equivalent structures. Disclaimer All references cited herein are incorporated by reference to the maximum extent allowable by law. Any incorporation by reference of documents above is limited such that no subject matter is incorporated that is contrary to the explicit disclosure herein. Any incorporation by reference of documents above is further limited such that no claims included in the documents are incorporated by reference herein. Any incorporation by reference of documents above is yet further limited such that any definitions or terminology provided in the documents are not incorporated by reference herein unless expressly included herein.

Claims

CLAIMS:

1. A computer-implemented platform that is operative to enable or facilitate, by an application controller: i) specification of the logic and associated data items for a first application that is arranged to perform, when executed, one or more tasks specified by the application controller; and ii) provision or presentation of the first application to at least one electronic device associated with a user via a second application that is arranged for execution on a computing system associated with an application deployer.

2. The computer-implemented platform of claim 1, wherein the platform is further operative to enable or facilitate, by the application controller: the creation and / or specification of at least one Application Programming Interface (API) configuration file for defining, influencing or controlling connectivity between the first application and an API.

3. The computer-implemented platform of claim 1 or 2, wherein the platform comprises one or more of: i) a dashboard component to enable or facilitate generation of the first application by the application controller; ii) at least one data storage resource for storage or retrieval of data items required for execution of the first application; iii) a no code tool comprising a graphical user interface that is operative to facilitate or enable generation of the first application, and or a User Interface of the first application, by the application controller without writing source code; iv) a flow composer component comprising a graphical user interface that enables or facilitates the creation and / or specification of one or more of the following elements of the first application : at least one action to be performed during execution of the first application, a plurality of data items required for performance of the at least one action, at least one API connection and at least one API configuration.

4. The computer-implemented platform of any preceding claim, wherein provision or presentation of the first application is performed in response to activation by the user of a trigger provided within the second application.

5. The computer-implemented platform of claim 4, wherein the trigger comprises a portion of code provided in the second application, wherein execution of the portion of code causes a signal to be sent from the computing system associated with the application deployer to the platform.

6. The computer-implemented platform of any preceding claim, wherein provision or presentation of the first application comprises: i) provision of, or provision of access to, an execution environment by the platform to the computing system associated with the application deployer; and / or ii) presentation of a representation of the execution of the first application, preferably wherein the representation is or comprises a user interface defined by the application controller and / or specified using the platform.

7. The computer-implemented platform of any preceding claim, wherein: i) access to the platform is restricted to the application controller; and / or ii) the first application is arranged to authenticate the user using the second application.

8. The computer-implemented platform of any preceding claim, wherein the platform is provided on a computing system that is associated with: i) the application controller; or ii) a platform provider.

9. The computer-implemented platform of any preceding claim, wherein deployment of the first application to the at least one electronic device associated with the user comprises presentation of the first application and its associated data items to the at least one electronic device by the second application.

10. The computer-implemented platform of any preceding claim, wherein the platform comprising one or a plurality of computer-implemented resources, and at least one of the computer-implemented resources comprises: a processor; and memory including executable instructions that, as a result of execution by the processor, causes the platform to perform or provide the feature(s) of any preceding claim.

11. A non-transitory computer-readable storage medium having stored thereon executable instructions that, as a result of being executed by a processor of a computer system comprising one or more computers, cause the computer system to provide the computer-implemented platform of any one of claims 1 to 10.

12. A computer-implemented method, performed by an application controller, comprising the step: using a computer-implemented platform to enable or facilitate: i) specification of the logic and associated data items for a first application that is arranged to perform, when executed, one or more tasks specified by the application controller; and ii) provision of the first application to at least one electronic device associated with a user via a second application that is arranged for execution on a computing system associated with an application deployer.

13. The computer-implemented platform of claim 12, and further comprising the step of using the platform, by the application owner, to enable or facilitate: the creation and / or specification of at least one Application Programming Interface (API) configuration file for defining, influencing or controlling connectivity between the first application and one or more APIs.

14. A computer-implemented method, performed by an application deployer having a computing system, comprising the step: providing or presenting, by a computing system of the application deployer and to an electronic device of a user, execution of a first application on behalf of anapplication controller of the first application; wherein execution of the first application is: i) performed, at least in part, at a computing system of the application controller; and ii) provided or presented by the application deployer’s system to the user’s electronic device via, by or using the execution of an executable software unit that is provided to or made accessible to the deployer’s system by a computing platform controlled by the application controller.

15. The computer-implemented method of claim 14, wherein one or more of the following apply: i) the computing platform is arranged and configured in accordance with any of claims 1 to 10; ii) connectivity or communication between the first application and at least one data source and / or data destination is controlled by at least one API configuration file that: - is stored at the platform or the owner’s system; and / or - comprises at least one rule, criteria or attribute specified by the controller to control or influence how the connectivity or communication is established or performed during execution of the first application; iii) the execution of the first application is initiated upon determination that the user has activated a trigger provided within a second application that is executing on the deployer’s system; preferably wherein: activation of the trigger by the user causes a signal to be sent from the deployer’s system to the platform to initiate the execution of the first application; iv) provision or presentation of the execution of the first application , by the computing system of the application deployer to the electronic device of the user, comprises presentation of a representation of the execution of the first application to the electronic device, preferably wherein the representation is or comprises a user interface defined by the application controller and / or specified using the platform.

Images