JP2024093620A - Information processing system, control method for information processing system, and program - Google Patents

Abstract

To reduce possibility of a user to overlook that a PWA of application software is available when the PWA is available.SOLUTION: A system includes: recording control means for controlling such that definition information relating to an application is recorded based on a user's operation; generation means for generating specific information to be used for installing a PWA corresponding to the application; and control means for controlling on a screen of the application such that an application to display a specific message prompting the installation of the PWA is constructed.SELECTED DRAWING: Figure 11

Description

This relates to information processing systems, control methods for information processing systems, and programs, and in particular to technologies suitable for use in building application software.

Conventionally, there are no-code/low-code development tools that do not require or require little coding in a programming language, and are application construction tools that construct application software (hereinafter referred to as applications) according to definitions. Patent Document 1 proposes that screen components such as buttons and text boxes can be placed by drag and drop on a layout editor screen for editing the screen of the web application to be constructed, and that the placed screen components are stored in an input/output definition table.

Progressive Web Apps (PWA) technology is also known, which is an application that combines the advantages of both the web and apps, and has the advantages of being able to use push notification functions, being able to operate offline, and being able to display an icon on the home screen. Patent Document 2 proposes using Progressive Web Apps (PWA) technology instead of native apps to enable a mobile website built on a cloud server on the Internet to be used like an app installed on a terminal device 60.

JP 2019-49858 A JP 2022-57113 A

It is possible to provide a pre-built application developed using a no-code development tool/low-code development tool such as that described in Patent Document 1, and a PWA corresponding to the pre-built application. However, there are cases where a user who uses the pre-built application does not realize that a corresponding PWA is available and misses an opportunity to use the PWA.

The present invention aims to provide a mechanism that reduces the likelihood that a user will overlook the fact that a PWA is available when the PWA of application software is available.

The information processing system of the present invention comprises:
a recording control means for controlling recording of definition information relating to an application based on a user's operation;
A generating means for generating specific information used for installing a PWA corresponding to the application;
A control means for controlling the construction of an application that displays a specific message on a screen of the application to prompt the user to install the PWA;
The present invention is characterized by having the following.

According to the present invention, when a PWA of application software is available, it is possible to reduce the possibility that a user will overlook the fact that a PWA is available.

FIG. 1 is a system configuration diagram of an information processing system. FIG. 2 is a hardware block diagram of a developer terminal 100, an application user terminal 200, and an application user terminal 201. 13 is a flowchart of a login process. 13 is a flowchart of a UI editor process. 13 is a display example in login processing and UI editor processing. 13 is a display example of an AppBar in a UI editor process. 13A is a flowchart of a context menu process, and FIG. 13B is a display example of an AppBar property box. 10A is a flowchart of a screen switching process, and FIG. 10B is a display example of an application setting screen. 1A is a flowchart of a save process performed by the development environment 300. FIG. 1B is a flowchart of a deploy process performed by the development environment 300. FIG. 11 is an information transition diagram of UI definition information. 13 is a display example when an application is executed on the application user terminal 201.

The following embodiments are described in detail with reference to the attached drawings. Note that the following embodiments do not limit the invention according to the claims, and not all combinations of features described in the embodiments are necessarily essential to the invention. Two or more of the features described in the embodiments may be combined in any desired manner. In addition, the same reference numbers are used for the same or similar configurations, and duplicate descriptions will be omitted.

The various features shown in the following embodiments can be combined with each other. In the following, "application" and "app" both refer to application software.

<System Configuration>
A system configuration diagram of an information processing system according to an embodiment of the present invention is shown in Fig. 1. Fig. 1 shows a system for developing software and a system for using the developed software.

The developer terminal 100 is an information processing device (information processing terminal) operated by a developer user that can be configured using a personal computer (hereinafter referred to as PC) or a smartphone. In other words, it is a user terminal of the developer user. The developer terminal 100 accepts design operations for an application to be developed from the developer, and transmits various definition information for the application, which is the designed content, to the development environment 300.

The development environment 300 is an environment that uses at least one hardware resource built on a network (on the cloud, on the Internet). The development environment 300 is a multi-tenant environment, into which multiple developer users can log in. The development environment 300 includes developer information 301, an execution engine 302, and storage 320. The development environment 300 is built by combining multiple web services (cloud services).

Developer information 301 is information that records the developer's account that can log in to development environment 300, such as an email address (user ID) that serves as the developer's account ID, and a password. Developer information 301 is recorded on at least one recording medium included in development environment 300.

The execution engine 302 is at least one hardware resource for executing the processing to be executed in the development environment 300, and includes a processor 303 and a memory 304. The processor 303 is composed of at least one processor, and may be a single processor on the cloud, or may be a processor group combining multiple processors. The memory 304 is at least one recording medium on which a program to be executed by the processor 303 is recorded. Among the various flowcharts described below, those described as being executed by the development environment 300 are executed by the execution engine 302. In other words, the program recorded in the memory 304 is expanded by the processor 303 into an area of the development environment 300 that serves as a work memory, and executed.

The distribution engine 305 transmits a client program 322 (such as HTML source code or JavaScript source code) to be executed on the developer terminal 100 to the developer terminal 100 that has accessed the development environment 300. The client program 322 is pre-recorded in the storage 320 included in the development environment 300.

Storage 320 is a memory area of at least one recording medium, and stores at least client programs 322 that are common to each developer. It also has a developer area, which is a memory area for each developer account. For example, if there are developer A, developer B, and developer C who can log in, it includes developer A area 323, which is an area for developer A, developer B area 324, which is an area for developer B, and developer C area 325, which is an area for developer C. Each developer area stores definition information for the apps developed by each developer. For example, app definition 323a is recorded in developer A area 323.

The developer accesses the development environment 300 by accessing the URL for accessing the development environment 300 from the browser software of the developer terminal 100, and logs in to the development environment. When the developer logs in to the development environment, the developer receives the client program 322 and the application definition (UI definition information) that is the content of the past development work and saved from the development environment. Then, the developer performs an operation to design a new application or an operation to update and design an existing (in-progress) application, and sends the resulting application definition information (application definition, UI definition information) to the development environment 300. The development environment 300 saves the received application definition in its developer area. In this way, in this embodiment, any terminal that can access the development environment 300 on the cloud can be used as the developer terminal 100 to design an application. Therefore, as long as there is a terminal that can connect to the Internet, the developer can develop an application regardless of location.

The execution environment 400 is an environment using at least one hardware resource constructed on a network (on a cloud or on the Internet). The execution environment 400 includes a multi-tenant execution environment 410 and multiple single-tenant execution environments (for example, single-tenant execution environments 450, 460, 470). The execution environment 400 is constructed by combining multiple Web services (cloud services). The execution environment 400 is an environment for deploying definition information (application definition) of an application developed using the developer terminal 100 and the development environment 300. The application user terminals 200 and 201 used by users who use the application access the execution environment 400 by accessing a URL for executing the application. The execution environment 400 executes various actions according to operations performed on the application user terminals 200 and 201, thereby executing the developed application and providing the application functions to the application user. The application constructed in the execution environment 400 on the network is a so-called WEB application.

The multi-tenant execution environment 410 is a multi-tenant execution environment shared by multiple developers, and applications developed by multiple developers are deployed in the multi-tenant execution environment 410. In other words, it is an environment shared by multiple developers, and is an environment in which multiple apps by multiple developers can be built. The multi-tenant execution environment 410 includes user information 411, an execution engine 412, a distribution engine 415, storage 420, and a DB set 433.

User information 411 is information that records the account of an app user who can log in to an application, such as an email address (username) that serves as the user account ID for the deployed application (constructed application) and a password. User information 411 is recorded in at least one recording medium included in the multi-tenant execution environment 410.

The execution engine 412 is at least one hardware resource for executing processing to be executed in the multitenant execution environment 410, and includes a processor 413 and a memory 414. The processor 413 is composed of at least one processor, and may be a single processor on the cloud, or may be a processor group combining multiple processors. The memory 414 is at least one recording medium on which a program to be executed by the processor 413 is recorded. Among the various flowcharts described below, those described as being executed by the multitenant execution environment 410 are executed by the execution engine 412. In other words, the processor 413 deploys and executes the program recorded in the memory 414 in an area of the multitenant execution environment 410 that serves as a work memory. The program executed here includes a program that executes the action of an application.

The distribution engine 415 transmits a client program 422 (such as HTML source code or JavaScript source code) to be executed on the application user terminal 200, 201 to the application user terminal 200, 201 that has accessed the multi-tenant execution environment 410. The client program 422 is pre-recorded in the storage 420 included in the execution environment 410.

Storage 420 is a storage area of at least one recording medium, and stores at least a client program 422 that is common to multiple applications. In addition, in a specified area (specified folder, specified bucket, specified level) of storage 420, access destination information 421 for accessing the execution environment (multi-tenant execution environment 410) is recorded. In addition, there is a developer area which is a storage area for each developer account. For example, it includes developer A area 423 which is an area for developer A, developer B area 424 which is an area for developer B, and developer C area 425 which is an area for developer C. In each developer area, definition information of an app developed by each developer and deployed from development environment 300 is stored. For example, app definition 423a is recorded in developer A area 423.

DB set 430 is a group of information about databases used by applications deployed in execution environment 410. DB set 430 is stored in the memory area of at least one recording medium.

