JP6843007B2 - Application generation support system - Google Patents

Description

The present invention relates to an application generation support system and an application generation support program.

Various applications have been developed as applications for mobile communication terminals. Mobile communication terminal applications are classified into Web applications, native applications, and hybrid applications. A Web application is a type of application that executes arithmetic processing on a server on a network. A native application is a type of application that executes arithmetic processing only on a communication terminal. A native application is an application having a feature that native functions unique to a communication terminal such as a camera, GPS, a microphone, and an acceleration sensor can be used. The hybrid application is an application having a feature that native functions can be used, an application corresponding to multiple platforms can be created, and Web View that uses the application like a web browser can be used.

As described above, the hybrid application has become the mainstream of the communication terminal application because it has the advantages of the Web application and the native application. For example, a hybrid application is widely used as an application used for a communication terminal for business use. In order to create a hybrid application for business use, it is necessary to develop an application suitable for the business purpose in each business organization.

Here, in order to develop an application, a dedicated terminal suitable for the OS of the communication terminal on which the application is installed is prepared, an application development tool suitable for the OS is introduced, and the programming language in the application development tool is used. You need to develop an application. As described above, in order to develop an application, it is necessary to prepare an application development environment such as preparing a dedicated terminal and introducing an application development tool, and to make various initial investments such as acquiring skills such as a programming language.

In order to reduce the burden of acquiring programming language skills, technologies have been developed to support program development. For example, in order to further simplify the program development, a program development device as in Patent Document 1 has been proposed.

Japanese Patent No. 6064889

However, in order to create an application that operates on a communication terminal and operates or displays a screen according to the operation of the communication terminal, a programming technique far more advanced than the technique described in Patent Document 1 is required. Furthermore, since it is necessary to incorporate various functions into the application according to the purpose of the application, the application developer is burdened with a large cost and time for developing the application running on the communication terminal as described above. It takes.

In view of the above circumstances, an object of the present invention is to provide an application generation support system and an application generation support program that can reduce the development burden on the application developer.

The application generation support system according to the embodiment of the present invention generates a setting unit that sets a setting file that defines the operation of the application according to parameters related to the operation of the communication terminal, and an application package based on the setting file. It has a generation unit and a generation unit.

It may further have a receiving unit that receives the parameters set by the first user via the network.

The setting unit may set the setting file according to the parameter received by the receiving unit.

It may further have a providing unit that provides the download information of the application package to the second user.

The setting file is related to the parameter and defines the operation of the application common to the operations of the plurality of communication terminals, and the operation of the application related to the parameter and input by the first user. It may include at least one of the specified application configuration files.

The OS setting file may be a file in which a part of the template prepared in advance in the application development support tool is replaced with the parameters related to the OS setting file.

The application setting file may be a file in which the information input by the first user is overwritten on the template prepared in advance in the application development support tool.

The application setting file may be a file in which the information input by the first user is overwritten on the template created by the third user and uploaded to the application development support tool.

A parameter check unit for checking the parameters related to the application setting file set by the first user may be further provided before the setting by the setting unit.

The application setting file includes the initial URL of the page displayed on the communication terminal of the second user when the application installed on the communication terminal of the second user is started based on the application package. The parameter check unit may check the format of the initial URL and notify the first user of an error message when the initial URL is not in the specified format.

The providing unit generates a download page in which the application package generated by the generating unit is registered, and provides the second user with the download information including the information of the download page via the application development support tool. You may.

The setting file may include a plug-in file that causes the communication terminal to execute a native function specific to the communication terminal.

The plug-in file may be a file in which the information input by the first user is updated with respect to the template created by the third user and uploaded to the application development support tool.

It further has an electronic certificate management unit that manages an electronic certificate that identifies the application package, and the electronic certificate may be added to the application package by the electronic certification management unit.

In the application generation support system according to the embodiment of the present invention, an association unit that associates a plurality of templates that define the operation of the communication terminal and each of the operations defined by the plurality of templates are realized on the application of the communication terminal. It has an update unit that updates a part of the template so as to be possible.

The update unit may include at least one of replacing a part of the template with a parameter set by the user or overwriting a part of the template with information input by the user. ..

The association unit associates a plug-in file that causes the communication terminal to execute a native function peculiar to the communication terminal with the plurality of templates, and the update unit operates the operation of the communication terminal defined by the plug-in file. A part of the plug-in file may be updated so as to be feasible on the communication terminal.

The application generation support program according to the embodiment of the present invention sets a setting file that defines the operation of the application according to the parameters related to the operation of the communication terminal, and generates an application package based on the setting file. Let the computer do it.

It may further include receiving the parameters set by the first user over the network.

The configuration file may be set according to the parameters received via the network.

It may further include providing the download information of the application package to the second user.

The setting file is related to the parameter and defines the operation of the application common to the operations of the plurality of communication terminals, and the operation of the application related to the parameter and input by the first user. It may include at least one of the specified application configuration files.

The OS setting file may be a file in which a part of the template prepared in advance in the application development support tool is replaced with the parameters related to the OS setting file.

The application setting file may be a file in which the information input by the first user is overwritten on the template prepared in advance in the application development support tool.

The application setting file may be a file in which the information input by the first user is overwritten on the template created by the third user and uploaded to the application development support tool.

Prior to setting the configuration file, the parameters associated with the application configuration file set by the first user may be checked.

The application setting file includes the initial URL of the page displayed on the communication terminal of the second user when the application installed on the communication terminal of the second user is started based on the application package. The parameter check may check the format of the initial URL and notify the first user of an error message when the initial URL is not in the specified format.

The generated download page in which the application package is registered is generated, and the download information is provided by providing the download information including the information of the download page to the second user via the application development support tool. May be good.

The setting file may include a plug-in file that causes the communication terminal to execute a native function specific to the communication terminal.

The plug-in file may be a file in which the information input by the first user is updated with respect to the template created by the third user and uploaded to the application development support tool.

The digital certificate that identifies the application package is managed, and the digital certificate may be added to the application package.

The application generation support program according to the embodiment of the present invention associates a plurality of templates that define the operation of the communication terminal, and each of the operations defined by the plurality of templates can be realized on the application of the communication terminal. As described above, a part of the template is updated.

The template update may include at least one of replacing a portion of the template with parameters set by the user or overwriting a portion of the template with information entered by the user. Good.

A plug-in file that causes the communication terminal to execute a native function unique to the communication terminal is associated with the plurality of templates so that the operation of the communication terminal defined by the plug-in file can be realized on the communication terminal. In addition, a part of the plug-in file may be updated.

According to the present invention, it is possible to provide an application generation support system and an application generation support program that can reduce the development burden on the application developer.

