WO2013093651A1 - A system and method for developing and running mobile applications - Google Patents

Abstract

The present invention relates to a system (1) and method (100) which enables to develop mobile applications independently of development platform, run applications developed on different mobile devices (2) and operating systems without the need for amendment, and update applications on server (3). The said system (1) comprises mobile device (2), application unit (21), connection unit (22), parsing unit (23), operating unit (24), interface (25), server (3) and database (4)·

Description

A SYSTEM AND METHOD FOR DEVELOPING AND RUNNING

MOBILE APPLICATIONS

Technical Field

The present invention relates to a system and method which enables to develop mobile applications independently of development platform, run applications developed on different mobile devices and operating systems without the need for amendment, and update applications on server.

Background of the Invention

Today, widespread use of mobile device has significantly increased the number of service that can be provided to subscribers using features of mobile devices. Mobile devices have become devices wherein that kind of services can be used easily because of transport and communication facilities. The said services can be provided to the user generally by means of mobile applications which are installed and run on mobile devices. Upon mobile devices with advanced features which are also known as smart phone becoming widespread, it is started to develop mobile applications that are available in many kinds and serve many purposes, for mobile devices by application developers.

Mobile applications are prepared in different languages and different development environments for different platforms today. This leads to requirement that each application developer needs to learn different development languages for different platforms and develop the mobile application desired to be developed in these languages. At the same time, lack of a general language and development environment independent of platform for mobile applications stands out when it is taken into account that development platforms of applications which can be written in different languages may be different sometimes as well. Some platforms and development languages existing in the present condition are as follows:

It is necessary to develop application in Objective C language for Apple iOS operating system. Objective C can be developed on MacOS platform. It is necessary to develop application in J2ME (Java 2 Platform, Micro Edition) language for Android operating system.

It is necessary to develop application in C# language for Windows Phone operating system. C# is developed on environments such as .NET Framework.

In the state of the art, it is necessary to make development in same language and environment for updating, versioning and maintenance operations of applications to be used in this kind of platforms.

In addition, updating operation needs to be carried out by downloading new version of the said application to the mobile device by the user. When file sizes of applications are considered, this operation takes a long time, may be cut-off at times and leads to decrease in data-packet quota used by the user.

In the state of the art, there is no system and method which enables to develop mobile application independently of platform and makes it possible to use these mobile applications without the need for any change in different mobile devices and operating systems and besides ensures that user action is not required by carrying out mobile application operations such as updating, maintenance by the server.

The United States patent document no. US2005197157, an application in the state of the art, discloses a system operating on small mobile devices such as smart phones and using a description language, like sign language, that is used in thin- clients working like a fat-client.

The United States patent document no. US2006063518, an application in the state of the art, discloses a system and method for developing applications which are independent of device for mobile devices having different operating systems.

Summary of the Invention An objective of the present invention is to realize a system and method which enables to develop application without having to develop software in different platforms and languages for different devices and operating systems during development of mobile application. Another objective of the present invention is to realize a system and method which ensures that mobile applications are run by being received from database through server and thus, operations such as updating, maintenance concerning the application on the mobile device are not necessary anymore. Description of the Invention

"A System and Method for Developing and Running Mobile Applications" realized to fulfill the objectives of the present invention is shown in the figures attached, in which:

Figure 1 is a schematic block diagram of the inventive system.

Figure 2 is a flowchart of the inventive method.

The components illustrated in the figures are individually numbered, where the numbers refer to the following: System

Mobile device

21. Application unit

22. Connecting unit

23. Parsing unit

24. Operating unit

25. Interface

Server

Database

Method

Application developers

User

A system (1) which enables to develop and run mobile applications comprises:

at least one mobile device (2) on which mobile applications are run; at least one application unit (21) which is included in the mobile device (2) and where mobile applications run on the mobile device (2) are kept;

at least one connecting unit (22) which is included in the application unit (21) and enables application files to be put in the application unit

(21);

at least one parsing unit (23) which is included in the application unit (21) and enables to parse application files;

at least one operating unit (24) which is included in the application unit (21), enables to run application files and gets in contact with the connecting unit (22) according to selections and inputs of the user (K); at least one interface (25) which displays application properties, results and design to the user (K) and can receive inputs related to application selection or operation from the user (K); at least one server (3) which enables to carry out operations relating to files of applications developed by the application developers (A); at least one database (4) where files of applications developed by the application developers (A) are kept (Figure 1).

In a preferred embodiment of the invention, the mobile device (2) is a mobile phone on which mobile applications can be run.

The application unit (21) is a unit located on the mobile device (2) and where applications run on the mobile device (2) are kept.