Single tenant execution environments 1 (450), 2 (460), and 3 (470) are each execution environments dedicated to one developer (one developer account), and applications developed by the developer who is the owner using the development environment 300 are deployed therein. In this embodiment, as an example, the owner of single tenant execution environment 1 (450) is Developer A, the owner of single tenant execution environment 2 (460) is also Developer A, and the owner of single tenant execution environment 3 (470) is Developer B. In this way, one developer can own multiple single tenant execution environments. Single tenant execution environments 1 (450), 2 (460), and 3 (470) each include user information 451, 461, and 471, execution engines 452, 462, and 472, distribution engines 455, 465, and 475, storage 456, 466, and 476, and DB sets 457, 467, and 477. These have the same functions as the user information 411, execution engine 412, delivery engine 415, storage 420, and DB set 433 of the multi-tenant execution environment 410 described above, except that they are dedicated to one developer, so detailed explanations will be omitted. It is possible to build many more single-tenant execution environments than the three shown in the figure.

Using the system of FIG. 1, for example, an operator could provide the multi-tenant execution environment 410 to developers free of charge and the single-tenant execution environment for a fee. The operator of this system must pay maintenance costs to the resource and service provider (cloud service operator) for both the multi-tenant execution environment 410 and each single-tenant execution environment. By having the operator bear the maintenance costs of the multi-tenant execution environment 410 and provide it free of charge to multiple developers, developers do not need to bear the costs for trialing the system, making it easy for many developers to use and promoting the spread of the system. The operator recovers costs by charging developers for the single-tenant execution environments.

There is an upper limit to the number of processing requests that can be processed per unit time in one execution environment, and if many applications are built in a multi-tenant execution environment and many app users access it simultaneously, it is possible that the requests cannot be processed and the applications may run slowly. In addition, there are some restrictions on the deployment and execution of many applications developed by many developers in a multi-tenant execution environment, and these restrictions may prevent the applications from performing adequately. If developers pay to own a dedicated single-tenant execution environment, they can avoid (or reduce) problems caused by the restrictions of such multi-tenant execution environments. In other words, by building applications in a single-tenant execution environment, applications that perform adequately can be built.

Considering the characteristics of both the multi-tenant execution environment and the single-tenant execution environment, developers can use this system as follows. For example, when using this system for the first time, developers can build an application developed using this system in the multi-tenant execution environment 410 and test it, and then, if they determine that this system is useful for the developer's software development, they can introduce the single-tenant execution environment for a fee. Also, when a developer develops a specific application X, an alpha version of application X is built in the multi-tenant execution environment 410 for a limited number of test users to try out before releasing it to general users. There, application X is tested, and modifications are made to application X, and further development is carried out. Then, after the development is completed to a level where it can be released to general users without any problems, a production version of application X is built in the single-tenant execution environment and released to general users. By using it in this way, developers can reduce development costs during the development period and operate applications that can be used by a large number of general users without any problems.

Figure 2 shows a hardware block diagram of an information processing device as an example of a device (electronic device) applicable as developer terminal 100, application user terminal 200, and application user terminal 201. In Figure 2, CPU 101, memory 102, non-volatile memory 103, image processing unit 104, display 105, operation unit 106, recording medium I/F 107, external I/F 109, and communication I/F 110 are connected to internal bus 150. Each unit connected to internal bus 150 is capable of exchanging data with each other via internal bus 150.

The memory 102 is, for example, a RAM (such as a volatile memory using semiconductor elements). The CPU 101 uses the memory 102 as a work memory to control each part of the information processing device according to a program stored in, for example, the non-volatile memory 103. The non-volatile memory 103 stores image data, audio data, other data, various programs for the operation of the CPU 101, and the like. The non-volatile memory 103 is, for example, composed of a hard disk (HD) or ROM.

Based on the control of the CPU 101, the image processing unit 104 performs various image processing on image data stored in the non-volatile memory 103 or the recording medium 108, video signals acquired via the external I/F 109, image data acquired via the communication I/F 110, captured images, etc. The image processing performed by the image processing unit 104 includes A/D conversion processing, D/A conversion processing, image data encoding processing, compression processing, decoding processing, enlargement/reduction processing (resizing), noise reduction processing, color conversion processing, etc. The image processing unit 104 may be configured with a circuit block dedicated to performing specific image processing. Also, depending on the type of image processing, it is possible for the CPU 101 to perform image processing according to a program without using the image processing unit 104.

Under the control of CPU 101, display 105 displays images and GUI screens constituting a GUI (Graphical User Interface). CPU 101 generates a display control signal according to a program, and controls each part of the information processing device to generate a video signal for display on display 105 and output it to display 105. Display 105 displays an image based on the output video signal. Note that the configuration of the information processing device itself is limited to an interface for outputting a video signal for display on display 105, and display 105 may be configured as an external monitor (such as a television). Hereinafter, unless otherwise specified, the display destination in the processes executed by developer terminal 100, application user terminal 200, and application user terminal 201 is assumed to be the display 105 of each operator.

The operation unit 106 is an input device for receiving user operations, including a character information input device such as a keyboard, a pointing device such as a mouse or a touch panel, a button, a dial, a joystick, a touch sensor, a touch pad, etc. The touch panel is an input device that is configured as a planar panel overlaid on the display 105 and outputs coordinate information according to the touched position.

The recording medium I/F 107 allows a recording medium 108 such as a memory card, CD, or DVD to be attached, and reads data from the attached recording medium 108 and writes data to the recording medium 108 based on the control of the CPU 101. The external I/F 109 is an interface that connects to an external device via a wired cable or wirelessly, and inputs and outputs video signals and audio signals. The communication I/F 110 is an interface that communicates with an external device, the Internet 111, etc., and transmits and receives various data such as files and commands. The developer terminal 100 can communicate with the development environment 300 on the Internet 111 (can transmit and receive information) using the communication I/F 110. The application user terminals 200 and 201 can communicate with the execution environment 400 on the Internet 111 (can transmit and receive information) using the communication I/F 110.

<Login process>
3A and 3B show flow charts of the login process. This process is a process from logging in to the development environment 300 from the developer terminal 100 to displaying a UI editor. When the developer terminal 100 starts the Internet browser software and receives an instruction to access the development system (application development platform) of this embodiment by specifying the URL, the process of FIG. 3A is started. The process of FIG. 3A is realized by the CPU 101 of the developer terminal 100 expanding a program recorded in the non-volatile memory 103 for executing the Internet browser software and a client program 322 received from the development environment 300 in the memory 102 and executing them. Hereinafter, what is simply described as a process executed by the developer terminal 100 is assumed to be a process in which the CPU 101 of the developer terminal 100 expands a program recorded in the non-volatile memory 103 for executing the Internet browser software and a client program 322 received from the development environment 300 in the memory 102 and executes them.

When an Internet browser software is launched on the developer terminal 100 and the URL of the development system (application development platform) of this embodiment is specified and accessed, the distribution engine 305 of the development environment 300 detects the access and transmits the client program 322 to the developer terminal 100 that is the source of the access.

In S301, the developer terminal 100 determines whether or not it has received the client program 322 sent from the development environment 300. If it has not been received, it waits for reception in S301, and if it has been received, it proceeds to S302.

In S302, the developer terminal 100 records the client program 322 received from the development environment 300 in memory 102.

In S303, the developer terminal 100 displays a login screen on the display 105 in accordance with the client program 322. The login screen displays a message indicating that this is a login screen for the development system of this embodiment, as well as fields for inputting a developer ID and password, a new registration button (icon), and a login button (icon).

In S304, the developer terminal 100 accepts input operations into the input fields of the login screen for the developer ID and password. The user's input operations are performed using the operation unit 106. The developer ID is user identification information for identifying (specifying) the developer user. In this embodiment, the developer ID (user name) is an email address. In addition, the password used as the secret information is an arbitrary character string, but it may be other secret information such as biometric authentication information (fingerprint authentication is information used for face authentication) or pattern authentication information (information of the trajectory pattern entered on the screen).

In S305, the developer terminal 100 determines whether an operation has been performed (e.g., a click) to instruct the New Registration button on the login screen. Note that hereinafter, an operation to instruct a display item (a display object such as a button or icon, a display item) by clicking with the mouse included in the operation unit 106 or by touching the touch panel will be referred to simply as "pressing". If the New Registration button has been pressed, proceed to S306; if not, proceed to S307.

In S306, the developer terminal 100 performs a developer account registration process. The developer account registration process is a process for registering information about a new account in the developer information 301.

In S307, the developer terminal 100 determines whether the login button on the login screen has been pressed. If the login button has been pressed, the process proceeds to S308; if not, the process returns to S304.

In S308, the developer terminal 100 transmits the information entered in the developer ID and password input fields on the login screen (the entered developer ID and password) as login information to the development environment 300. After transmission, an authentication process is performed in the development environment 300, and the result is awaited.

In S309, the developer terminal 100 determines whether or not it has received information about a login error from the development environment 300. If it has received information about a login error, it returns to S304 to accept the input of login information again, and if not, it proceeds to S310.

In S310, the developer terminal 100 determines whether or not it has received an execution environment list from the development environment 300. If the login authentication is successful, the development environment 300 sends the execution environment list to the developer terminal 100, so receiving the execution environment list means that the login authentication was successful (login was successful). If the execution environment list has been received, proceed to S311; if not, return to S309.

In S311, the developer terminal 100 records the execution environment list received in S310 in memory 102 as the development screen for the app after login, and displays execution environment options based on the received execution environment list on the display 105. The execution environment list indicates the execution environments that the logged-in developer can access. Note that screens displayed on the developer terminal 100 after S311 that are different from the screen of the constructed app are collectively referred to as development screens.

Figure 5 (a) shows an example of the display of execution environment options in S311. In the display example of Figure 5 (a), two options are displayed as execution environments that the logged-in developer can access: option 551 corresponding to the multi-tenant execution environment 410, and option 552 corresponding to the single-tenant execution environment. The developer user can select one of these options by pressing it, and confirm the selection by pressing the SAVE button 553. What is selected here is the destination to which the application updated in the subsequent work during this login will be deployed. The execution environment is not accessed at this point. Furthermore, the execution environment selected here can be changed by the operation described below.