It is a figure which shows the outline of the application generation support system which concerns on one Embodiment of this invention. It is a schematic diagram which shows the hardware configuration of the server used for the application generation support system which concerns on one Embodiment of this invention. It is a schematic diagram which shows the hardware configuration of the communication terminal of the 1st user used in the application generation support system which concerns on one Embodiment of this invention. It is a schematic diagram which shows the hardware configuration of the communication terminal of the 2nd user used in the application generation support system which concerns on one Embodiment of this invention. It is a block diagram which shows the functional structure of the server used in the application generation support system which concerns on one Embodiment of this invention. It is a block diagram which shows the detail of the setting file setting part of the server used for the application generation support system which concerns on one Embodiment of this invention. It is a flowchart which shows the application generation operation of the application generation support system which concerns on one Embodiment of this invention. It is an interface in the parameter input operation of the application generation support system which concerns on one Embodiment of this invention. It is a figure explaining the detail of the parameter of the application generation support system which concerns on one Embodiment of this invention. It is a figure explaining the sequence of the parameter check of the application generation support system which concerns on one Embodiment of this invention. It is a figure explaining an example of the error message of the application generation support system which concerns on one Embodiment of this invention. It is a figure explaining the sequence which sets the setting file of the application generation support system which concerns on one Embodiment of this invention. It is a figure explaining an example of the setting file of the application generation support system which concerns on one Embodiment of this invention. It is a flowchart which shows the application acquisition operation of the application generation support system which concerns on one Embodiment of this invention. This is an interface in the parameter acquisition operation of the application generation support system according to the embodiment of the present invention. It is a flowchart which shows the registration operation of the application setting file of the application generation support system which concerns on one Embodiment of this invention. It is a flowchart which shows the application generation operation of the application generation support system which concerns on one Embodiment of this invention. It is an interface in the parameter input operation of the application generation support system which concerns on one Embodiment of this invention. It is a figure explaining the sequence which sets the setting file of the application generation support system which concerns on one Embodiment of this invention. This is an interface in the parameter acquisition operation of the application generation support system according to the embodiment of the present invention. It is a flowchart which shows the registration operation of the plug-in file of the application generation support system which concerns on one Embodiment of this invention. It is a block diagram which shows the functional structure of the server used in the application generation support system which concerns on one Embodiment of this invention. It is a figure explaining the sequence which adds the digital certificate of the application generation support system which concerns on one Embodiment of this invention to an application package.

Hereinafter, the server, the communication terminal, and the program for operating these, which are used in the application generation support system according to the present invention, can be implemented in many different modes with reference to the drawings, and the implementations shown below can be implemented. It is not construed as being limited to the description content in the form of. In the drawings referred to in the present embodiment, the same number or a part having the same function is designated by the same number or a reference numeral with an alphabet added after the same number, and the repeated description thereof will be omitted.

<First Embodiment>
Using FIGS. 1 to 15, the application generation support system 10 according to the first embodiment of the present invention, the server 100 used for the application generation support system 10, the first communication terminal 200, the second communication terminal 300, and these are used. The program for operating will be described in detail. The application generation support system 10 shown in the first embodiment is a system in which the server 100 generates an application based on the parameters set by the first communication terminal 200 connected to the server 100 via the network 400. The generated application is downloaded by the second communication terminal 300 connected to the server 100 via the network 400.

In the following description, the first communication terminal 200 is a non-mobile communication terminal such as a desktop personal computer (PC). The second communication terminal 300 is a mobile communication terminal such as a smartphone or a tablet terminal. However, the configuration is not limited to the above. For example, the first communication terminal 200 may be a mobile communication terminal, and the second communication terminal 300 may be a non-mobile communication terminal.

[Overview of application generation support system 10]
FIG. 1 is a diagram showing an outline of an application generation support system according to an embodiment of the present invention. As shown in FIG. 1, the application generation support system 10 according to the present invention includes a server 100, a first communication terminal 200, and a second communication terminal 300. The server 100 is an information processing device. The first communication terminal 200 is a communication terminal that is not for mobile use. The second communication terminal 300 is a mobile communication terminal. The server 100 is connected to the database 102.

The server 100, the first communication terminal 200, and the second communication terminal 300 are each connected to the network 400. In the present embodiment, the network 400 is a local network such as an in-house LAN, but it may be a general World Wide Web (WWW). The first communication terminal 200 communicates with the server 100 via the network 400. Similarly, the second communication terminal 300 communicates with the server 100 via the network 400.

FIG. 1 illustrates a configuration in which the database 102 is directly connected to the server 100, but the configuration is not limited to this configuration. For example, the database 102 may be directly connected to the network 400.

[Hardware configuration of server 100]
FIG. 2 is a schematic diagram showing a hardware configuration of a server used in the application generation support system according to the embodiment of the present invention. As shown in FIG. 2, the server 100 includes a server control unit 110, a server recording unit 120, and a server communication unit 130.

The server control unit 110 includes a central processing unit (CPU: Central Processing Unit) and storage devices such as registers and memories. The server control unit 110 executes a program temporarily stored in the memory by the CPU, and performs arithmetic processing in response to instruction signals from the first communication terminal 200 and the second communication terminal 300.

The server recording unit 120 is a recording device capable of recording a large amount of data, and records programs and the like required for arithmetic processing. The program recorded in the server recording unit 120 is read out by the server control unit 110 and temporarily stored in the storage device of the server control unit 110. Further, the server recording unit 120 records the information transmitted from the first communication terminal 200 and the second communication terminal 300. The server recording unit 120 may be a hard disk, or may be a volatile or non-volatile memory. The information recorded in the server recording unit 120 may be recorded in the database 102 instead of the server recording unit 120.

The server communication unit 130 is a control device capable of transmitting and receiving data to an external device, and controls the transmission and reception of data to and from the network 400.

[Hardware configuration of the first communication terminal 200]
FIG. 3 is a schematic view showing the hardware configuration of the communication terminal of the first user used in the application generation support system according to the embodiment of the present invention. As shown in FIG. 3, the first communication terminal 200 includes a PC main body 210, a display device 220, and an input device 230. The PC main body 210 has a terminal storage device 211, a terminal control device 213, and a terminal communication unit 215. In FIG. 3, a desktop PC is illustrated as the first communication terminal 200, but the present invention is not limited to this example. The first communication terminal 200 can connect to the server 100 via the network 400, can display the graphic user interface (GUI) provided by the server 100, and set or input parameters to the GUI. It may be a smartphone, a mobile phone, a tablet PC, a PDA, a notebook PC, or a PHS.

The terminal storage device 211 records data such as a program for causing the first communication terminal 200 to execute a specific function and terminal information of a user who owns the first communication terminal 200. As the terminal storage device 211, a non-volatile memory such as a hard disk and a flash memory and a volatile memory such as an SRAM and a DRAM are used. Data such as a program is recorded in the non-volatile memory, is read from the non-volatile memory when the program is executed, and is temporarily stored in the volatile memory.

