METHOD FOR CONVERTING MOBILE WEB APPLICATION INTO NATIVE APPLICATION AND APPARATUS USING THE SAME

• US 20120159310A1
• Filed: 12/14/2011
• Published: 06/21/2012
• Est. Priority Date: 12/16/2010
• Status: Abandoned Application

• Current Assignee: Electronics and Telecommunications Research Institute
• Original Assignee: Electronics and Telecommunications Research Institute
• Inventors: CHANG, Yoon-Seop, Lee, Seong Ho, Kim, Jae Chul, Kim, Kyung Ok, Yoon, Chang Rak, Kim, Hak Cheol, Lee, Ki Jung, Shin, Sung Woong
• Application Number:
  US13/325,965
• Publication Number:
  US 20120159310A1
• Time in Patent Office: Days
• US Class Current: 715/239
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 8/40 Transformation of program code

Abstract

A method for converting a mobile web application into a native application (the term “app” has the same meaning as the native application) and an apparatus using the method are disclosed. The method for converting a mobile web application into a native application may include: the steps of receiving at least one of a web implementation document that implements the mobile web application and a uniform resource locator (URL) for a local file; separating and analyzing a user interface element of the mobile web application based on the at least one of the web implementation document and the local file; and converting the mobile web application into the native application by mapping the analyzed user interface element to a native control that implements the native application.

Claims

1. A method for converting a mobile web application into a native application, the method comprising:

receiving at least one of a web implementation document that implements the mobile web application and a uniform resource locator (URL) for a local file;

separating and analyzing a user interface element of the mobile web application based on the at least one of the web implementation document and the local file; and

converting the mobile web application into the native application by mapping the analyzed user interface element to a native control that implements the native application.

2. The method of claim 1, wherein the web implementation document is at least one of a hypertext markup language (HTML) and an extensible markup language (XML) document.

3. The method of claim 1, further comprising packaging the implemented native application and uploading the packaged native application to a server.

4. The method of claim 1, wherein the separating and analyzing the user interface element of the mobile web application based on the at least one of the web implementation document and the URL for the local file comprises:

analyzing the user interface element of the mobile web application with at least one of user interface information, style information, script information, and external object information.

5. The method of claim 1, wherein the separating and analyzing the user interface element of the mobile web application based on the at least one of the web implementation document and the URL for the local file comprises:

analyzing at least one of user interface information of a mobile web document that implements the mobile web application and a file including the user interface information that constitutes the mobile web application;

analyzing at least one of style information of the web implementation document that implements the mobile web application and a file including the style information that constitutes the mobile web application;

analyzing at least one of script information of the web implementation document that implements the mobile web application and a file including the script information that constitutes the mobile web application; and

analyzing at least one of external object information of the mobile web document that implements the mobile web application and a file including the external object information that constitutes the mobile web application.

6. The method of claim 1, wherein the converting the mobile web application into the native application by mapping the analyzed user interface element to a native control that implements the native application comprises:

disposing the user interface element in the native application by mapping the user interface element to the native control by referring to a mapping table for mapping the user interface element of the mobile web application to the native control of the native application;

applying the style information that implements the mobile web application to style attributes of the native control;

connecting the script information that implements the mobile web application to attribute information of the native control; and

disposing the external object information in the native application by connecting the external object information that implements the mobile web application to the native control.

7. The method of claim 1, further comprising

converting the mobile web application into the native application by correcting native control information of the mapped native application and additionally mapping information of the native application, which is not mapped to the native control, to the native application.

8. The method of claim 7, wherein the converting the mobile web application into the native application by correcting the native control information of the mapped native application and additionally mapping the information of the native application, which is not mapped to the native control, to the native application comprises:

moving the native control or changing at least one of size information and attribute information of the native control;

additionally applying style information, which is not applied to the native control, to the native control;

changing and storing a source code of the script information; and

implementing the native application by changing the link and parameter of the external object disposed in the native control and deleting external object information which is not mapped to the native control or replacing the external object information with another external object.

9. An apparatus of converting a mobile web application into a native application, the apparatus comprising:

a web application reader for receiving at least one of a web implementation document that implements the mobile web application and a uniform resource locator (URL) for a local file;

a web application analyzer for analyzing a user interface element of the mobile web application based on the at least one of the web implementation document and the local file provided by the web application reader; and

a native control mapping module for mapping the user interface element analyzed by the web application analyzer to a native control that implements the native application.

10. The apparatus of claim 9, wherein the web implementation document is at least one of a hypertext markup language (HTML) and an extensible markup language (XML) document.

11. The apparatus of claim 9, wherein the web application analyzer comprises:

a user interface analysis module for analyzing at least one of the user interface element that implements the mobile web application and a file including the user interface information that constitutes the mobile web application;

a style analysis module for analyzing at least one of style information of the web implementation document that implements the mobile web application and a file including the style information that constitutes the mobile web application;

a script analysis module for analyzing at least one of script information of the web implementation document that implements the mobile web application and a file including the script information that constitutes the mobile web application; and

an external object analysis module for analyzing at least one of external object information of the mobile web document that implements the mobile web application and a file including the external object information that constitutes the mobile web application.

12. The apparatus of claim 9, further comprising an app author for implementing the native application by correcting native control information of the mapped native application and additionally mapping information of the native application, which is not mapped to the native control, to the native application.

13. The apparatus of claim 12, further comprising:

an app packaging module for packaging the native application implemented by the app author to be uploaded to a server; and

an app upload module for uploading the native application packaged by the app packaging module to the server.

14. The apparatus of claim 13, further comprising an app market for distributing the native application uploaded from the app upload module to the server.