In S312, the developer terminal 100 determines whether an execution environment has been selected. If one of the execution environment options has been pressed and the SAVE button 553 has been pressed, the process proceeds to S313; otherwise, the process waits for the selection of an execution environment in S312.

In S313, the developer terminal 100 records information (such as the execution environment ID) that identifies the execution environment selected in S312 in memory 102 as the "selected execution environment" and transmits it to the development environment 300. In response to receiving the information that identifies the selected execution environment (selected environment), the development environment 300 transmits, as app information, information (such as the app ID and app name) that identifies all applications owned by the logged-in developer (applications that have been generated in the past and recorded in storage 320).

In S314, the developer terminal 100 determines whether or not app information has been received from the development environment 300. If app information has been received, the process proceeds to S315; if not, the process waits for reception of app information in S314.

In S315, the developer terminal 100 records the received app information in memory 102 and displays a list of applications (app list) owned (under development) by the logged-in user on the display 105 based on the app information.

In S316, the developer terminal 100 determines whether any application has been selected from the list of applications displayed in the app list. If any application has been selected, the process proceeds to S317; if not, the process proceeds to S320.

At S317, the developer terminal 100 records information identifying the selected app (such as the app ID and app name) in memory 102 as the "selected app" for the application selected from the app list, and transmits the information to the development environment 300. When the development environment 300 receives the information identifying the selected app, it obtains definition information (app definition) for the selected app from the area of storage 320 for the logged-in developer, and transmits the information to the developer terminal 100.

In S318, the developer terminal 100 determines whether or not it has received definition information (UI definition information) of the selected application from the development environment 300. If it has received definition information of the selected application, it records the received definition information of the selected application in memory 102 and proceeds to S319, otherwise, it waits for the reception of definition information in S318. In this embodiment, this definition information is a Json file in which various definitions related to the application are described in Json format. Thereafter, when the selected application is displayed on the display 105, it is displayed based on the definition information recorded in memory 102. When an operation to update the selected application (for example, changing the layout of UI parts) is performed in a UI editor process described later, the definition information in memory 102 is updated to define the updated content. Then, when a save instruction is given, the latest definition information recorded in memory 102 is sent to the development environment 300 and saved in the login developer's area of the storage 320. In this way, an increase in the frequency of communication with the development environment 300 is suppressed, and a decrease in response due to communication is suppressed, allowing for comfortable update work.

In S319, the developer terminal 100 displays a UI editor screen on the display 105 and displays based on the received definition information. For example, a canvas (editing area of the UI screen) with a shape according to whether the selected application is for desktop or mobile (i.e., a shape according to the type of device using the application) is displayed. If it is for desktop, a rectangular canvas with a ratio of 16:9 is used, and if it is for mobile, a canvas with a vertical aspect ratio imitating a smartphone is used. In the submenu area (described later), a list of UI screens that the selected application has (belongs to the selected application) is displayed (this process is strictly performed in S401 in FIG. 4 described later). In addition, the canvas displays components (UI parts to be placed on the UI screen) that are placed on the UI screen selected by default (initial UI or the UI screen that was edited when last saved). Note that the UI screen to be edited may not be selected by default, and nothing may be displayed on the canvas at this point. The login process is terminated in the process of S319, and the process proceeds to S401 in FIG. 4.

On the other hand, in S320, the developer terminal 100 determines whether an icon (a + mark, not shown) for creating a new application displayed on the screen displaying the list of apps has been pressed, instructing the creation of a new application. If it determines that a command has been issued to create a new application, the process proceeds to S321, and if not, the process returns to S316.

In S321, the developer terminal 100 displays a selection screen for whether the newly created application is for desktop (PC) or mobile use, and accepts an operation to select one of them. A desktop application is an application that is intended to be accessed and operated from an app user terminal 200 such as a desktop PC or notebook PC. A mobile application is an application that is intended to be accessed and operated from an app user terminal 201 such as a smartphone.

In S322, the developer terminal 100 displays a screen for accepting input of basic app information (at least the app name and app ID) for the newly created application, and accepts input operations to set the app information. When the input of the app information is accepted, the information on whether the application is for desktop (PC) or mobile, accepted in S321, and the app information accepted in S322 are sent to the development environment 300. In this way, definition information for the new application is created in the storage 320 of the development environment 300 as definition information for the newly created application, and the information on whether the application is for desktop (PC) or mobile, the app name, and the app ID are recorded. In this way, the information on whether the application is for desktop (PC) or mobile, the app name, and the app ID are also recorded in the definition information of applications that have already been created in the past.

In S323, the developer terminal 100 displays a UI editor screen as an editing screen for the newly created application. In this case, the canvas is displayed in a shape according to whether it is for desktop or mobile use, selected in S321. The canvas is also displayed as blank information with no components placed on it. The login process ends in the process of S323, and the process proceeds to S401 in FIG. 4.

Figure 3(b) shows the login process on the development environment 300 side, which cooperates with the login process on the developer terminal 100 side in Figure 3(a). The process in Figure 3(b) is realized by the processor 303 of the development environment 300 expanding and executing a program recorded in memory 304 in an area of the development environment 300 that serves as a work memory. Hereinafter, what is simply described as a process executed by the development environment 300 is assumed to be a process executed by the execution engine 302 of the development environment 300, or more specifically, by the processor 303.

In S331, the development environment 300 determines whether or not the login information sent from the developer terminal 100 in S308 has been received. If the login information has been received, the process proceeds to S332; if not, the process waits for the login information to be received.

In S332, the development environment 300 compares the received login information with the developer information 301 and performs login authentication (user authentication). More specifically, it determines whether the developer information 301 (user information) contains information that matches the developer ID and password pair contained in the received login information. If so, authentication is successful.

In S333, the development environment 300 determines whether the result of the authentication process in S332 is that login is OK (authentication was successful, was authenticated, authentication is OK). If login is OK, the process proceeds to S335, and if login is not OK, the process proceeds to S334 and sends information to the developer terminal 100 indicating that there is a login error.

In S335, the development environment 300 transmits to the developer terminal 100 a list of execution environments of the developer (login developer) whose login has been approved and is included in the developer information 301. In addition to the email address (username, developer ID) and password, the developer information 301 records the accessible execution environment ID for each developer. Each execution environment ID is an account ID in a cloud service (Web service), and is a 12-digit ID in this embodiment. In the case of a developer who can access multiple execution environments, the 12-digit execution environment ID is recorded separated by a comma. In S335, the accessible execution environment ID (one or more execution environment IDs separated by a comma) for the login developer is transmitted to the developer terminal 100. That is, in S335, the execution environment that the login developer can access is specified by referring to the developer information 301. In this way, the accessible execution environment of each developer (the execution environment that each developer can use) is recorded in the developer information 301 recorded in the development environment 300. This execution environment that can be logged in can only be obtained by the developer who has been granted permission to log in. Furthermore, only the execution environment that can be accessed by the developer who has been granted permission to log in can be obtained. In this way, the developer does not need to manage information for accessing the execution environment that can be accessed by the developer separately from information for logging in to the development environment 300. It is also possible to prevent other users from illegally accessing the execution environment.

In S336, the development environment 300 determines whether or not it has received information (environment identification information) that identifies the selected execution environment transmitted from the developer terminal 100 in S313. If it has received information that identifies the selected execution environment, it proceeds to S337; if not, it waits for reception of information that identifies the selected execution environment.

In S337, the development environment 300 records the selected execution environment in a settings management file stored in the logged-in developer area of storage 320 based on the information identifying the selected execution environment received in S336.

In S338, the development environment 300 retrieves app information indicating all applications owned by the logged-in developer (created by the logged-in developer) from the logged-in developer's area in storage 320, and transmits this information to the developer terminal 100. The app information transmitted here is only the app definition information necessary to display the list of apps mentioned above in S315, and does not include detailed definition information about each app (such as information indicating the placement and actions of components).

In S339, the development environment 300 determines whether information about the new app (information including whether it is for desktop (PC) or mobile use, the app name, and the app ID) that was sent from the developer terminal 100 in S322 has been received. If information about the new app has been received, the process proceeds to S340; if not, the process proceeds to S341.

In S340, the development environment 300 creates and records definition information for a new application in the login developer's area of the storage 320 based on the information on the new application received in S339. The definition information recorded here includes information on whether the application is for desktop (PC) or mobile use, the application name, and the application ID. In the development environment 300, in order to distinguish the application from applications of other users in the multi-tenant execution environment 410, an eight-digit developer code that uniquely corresponds to the developer ID of the developer who owns the application is added immediately before the ID input by the developer in S322 as the application ID and recorded. Then, the login process ends. After this, when performing internal processing or when displaying in a programming language on the action board, if an application ID is used, the process is performed with the ID to which the developer code of the login developer is added. In addition, when displaying as an application ID in a UI editor, etc., only the ID part input by the developer in S322 is displayed, excluding the developer code.

In S341, the development environment 300 determines whether or not information identifying the selected app transmitted from the developer terminal 100 in S317 has been received. If information identifying the selected app has been received, the process proceeds to S342; otherwise, the process returns to S339.

In S342, the development environment 300 retrieves definition information (app definition) for the selected app from the logged-in developer's area of storage 320 based on the information identifying the selected app received in S341, and transmits the information to the developer terminal 100. The definition information transmitted here includes detailed definition information about the selected app (such as information indicating the placement and actions of components). Then, the login process ends.

<UI Editor Processing>
The UI editor process is described below with reference to Fig. 4 and Fig. 5B. The UI editor process is a process for performing various definitions (UI part definitions, action definitions) of an application to be constructed in response to operations by a developer (user) on a UI editor screen (application development screen).