The terminal control device 213 has an arithmetic circuit such as a CPU and a storage circuit such as a memory and a register. The terminal control device 213 executes the program recorded in the terminal storage device 211 by the CPU, and realizes various functions of the first communication terminal 200 in response to the instruction signal input by the first communication terminal 200.

The terminal communication unit 215 is a control device capable of transmitting and receiving data to an external device, and controls the transmission and reception of data to and from the network 400.

[Hardware configuration of the second communication terminal 300]
FIG. 4 is a schematic view showing a hardware configuration of a communication terminal of a second user used in the application generation support system according to the embodiment of the present invention. As shown in FIG. 4, the second communication terminal 300 includes a terminal recording unit 310, a terminal control unit 320, a terminal communication unit 330, a display 340, a camera 350, an operation button 360, a speaker 370, and a microphone 380.

The terminal recording unit 310 includes data such as a program for causing the second communication terminal 300 to execute a specific function, an application program installed on the second communication terminal 300, and terminal information of a user who owns the second communication terminal 300. To record. As the terminal recording unit 310, a non-volatile memory such as a flash memory and a volatile memory such as SRAM and DRAM are used. Data such as a program is recorded in the non-volatile memory, is read from the non-volatile memory when the program is executed, and is temporarily stored in the volatile memory.

The terminal control unit 320 has an arithmetic circuit such as a CPU and a storage circuit such as a memory and a register. The terminal control unit 320 executes the program recorded in the terminal recording unit 310 by the CPU, and realizes various functions of the second communication terminal 300 in response to the instruction signal input by the second communication terminal 300.

The terminal communication unit 330 is a control device capable of transmitting and receiving data to an external device, and controls the transmission and reception of data to and from the network 400. Further, the terminal communication unit 330 may have a Global Positioning System (GPS) function. The GPS function is one of the native functions of the second communication terminal 300. When the application for enabling the GPS function is started, the terminal communication unit 330 receives a signal from a satellite in the sky and can know the current position of the second communication terminal 300.

As the display 340, a liquid crystal display, an organic EL display, or the like can be used. Further, the display 340 may have a touch sensor. As the touch sensor, a resistive film type sensor, a capacitance type sensor, an optical type sensor, or the like can be used.

The camera 350 is provided on the opposite side of the display 340. That is, the camera 350 is provided on the back surface, assuming that the side on which the display 340 is provided is the front surface. A camera separate from the camera 350 may be provided on the surface. The camera 350 has a lens unit and an image sensor. The function of the camera 350 is one of the native functions of the second communication terminal 300. When the application for enabling the function of the camera 350 is started, the image detected by the image sensor via the lens unit is displayed on the display 340. If an operation instruction is input by the user while this image is being detected by the image sensor, the terminal control unit 320 acquires a still image of the image detected by the image sensor in response to the operation instruction.

FIG. 4 illustrates a configuration in which the second communication terminal 300 has an operation button 360, a speaker 370, and a microphone 380, but the configuration is not limited to this configuration. If not necessary, the operation button 360, the speaker 370, and the microphone 380 may be omitted.

In FIG. 4, a smartphone is shown as an example of the second communication terminal 300, but the second communication terminal 300 used in the application generation support system 10 is not limited to the smartphone. As the second communication terminal 300 used in the application generation support system 10, a mobile phone, a tablet PC, a PDA, a notebook PC, a PHS, or the like may be used in addition to the smartphone.

[Functional configuration of server 100]
FIG. 5 is a block diagram showing a functional configuration of a server used in the application generation support system according to the embodiment of the present invention. As shown in FIG. 5, the server 100 has an application development support tool 140 and a build shell 150. The application development support tool 140 has a GUI providing unit 141 and a parameter receiving unit 143. The build shell 150 has a parameter receiving unit 151, a parameter checking unit 153, a file setting unit 155, an application package generation unit 157, and a download (DL) information providing unit 159. The functions of the above-mentioned functional units are realized by the server control unit 110 of the server 100 executing the program recorded in the server recording unit 120 by the CPU. In this embodiment, the configuration in which the application development support tool 140 and the build shell 150 are included in one server 100 is illustrated, but the configuration is not limited to this configuration. For example, the application development support tool 140 and the build shell 150 are included in different servers, and the application generation support system 10 may be realized by the cooperation of these servers.

The GUI providing unit 141 provides the first user who operates the first communication terminal 200 with an interface for selecting or inputting parameters for setting a function installed in the application. The interface provided by the GUI providing unit 141 is displayed on the display device 220 of the first communication terminal 200.

The parameter receiving unit 143 receives the parameters selected or input by the first communication terminal 200 with respect to the interface provided by the GUI providing unit 141.

The application development support tool 140 stores tools necessary for developing an application. That is, a plurality of functional program templates necessary for application development are registered in the application development support tool 140. The GUI providing unit 141 provides the first user with an interface capable of selecting a plurality of templates. The above template defines the basic operation of the second communication terminal 300 in which the application is installed.

The application development support tool 140 stores, for example, a text editor, an interface builder, a debugger, a compiler, an OS simulator, and the like. A text editor is a tool for writing programs. For example, a text editor has the functions of program auto-filling and program syntax highlighting (syntax highlighting). Interface Builder is a tool for creating interfaces for applications. For example, an interface builder creates an interface by arranging parts such as buttons and switches by dragging and dropping. The debugger is a tool that stops the operation during the execution of the program and checks the state inside in order to check whether there is a problem in the operation of the program. A compiler is a tool that transforms a program into a computer-understandable format. The OS simulator is a tool for confirming the operation of an application by a "simulator" that operates similar to the operation of the OS of a communication terminal that downloads the application.

When the first user selects a desired function program from the template provided by the GUI providing unit 141, the parameter receiving unit 143 accepts that the specific function program has been selected as a parameter.

As the application development support tool 140, for example, Xcode (registered trademark), JAVA (registered trademark) software development kit (Soft Development Kit; SDK), or Android SDK can be used. When Xcode is used as the application development support tool 140, Jenkins (registered trademark) may be used. Jenkins is an open source continuous integration tool written in JAVA.

The parameter receiving unit 151 receives the parameters set by the first user who operates the first communication terminal 200 via the network 400. Although details will be described later, the parameters set by the first user are parameters related to the operation of the second communication terminal 300 in which the application is installed. In other words, the parameter is a parameter including parameters related to the setting file (OS setting file and application setting file) and the plug-in file described later.

The parameter check unit 153 checks whether or not the format of the parameter received by the parameter reception unit 151 conforms to the specified format. For example, when a hybrid application is generated by the application generation support system 10 and installed on the second communication terminal 300 of the second user, the second communication terminal 300 is the first when the application is started on the second communication terminal 300. It is necessary to set the initial URL of the Web page to access. Since the format of the URL is defined as "http: //" or "https: //", the parameter check unit 153 checks whether the format of the initial URL conforms to the above format. .. Details will be described later, but if the parameter check unit 153 determines that the parameter format is not the specified format, an error message is notified. In addition to the above functions, the parameter check unit 153 checks the format of the setting file required to generate the application.