The connecting unit (22) is a unit which is included in the application unit (21) and enables to receive application files from the server (3) and to transfer the application files to the parsing unit (23) according to inputs received from the user (K) by means of the interface (25).

The parsing unit (23) is a unit which is included in the application unit (21) and enables to parse parts of application files, transferred by the connecting unit (22) and in the form of text, and transfer the application files parts of which are parsed to the operating unit (24). The parsing unit (23) is a unit which is developed and coded individually for each mobile device (2) and operating system on the mobile device (2) and its main task is to parse parts of application files which are received to the application unit (21) from the server (3) and to transfer these parts to the operating unit (24). In a preferred embodiment of the invention, the parsing unit (23) is a XML (Extensible Markup Language) parser.

The operating unit (24) is a unit which is included in the application unit (21) and enables to run parts of application files parsed by the parsing unit (23) and display results on the interface (25). The operating unit (24) is a unit which is developed and coded individually for each mobile device (2) and operating system on the mobile device (2) and its main task is to enable the files received to the application unit (21) from the server (3) to run and get in contact with the connecting unit (22) with respect to application files to be received from the server (3) and external network (web) services to be accessed, according to selections and inputs of the user (K). In a preferred embodiment of the invention, the operating unit (24) is a unit which can be operate the files thereof written in XML language together with formatting tags on the files..

The interface (25) is a unit which is included in the application unit (21) and after operations of the operating unit (24), displays results such as application type, properties, inputs and design to the user (K) and can receive inputs related to selection or operation of application from the user (K).

The server (3) performs tasks of: saving applications, which are developed by the application developers (A), to the database (4); carrying out operations necessary for the files to be transferred to the application unit (21) by the connecting unit (22) after being received from the database (4); and accessing various external network services in case of necessity. The database (4) is a unit where files of applications developed by the application developers (A) are kept.

A method (100) which enables to develop and run mobile applications comprises steps of:

- the application developers (A) transferring files with text format, which belong to mobile applications developed by them, to the database (4) by means of the server (3) (101);

- the user (K) installing the operating unit (24) and the parsing unit (23) to the application unit (21 ) ( 102); the user (K) making selection of mobile application using the interface (25) (103);

transmitting the user (K) inputs to the server (3) by means of the connecting unit (22) (104);

receiving the files related to the mobile application from the database (4) by means of the connecting unit (22) and the server (3) (105);

parsing the application files received in the parsing unit (23) (106); running each part of the application file in the operating unit (24) (107);

showing results of application files run to the user (K) on the interface (25) (108);

controlling whether the user (K) carried out a new operation on the application run (109);

if the user (K) made a new operation on the application run, transmitting the user (K) inputs to the server (3) by means of the connecting unit (22) (104) (in other words, returning the step 104); if the user (K) did not make a new operation on the application run, ending the operation (110) (Figure 2). The operating unit (24) provided in the inventive system (1) is adapted to perform operations of: running the parsed parts of the application file by the parsing unit (23); displaying the results, which are obtained as a result of the parts run, on the interface (25);

getting in contact with the connecting unit (22) with respect to application files to be received from the server (3) and external network (web) services to be accessed, according to selections and inputs of the user (K). In the inventive method (100), the application developers (A) transfer the files with text format, which belong to the mobile applications developed by them, to the database (4) by means of the server (3) (101) at first. The applications which are developed by the application developers (A) are in the form of a web service whereas, the files with text format may be prepared in one of languages such as XML, XAML (Extensible Application Markup Language). In order to run these files prepared by the application developers (A), the user (K) installs the operating unit (24) and the parsing unit (23) to the application unit (21) (102) and then, makes selection of mobile application using the interface (25) (103). In an embodiment of the invention, this selection takes place such that the applications are selected by making selection of application directly from the list that is present on the interface (25) as embedded and arrived at their locations in the database (4) whereas in another embodiment of the invention, it takes place such that a page where list of the applications in the database (4) exists is reached over the interface (25) and selection is made in this page. The application list used in this case is also kept in the database (4) and the interface (25) serves as an input port to access the mobile application list. After the user (K) makes selection, the user (K) transmits the inputs to the server (3) by means of the connecting unit (22) (104). In an embodiment of the invention, the user (K) inputs are mobile application selection of the user (K)whereas in another embodiment of the invention, the user (K) inputs may consist of information that will be needed before starting the mobile application together with selection of the mobile application. Then, within the method (100), operation of receiving the files related to the mobile application from the database (4) by means of the connecting unit (22) and the server (3) is carried out (105). The application files received in the parsing unit (23) are parsed (106). These parts are found in the way that various functional and formatting tags on the file with text format are determined. Then, each of these parts is run in the operating unit (24) (107) and results of the application files run are displayed to the user (K) on the interface (25) (108). The results displayed to the user (K) are various functional and formatting features of the mobile application. Functional features express the content on the mobile application, outputs which are obtained by the user (K) inputs, sections which enable the user (K) to carry out a new operation and input information that may be required in new operations. Whereas formatting features express representation forms of the images and the existing content on the mobile application to the user.