Figure 5(b) shows an example of a layout editing screen displayed by the UI editor process on the display 105. The screen in Figure 5(b) includes a header menu area 500, a main menu area 510, a sub-menu area 520, and a canvas 530 (an editing reception area of the UI screen).

The header menu area 500 displays a selected execution environment box 501, a selected app box 502, a selected UI screen box 503, a save button 504, a preview button 505, and a deploy button 506.

The selected execution environment box 501 displays the selected execution environment ID as information representing the selected execution environment. By pressing the arrow icon on the right end of the selected execution environment box 501, a list of execution environments accessible to the logged-in developer obtained in S310 is displayed as a pull-down menu, and the selected execution environment can be changed by selecting any execution environment from the list. Even if the selected execution environment is changed, the selected app does not change, and the contents displayed in the main menu area 510, submenu area 520, and canvas 530 do not change. In this way, by changing the selected execution environment to which the same application is to be deployed, it is possible to deploy the same application to any number of execution environments.

The selected app box 502 displays the name of the selected app as information representing the selected app. By pressing the arrow icon on the right end of the selected app box 502, a list of apps owned by the logged-in developer obtained in S314 is displayed as a pull-down menu, and the selected app can be changed by selecting any app from the list. When the selected app is changed, the content to be displayed in the submenu area 520 and the canvas 530 changes.

The selected UI screen box 503 displays the name of the UI screen being edited as information representing the UI screen being edited in the canvas 530. By pressing the arrow icon in the selected UI screen box 504, a list of UI screens belonging to the selected app based on the definition information of the selected app acquired in S318 is displayed as a pull-down menu, and the UI screen to be edited and displayed on the canvas 530 can be changed by selecting any UI screen from the list.

In the main menu area 510, an app list button 511, a UI screen button 512, a workflow button 513, a settings button 514, an environment list button 515, a database button 516, a file manager button 517, a user management button 518, and a snapshot button 519 are displayed as option icons for the menu items of the main menu. The processing in response to pressing these options will be described later in the screen switching processing of FIG. 8(a).

The submenu area 520 displays a submenu corresponding to the item selected in the main menu. In the example of FIG. 5(b), a UI component list (UI part list) is displayed as a lower-level menu of the UI screen button 512.

The canvas 530 is a layout editing area for the selected UI screen of the selected application (the UI screen of the UI screen name displayed in the selected UI screen box 503). The canvas 530 in FIG. 5B is an example of a canvas display for a desktop application, and is displayed in a desktop shape. The user can select any UI part (UI component) from the UI parts list displayed in the submenu area 520 and place it in the canvas area 530 by dragging and dropping it. The size and position of the UI part placed in the canvas area 530 can be adjusted by selecting it. In addition, by selecting a UI part placed in the canvas area 530 and right-clicking it to display a right-click menu (context menu), more detailed settings such as color scheme can be made. Furthermore, by selecting an action also included in the context menu, an action board is displayed, and an action to be executed when the UI part is operated can be set. By right-clicking with the cursor in a blank area of the canvas 530, the canvas's context menu can be displayed, and by selecting an action from the menu, it is possible to set the action to be executed when the UI screen of that canvas is loaded in the constructed application (to be executed when the UI screen is displayed).

Figure 5 (b) shows an example in which a pie chart 531, a button 532, text fields 533 and 534, an output field 535, and a tab component 536 are arranged as UI components on a canvas 530 with a UI screen name "ui1" of an application with an application name "UI1". Operation path 531a is a selection frame indicating the selected UI component and an operation path (operation handle) that accepts zoom instructions, and indicates that pie chart 531 is selected.

Figure 4 shows a flowchart of the UI editor process. This process is executed by the developer terminal 100 and follows S319 or S323 in Figure 3.

In S401, the developer terminal 100 displays a list of UI screens of the selected app as options in the submenu area 520 based on the definition information of the selected app. Each screen displayed in this UI screen list is designed as a screen to be displayed when the selected app is deployed and constructed in an execution environment, and is accessed from the app user terminal 200, 201 and executed. This UI screen list can also accept operations to add new UI screens and delete UI screens.

In S402, the developer terminal 100 determines whether an operation to select any of the UI screens from the list of UI screens displayed in S401 has been performed. If any of the UI screens has been selected, the process proceeds to S404; otherwise, the process proceeds to S403.

In S403, it is determined whether or not an operation to select any of the options displayed in the main menu area 510 has been performed. If an option displayed in the main menu area 510 has been selected, the UI editor process ends and the process proceeds to the screen switching process described later with reference to FIG. 8(a). If not, the process returns to S402.

In S404, the developer terminal 100 displays the UI screen selected in S402 on the canvas 530 based on the definition information of the selected application recorded in the memory 102. If the UI screen has UI parts previously placed on it, the UI parts previously placed according to the definition information are displayed on the canvas 530. In other words, if the UI screen was created only partially in the past, it is possible to continue development. If the UI screen selected in S402 is a newly created UI screen, the canvas 530 is displayed blank with no UI parts placed on it. If the UI screen selected in S402 is a UI screen (template screen) that has been prepared in advance as a template, a template component with a predetermined action defined is displayed in a predetermined position on the canvas 530, even if the user has not previously placed UI parts on that UI screen.

In S405, the developer terminal 100 displays a list of UI parts in the submenu area 520. That is, the display is switched from the UI screen list of the selected application to the UI parts list. UI parts that can be arranged on the canvas 530 include types INPUT, Button, Display (information display part), Navigation, Layout, and Chart, and multiple UI parts are classified into each type. In the UI parts list, first, as shown in FIG. 5(c), a list of UI part types is displayed, and in response to an operation to select one of the displayed types, UI parts classified into the selected type are expanded and displayed. The above-mentioned FIG. 5(b) is an example in which the option 522 of the type corresponding to INPUT is selected and a list of UI parts classified into INPUT is displayed. UI parts classified into INPUT include, for example, a text field 523 and a text area 524. The submenu area 520 is scrollable, and options that cannot be displayed (options for the UI part of the expanded type and options for other types) can be scrolled to display them. When an option 522 for an expanded type is operated as in FIG. 5(b), the list of UI parts of the expanded type is collapsed, and a list of UI part types is displayed.

In S406, the developer terminal 100 determines whether or not a UI part displayed in the submenu area 520 has been selected. More specifically, it determines whether or not an operation to drag the UI part displayed in the submenu area 520 has been performed. If a UI part displayed in the submenu area 520 has been selected, the process proceeds to S407; if not, the process proceeds to S411.

In S407, the developer terminal 100 determines whether an operation to specify a position on the canvas 530 has been performed. More specifically, it determines whether an operation to drop the dragged UI part onto the canvas 530 has been performed. If an operation to specify the canvas 530 has been performed, the process proceeds to S408, and if not, the process waits for the specification of a position on the canvas 530 in S407. Note that, although an example of drag and drop is described in this embodiment, the operation method is not limited to this as long as it is an operation to select a UI part from the submenu area 520 and place it at a specified position on the canvas 530.

In S408, the developer terminal 100 determines whether the UI component dropped in S407 was an AppBar (application bar). If it was an AppBar, the process proceeds to S410; if not, the process proceeds to S409.

In S409, the developer terminal 100 places the UI part selected in S406 from the submenu area 520 at the specified position on the canvas 530 at a default size, and records information defining this in the definition information recorded in memory 102. That is, in the definition information, the type of UI part placed in S410, the UI part ID, placement coordinates, placement size, etc. are associated with the ID of the destination UI screen (the UI screen being edited) and recorded.

In S410, the developer terminal 100 refers to the application settings included in the definition information acquired from the development environment 300 and stored in the memory 102, and determines whether or not PWA (Progressive web apps) is set to on. If PWA is set to on, the process proceeds to S411, and if not, the process proceeds to S412.

In S411, the developer terminal 100 places the AppBar containing the PWA installation item in a predetermined position on the canvas 530 (in this embodiment, the top of the UI screen) regardless of the position specified in S407, at a default size, and records the information defining this in the definition information stored in memory 102.

In S412, the developer terminal 100 places an AppBar without a PWA installation item in a predetermined position on the canvas 530, regardless of the position specified in S407, at a default size, and records information defining this in the definition information stored in memory 102.

Figures 6(a) and 6(b) show display examples when an AppBar is placed. Figure 6(a) shows an example when UI components AppBar 650, TextField 661, and Button 662 are placed on canvas 530. AppBar 650 is a single UI component, and contains an element icon 651. In the constructed application, element icon 651 is a display item that accepts instructions for displaying a drawer menu.

When the position of the element icon 651 of the placed AppBar 650 is clicked, the operation path 650a for the AppBar 650 is displayed (S414) and the drawer menu is displayed as an element screen. This causes a transition from the display state of FIG. 6(a) to the display state of FIG. 6(b). In FIG. 6(b), the operation path 650a for the AppBar 650 is displayed, and the drawer menu 651a, which is the element screen corresponding to the element icon 651, is displayed. The drawer menu 651a is an area that is displayed by pulling it out from the left edge of the screen to the right, and displays one or more menu items. As a menu item included in this drawer menu 651a, if the PWA setting is on, the PWA installation item 652 is displayed, and if the PWA setting is off, the PWA installation item 652 is not displayed. When the PWA installation item 652 is pressed in the constructed application, the application user terminal 201 displaying the constructed application screen is controlled to download and install the corresponding PWA. The AppBar is a UI part located at the top of the application, and shortcuts to frequently used functions of the application and navigation to various functions are displayed in a drawer menu. Therefore, when an application user performs some operation related to the application, the user is likely to first open the AppBar drawer menu. Therefore, by displaying the PWA installation item 652 as one of the options displayed in this drawer menu along with options corresponding to multiple screens or multiple functions of the application, the user can be made more reliably aware that a PWA is available for use.