The file setting unit 155 sets a setting file that defines the operation of the application according to the parameters received by the parameter receiving unit 151 and passing the check of the parameter checking unit 153. In other words, the file setting unit 155 sets a setting file that defines the operation of the application according to the parameters related to the operation of the second communication terminal 300.

Here, a more detailed function of the file setting unit 155 will be described with reference to FIG. FIG. 6 is a block diagram showing details of a setting file setting unit of a server used in the application generation support system according to the embodiment of the present invention. As shown in FIG. 6, the file setting unit 155 includes a parameter confirmation unit 1551, a template association unit 1553, and a program update unit 1555.

The parameter confirmation unit 1551 confirms the parameters set by the first user and determines the function to be incorporated in the application. The parameter confirmation unit 1551 selects a template related to the parameter from a plurality of templates prepared in advance in the application development support tool 140 based on the confirmed parameter.

The template association unit 1553 associates the templates selected by the parameter confirmation unit 1551 with each other. That is, the template association unit 1553 defines a set of functions incorporated in the application. The functions associated with each other by the template association unit 1553 become the functions of the finally generated application.

The program update unit 1555 sets a part of the template so that each of the operations defined by the templates associated with each other by the template association unit 1553 can be realized on the application installed in the second communication terminal 300. Update. The above template defines the basic operation of the second communication terminal 300 on which the application is installed, but in the template before the update, the display of the application should be adjusted according to the operation of the second communication terminal 300. May not be possible. The program update unit 1555 updates a part of the template so that the display of the application is normally adjusted according to the operation of the second communication terminal 300.

For example, if the template that defines the operation of rotating the second communication terminal 300 to the right by 90 degrees is incorporated into the application without updating, the display of the application is displayed even if the second communication terminal 300 is rotated by 90 degrees to the right. The display may not be suitable for the screen of the second communication terminal 300 rotated by 90 degrees. Even in such a case, by updating the template by the program update unit 1555, the display of the application is rotated according to the rotation operation of the second communication terminal 300, and the display is suitable for the state of the second communication terminal 300.

As will be described later, the template includes a template for the OS setting file and a template for the application setting file. The template for the OS setting file is a template in which operations common to different types of second communication terminals 300 are specified, and the operations of applications related to the operations of the second communication terminal 300 are specified. The template for the application setting file is a template including a blank that accepts a parameter input by the first user, and defines the operation of the application related to the operation of the second communication terminal 300. The OS setting file can be obtained by replacing a part of the template for the OS setting file with the parameters set by the first communication terminal 200. On the other hand, the application setting file is obtained by overwriting the information input by the first communication terminal 200 on a part of the template for the application setting file.

Hereinafter, the remaining functional parts of the build shell 150 will be described with reference to FIG.

The application package generation unit 157 generates an application package based on the setting file set by the file setting unit 155 as described above. Specifically, the application package generation unit 157 compiles the above setting file and generates an archive format file in which the application can be installed on the second communication terminal 300.

The DL information providing unit 159 provides the second communication terminal 300 with the download information of the application package generated by the application package generating unit 157. For example, the DL information providing unit 159 may generate a download page in which the application package is registered and provide the URL of the generated download page to the second communication terminal 300. The URL of the download page may be displayed on the second communication terminal 300 via the interface provided by the application development support tool 140.

[Operation flow of application generation support system 10]
The operation of each functional block of the application generation support system 10 shown in FIGS. 5 and 6 will be described in detail with reference to FIGS. 7 to 15 by using a flowchart and an example of an interface displayed to the user.

First, with reference to FIGS. 7 to 13, an operation of generating an application based on a parameter set by a first user and providing the application for download will be described. FIG. 7 is a flowchart showing an application generation operation of the application generation support system according to the embodiment of the present invention. In FIG. 7, the operation in which the first user sets the functions required for the application using the first communication terminal 200, the build shell 150 generates the application package based on the setting, and provides the download information of the application package. Will be described.

First, by the operation of the first user, the first communication terminal 200 connects to the application development support tool 140 via the network 400 by HTTP (step 501). The application development support tool 140 accessed by the first communication terminal 200 provides the first communication terminal 200 with a parameter setting GUI (step 511). The provided parameter setting GUI is displayed to the first user by the display device 220 of the first communication terminal 200.

An example of the parameter setting GUI displayed on the first communication terminal 200 will be described with reference to FIG. FIG. 8 is an interface in the parameter input operation of the application generation support system according to the embodiment of the present invention. As shown in FIG. 8, the interface 600 includes a project name 610, an item name 620, an input field 630, and an application generation button (build button) 640.

In the project name 610, a name for identifying the project that generates the application is displayed. The name displayed in the project name 610 may be a name specified by the user or a name automatically assigned by the server.

In the item name 620, a name indicating a function executed by the application is displayed. Details of the items displayed in the item name 620 of FIG. 8 will be described later.

The input field 630 is provided with an area for accepting input or selection by the user. The input format of the input field 630 differs depending on the item name 620. For example, the input fields 630 of "CFBUNDLE_DISPLAY_NAME" and "INFO_CFBUNDLE_VERSION" accept arbitrary character strings. These item names 620 are used as information for identifying the application.

The input fields 630 of "LANDSCAPE_LEFT", "PORTRAIT_UPSIDE_DOWN", and "LANDSCAPE_RIGHT" accept the input in the check box format. That is, the user can select whether or not to install the functions related to these item names in the application.

The input field 630 of "APP_START_PAGE_URL" accepts a character string in a specified format. In the input field 630, the URL of the Web page displayed when the user starts the application is input. That is, a character string in a specified format such as "http: //" or "https: //" is input in the input field 630. For this item, a function for testing whether or not the input character string is in the specified format may be provided. For example, a test button may be arranged, and when the test button is selected, a temporarily entered URL may be displayed. Alternatively, every time the input content of the input field 630 of this item is updated, a test is automatically performed to check the existence of the page corresponding to the input URL, and the validity of the input URL is an interface. The user may be notified on 600.

The input field 630 of "APPLICATION_PLIST" accepts an address indicating the position where the file for setting the application setting file is stored. The user may directly input an address in the input field 630, or may specify an address to be referred to by clicking "Browse" to the right of the blank box. These item names 620 are functions installed in the application.

Among the item names 620 related to the functions installed in the application, whether or not the functions are installed in the application for the items whose functions are predetermined such as "LANDSCAPE_LEFT", "PORTRAIT_UPSIDE_DOWN", and "LANDCASPE_RIGHT". The user's parameter setting is completed just by deciding.

By selecting the build button 640 after inputting the necessary items in the input field 630, the user's operation is completed, and the items input in the input field 630 are transmitted to the server 100 as parameters set by the user.

