Method and system for platform-independent application development

• US 9,069,375 B2
• Filed: 04/30/2013
• Issued: 06/30/2015
• Est. Priority Date: 04/30/2013
• Status: Active Grant

• Current Assignee: JYBE Technology LLC
• Original Assignee: Mobiledataforce, Inc.
• Inventors: Padmavilasom, Priyesh
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Wang, Ben C
• Application Number:
  US13/874,305
• Publication Number:
  US 20140325470A1
• Time in Patent Office: 791 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/00 Arrangements for software engineering testing or debugging G06F11/36; administrative, planning or organisation aspects of software project management G06Q10/06
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 8/76 Adapting program code to run in a different environment; Porting
• CPC Class Codes: G06F 9/45508 Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation
• CPC Class Codes: G06F 9/45512 Command shells
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

A non-transitory computer-readable medium having instructions that when executed cause the implementation of a method is disclosed herein. The medium has instructions for facilitating the execution of at least a first hybrid application on a first device, the first hybrid application comprising commands related to platform-specific functionality and platform-independent functionality of the first device. The method includes initializing a loosely-coupled native engine configured to receive commands from the first hybrid application and to facilitate platform-specific functionality on the first device. The loosely-coupled native engine comprises a webserver module. The method includes receiving commands from the first hybrid application, wherein at least one of the commands comprises a device command to be converted to a corresponding platform-specific code prior to execution of the platform-specific code. And the method includes creating a handler to serve the device command and facilitate execution of the corresponding platform-specific code.

Claims

1. A method of executing a hybrid application on a device, the hybrid application comprising commands related to platform-specific functionality and platform-independent functionality of the device, the method comprising:

initializing a loosely-coupled native engine configured to receive commands from the hybrid application, and further configured to facilitate implementation of platform-specific functionality on the device, and wherein the loosely-coupled native engine comprises a hypertext transfer protocol (HTTP) server and initializing the loosely-coupled native engine comprises initializing the HTTP server;

assigning a unique instance identifier (ID) to the HTTP server, and configuring the HTTP server to only accept commands comprising the unique instance ID;

initializing the hybrid application;

receiving commands from the hybrid application, wherein the commands comprise the unique instance ID of the HTTP server, and further wherein at least one of the commands comprises a device command to be converted to a corresponding platform-specific executable code prior to execution of the platform-specific executable code;

verifying that the commands comprise the unique instance ID of the HTTP server; and

creating a handler to serve the device command and facilitate execution of the corresponding platform-specific executable code.

2. The method of claim 1 further comprising executing the corresponding platform-specific executable code on the device.

3. The method of claim 1 further comprising:

receiving an unauthorized command that does not comprise the unique instance ID of the HTTP server; and

rejecting the unauthorized command.

4. The method of claim 1 further comprising:

determining whether the initialization of the loosely-coupled native engine is a first ever initialization of the loosely-coupled native engine on the device; and

synchronizing application data upon a determination that the initialization of the loosely-coupled native engine is the first ever initialization, wherein application data comprises data related to at least one of the loosely-coupled native engine and the hybrid application.

5. The method of claim 1 further comprising:

determining whether additional hybrid applications are installed or otherwise associated with the device; and

displaying a list of the additional hybrid applications available on the device.

6. The method of claim 1 further comprising:

parsing the received commands;

detecting whether the received commands comprise JavaScript commands; and

sending detected JavaScript commands to the webserver module.

7. The method of claim 1 further comprising:

transmitting a communication to a synchronization server residing on a remote server; and

receiving synchronization data in response to the transmission.

8. The method of claim 1 further comprising:

verifying a license associated with the loosely-coupled native engine; and

granting access to the loosely-coupled native engine upon a determination that the license is valid.