In S413, the developer terminal 100 determines whether a UI component already placed on the canvas 530 has been selected by clicking or the like. If a UI component already placed has been clicked (selected), the process proceeds to S414; if not, the process proceeds to S415.

In S414, the developer terminal 100 displays an operation path for the UI component clicked in S413. Examples of operation path displays are the above-mentioned operation path 531a and operation path 601a.

In S415, the developer terminal 100 determines whether or not an operation to drag an already placed UI component on the canvas 530 has been performed. If an operation to drag an already placed UI component has been performed, the process proceeds to S416; if not, the process proceeds to S417. In S416, the developer terminal 100 changes the position of the dragged UI component (selected component) in response to the drag operation. Specifically, it places it at the dropped position. When the position is changed, the definition information recorded in memory 102 is also updated to indicate the changed position.

In S417, the developer terminal 100 determines whether or not an operation has been performed on the operation path of a UI component already placed on the canvas 530. If an operation has been performed on the operation path, the process proceeds to S418; if not, the process proceeds to S419. In S418, the developer terminal 100 changes the size of the UI component (selected component) to which the operation path has been assigned in response to the operation on the operation path. When the size is changed, the definition information recorded in memory 102 is also updated to indicate the changed size.

In S419, the developer terminal 100 determines whether or not an instruction operation (in this embodiment, a right click of the mouse) to display a context menu has been performed in any area of the canvas 530. If a right click has been performed, the process proceeds to S420, and if not, the process proceeds to S421. In S420, a context menu (right click menu) is displayed according to the position of the mouse cursor when the right click has been performed, and a context menu process is performed to perform a process according to the operation on the context menu. For example, if a right click is performed with the mouse cursor on the button 532 in FIG. 5(b), a context menu 540 related to the button 532 (designated UI part) as shown in FIG. 5(d) is displayed. The context menu 540 displays properties 541, actions 542, and delete 543 as menu items to be selected. When properties 541 is selected, a property box (detailed settings dialog) related to the button 532 is displayed, and detailed settings such as the button name (label) to be displayed on the button 532, the color of the button 532, and the size specified by a numerical value can be performed. When action 542 is selected, an action board related to button 532 is displayed, and an action can be input to the action board in JavaScript, a programming language. The action input here is the process to be executed when button 532 (designated UI component) is pressed in the constructed application. When delete 543 is selected, button 532 is deleted (removed) from canvas 530. Details of the context menu process will be described later with reference to FIG. 7(a).

In S421, the developer terminal 100 determines whether the Save button 504 has been pressed. If the Save button 504 has been pressed, the process proceeds to S422; if not, the process proceeds to S423. In S422, the developer terminal 100 transmits the definition information of the application being edited that is recorded in memory 102 to the development environment 300.

In S423, the developer terminal 100 determines whether the preview button 505 has been pressed. If it is determined that the preview button 505 has been pressed, the process proceeds to S424, and if not, the process proceeds to S425. In S424, the developer terminal 100 performs a preview process. In the preview process, the canvas 503 is hidden, and a preview is displayed of the UI screen being edited in the canvas 503 based on the definition information recorded in the memory 102 or the definition information recorded in the development environment 300, so that the UI screen will look the same as if the UI screen were viewed in the constructed application. In the preview, the operation path for operating the UI parts is not displayed. In addition, some operations that are not performed on the UI editor screen (not performed by operations on the canvas 530) are performed in the preview. For example, when a UI part for screen transition or a link part is operated, a screen transition or a transition to a link destination is performed. In addition, an operation such as moving a selection frame for an item by operating the tab key on the keyboard is also performed. Note that actions entered by the developer in the action boat and database references will not be performed. Instead, the preview process can be displayed faster than if you were to actually deploy and check the results.

In S425, the developer terminal 100 determines whether the deploy button 506 has been pressed. If the deploy button 506 has been pressed, the process proceeds to S426; if not, the process proceeds to S427. In S426, the developer terminal 100 sends a deploy request to the development environment 300 to instruct the development environment 300 to deploy.

In S427, the developer terminal 100 determines whether an operation to change the selected execution environment has been performed. Specifically, it determines whether an operation to change the selected execution environment has been performed on the selected execution environment box 501. If an operation to change the selected execution environment has been performed, the process proceeds to S428; if not, the process proceeds to S429. In S428, the developer terminal 100 records information identifying the selected execution environment (such as an execution environment ID) in memory 102 as the "selected execution environment" and transmits the information to the development environment 300. The developer terminal 100 also updates the display content of the selected execution environment box 501 to represent the changed selected execution environment. When the development environment 300 receives the information identifying the selected execution environment, the development environment 300 records the selected execution environment in a file for setting management stored in an area for the logged-in developer in storage 320 based on the information.

In S429, the developer terminal 100 determines whether an operation to change the application to be edited has been performed. Specifically, it determines whether an operation to change the selected app has been performed in the selected app box 502. If an operation to change the selected app has been performed, the process proceeds to S317 in FIG. 3, and the process from S317 onwards is executed based on the changed selected app. That is, the display contents of the submenu area 520 and the canvas 530 are updated. If an operation to change the selected app has not been performed, the process proceeds to S430.

In S430, the developer terminal 100 determines whether or not an operation to change the UI screen to be edited has been performed. Specifically, it determines whether or not an operation to change the selected UI screen has been performed for the selected UI screen box 503. If an operation to change the selected UI screen has been performed, the process proceeds to S404, and processing is performed based on the changed selected UI screen. In other words, the display content of the canvas 530 is updated (switched) to the content of the changed selected UI screen. If no operation to change the selected UI screen has been performed, the process proceeds to S431.

In S431, the developer terminal 100 determines whether or not an operation has been performed to select any of the options displayed in the main menu area 510. If an option displayed in the main menu area 510 has been selected, the UI editor process ends and the process proceeds to the screen switching process described later in FIG. 8(a). If not, the process returns to S406.

<Context menu processing>
7A shows a flowchart of the context menu process, which is a detailed flowchart of S420 in FIG.

In S701, the developer terminal 100 determines whether the context menu to be displayed is related to a UI part of the button type. More specifically, it determines whether the type of the UI part (specified UI part) specified with the mouse when the right-click was accepted in S419 is a button. If it is a button, the process proceeds to S710, and if not, the process proceeds to S702.

In S702, the developer terminal 100 determines whether the context menu to be displayed is related to the canvas. More specifically, it determines whether the position designated by the mouse when the right-click was accepted in S419 was a blank area of the canvas 530 where no UI components were placed. If it is a blank area (if the context menu to be displayed is related to the canvas), the process proceeds to S703; otherwise, the process proceeds to S704.

In S703, the developer terminal 100 performs canvas context menu processing.

In S704, the developer terminal 100 determines whether the context menu to be displayed is related to a UI part of the AppBar type. More specifically, it determines whether the type of the UI part (specified UI part) specified with the mouse when the right-click was accepted in S419 is an AppBar. If it is an AppBar, the process proceeds to S705, and if not, the process proceeds to S709.

In S705, the developer terminal 100 displays the AppBar context menu. The AppBar context menu includes a properties item.

In S706, the developer terminal 100 determines whether an operation to select a property item has been performed in the context menu of the AppBar. If an operation to select a property item has been performed, the process proceeds to S707; if not, the process proceeds to S708.

In S707, the developer terminal 100 displays the AppBar property box (detailed settings dialog) and accepts various setting operations for the property box (setting operations related to the AppBar, which is the specified UI component).

Figure 7 (b) shows an example of the possession of the AppBar property box 730. The AppBar property box 730 includes a setting item for DRAWER ITEMS, and when a setting item for DRAWER ITEMS is selected, a dialog box 740 for setting the DRAWER ITEMS is popped up and displayed in a superimposed manner. The dialog box 740 is a screen for setting the DRAWER ITEMS (menu items included in the drawer menu), and displays a list of menu items that have already been set to be displayed in the drawer menu in a table format. In the illustrated example, Item1 and Item2 are items that have been set to be displayed as menu items in the AppBar drawer menu. For each item, ID 741, ICON 742, LABEL 743 (the name to be displayed), click event 744, and NEXT UI 745 (the UI screen to which the item transitions in response to being clicked) can be set. When the PWA setting is on and the PWA installation item 652 is set to be placed, the items corresponding to the PWA installation item 652 are listed and displayed in the dialog box 740. Note that, for the PWA installation item 652, a prefix character string is added to the ID to identify it as a PWA installation item, and the prefix character string cannot be changed. Also, the click event 744 and the NEXT UI 745 cannot be changed. This is because the PWA installation item 652 is automatically set with a click event in which the application user terminal 201 displaying the screen of the constructed application downloads and installs the corresponding PWA. For the PWA installation item 652, the ICON 742 and the LABEL 743 can be changed. That is, the appearance (display form) of the PWA installation item 652 can be changed. When the PWA setting is on and the PWA installation item 652 is set to be placed, it is also possible to set it to delete the PWA installation item 652 (not to display it in the AppBar drawer menu). As will be described later, if an installation component is placed in the initial UI, the PWA installation item is not necessarily required in the AppBar drawer menu.

When the setting is for a mobile app, the PWA setting is off, and the PWA installation item 652 is not arranged, the item addition button 746 included in the dialog box 740 may be pressed to add the PWA installation item 652 and turn on the PWA setting. In this case, when the operation to add the PWA installation item 652 is performed, a confirmation display may be displayed to notify and confirm that the PWA setting will be turned on in the app settings (the setting is performed by the processing of S810 to S819 in FIG. 8(a) described later), and in response to an operation to approve from the user, the PWA installation item 652 may be added and the PWA setting may be turned on.