The item name 620 illustrated in FIG. 8 and the functions related to the item name will be described with reference to FIG. FIG. 9 is a diagram illustrating details of parameters of the application generation support system according to the embodiment of the present invention. The item name 620 shown in FIGS. 8 and 9 shows an example of the function of the application, and does not limit the function of the application of the present invention.

"CFBUNDLE_DISPLAY_NAME" is an item for designating an application name. In this item, a character string for setting the display character of the application icon is set. That is, "CFBUNDLE_DISPLAY_NAME" is used to clearly identify a particular application.

"INFO_CFBUNDLE_VERSION" is an item that specifies the bundle version of the application. In this item, a character string for setting the application version is set. "INFO_CFBUNDLE_VERSION" is used to identify a particular application version.

“LANDSCAPE_LEFT” and “LANDSCAPE_RIGHT” are items for designating screen control when the second communication terminal 300 is rotated to the left side and the right side. In these items, when the screen of the second communication terminal 300 is rotated left sideways and right sideways, whether or not to display the application in front on the screen of the second communication terminal 300 is set by checking or not.

"PORTRAIT_UPSIDE_DOWN" is an item for designating screen control when the second communication terminal 300 is rotated upside down. In this item, when the screen of the second communication terminal 300 is rotated upside down, whether or not to display the application in front on the screen of the second communication terminal 300 is set by checking or not.

"APP_START_PAGE_URL" is an item that specifies the URL of the Web page designated as the start page of the application. In this item, a character string for setting the URL of the Web page displayed when the application is started is set. In this item, a character string in a predetermined format such as "http: //" or "https: //" is set in order to display the URL.

"APPLICATION_PLIST" is an item for designating an application setting file. In this item, the application setting file to be installed in the application is set, and the setting file is uploaded to the server 100. The application setting file set in "APPLICATION_PLIST" may be a setting file created by the first user who operates the first communication terminal 200, or may be a setting file created by another third user. Good.

Hereinafter, a flowchart showing the application generation operation will be described with reference to FIG. 7.

The first communication terminal 200 sets options for functions installed in the application by inputting or selecting necessary items for each item shown in FIGS. 8 and 9 (step 503). When the option setting is completed, the first communication terminal 200 selects the build button 640 of FIG. 8 (step 505) and requests the application development support tool 140 to generate an application. By selecting the build button in step 505, various parameters set in the interface 600 of FIG. 8 are transmitted from the first communication terminal 200 to the application development support tool 140 of the server 100.

The application development support tool 140 receives the parameters transmitted from the first communication terminal 200, and transfers the received parameters to the build shell 150 (step 513).

The build shell 150 receives the parameters transferred by the application development support tool 140 (step 521). The build shell 150 checks the received parameters (step 523). The parameter check in step 523 is performed before the setting file described later is set. In step 523, the sequence of checking the parameters will be described with reference to FIG.

FIG. 10 is a diagram illustrating a parameter check sequence of the application generation support system according to the embodiment of the present invention. As shown in FIG. 10, the parameters received in step 521 are checked (step 5231). In step 5231, for example, the setting state such as whether or not the format of the set parameter conforms to the specified format and whether or not the format of the application setting file conforms to the specified format is checked. In the example shown in FIGS. 8 and 9, it is checked whether or not the URL entered in "APP_START_PAGE_URL" is in the format of "http: //" or "https: //". Similarly, "APPLICATION_PLIST" checks whether the application setting file has the specified file format. Further, as will be described in detail later, it is checked whether or not the plug-in file related to the native function of the second communication terminal 300 has a specified file format as a function installed in the application.

If the parameter format set in the parameter check in step 5231 conforms to the specified format (“OK” in step 5231), it is determined that the parameter check is completed (step 5233), and the process ends. On the other hand, if the set parameter format does not conform to the specified format (“NG” in step 5231), an error message is notified (step 5235), and the process ends. The notification of the error message is displayed on the first communication terminal 200 via the interface 600 of FIG. 8, for example.

FIG. 11 is a diagram illustrating an example of an error message of the application generation support system according to the embodiment of the present invention. In FIG. 11, as an example of the error message notification, error messages related to the items of "APP_START_PAGE_URL", "APPLICATION_PLIST", and "PLUGIN_FILES" are given. For "APP_START_PAGE_URL", when a character string other than the character string starting with "http: //" or "https: //" is input, the error message "[INPUT EROR] APP_START_PAGE_URL input value is invalid." Is displayed. For "APPLICATION_PLIST", when a file whose file name is other than "application.list" is uploaded, the error message "[INPUT EROR] APPLICATION_PLIST input value is invalid." Is displayed. For "PLUGIN_FILES", when a file other than the specified file format is uploaded, the error message "[INPUT EROR] PLUGIN_FILES input value is invalid." Is displayed.

Hereinafter, a flowchart showing the application generation operation will be described with reference to FIG. 7.

When the parameter check in step 523 is completed, the OS setting file is replaced (step 525). Subsequently, the application setting file is overwritten (step 527). In some cases, these operations are combined to update the configuration file. Here, in step 525 and step 527, the sequence of updating the configuration file will be described with reference to FIG. Further, the setting file processed in step 525 and step 527 will be described with reference to FIG.

FIG. 12 is a diagram illustrating a sequence for setting a setting file of the application generation support system according to the embodiment of the present invention. FIG. 12 describes a case where the start page designation URL and the OS setting file are indispensable setting items. As shown in FIG. 12, the start page designation URL is first set (step 5261). Subsequently, the OS setting file is set (replacement process) (step 5263). Subsequently, the necessity of setting the application setting file is confirmed (step 5265). In step 5265, the necessity of setting the application setting file is confirmed by confirming the setting state of the parameters that have passed through steps 521 and 523. If it is confirmed in step 5265 that the application setting file needs to be set (“OK” in step 5265), the application setting file is set (overwritten) (step 5267), and the process ends. On the other hand, if it is not confirmed that the setting of the application setting file is not necessary (“NG” in step 5265), the process ends without setting the application setting file.

FIG. 13 is a diagram illustrating an example of a setting file of the application generation support system according to the embodiment of the present invention. The "icon designation", "application name designation", and "screen rotation control designation" in FIG. 13 correspond to the OS setting file. That is, "CFBUNDLE_DISPLAY_NAME", "INFO_CFBUNDLE_VERSION", "LANDCAPE_LEFT", "PORTRAIT_UPSIDE_DOWN", and "LANDCAPE_RIGHT" in FIGS. 8 and 9 correspond to the OS setting files. The operations related to these OS setting files are operations common to a plurality of second communication terminals 300. "Address bar display", "Screen copy and paste control", "Communication protocol restriction", "No operation timeout specification", "Single sign-on setting", and "Back button usage restriction" in FIG. 13 are application setting files. Corresponds to. That is, the above item is an example of "APPLICATION_PLIST". The operation related to these application setting files is the operation of the second communication terminal 300 input by the first communication terminal 200, and may be an operation common to a plurality of second communication terminals 300, and may be a specific second communication terminal 300. It may be an operation peculiar to the communication terminal 300.