After the results of the application files are displayed to the user (K) on the interface (25), it is controlled whether the user (K) carried out a new operation on the application run (109). And this operation can be carried out in the way that the user (K) uses one or more of the functional features displayed to him/her on the interface (25). If the user (K) made a new operation on the application run, the user (K) inputs are transmitted to the server (3) by means of the connecting unit (22) (104). In other words, it is returned to the step 104 and the method (100) steps are continued from the step 104. But the operation is ended if the user (K) did not make a new operation on the application run (110).

As an example of the inventive system (1) and method (100), a weather forecast mobile application can be considered. When the user (K) wants to use a weather forecast mobile application, s/he first installs the parsing unit (23) and the operating unit (24) to the application unit (21) in his/her mobile device (2) and reaches the interface (25). Then, s/he directly selects the weather forecast mobile application over the interface (25) or accesses the list of mobile application over the interface (25) and selects the weather forecast mobile application from there. In this case, the application unit (21) reaches the files of weather forecast mobile application which were put in the database (4) upon being prepared by the application developers (A) previously, by reaching the database (4) by means of the server (3). These files are preferably XML or XAML files. These files are received by the application unit (21) and transferred to the parsing unit (23). Here, by parsing the XML file, it is determined which part composes selection of location weather condition of which will be learned and selection of heat unit (such as centigrade degree or Fahrenheit degree) and which part brings visuality (logo of the company providing weather service etc.) to the application in the file. These parts are processed in the operating unit (24) by means of an operation such as XML render or process such that they will express meaningful information and visuality for the user (K) and representation of visual elements is enabled on the interface (25) via the weather location selection menu. The user (K) makes selections of location, etc. from the application provided to him/her on the interface (25) and this time, the connecting unit (22) reaches the server (3) and the database (4) via these inputs. Again, as a result of operations of the parsing unit (23) and the operating unit (24), the user (K) sees weather information and various visual elements of the location selected by him/her. In any case, many options, information and visuality can be provided to the user on screens formed on the interface (25) with the XML files being processed. When it is desired to make change in presentation of these options, information and visuality; only changes to be made on the database (4) will be sufficient for amendments to be made about operation and visuality of the mobile application without the need for change within the application unit (21) on the mobile device (2) of the user (K).

In the inventive system (1) and method (100), operation of developing application without having to develop software in different platforms and languages for different mobile devices (2) and operating systems during development of mobile application is realized. When the said operation is carried out, advantage of the parsing unit (23) and the operating unit (24) which are provided in the application unit (21) within the mobile device (2) that they can provide application files with text format received from the server (3) to the user (K) as meaningful images. Thus, it is ensured that it is enough for application developers (A) to prepare only file with text format such that it can be used in any mobile device (2) via the parsing unit (23) and the operating unit (24) without having to prepare application in different programming languages for each mobile device (2) and operating system.

In the inventive system (1) and method (100), it is realized that mobile applications are run by being received from the database (4) by means of the server (3) and thus, operations such as updating, maintenance related to the application on the mobile device (2) are not necessary anymore. When the said operations are carried out, files with text format related to the mobile application which is selected by the user (K) are received from the database (4) by means of the connecting unit (22) and the server (3) and it is enabled that results are displayed on the interface (25) by running these files by means of the parsing unit (23) and the operating unit (24). In this case, adjustments and updates to be made in regard to mobile applications are directly carried out on files only on the database (4); it is ensured that the user (K) does not need to carry out any download operation to the mobile device (2) regarding the adjustments and updates on the mobile applications.

It is possible to develop various embodiments of the inventive "system (1) and method (100)", it cannot be limited to examples disclosed herein and it is essentially according to claims.

Claims

A method (100) enabling to develop and run mobile applications characterized in that

- the application developers (A) transferring files with text format, which belong to the mobile applications developed by them, to the database (4) by means of the server (3) (101);

- the user (K) installing the operating unit (24) and the parsing unit (23) to the application unit (21) (102);

- the user (K) making selection of mobile application using the interface (25) (103);

- transmitting the user (K) inputs to the server (3) by means of the connecting unit (22) (104);