In the case where the setting is for a mobile app, the PWA setting is off, and the PWA installation item 652 is not arranged, when an operation to add the PWA installation item 652 is performed by pressing the item addition button 746 included in the dialog box 740, a warning is issued that PWA needs to be turned on in the app settings, and the PWA setting cannot be turned on by operating the dialog box 740. When this warning is issued, a shortcut item that displays the app setting screen (a screen including setting items 841 to 848) in FIG. 8(b) described later may be displayed, and in response to the shortcut item being operated, the app setting screen (a screen including setting items 841 to 848) in FIG. 8(b) may be displayed, and the process may proceed to S811 in FIG. 8(a) described later.

In S708, the developer terminal 100 performs processing related to items other than the property item in the AppBar context menu. Details are omitted.

In S709, as other processing, the developer terminal 100 displays a context menu related to the specified target corresponding to the specified position and performs processing according to the operation. Details are omitted.

In S710, the developer terminal 100 determines whether the UI screen to be edited (selected UI screen) is a template screen. If it is a template screen, the process proceeds to S721; if not, the process proceeds to S711.

In S711, the developer terminal 100 displays the button context menu shown in FIG. 5(d) superimposed near the specified position (mouse cursor position) as a context menu for the specified UI component.

In S712, the developer terminal 100 determines whether or not a property (property 541 in FIG. 5(d)) has been selected from the options included in the context menu. If a property has been selected, the process proceeds to S713; if not, the process proceeds to S714.

In S713, the developer terminal 100 displays a property box for the button superimposed on the canvas 530 as a property box (detailed settings dialog) for the specified UI part. Then, various setting operations for the property box are accepted. Here, detailed settings can be made, for example, such as the button name (label) to be displayed for the button, which is the specified UI part, the button color, and the size specified by a numerical value. When the settings are made and an operation to reflect them is performed, the specified UI part is displayed on the canvas 530 in a display form that reflects the settings.

In S714, the developer terminal 100 determines whether an action (property 542 in FIG. 5(d)) has been selected from the options included in the context menu. If an action has been selected, the process proceeds to S715; if not, the process proceeds to S716.

At S715, the developer terminal 100 performs action board processing for the button, which is the specified UI part. That is, an action board corresponding to the button, which is the specified UI part, is displayed, and input is accepted for describing a string (a string that defines an action) in JavaScript, a programming language, for the action board. The action entered here is the process to be executed when the specified UI part is pressed in the constructed application.

In S716, the developer terminal 100 determines whether or not "Delete" (Delete 543 in FIG. 5(d)) has been selected from the options included in the context menu. If "Delete" has been selected, the process proceeds to S717; if not, the process proceeds to S718.

In S717, the developer terminal 100 erases the specified UI component, and erases information about the specified UI component (definitions such as position and size, properties and actions, etc.) from the definition information recorded in memory 102. As a result, the specified UI component is erased (deleted) and hidden from the canvas 530.

In S718, the developer terminal 100 determines whether another option has been selected from the options included in the context menu. If another option has been selected, the process proceeds to S719, where processing according to the selected option is performed. If not, the process proceeds to S720.

In S720, the developer terminal 100 determines whether an operation to close the context menu has been performed (for example, an operation of clicking outside the area in which the context menu is displayed). If an operation to close the context menu has been performed, the context menu is hidden and the processing of FIG. 7(a) ends. If no operation to close the context menu has been performed, the processing returns to S712.

Meanwhile, in S721, the developer terminal 100 displays a context menu for the template screen and for the button as a context menu for the specified UI part, superimposed near the specified position (mouse cursor position). Unlike the context menu for a normal UI screen (context menu 540 shown in FIG. 5(d)), the context menu for the template screen does not display options such as action or delete, but only properties. In other words, for UI parts placed on the template screen among the UI screens, the developer is not allowed to set the action to be taken when the UI part is operated.

In S722, the developer terminal 100 determines whether or not Properties has been selected from the options included in the context menu. If Properties has been selected, the process proceeds to S723; if not, the process proceeds to S724. The process of S723 is the same as S713.

In S724, the developer terminal 100 determines whether an operation to close the context menu has been performed (for example, an operation of clicking outside the area in which the context menu is displayed). If an operation to close the context menu has been performed, the context menu is hidden and the processing of FIG. 7(a) ends. If no operation to close the context menu has been performed, the processing returns to S722.

<Screen switching process>
Fig. 8A shows a flowchart of the screen switching process, which is performed in response to the selection of an option displayed in the main menu area 510 described above in the display example of Fig. 5B.

In S801, the developer terminal 100 determines whether the application list button 511 has been pressed. If the application list button 511 has been pressed, the process proceeds to S315 in FIG. 3; if not, the process proceeds to S802.

In S802, the developer terminal 100 determines whether the UI screen button 512 has been pressed. If the UI screen button 512 has been pressed, the process proceeds to S803; if not, the process proceeds to S804. In S803, the UI editor process of FIG. 4 is performed.

In S804, the developer terminal 100 determines whether or not the workflow button 513 has been pressed. If it is determined that the workflow button 513 has been pressed, the process proceeds to S805; otherwise, the process proceeds to S806.

In S805, the developer terminal 100 performs a workflow creation process. Details are omitted.

In S806, the developer terminal 100 determines whether the setting button 514 has been pressed. If the setting button 514 has been pressed, the process proceeds to S810; if not, the process proceeds to S820.

At S810, the developer terminal 100 displays an application setting screen. The application setting screen is a screen that accepts setting operations related to the selected application.

FIG. 8B shows a display example of the application setting screen. The application setting screen includes a setting upper menu display area 830 and a setting area 840 that accepts the setting of various setting items corresponding to a selected menu item among the menu items displayed in the upper menu display area 830. The selected application box 502 described above is also displayed. The selected application displayed in the selected application box 502 is the application to be set on the application setting screen. The upper menu display area 830 displays a plurality of menu items corresponding to the classification of setting items. The displayed menu includes a general setting 831. If the application to be set is for mobile use, the upper menu display area 830 includes (displays) a menu item 832 related to PWA. If the application to be set is not for mobile use (for PC use), the upper menu display area 830 does not include (does not display) the menu item 832 related to PWA. If the menu item 832 related to PWA is selected, the setting area 840 displays setting items 841 to 848 as setting items related to PWA.
A setting item 841 is a setting item for switching the PWA setting on/off.
Setting items 842 to 848 are setting items reflected in the PWA manifest.
Setting item 842 is an item for setting the name of the application to be displayed on the application user terminal 201 when the PWA is installed. Setting item 843 is an item for setting a short name of the application to be displayed on the application user terminal 201 when the PWA is installed.
The setting item 844 is an item for setting a Description, which is a description of the application.
Setting items 845 to 848 are items for setting images to be used for application icons on the home screen. Images of multiple sizes can be set for non-maskable icons and maskable icons, respectively.

In S811, the developer terminal 100 determines whether the application to be configured is for mobile use. If it is for mobile use, the process proceeds to S812; if not, the process proceeds to S818.

In S812, the developer terminal 100 determines whether or not an operation to switch the PWA setting on/off has been performed. Specifically, after selecting the menu item 832 related to the PWA, it determines whether or not an operation has been performed on the setting item 841. If an operation to switch the PWA setting on/off has been performed, the process proceeds to S813; if not, the process proceeds to S817.

In S813, the developer terminal 100 switches the PWA setting on/off, and updates the definition information recorded in memory 102 based on the result of the switch. Specifically, if it was on before the operation to switch the PWA setting on/off was performed, it is set to off (PWA disabled), and if it was off before the operation to switch the PWA setting on/off was performed, it is switched to on (PWA enabled).

In S814, the developer terminal 100 determines whether the PWA setting is on or not. If it is on, the process proceeds to S815, and if it is off, the process proceeds to S818. If S812 is determined as Yes and then S814 is proceeded to, the determination in S814 is whether the PWA setting has been turned on as a result of an operation to switch the PWA setting on/off.

In S815, the developer terminal 100 references the definition information of the UI screen set in the initial UI (the UI screen, top screen, top page, that is the first UI screen to be displayed after the completion of application authentication) in the application settings, and determines whether or not a UI component (installation component) that instructs the installation of the PWA has been placed. This determination is made based on whether or not a specific UI component ID indicating an installation component is present in the UI component defined to be placed in the initial UI. If an installation component has been placed in the initial UI, the process proceeds to S818, and if not (if not yet placed), the process proceeds to S816. This determination is made to prevent multiple installation components from being placed.

In S816, the developer terminal 100 automatically places the installation component on the UI screen set as the initial UI. The installation component is a UI component with a predefined click event, and an event of installing the PWA of the target application is predefined. The click event set in the installation component is a process executed by the application user terminal 201, and is different from the process that can be set in the action board of other UI components and should be executed by the execution environment 400. The action of the installation component cannot be changed or deleted, and the action board cannot be opened for the installation component. In addition, since the installation component is a UI component, it is possible to display the initial UI in a UI editor and change the contents that can be changed in the property box, such as the position, size, and color of the installation component. In addition, in the constructed application, the installation component is controlled by the application user terminal 201 so that if a PWA has already been installed in the application user terminal 201 displaying the initial UI, it is not displayed, and if it has not been installed, it is displayed.