In other words, the configuration file of this embodiment includes an OS configuration file and an application configuration file. The OS setting file is a setting file that defines the operation of the application that is related to the parameters received by the build shell 150 and is common to the operations of the plurality of second communication terminals 300. The application setting file is a setting file that defines the operation of the application based on the information input by the first user who operates the first communication terminal 200 in relation to the parameters received by the build shell 150. The OS setting file and the application setting file shown in FIG. 13 are examples, and do not limit the "APPLICATION_PLIST" of the present invention.

Hereinafter, a flowchart showing the application generation operation will be described with reference to FIG. 7.

When the update of the setting file in step 525 and step 527 is completed, a project file including the OS setting file replaced in step 525 and the application setting file overwritten in step 527 is generated (step 529). Here, the project file is a file in which files and resources (components) necessary for constructing an application in the application development support tool 140 are stored. The project file collectively contains the components necessary for building the application, and also manages the relationships between the components.

An application package is generated by performing a build process including compiling each file on the project file generated in step 529 (step 531). The application package functions as an installer for installing the application on the second communication terminal 300. The application package is an archive format file that includes the configuration file set above in addition to the application executable file.

Subsequently, the download information of the application package generated in step 531 is generated (step 533). For example, upload an application package to a download page and generate the URL of that download page. Then, the download information generated in step 533 is provided from the build shell 150 to the application development support tool 140 (step 535). For example, the URL of the above download page is provided to the application development support tool 140.

The application development support tool 140 receives the download information provided in step 535 (step 515), and provides the download information to the first communication terminal 200 and the second communication terminal 300 via the download information providing GUI (step 515). Step 515).

Next, the operation of downloading the generated application by the user will be described with reference to FIGS. 14 and 15. FIG. 14 is a flowchart showing an application acquisition operation of the application generation support system according to the embodiment of the present invention.

First, by the operation of the second user, the second communication terminal 300 makes an HTTP connection to the application development support tool 140 via the network 400 (step 541) and requests the application package (step 543). The application development support tool 140 accessed by the second communication terminal 300 provides the download information GUI to the second communication terminal 300 (step 551). The provided download information GUI is displayed to the second user by the display 340 of the second communication terminal 300.

An example of the download information GUI displayed on the second communication terminal 300 will be described with reference to FIG. FIG. 15 is an interface in the parameter acquisition operation of the application generation support system according to the embodiment of the present invention. As shown in FIG. 15, the interface 650 includes a project name 660, an item name 670, a setting value 680, and a download button 690.

In the project name 660, the project name corresponding to the project name 610 in FIG. 8 is displayed. In the item name 670, the item set by the user among the item names 620 in FIG. 8 is displayed. In FIG. 15, the OS setting files are organized in "INFO_PLIST". The set value 680 displays the functions set by the user in FIG. 8 and installed in the generated application. The character strings input in FIG. 8 are displayed in the set values 680 of "CFBUNDLE_DISPLAY_NAME", "INFO_CFBUNDLE_VERSION", and "APP_START_PAGE_URL", respectively. The item checked in FIG. 8 is displayed in the set value 680 of "INFO_PLIST". By selecting the download button 690 after confirming the above setting items, the application package is downloaded to the second communication terminal 300.

Hereinafter, a flowchart showing the application acquisition operation will be described with reference to FIG.

The second communication terminal 300 requests the application development support tool 140 to download the application package by selecting the download button 690 shown in FIG. 15 (step 545). In response to step 545, the application development support tool 140 provides an application package (step 553). Then, the second communication terminal 300 downloads the provided application package (step 547).

As described above, according to the application generation support system 10 according to the first embodiment, the build shell 150 of the server 100 automatically generates and downloads the application package only by setting the parameters by the first communication terminal 200. Can be provided to the second communication terminal 300. That is, the development burden on the application developer can be reduced.

<Second Embodiment>
Using FIG. 16, a program for operating the application generation support system 10A according to the second embodiment of the present invention, and the server 100A, the first communication terminal 200A, and the second communication terminal 300A used for the application generation support system 10A. Will be described in detail. Regarding the hardware configuration and functional configuration of the server 100A, the first communication terminal 200A, and the second communication terminal 300A of the application generation support system 10A according to the second embodiment, the application generation support system according to the first embodiment. The description of the hardware configuration and the functional configuration similar to 10 will be omitted, and the differences from the application generation support system 10 will be described.

In the second embodiment, the configuration in which the template for the application setting file is uploaded by a third user different from the first user and the second user will be described. FIG. 16 is a flowchart showing a template registration operation for an application setting file of the application generation support system according to the embodiment of the present invention.

First, by the operation of the third user, the third communication terminal 290A connects to the application development support tool 140A via the network 400A by HTTP (step 561A), and requests the upload of the template for the application setting file (step 563A). The application development support tool 140A accessed by the third communication terminal 290A provides the third communication terminal 290A with a GUI for an application setting file (step 571A). The provided GUI for application setting file is displayed to the third user by the display device of the third communication terminal 290A.

The third communication terminal 290A prepares a template for the application setting file (step 565A), and uploads the template prepared via the GUI provided in step 571A to the application development support tool 140A of the server 100A (step 567A). ). The template prepared in step 565A may be created by a third user who operates the third communication terminal 290A, or may be created by another user. The uploaded template is registered in the application development support tool 140A (step 573A). The template for the application setting file registered in step 573A is provided to the first communication terminal 200, for example, as the parameter setting GUI in step 511 of FIG. That is, the template for the application setting file provided to the first communication terminal 200A in the second embodiment is a template created by the third user or another user and uploaded to the application development support tool 140A.

As described above, according to the application generation support system 10A according to the second embodiment, the template for the application setting file prepared in the application generation support system 10A is increased by being uploaded by the third communication terminal 290A. Therefore, the first communication terminal 200A can use templates for various application setting files when setting parameters.

<Third Embodiment>
17 to 21 are used to operate the application generation support system 10B according to the third embodiment of the present invention, and the server 100B, the first communication terminal 200B, and the second communication terminal 300B used for the application generation support system 10B. The program for this will be described in detail. Regarding the hardware configuration and functional configuration of the server 100B, the first communication terminal 200B, and the second communication terminal 300B of the application generation support system 10B according to the third embodiment, the application generation support system according to the first embodiment. The description of the hardware configuration and the functional configuration similar to 10 will be omitted, and the differences from the application generation support system 10 will be described.

[Functional configuration of server 100B]
The configuration of each function of the server 100B in the application generation support system 10B of the present embodiment is the same as the configuration of each function of the server 100 of the first embodiment. Therefore, the functional part of the server 100B will be described with reference to FIG. The file setting unit 155B included in the build shell 150B of the application generation support system 10B sets the plug-in file related to the native function of the second communication terminal 300B in addition to the OS setting file and the application setting file. It is different from the file setting unit 155 of the first embodiment. The file setting unit 155B sets the plug-in file in the same manner as the OS setting file and the application setting file when the parameters related to the plug-in file are set in the parameters received by the parameter receiving unit 151B.

