Search

EP-4742704-A2 - APPLICATION MANAGING APPLICATION

EP4742704A2EP 4742704 A2EP4742704 A2EP 4742704A2EP-4742704-A2

Abstract

A System Solution automatically generates a set of Native and Non-Native Application Clients which include updating functionality capable of generating update commands to instruct the System Solution to generate an updated set of Native and Non-Native Application Clients. Using the generated Application Clients, an employee of a Business Entity coupled with the System Solution instructs the System Solution to create a new updated set of Native and Non-Native Application Clients that are automatically downloaded to devices used by the customers of the Business Entity. The System Solution also automatically generates an Update Command Dictionary which, when downloaded to a Manager Client Device, allows an employee of the Business Entity to use a General Third Party Application, such as a SMS, email, or messaging application commonly available on a mobile device, to generate update commands to instruct the System Solution to generate an updated set of Native and Non-Native Application Clients.

Inventors

  • CHIUSSI, FABIO
  • HEDGE, Parameshwar

Assignees

  • Gadget Software, Inc.

Dates

Publication Date
20260513
Application Date
20150417

Claims (15)

  1. A method of using a backend server to enable a first application running on a first client device to cause a download of an updated application on a second client device, the method comprising: receiving, by the first client device, a dictionary of update commands from the backend server; selecting, by a user, an update command from the dictionary of update commands at the first client device; using the first client device to send the selected update command to the backend server; and receiving, by the second client device the updated application from the backend server based on the selected update command.
  2. The method of claim 1, further comprising the steps of: running a second application on the second client device; and replacing the second application running on the second client device with the updated application.
  3. The method of claim 1, further comprising instructing the backend server to generate the updated application from the selected update command.
  4. The method of claim 1, further comprising the steps of: sending the selected update command via a Short Message Service (SMS) communication mechanism; and/or translating the selected update command to a corresponding update to be added to the updated application.
  5. The method of claim 1, wherein the first application is a General Third Party Application; and/or wherein the first client device is a Manager Client Device and the second client device is a Customer Client Device.
  6. A method of using a backend server to and a dictionary to generate an updated application, the method comprising: downloading a dictionary of update commands from the backend server to a first client device; receiving, by the backend server, an update command selected by a user from the dictionary of update commands from the first client device; using a decoder and the selected update command on the backend server to generate an updated data model replacing an existing data model; and using the updated data model to generate the updated application.
  7. The method of claim 6, further comprising the steps of: running a second client device with an application; downloading the updated application from the backend server to the second client device; and replacing the application running on the second client device with the updated application.
  8. The method of claim 7, wherein the updated application is generated using the backend server.
  9. The method of claim 6, further comprising the steps of: sending the selected update command via a Short Message Service (SMS) communication mechanism.
  10. The method of claim 6, further comprising the steps of decoding a value using the decoder selected from the group consisting of SMS, email, Application, chat, messenger and Voice-to-Text dependent decoders; and/or translating the selected update command into the updated data model by using the dictionary selected from the group consisting of SMS, email, Application, chat, messenger and Voice-to-Text command dictionaries.
  11. The method of claim 6, further comprising the steps of: using the backend server to generate a Dynamically Updated (DU) Data Model to execute a desired Update Command to generate the updated application selected from the group consisting of DU Native Mobile Application Clients (AP), DU Native Non-Mobile AP, DU Non-Native Mobile AP, DU Non-Mobile AP, DU Cloud AP, and DU Application Components.
  12. An apparatus of a backend server comprising: a first client device configured to run a first application; the backend server configured to download a dictionary comprising a plurality of update commands to the first client device, the first client device further configured to present the plurality of update commands to a user, wherein the user selects an update command from the plurality of update commands; the first client device further configured to upload a selected update command to the backend server; and the backend server configured to generate an updated application based on the selected update command.
  13. The apparatus of claim 12, further comprising: a second application configured to run on a second client device, wherein the second application running on the second client device is replaced with s the updated application; and/or wherein a second client device is configured to receive the updated application from the backend server.
  14. The apparatus of claim 12, further comprising: a communication mechanism configured to send the selected update command, wherein the communication mechanism is selected from the group consisting of Short Message Service (SMS), email, Application Dependent Messaging, chat, messenger and Voice-to-Text.
  15. The apparatus of claim 14, further comprising: a corresponding update translated from the selected update command by the backend server and added to the updated application; and/or wherein the first application is a General Third Party Application.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS The U.S. applications Ser. No. 13/833,589 entitled "Apparatus for Single Workflow for Multi-Platform Mobile Application Creation and Delivery" , Ser. No. 13/833,669 entitled "Method for Single Workflow for Multi-Platform Mobile Application Creation and Delivery", and Ser. No. 13/833,775 entitled "Dynamic User Interface Delivery System", all filed on March 15, 2013, which are assigned to the same assignee as the present application and invented by the same inventors as the present application are incorporated herein by reference in its entirety. BACKGROUND OF THE INVENTION The internet is a communication system that interconnects the world. The internet has been structured to provide connectivity to billions of users with laptops, notebooks, desktops, Internet Enabled TV sets, cellular phones, smartphones like the IPHONE™, ANDROID™ and BLACKBERRY™, wearable devices, and tablets. The internet 1-3 connects a Client Device 1-2 to a server 1-4 and the server to the same Client Device as illustrated in 1-1 of FIG. 1A or to another Client Device (not illustrated). The Client Device 1-2 can have at least one display screen 1-8 that can be a touch sensitive screen, pen based or both. The screen can display various icons or be attached to a physical keypad 1-9. As illustrated in 1-1, the Client Devices are physical and can be either mobile, such as cellular phones, smartphones, wearable devices, and tablets, or non-mobile, such as laptops, desktops, and TV sets, The Client Devices 1-2 are coupled to the internet by wired (a physical interconnect), wirelessly (waves through space), or both wired /wireless networks. The wireless connectivity can be cellular (3G, 4G, etc.), Wi-Fi, Bluetooth, WiMax, etc. The Client Device 1-2 runs the Application Client which is the actual application software running on device. FIG. 1A also shows an Application Store 1-10 connected to the Internet. The Application Store 1-10 makes application clients available for download to the Client Devices. There is a plurality of Application Stores, each of the Application Stores dedicated to make available for download Application Clients for a certain type of Client Device or Client Device Operating System. For example, the APPLE™ Application Store makes Application Clients for the IPHONE™ and IPAD™ available for download, the ANDROID™ Application Store makes Application Clients for smartphones and tablets running the ANDROID™ Operating System available for download, etc. There are Application Stores dedicated to support mobile Client Devices (for example, the IPHONE™/IPAD™ APPLE™ Application Store, the BLACKBERRY™ Application Store, etc.), and Application Stores dedicated to support non-mobile Client Devices (for example, the MAC™ APPLE™ Application Store, which makes applications for APPLE™ computers running the MAC™ Operating System available for download). The Cloud uses the network of the internet to offer services to users by using a combination of hardware and software embedded in the network. For example, ADOBE™ and MICROSOFT™ offer the ability of using their software programs via the Cloud, while other companies offer storage capabilities via the Cloud to their customers. An Application Client can be in the Cloud, but in this case the Client Device is a "virtual" Client Device. The "virtual" Client Device has a way to provide access to the Application Client running in the cloud via a physical Client Device. For example, as in the example listed in 1-5 of FIG. 1B,a web browser 1-6 running on the physical Client Device 1-2 and coupled to the client/server 1-7 in the Cloud via the Internet accesses the Application Client running in the Cloud, which performs the actual application software. For the Cloud, there are two cases: the entire Application Client runs in the Cloud, or a small portion of the Application Client runs on a physical Client Device while most of the logic runs in the Cloud. FIG. 2Aillustrates a system 2-1 with the hardware 2-16 and software 2-15 of a Client Device 1-2. The Client Device 1-2 is coupled to the Internet 1-3 via wireline connection or Radio Frequency (RF) wireless transmission network (wired/wireless) 2-2 and further coupled to a bank of servers 2-4 via a second interconnection 2-3 that can be wired or wireless. The communication link is a receiver and a transmitter known as a transceiver and is coupled to either a wired connector or an antenna (not illustrated) for the wireline connection or RF wireless transmission network, respectively. In general, these links: wired, wireless, cellular, internet, etc. are called the Communication network. The Communication network couples all components together. The server's bank 2-4 comprises server-0 2-11 to server-N 2-12. The bank contains at least one server and these servers can be localized, coupled by an Intranet, or be physically separated from one another, coupled by the Internet. The Operating System (OS) 2-13 running in