In S817, the developer terminal 100 determines whether or not an operation to change the initial UI has been performed. Specifically, after selecting general settings 831, it determines whether or not a setting change operation has been performed on the setting item (not shown) of the initial UI displayed in the setting area 840. If a setting change operation to change the initial UI has been performed, the process proceeds to S813, where the initial UI setting is changed according to the setting change operation, and the definition information is updated. Thereafter, in S814, it is determined that the PWA setting is on, and if in S815, it is determined that an installation component has not been placed in the changed initial UI, in S816, an installation component is automatically placed in the changed initial UI. It is determined whether or not an operation to change the initial UI has been performed, and if there has been no setting change operation to change the initial UI that was on, the process proceeds to S818.

In S818, the developer terminal 100 performs other application settings in response to operations by the developer. For example, language settings (whether to display in Japanese or English) can be set.

In S819, the developer terminal 100 determines whether or not an operation has been performed to end the application settings and close the application settings screen. If the application settings are not to be ended, the process proceeds to S811 and the process is repeated, and if the application settings are to be ended, the process proceeds to S801.

In S820, the developer terminal 100 determines whether or not another option displayed in the main menu area 510 has been selected. If another option has been selected, the process proceeds to S821; if not, the process proceeds to S822.

In S821, the developer terminal 100 performs processing according to the option selected in S820. Details are omitted.

In S822, the developer terminal 100 determines whether or not an end operation has been performed. If an end operation has not been performed, the process proceeds to S801 and the process is repeated, and if an end operation has been performed, the screen switching process ends.

<Preservation treatment>
9A shows a flowchart of the save process (record control process) executed by the development environment 300, which is the recording destination of the definition information. This process is executed in conjunction with receiving the definition information transmitted from the developer terminal 100 in S422 of FIG. 4 described above.

Figure 10 also illustrates the transition of information recorded in the developer terminal 100, development environment 300, execution environment 400, and application user terminal 201. Figure 10 is a schematic diagram showing the transition of information due to the processing of the flowcharts in Figures 9(a) and 9(b).

In S901 of FIG. 9(a), the development environment 300 determines whether or not it has received definition information (UI definition information) of the selected app from the developer terminal 100. The definition information received here is the information sent from the developer terminal 100 in S422 of FIG. 4 described above. If a UI definition has been received, the process proceeds to S902; if not, the process waits in S901.

In FIG. 10, the UI definition information 1001 recorded in the memory 102 of the developer terminal 100 is the definition information received in S901. In this embodiment, the UI definition information is a plurality of text files written in JSON format with the file names "uiDef.json" and "appDef.json". Json is an abbreviation for JavaScript Object Notification, and is a document standard for handling values in JavaScript, and is a data description language. The UI definition information 1001 includes various settings related to the application, such as the initial UI, and information defining the information (position, size, color, etc.) of the UI components (UI parts) for each UI screen. In particular, "appDef.json" records the contents set in the application setting process of S810 to S819, and also records the settings related to PWA (PWA on/off setting, and settings related to the manifest when PWA is on). In addition, the UI definition information 1001 includes an action description portion 1002. This action description portion 1002 is a character string entered into the action board of each UI part or canvas, or into the function setting screen (including the creation function setting screen). The action description portion 1002 includes an action described in JavaScript, and a function definition in Json format that describes the contents set in the function setting screen without entering JavaScript. This UI definition information 1001 is sent (uploaded) from the developer terminal 100 to the development environment 300, and is received by the development environment 300 in S901.

In S902, the development environment 300 saves the UI definition information in an area of the storage 320 for the logged-in developer. As a result, as shown in FIG. 10, the UI definition information 1011 is recorded in the development environment 300. Immediately after this saving, the UI definition information 1011 recorded in the development environment 300 is the same information as the UI definition information 1001 recorded in the developer terminal 100.

In S903, the development environment 300 extracts action information from the UI definition information saved in S902. That is, the development environment 300 extracts the action description portion 1012 from the UI definition information 1011 in FIG. 10.

In S904, the development environment 300 generates an execution environment program from the action description portion 1012 extracted in S903 and saves it in an area of the storage 320 for the logged-in developer. That is, based on the action description portion 1012 extracted from the UI definition information 1011 in FIG. 10, an execution environment program 1013 is generated and saved in the development environment. The execution environment program 1013 is text data written in JavaScript. The execution environment program 1013 is a program that adds supplementary parts necessary for execution by the execution engine of the execution environment to the character strings entered in the action board obtained from the action description portion 1012.

In S905, the development environment 300 reads the PWA settings from the UI definition information saved in S902, and determines whether the PWA is on. If it is on, the process proceeds to S907, and if it is not, the process proceeds to S906.

In S906, the development environment 300 generates the client UI definition information 1015. The client UI definition information 1015 is assumed to be a Json format file with the file name "ClientDef.json", for example. The client UI definition information 1015 includes, as information acquired from the UI definition information 1011, various setting information related to the application, such as the initial UI, information on the UI parts (components) for each UI screen (such as the contents set by the UI part ID and properties, the layout position and size of the UI parts), the canvas action identifier, and the UI part action identifier. The client UI definition information 1015 also records the input/output item definition for each action (definition of which parts are in each input item and output item). The character string (the source code of the action) written in JavaScript (programming language) written on the action board itself is not recorded. That is, the generated client UI definition information 1015 includes the action identifier and information on the input/output item definition for each action, but does not include information indicating the action content. Also, when the PWA is set to off, it does not include information for performing an action such as installing the PWA in response to the operation of a display item that instructs the installation of the PWA as a button click action on the client terminal (application user terminal 201).

In S905, the development environment 300 reads the UI definition information saved in S902 and determines whether or not the setting is set to place an item for PWA installation (a PWA installation item included in the AppBar drawer menu or an installation component placed in the initial UI). If the setting is set to place an item for PWA installation, the process proceeds to S908; if not, the process proceeds to S909.

In S908, the development environment 300 generates the client UI definition information 1015 in the same manner as in S906. In addition, in S908, the development environment 300 sets (records) the installation operation information 1026 for the PWA installation item (at least one of the PWA installation item included in the AppBar drawer menu and the installation component placed in the initial UI) that is set to be placed in the client UI definition information 1015. The installation operation information 1026 is information that performs an operation of installing the PWA in response to the operation of a display item that instructs the PWA installation as a button click operation in the client terminal (app user terminal 201). In other words, it is operation information for controlling the app user terminal 201 to install the PWA when the PWA installation item is operated in the app user terminal 201 that displays the application screen. When the constructed application is executed, the application user terminal 201 refers to this operation information and is controlled to install the PWA in response to the operation of the item for installing the PWA.

In S909, the development environment 300 generates the client UI definition information 1015 in the same manner as in S906. In addition, in S909, the development environment 300 sets (records) definition information for displaying a pop-up recommending the installation of the PWA in the client UI definition information 1015. This is information required by the client terminal (app user terminal 201) to display a pop-up 1130 described later in FIG. 11(c). In addition, in S909, the development environment 300 sets (records) installation operation information 1026 for an item for PWA installation (an install button 1133 described later included in the recommended pop-up) that is set to be placed in the client UI definition information 1015. The installation operation information 1026 is information that performs an operation of installing the PWA in response to the operation of a display item that instructs the installation of the PWA as a button click operation in the client terminal (app user terminal 201). When the constructed application is executed, the application user terminal 201 refers to this operation information and is controlled to install the PWA in response to the operation of the item for installing the PWA.

As a result, as shown in FIG. 10, UI definition information 1011, execution environment program 1012, and client UI definition information 1015 are recorded in the development environment 300.

<Deployment process>
9B shows a flowchart of the deployment process. This process is executed by the development environment 300 and starts when the development environment 300 receives the deployment request sent from the developer terminal 100 in S426 of FIG.

In S911, the development environment 300 acquires the definition information of the selected application to be deployed from the definition information of the application stored in the developer area of the logged-in developer in the storage 320 of the development environment 300. The definition information acquired here includes the UI definition information 1011, the program for execution environment 1013, and the UI definition information for client 1015.

In S912, the development environment 300 refers to the UI definition information 1011 and determines whether the PWA is set to on. If the PWA is on, the process proceeds to S914; if not, the process proceeds to S913.

In S913, the development environment 300 references the UI definition information 1011, generates a client program 1027, and includes it in the deployment target. The client program 1027 generated here is any one of the client programs 422, 456c, 466c, 476c, ... shown in FIG. 1, which is deployed to the selected execution environment. The client program 1027 generated here is a program (such as HTML source code or JavaScript source code) to be executed on the application user terminal 200, 201, which is sent to the application user terminal 200, 201 that has accessed the execution environment 400. The client program generated in S913 does not include PWA manifest information because PWA is off.

In S914, the development environment 300 references the UI definition information 1011, generates a client program 1027, and includes it in the deployment target. The client program 1027 generated here is any one of the client programs 422, 456c, 466c, 476c, ... shown in FIG. 1, which is deployed to the selected execution environment. The client program generated here is a program (such as HTML source code or JavaScript source code) to be executed on the application user terminal 200, 201, which is sent to the application user terminal 200, 201 that has accessed the execution environment 400. Since the PWA is on, the client program 1027 generated in S914 includes PWA manifest information (contents set in the above-mentioned setting items 842 to 848).

In S915, the development environment 300 determines whether the selected execution environment is a multi-tenant execution environment. If it is a multi-tenant execution environment, the process proceeds to S916. If it is not (if it is a single-tenant execution environment), the process proceeds to S917.

At S916, the development environment 300 stores information on the deployment target related to the selected app in the developer area (dedicated folder) of the logged-in developer in the storage 420 of the multitenant execution environment 410. More specifically, the development environment 300 transmits information on the deployment target to the multitenant execution environment 410 and instructs the multitenant execution environment 410 to record it in the developer area (folder for each developer) of the logged-in developer. If this recording is completed without any problems, the deployment is successful.