As shown in FIG. 6, the file setting unit 155B includes a parameter confirmation unit 1551B, a template association unit 1553B, and a program update unit 1555B. The parameter confirmation unit 1551B has the same function as the parameter confirmation unit 1551 of the first embodiment. The template association unit 1553B associates the template for the plug-in file with another template selected by the parameter confirmation unit 1551B, in addition to the same function as the template association unit 1553 of the first embodiment. In addition to the same functions as the program update unit 1555 of the first embodiment, the program update unit 1555B realizes each of the operations defined by the template for the plug-in file on the application installed on the second communication terminal 300. Update a part of the template so that it is possible.

As described above, the plug-in file is a setting file for causing the second communication terminal 300B to execute native functions unique to the device of the second communication terminal 300B, such as a camera, GPS, microphone, and acceleration sensor, by an application. is there. The plug-in file is a setting file related to the parameters received by the build shell 150B, like the OS setting file and the application setting file.

As described in the first embodiment, the application development support tool 140B is prepared in advance with a template for the OS setting file and a template for the application setting file. Similarly to these, the application development support tool 140B is prepared with a template for the plug-in file. From the template for this plug-in file, a template related to the parameter received by the build shell 150B is selected, and a part of the template is updated to set the plug-in file. The template for the plug-in file may be prepared in advance in the application development support tool 140B, or may be created by another third user as described later.

[Operation flow of application generation support system 10B]
The operation of each functional block of the application generation support system 10B of the present embodiment will be described in detail with reference to FIGS. 17 to 21 by using a flowchart and an example of an interface displayed to the user.

First, with reference to FIGS. 17 to 19, an operation of generating an application based on the parameters set by the first communication terminal 200B and providing the application for download will be described. FIG. 17 is a flowchart showing an application generation operation of the application generation support system according to the embodiment of the present invention. The flowchart of FIG. 17 is similar to the flowchart of FIG. 7, but in the flowchart of FIG. 17, step 528B for setting a plug-in file is provided between step 527B and step 529B. It is different from the flowchart. Further, since step 528B is provided, the interface 600B provided to the first communication terminal 200B in step 511B is different from the interface 600 of FIG. In the following description, the same operation as the operation flow of FIG. 7 will be omitted, and an operation different from the operation flow of FIG. 7 will be described.

First, the parameter setting GUI provided to the first communication terminal 200B in step 511B of FIG. 17 will be described. FIG. 18 is an interface in the parameter input operation of the application generation support system according to the embodiment of the present invention. The interface 600B shown in FIG. 18 is similar to the interface 600 of FIG. 8, but the interface of FIG. 8 is provided with "PLUGIN_FILES" under "APPLICATION_PLIST" in the item name 620B of the interface 600B of FIG. It is different from 600.

The input field 630B of "PLUGIN_FILES" accepts an address indicating the position where the template for the plug-in file is stored. The user may directly input an address in the input field 630B, or may specify an address to be referred to by clicking "Browse" on the right side of the blank box. The template for the plug-in file is stored in the compressed file format at the specified address. However, the file may be stored in a format other than the compressed file format.

By selecting the build button 640B after inputting the necessary items in the input field 630B, the user's operation is completed, and the items input in the input field 630B are transmitted to the server 100B as parameters set by the user.

As described above, the interface 600B is provided with an item for setting the plug-in file in the interface 600B, and the interface 600B is added to the parameters transmitted from the first communication terminal 200B to the build shell 150B via the application development support tool 140B. Since the operation up to step 527B in FIG. 17 is the same as in FIG. 7, except that the parameters related to the plug-in file set in FIG. 17 are included, the description thereof will be omitted.

As shown in FIG. 17, following the overwriting process of the application setting file in step 527B, the plug-in file is set (step 528B). The setting of the plug-in file may be to update the setting file in the same manner as the replacement of the OS setting file and the overwriting process of the application setting file. Here, in step 528B, the sequence for setting the plug-in file will be described with reference to FIG.

FIG. 19 is a diagram illustrating a sequence for setting a setting file of the application generation support system according to the embodiment of the present invention. FIG. 19 describes a case where the start page designation URL and the OS setting file are indispensable setting items. As shown in FIG. 19, the start page designation URL is first set (step 5261B). Subsequently, the OS setting file is set (replacement process) (step 5263B). Subsequently, the necessity of setting the application setting file is confirmed (step 5265B). In step 5265B, the necessity of setting the application setting file is confirmed by confirming the setting state of the parameters that have passed through steps 521B and 523B. If it is confirmed in step 5265B that the application setting file needs to be set (“OK” in step 5265B), the application setting file is set (overwritten) (step 5267B). On the other hand, if it is not confirmed that the setting of the application setting file is not necessary (“NG” in step 5265B), the setting of the application setting file is not performed and the process proceeds to the next step.

Following the above steps, it is confirmed whether or not the plug-in file needs to be set (step 5281B). In step 5281B, the necessity of setting the plug-in file is confirmed by confirming the setting state of the parameters that have passed through steps 521B and 523B. If it is confirmed in step 5281B that the plug-in file needs to be set (“OK” in step 5281B), the plug-in file is set (step 5283B), and the process ends. On the other hand, if it is not confirmed that the plug-in file setting is not necessary (“NG” in step 5281B), the process ends without setting the plug-in file.

The operation flow of FIG. 17 after step 529B is the same as that of FIG. 7 except that the project file generated in step 529B and the application package generated in step 531B include the plug-in file, and thus the description thereof will be omitted.

Since the operation flow for the user to download the generated application is the same as the operation flow of FIG. 14, the description thereof will be omitted. However, since the application package includes the plug-in file, the interface 650B provided to the second communication terminal 300B for downloading the application package is different from the interface 650 of FIG.

FIG. 20 is an interface in the parameter acquisition operation of the application generation support system according to the embodiment of the present invention. The interface 650B shown in FIG. 20 is similar to the interface 650 of FIG. 15, but the interface of FIG. 15 is provided with "PLUGIN_FILES" under "APPLICATION_PLIST" in the item name 670B of the interface 650B of FIG. It is different from 650. In addition, in the set value 680B of "PLUGIN_FILES" of FIG. 20, "Browser_camera" input by the interface 600B of FIG. 18 is displayed. "Browser_camera" is a plug-in file that activates the camera, which is a native function of the communication terminal in which the application is installed, on the browser and shoots. However, the function of the plug-in file is not limited to the above function, and can have various other functions.

In the present embodiment, a configuration in which a template for a plug-in file is uploaded by a third user different from the first user and the second user will be described. FIG. 21 is a flowchart showing a plug-in file registration operation of the application generation support system according to the embodiment of the present invention.