- receiving the files related to the mobile application from the database (4) by means of the connecting unit (22) and the server (3) (105);

- parsing the application files received in the parsing unit (23) (106);

- running each part of the application file in the operating unit (24) (107);

- showing results of the application files run to the user (K) on the interface (25) (108);

- controlling whether the user (K) carried out a new operation on the application run (109);

- if the user (K) made a new operation on the application run, transmitting the user (K) inputs to the server (3) by means of the connecting unit (22) (104),

- if the user (K) did not make a new operation on the application run, ending the operation (110).

2. A method (100) according to Claim 1 , characterized in that applications which are developed by application developers (A) are in the form of a web service.

3. A method (100) according to Claim 1 or 2, characterized in that files with text format belonging to applications, which are developed by application developers (A), are prepared in XML language.

4. A method (100) according to Claim 1 or 2, characterized in that files with text format belonging to applications, which are developed by application developers (A), are prepared in XAML language.

5. A method (100) according to any of the preceding claims, characterized in that at the step of the user (K) making selection of mobile application using the interface (25) (103); selection of mobile application is made such that the applications are selected by making selection of application directly from the list that is present on the interface (25) as embedded and arrived at their locations in the database (4).

6. A method (100) according to Claim 1 to 5, characterized in that at the step of the user (K) making selection of mobile application using the interface (25) (103); selection of mobile application is made such that a page where list of the applications in the database (4) exists is reached over the interface (25) and selection is made in this page.

7. A method (100) according to any of the preceding claims, characterized in that at the step of transmitting the user (K) inputs to the server (3) by means of the connecting unit (22) (104); user (K) input expresses mobile application selection of the user (K).

8. A method (100) according to any of the preceding claims, characterized in that at the step of transmitting the user (K) inputs to the server (3) by means of the connecting unit (22) (104); user (K) inputs consist of information which will be needed before initiation of the mobile application.

9. A method (100) according to any of the preceding claims, characterized in that at the step of parsing the application files received in the parsing unit (23) (106); parts are obtained such that various functional and formatting tags on the file with text format are parsed.

10. A method (100) according to any of the preceding claims, characterized in that at the step of showing results of application files run to the user (K) on the interface (25) (108); results displayed to the user (K) are functional and formatting features of the mobile application.

11. A method (100) according to any of the preceding claims, characterized in that at the step of showing results of application files run to the user (K) on the interface (25) (108); functional features shown to the user (K) express the content on the mobile application, outputs which are obtained by the user (K) inputs, sections which enable the user (K) to make a new operation and input information that may be required in new operations.

12. A method (100) according to any of the preceding claims, characterized in that at the step of showing results of application files run to the user (K) on the interface (25) (108); formatting features displayed to the user (K) express representation forms of the images and the existing content on the mobile application to the user.

13. A method (100) according to any of the preceding claims, characterized in that at the step of controlling whether the user (K) carried out a new operation on the application run (109); operation, which is controlled whether to be carried out, can be carried out in the way that the user (K) uses one or more of the functional features displayed to him/her on the interface (25).

14. A system (1) enabling to develop and run mobile applications comprising at least one mobile device (2) on which mobile applications run;

at least one application unit (21) which is included in mobile device (2) and where mobile applications run on the mobile device (2) are kept; - at least one connecting unit (22) which is included in the application unit (21) and enables application files to be put in the application unit

(21);

at least one parsing unit (23) which is included in the application unit (21) and enables to parse parts of application files;

- at least one interface (25) which displays application properties, results and design to the user (K) and can receive inputs related to selection or operation of the application from the user (K);

at least one server (3) which enables to carry out operations related to files of applications developed by the application developers (A); - at least one database (4) where files of applications developed by the application developers (A) are kept;

and characterized by

at least one operating unit (24) which is included in the application unit (21), enables to run application files and gets in contact with the connecting unit (22) according to selections and inputs of the user (K).

15. A system (1) according to Claim 1, characterized by mobile device (2) which is a mobile phone on which mobile applications can run.

16. A system (1) according to any of Claim 14 or 15, characterized by parsing unit (23) which is a XML parser.

17. A system (1) according to any of Claim 14 or 15, characterized by parsing unit (23) which is a XAML parser.

18. A system (1) according to any of Claim 14 to 17, characterized by an operating unit (24) which is adapted to perform operations of:

- running parts of application file parsed by the parsing unit (23);

- displaying the results, which are obtained as a result of the parts run, on the interface (25);

- getting in contact with the connecting unit (22) with respect to application files to be received from the server (3) and external network (web) services to be accessed, according to selections and inputs of the user (K).