In S917, the development environment 300 stores the information to be deployed in the storage of the single-tenant execution environment, which is the currently selected execution environment (a folder directly under the bucket of the single-tenant execution environment). More specifically, the development environment 300 sends the information to be deployed to the single-tenant execution environment, which is the currently selected execution environment, and instructs the single-tenant execution environment to record it in a folder directly under the bucket. If this recording is completed without any problems, the deployment is successful.

In S918, the development environment 300 determines whether the deployment has failed. If the deployment has failed, the process proceeds to S919, otherwise the process proceeds to S920. The deployment may fail if the definition information cannot be sent or recorded in the execution environment due to a communication failure or other reason.

In S919, the development environment 300 sends a failure notification to the developer terminal 100 indicating that the deployment has failed.

In S920, the development environment 300 determines whether the deployment has been completed (successful). If the deployment has been completed, the process proceeds to S921; if not, the process proceeds to S918.

At S921, the development environment 300 sends a deployment success notification to the developer terminal 100, including information on the URL of the deployed app (information on the access destination for accessing the app deployed to the execution environment).

The description will be given with reference to FIG. 10. The UI definition information 1011, the program for execution environment 1013, and the UI definition information for client 1015 saved in the development environment 300 by the save process described in FIG. 9A are deployed (placed, saved, recorded, constructed) in the execution environment 400 by the deploy process (processing of S916 or S917). As a result, as shown in FIG. 10, the UI definition information 1021, the program for execution environment 1023, and the UI definition information for client 1025 are recorded in the execution environment 400. The UI definition information 1021 and the program for execution environment 1023 in the execution environment 400 are the same information as the UI definition information 1011 and the program for execution environment 1013, respectively. In addition, the program for client 1027 generated by the process of S913 or S914 is deployed (placed, saved, recorded, constructed) in the execution environment 400 by the deploy process (processing of S916 or S917). This is the state after the app has been generated.

When an application is executed, application user terminal 201 accesses execution environment 400, downloads client UI definition information 1025 and client program 1027, and records them in application user terminal 201 as client UI definition information 1035 and client program 1037. When an application is executed, application user terminal 201 performs control related to the PWA described in FIG. 11 based on client UI definition information 1035 and client program 1037.
<Example of processing when the app is running>
Figures 11 (a) to (c) show examples of the display when an app that has been built (deployed) in execution environment 400 with the PWA setting turned on is accessed and executed from app user terminal 201 (mobile terminal), and the app screen is displayed on the display of app user terminal 201.

Figure 11 (a) is a display example of the initial UI 1100 of an application in which the PWA is turned on and the initial UI is a UI screen on which both the AppBar and the installation component are arranged. The initial UI 1100 displays the installation component 1110, which is a UI component that is automatically arranged by the processing of S816 described above. When the installation component 1110 is pressed, the application user terminal 201 performs control to install the PWA based on the installation operation information 1036 and the manifest information included in the client program 1037. Also, the AppBar 1120 is displayed. When the icon 1121 included in the AppBar 11120 is pressed, a drawer menu 1122 is displayed as an element screen.

11B is a display example in which the icon 1121 is pressed from the state of FIG. 11A to display the drawer menu 1122. The PWA installation item 1123 arranged by the processing of S411 is displayed in the drawer menu 1122. The PWA installation item 1123 is displayed with an emphasis icon 1123a with "Recommend" written on it, and is displayed with emphasis compared to other menus included in the drawer menu 1122. Note that the method of highlighting is not limited to the method of displaying with the emphasis icon 1123a, and other methods such as making the color of the item 1123 different from other icons (e.g., red), making it bold, underlining, or italicizing it may be used. When the item 1123 is pressed, the application user terminal 201 controls to install the PWA based on the installation operation information 1036 and the manifest information included in the client program 1037. Note that installing a PWA is a process that differs from installing a native app, and is performed by referencing manifest information, and includes at least one of the following processes: a process that enables the push notification function to be used, a process that enables offline operation, and a process for displaying an icon on the home screen.

Figure 11 (c) is a display example of the initial UI 1101 of an application in which the PWA is turned on and a UI screen on which neither the AppBar nor the installation component is placed is set as the initial UI. When the initial UI 1101 is displayed, a pop-up 1130 (dialog) is superimposed on the initial UI 1101. The pop-up 1130 displays a message 1131 indicating that the PWA is available and prompting the user to press an install button to install it. In addition, a check box 1132 is displayed to accept an instruction to set the pop-up 1130 not to be displayed the next time the initial UI 1101 is displayed. If this check box 1132 is checked, the application user terminal 201 controls so that the pop-up 1130 is not displayed from the next time. In addition, the pop-up 1130 displays an install button 1133 to accept an instruction to install the PWA. The install button 1133 is set to the same action as the install component 1110, and when the install button 1133 is pressed, the application user terminal 201 performs control to install the PWA based on the installation operation information 1036 and the manifest information included in the client program 1037.

In the present embodiment, an example has been described in which an app is generated that displays the pop-up 1130 when no installation component is placed in the initial UI and no appbar containing installation items is placed, but this is not limiting. An app may be generated that displays the pop-up 1130 when at least one of the following cases is present: when an installation component is placed in the initial UI and when an appbar containing installation items is placed.

According to the present embodiment described above, when the PWA of the application software is available, it is possible to build an application that reduces the possibility that the user will overlook that the PWA is available, and allows the user to use the PWA more easily. For example, when the built Web application is executed in a browser, if the browser does not have a function to notify that the corresponding PWA is available when the manifest information is present in the executed Web application, the user of the application may miss the opportunity to use the PWA without realizing that the PWA is available. In contrast, according to the present embodiment, a display item or a pop-up indicating that the PWA is available is displayed on the application screen regardless of the browser's function, so that the possibility that the user will overlook that the PWA is available can be reduced. In addition, the PWA can be easily installed without performing complicated operations, simply by operating a display item in the application in which the installation operation information 1036 is set.

The various controls described in each of the above flowcharts may be performed by a single piece of hardware, or the entire device may be controlled by multiple pieces of hardware (e.g., multiple processors or circuits) sharing the processing.
In addition, although the present invention has been described in detail based on the preferred embodiments, the present invention is not limited to these specific embodiments, and various forms within the scope of the gist of the present invention are also included in the present invention. Furthermore, each of the above-mentioned embodiments merely shows one embodiment of the present invention, and each embodiment can be appropriately combined.

Other Embodiments
The present invention can also be realized by executing the following process. That is, software (programs) that realize the functions of the above-described embodiments are supplied to a system or device via a network or various storage media, and the computer (or CPU, MPU, etc.) of the system or device reads and executes the program code. In this case, the program and the storage medium on which the program is stored constitute the present invention.

100: Developer terminal, 200: App user terminal, 201: App user terminal 201, 300: Development environment, 400: Execution environment

Claims (19)

a recording control means for controlling recording of definition information relating to an application based on a user's operation;
A generating means for generating specific information used for installing a PWA corresponding to the application;
A control means for controlling the construction of an application that displays a specific message on a screen of the application to prompt the user to install the PWA;
An information processing system comprising: The information processing system according to claim 1, characterized in that the control means controls the construction of an application in which a display item instructing the installation of the PWA is displayed on the screen of the application as the specific display. The information processing system according to claim 2, characterized in that the recording control means controls the definition information to record a setting that displays the display item in response to a change to a setting that enables PWA during development of the application. The information processing system according to claim 2, characterized in that the installation of the PWA includes at least one of the following processes: a process for enabling the use of a push notification function based on the specific information on a client device that displays the screen of the application; a process for enabling the application to operate offline; and a process for displaying an icon on a home screen. The information processing system according to claim 2, characterized in that the control means controls the construction of an application in which the display items are displayed on a top screen displayed by the application. The information processing system according to claim 5, characterized in that the top screen is the first screen displayed after authentication for the application is completed. The information processing system according to claim 5, characterized in that the recording control means controls the definition information to record a setting to display the display item in response to a change to the top screen. The information processing system according to claim 2, characterized in that the control means controls the construction of an application in which the display items are displayed together with options corresponding to multiple screens or multiple functions of the application. The information processing system according to claim 2, characterized in that the control means controls to construct an application in which the display items are displayed superimposed on the top screen of the application. The information processing system according to claim 2, characterized in that the control means controls the generation of operation information, which is information to be transmitted to a client device that displays a screen of the application based on the definition information, and is used to control the client device to install a PWA when the display item is operated on the client device. The information processing system according to claim 1, characterized in that the control means controls the construction of an application that displays the specific display when the PWA is set to be enabled based on the definition information, and controls the construction of an application that does not display the specific display when the PWA is not set to be enabled. The information processing system according to claim 1, characterized in that the specific information includes PWA manifest information. The information processing system according to claim 12, characterized in that the manifest information includes at least one of a description of the application and an image setting to be used for the application's icon on the home screen. The information processing system according to claim 1, characterized in that the generating means generates the specific information based on the definition information. The information processing system according to claim 1, characterized in that the generating means generates a client program for use on a client device that displays a screen of the application, including the specific information, when the definition information includes definition information that enables PWA, and generates a client program for use on the client device that does not include the specific information, when the definition information does not include definition information that enables PWA. The information processing system according to claim 1, characterized in that the recording control means controls to record definitions of components to be placed on a screen displayed by the application being constructed based on user operations on the development screen of the application. The information processing system according to claim 1, characterized in that the application is a web application. a recording control step of controlling so as to record definition information relating to an application based on a user operation;
A generating step of generating specific information used for installing a PWA corresponding to the application;
a control step of controlling to construct an application that displays a specific message on a screen of the application to prompt the user to install the PWA;
23. A method for controlling an information processing system comprising: A program for causing at least one computer to function as each of the means of the information processing system described in any one of claims 1 to 17.

Images