First, by the operation of the third user, the third communication terminal 290B makes an HTTP connection to the application development support tool 140B via the network 400B (step 581B), and requests the upload of the template related to the plug-in file (step 583B). .. The application development support tool 140B accessed by the third communication terminal 290B provides the third communication terminal 290B with a GUI for a plug-in file (step 591B). The provided GUI for application setting file is displayed to the third user by the display device of the third communication terminal 290B.

The third communication terminal 290B prepares a template for the plug-in file (step 585B), and uploads the template prepared via the GUI provided in step 591B to the application development support tool 140B of the server 100B (step 587B). ). The template prepared in step 585B may be created by a third user who operates the third communication terminal 290B, or may be created by another user. The uploaded template is registered in the application development support tool 140B (step 593B). The template related to the plug-in file registered in step 593B is provided to the first communication terminal 200B by, for example, the parameter setting GUI of step 511B of FIG. That is, the template for the plug-in file provided to the first communication terminal 200B in the third embodiment is a template created by the third user or another user and uploaded to the application development support tool 140B.

As described above, according to the application generation support system 10B according to the third embodiment, a plug-in file that realizes a native function peculiar to the second communication terminal 300B on which the application is installed can be mounted on the application. The number of templates related to the plug-in file prepared in the application generation support system 10B is increased by being uploaded by the third communication terminal 290B. Therefore, the first communication terminal 200B can use templates related to various plug-in files when setting parameters.

<Fourth Embodiment>
22 and 23 are used to operate the application generation support system 10C according to the fourth embodiment of the present invention, and the server 100C, the first communication terminal 200C, and the second communication terminal 300C used for the application generation support system 10C. The program for this will be described in detail. Regarding the hardware configuration and functional configuration of the server 100C, the first communication terminal 200C, and the second communication terminal 300C of the application generation support system 10C according to the fourth embodiment, the application generation support system according to the first embodiment. The description of the hardware configuration and the functional configuration similar to 10 will be omitted, and the differences from the application generation support system 10 will be described.

[Functional configuration of server 100C]
FIG. 22 is a block diagram showing a functional configuration of a server used in the application generation support system according to the embodiment of the present invention. As shown in FIG. 22, the functional configuration of the server 100C of the fourth embodiment is similar to the functional configuration of the server 100 of the first embodiment shown in FIG. 5, but the build shell 150C of the server 100C is electronically certified. It differs from the server 100 in that it has a management unit 161C.

The digital certificate management unit 161C manages the digital certificate that identifies the application package generated by the application package generation unit 157C. This digital certificate is a certificate that not only identifies the application package but also proves the validity of the user who generates the application package to the provider who provides the OS. The digital certificate management unit 161C adds the above digital certificate to the application package generated by the application package generation unit 157C.

[Operation flow of application generation support system 10C]
The operation flow of the application generation support system 10C of the present embodiment is substantially the same as the operation flow of the application generation support system 10 of the first embodiment. Therefore, the operation flow of the application generation support system 10C will be described with reference to FIG. 7. In the operation flow of the application generation support system 10C, when the application package is generated in step 531C, the necessity of setting the digital certificate is confirmed, and the digital certificate is added to the application package as needed. Here, in step 531C, the sequence of adding the digital certificate to the application package will be described with reference to FIG.

FIG. 23 is a diagram illustrating a sequence for adding the digital certificate of the application generation support system according to the embodiment of the present invention to the application package. In the sequence shown in FIG. 23, the steps up to step 5267C are the same as the steps up to step 5267 in FIG. 12, so the description thereof will be omitted. As shown in FIG. 23, the necessity of setting the digital certificate is confirmed following step 5267C (step 5311C). If it is confirmed in step 5311C that the digital certificate needs to be set (“OK” in step 5311C), the digital certificate is set (the digital certificate setting is added to the application package) (step 5313C), and the process is performed. Is finished. On the other hand, if it is not confirmed that the digital certificate setting is not necessary (“NG” in step 5311C), the process ends without setting the digital certificate setting.

As described above, according to the application generation support system 10C according to the fourth embodiment, the build shell 150C of the server 100C automatically generates and downloads the digital certificate that the application package creator had to set by himself / herself. It can be provided to the second communication terminal 300C as possible.

The present invention is not limited to the above embodiment, and can be appropriately modified without departing from the gist.

10: Application generation support system, 100: Server, 102: Database, 110: Server control unit, 120: Server recording unit, 130: Server communication unit, 140: Application development support tool, 141: Provider, 143: Parameter reception unit , 150: Build shell, 151: Parameter receiving unit, 153: Parameter checking unit, 155: File setting unit, 157: Application package generation unit, 159: Information providing unit, 161C: Electronic certification management unit, 200: First communication terminal , 210: Main unit, 211: Terminal storage device, 213: Terminal control device, 215: Terminal communication unit, 220: Display device, 230: Input device, 290A: Third communication terminal, 300: Second communication terminal, 310: Terminal Recording unit, 320: Terminal control unit, 330: Terminal communication unit, 340: Display, 350: Camera, 360: Operation buttons, 370: Speaker, 380: Microphone, 400: Network, 600: Interface, 610: Project name, 620 : Item name, 630: Input field, 640: Build button, 650: Interface, 660: Project name, 670: Item name, 680: Setting value, 690: Download button, 1551: Parameter confirmation part, 1553: Template association part, 1555: Program update department

Claims (2)

A setting unit that sets a setting file that defines the operation of the application executed on the mobile communication terminal according to the movement of the mobile communication terminal according to the parameters for executing the native function peculiar to the mobile communication terminal.
It has a generator that generates an application package based on a project file that includes the configuration file.
The setting unit includes an association unit that associates a plurality of templates that define the operation of the mobile communication terminal with each other, and an operation that accompanies the movement of the mobile communication terminal defined by the plurality of templates that are associated by the association unit. It includes a program update section that sets the plug-in file by updating a part of the template for the plug-in file related to the parameter so that it can be normally performed on the application of the mobile communication terminal.
The project file is an application generation support system that collectively stores the components necessary for constructing the application. A parameter check unit that checks parameters for executing native functions unique to mobile communication terminals,
A setting unit that sets a setting file that defines the operation of the application executed on the mobile communication terminal according to the movement of the mobile communication terminal according to the parameter after the check.
It has a generator that generates an application package based on a project file that includes the configuration file.
The setting unit includes an association unit that associates a plurality of templates that define the operation of the mobile communication terminal with each other, and an operation that accompanies the movement of the mobile communication terminal defined by the plurality of templates that are associated by the association unit. It includes a program update section that sets the plug-in file by updating a part of the template for the plug-in file related to the parameter so that it can be normally performed on the application of the mobile communication terminal.
The project file is an application generation support system that collectively stores the components necessary for constructing the application.

Images