IP Library › Granted Patent US 8,819,698
Granted Patent B2
US 8,819,698 · App. 13/437,703 · Granted Aug 26, 2014

Cross-platform web-based native device feature access

Inventors: Thomas E. Sandholm (Sunnyvale, CA); Francois-Xavier Kowalski (Lumbin, FR); David Penkler (Claix, FR)
Assignee: Hewlett-Packard Development Company, L. P.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,819,698
App. No.
13/437,703
Filed
Apr 2, 2012
Granted
Aug 26, 2014
Kind
B2
Art Unit
2194
USPC
719/310
Abstract

A method for cross-platform web-based native device feature access may include receiving a call from a web application to access a native device feature, with the call being redirected to a platform agnostic custom URL. The method may further include translating the custom URL into a native object call, and accessing the native device feature based on the native object call.

Claims (38)

1. A method for cross-platform web-based native device feature access, the method comprising:

receiving a call from a web application to access a native device feature, the call being redirected to a platform agnostic custom uniform resource locator (URL), wherein programming instructions, including code for the web application and code for a library for redirecting the call to the custom URL, are identical across different device platforms, and the library is used to generate the custom URL by serializing a JavaScript object to a JavaScript Object Notation (JSON) string that is encoded in the custom URL;

translating the custom URL into a native object call; and

accessing, by a processor, the native device feature based on the native object call.

2. The method of claim 1 , further comprising:

sending results from the accessing of the native device feature to a bridge server to provide a platform independent format of communicating back to the web application; and

forwarding the results from the bridge server to the web application.

3. The method of claim 2 , further comprising:

forwarding the results from the bridge server to the web application via a messaging bus built on bi-directional web communication technology.

4. The method of claim 1 , wherein the native device feature includes one of retrieval of device information, vibration of a device, selection of a photo from a photo gallery, uploading of a photo from the photo gallery, capturing of a photo from a device camera, and uploading of a photo from the device camera.

5. The method of claim 1 , further comprising:

including an action to be performed by the web application in the custom URL.

6. The method of claim 5 , wherein the action includes execution of the native device feature.

7. The method of claim 1 , wherein the web application includes a JavaScript based application programming interface (API), the method further comprising:

updating JavaScript API code online to update the web application.

8. The method of claim 1 , wherein the library is a JavaScript library.

9. The method of claim 1 , further comprising:

accessing code to translate the custom URL into the native object call; and

accessing the native device feature by accessing code to execute the native device feature,

wherein the code to translate the custom URL and the code to execute the native device feature is specific to a device platform.

10. The method of claim 1 , further comprising:

updating the web application to automatically implement the update on a plurality of devices including the different device platforms.

11. The method of claim 1 , further comprising:

permitting any web application that has proper authorization to be executed on a device including the native device feature, without an application store pre-approval process.

12. A system for web-based native device feature access, the system comprising:

a memory storing a module comprising machine readable instructions to:

receive a call from a web application to access a native device feature;

access code for a library to redirect the call to a platform agnostic custom uniform resource locator (URL), wherein programming instructions, including code for the web application and the code for the library, are identical across different device platforms, and the library is used to generate the custom URL by serializing a JavaScript object to a JavaScript Object Notation (JSON) string that is encoded in the custom URL;

access code to translate the custom URL into a native object call, the code to translate being specific to a device platform; and

access code to execute the native device feature based on the native object call, the code to execute being specific to the device platform; and

a processor to implement the module.

13. The system of claim 12 , wherein the native device feature includes one of retrieval of device information, vibration of a device, selection of a photo from a photo gallery, uploading of a photo from the photo gallery, capturing of a photo from a device camera, and uploading of a photo from the device camera.

14. The system of claim 12 , wherein the custom URL includes an action to be performed by the web application.

15. A non-transitory computer readable medium having stored thereon a computer executable program for web-based native device feature access, the computer executable program when executed causes a computer system to:

receive a call from a web application to access a native device feature;

redirect the call to a platform agnostic custom uniform resource locator (URL), wherein programming instructions, including code for the web application and code for a library for redirecting the call to the custom URL, are identical across different device platforms, and the library is used to generate the custom URL by serializing a JavaScript object to a JavaScript Object Notation (JSON) string that is encoded in the custom URL;

translate, by a processor, the custom URL into a native object call; and

access code to execute the native device feature based on the native object call, the code to execute being specific to a device platform.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 9, 2015
From: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 037079/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 4, 2012
From: SANDHOLM, THOMAS E.; KOWALSKI, FRANCOIS-XAVIER; PENKLER, DAVID
To: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
Reel/Frame 027987/0329 →
Continuity (1)
Related Publication 20130263160A1 · Oct 3, 2013