A check-in page configuration method, display method and device

Abstract

The application provides a check-in page configuration method, a display method and an apparatus. In response to a page creation request, a page editing interface is jumped to. In response to a component selection operation on a check-in page component, the check-in page component is displayed in a canvas area, and a plurality of check-in attribute setting items for configuring a page display form of the check-in page component are displayed in an attribute configuration area. In response to an attribute configuration operation on the plurality of check-in attribute setting items, the page display form of the check-in page component is configured, and check-in configuration data of the check-in page component is generated. The check-in configuration data is stored in a database component, so that a check-in page of a check-in activity is rendered by a mobile terminal through the check-in configuration data of the check-in page component. In this way, when there is a check-in page configuration requirement, the configuration of the check-in page is quickly completed without code writing by a developer, and thus the development speed of the check-in page is improved.

Description

Technical Field

[0001] This application relates to the field of web page design technology, and in particular to a method for configuring, displaying, and assembling a check-in page. Background Technology

[0002] In existing software development technologies, developing web pages for events typically requires writing extensive code to implement the basic design of the web pages, incorporating relevant event information. However, due to differences in event content, the content displayed on the web pages varies, leading to different design requirements for the web pages related to the event. In practice, this approach of tailoring check-in pages to different users' needs and habits through extensive coding results in low development efficiency, high development costs, and difficulty in maintenance. Furthermore, the design of check-in pages differs significantly from other similar component pages, requiring specific design tailored to check-in requirements, which adds further challenges to check-in page development. Summary of the Invention

[0003] In view of this, the purpose of this application is to provide a configuration method, display method and device for a check-in page. When there is a need to configure a check-in page, the configuration of the check-in page can be quickly completed by using the pre-configured check-in page components. The configuration of the check-in page can be completed without developers writing code, thereby improving the development speed of the check-in page.

[0004] This application provides a method for configuring a check-in page, applied to a configuration terminal. The configuration method includes:

[0005] In response to the page creation request, the user is redirected to the page editing interface; the page editing interface includes a canvas area, a component list, and an attribute configuration area; the component list displays the sign-in page component;

[0006] In response to a component selection operation for the check-in page component, the check-in page component is displayed in the canvas area, and multiple check-in attribute settings for configuring the page display format of the check-in page component are displayed in the attribute configuration area;

[0007] In response to attribute configuration operations for the multiple check-in attribute settings, configure the page display format of the check-in page component and generate check-in configuration data for the check-in page component;

[0008] The check-in configuration data is stored in the database component so that the mobile terminal can render the check-in page of the check-in activity through the check-in configuration data of the check-in page component.

[0009] In one possible implementation, the plurality of check-in attribute settings include calendar-style configuration items; the check-in configuration data includes calendar display data; the response to the attribute configuration operation for the plurality of check-in attribute settings, configuring the page display format of the check-in page component, and generating the check-in configuration data for the check-in page component, includes:

[0010] In response to the format attribute configuration operation for the calendar format configuration item, configure the time display format of the calendar time component in the check-in page component, and generate calendar display data indicating the time display format of the calendar time component; wherein, the time display format includes display by week and display by month.

[0011] In one possible implementation, the plurality of check-in attribute settings include reward method configuration items, reward content configuration items, and reward icon configuration items; the check-in configuration data includes reward configuration data; the response to the attribute configuration operation for the plurality of check-in attribute settings, configuring the page display format of the check-in page component, and generating the check-in configuration data of the check-in page component, includes:

[0012] In response to the configuration operation for the reward method configuration item, determine the reward distribution method for each reward item during the execution of the check-in activity, and generate first reward data indicating the reward distribution method for each reward item;

[0013] In response to the content configuration operation for the reward content configuration item, determine the reward content of each reward node during the execution of the check-in activity, and generate second reward data indicating the reward content of each reward node;

[0014] In response to the icon configuration operation for the reward icon configuration item, determine the display icon for the reward date corresponding to each reward node in the calendar time component, and generate third reward data indicating the display icon for the reward date corresponding to each reward node;

[0015] Based on the first reward data, the second reward data, and the third reward data, the reward configuration data included in the check-in configuration data is generated.

[0016] In one possible implementation, the plurality of check-in attribute settings include jump type configuration items and jump link configuration items; the check-in configuration data includes page link data; the response to the attribute configuration operation for the plurality of check-in attribute settings, configuring the page display format of the check-in page component, and generating the check-in configuration data of the check-in page component, includes:

[0017] In response to the type configuration operation for the jump type configuration item, configure the jump method and the jump type when the sign-in page jumps when claiming the reward content of any reward node, and generate first jump data indicating the jump method and the jump type;

[0018] In response to a link configuration operation for the jump link configuration item, configure the page link to be jumped to in the event of a jump, and generate second jump data indicating the page link;

[0019] Based on the first redirect data and the second redirect data, the page link data included in the check-in configuration data is generated.

[0020] In one possible implementation, the plurality of check-in attribute settings include a make-up check-in task configuration item; the check-in configuration data includes make-up check-in task data; the response to the attribute configuration operation for the plurality of check-in attribute settings, configuring the page display format of the check-in page component, and generating the check-in configuration data of the check-in page component, includes:

[0021] In response to the supplementary signature configuration operation for the supplementary signature task configuration item, determine the supplementary signature task to be executed and the supplementary signature icon for each supplementary signature date, and generate supplementary signature task data indicating the supplementary signature date and the supplementary signature task corresponding to each supplementary signature date.

[0022] This application also provides a method for displaying a check-in page, applied to a mobile terminal, the method comprising:

[0023] In response to logging into the mobile terminal check-in page, retrieve the check-in configuration data that should be displayed in the check-in page component of the mobile terminal check-in page at the current time from the database component of the configured terminal;

[0024] According to the time display format carried by the check-in configuration data, the check-in page component is rendered onto the mobile terminal check-in page using the check-in configuration data; wherein, the time display format includes either weekly display or monthly display.

[0025] In one possible implementation, the step of retrieving check-in configuration data from the database component configuring the terminal's page data, in response to logging into the mobile terminal's check-in page, for the check-in page component that should be displayed on the mobile terminal's check-in page at the current time, includes:

[0026] In response to logging into the mobile terminal check-in page, determine the component identifier of the check-in page component that should be displayed on the mobile terminal check-in page;

[0027] Using the component identifier, the check-in configuration data of the check-in page component is determined by searching the database component of the configuration terminal.

[0028] In one possible implementation, rendering the check-in page component onto the mobile terminal check-in page according to the time display format carried in the check-in configuration data includes:

[0029] The check-in configuration data is parsed to determine the checked-in date, the checked-in icon for the checked-in date, the button icon for the check-in button in the check-in page component, the date to be checked in, the check-in icon for the date to be checked in, and the display icon for the reward date;

[0030] Based on the time display format and the current time, determine the target time period for the sign-in page component to be displayed on the sign-in page;

[0031] The system tracks the number of times a user has checked in, the number of dates to be missed, the dates to be missed due, and the dates not checked in during the target time period.

[0032] By combining the checked-in dates, the number of checked-ins, and the unchecked-in dates, the reward dates for the reward nodes that will reward the user within the target time period are determined.

[0033] By combining the time display format, the already checked-in icon, the button icon, the make-up check-in icon, and the display icon, the check-in page components for the target time period are rendered onto the mobile terminal check-in page.

[0034] This application embodiment also provides a configuration device for a check-in page, applied to a configuration terminal, the configuration device comprising:

[0035] The interface navigation module is used to respond to a page creation request and navigate to the page editing interface; wherein, the page editing interface includes a canvas area, a component list, and an attribute configuration area; the component list displays the sign-in page component;

[0036] The component selection module is used to respond to the component selection operation for the check-in page component, display the check-in page component in the canvas area, and display multiple check-in attribute settings for configuring the page display format of the check-in page component in the attribute configuration area;

[0037] The attribute configuration module is used to respond to attribute configuration operations for the multiple check-in attribute settings, configure the page display format of the check-in page component, and generate the check-in configuration data of the check-in page component.

[0038] The data storage module is used to store the check-in configuration data in the database component, so that the mobile terminal can render the check-in page of the check-in activity through the check-in configuration data of the check-in page component.

[0039] In one possible implementation, the plurality of check-in attribute settings include calendar-style configuration items; the check-in configuration data includes calendar display data; when the attribute configuration module responds to attribute configuration operations for the plurality of check-in attribute settings, configures the page display format of the check-in page component, and generates the check-in configuration data for the check-in page component, the attribute configuration module is used to:

[0040] In response to the format attribute configuration operation for the calendar format configuration item, configure the time display format of the calendar time component in the check-in page component, and generate calendar display data indicating the time display format of the calendar time component; wherein, the time display format includes display by week and display by month.

[0041] In one possible implementation, the plurality of check-in attribute settings include reward method configuration items, reward content configuration items, and reward icon configuration items; the check-in configuration data includes reward configuration data; when the attribute configuration module responds to attribute configuration operations for the plurality of check-in attribute settings, configures the page display format of the check-in page component, and generates the check-in configuration data for the check-in page component, the attribute configuration module is used to:

[0042] In response to the configuration operation for the reward method configuration item, determine the reward distribution method for each reward item during the execution of the check-in activity, and generate first reward data indicating the reward distribution method for each reward item;

[0043] In response to the content configuration operation for the reward content configuration item, determine the reward content of each reward node during the execution of the check-in activity, and generate second reward data indicating the reward content of each reward node;

[0044] In response to the icon configuration operation for the reward icon configuration item, determine the display icon for the reward date corresponding to each reward node in the calendar time component, and generate third reward data indicating the display icon for the reward date corresponding to each reward node;

[0045] Based on the first reward data, the second reward data, and the third reward data, the reward configuration data included in the check-in configuration data is generated.

[0046] In one possible implementation, the plurality of check-in attribute settings include jump type configuration items and jump link configuration items; the check-in configuration data includes page link data; when the attribute configuration module responds to attribute configuration operations for the plurality of check-in attribute settings, configures the page display format of the check-in page component, and generates the check-in configuration data of the check-in page component, the attribute configuration module is used to:

[0047] In response to the type configuration operation for the jump type configuration item, configure the jump method and the jump type when the sign-in page jumps when claiming the reward content of any reward node, and generate first jump data indicating the jump method and the jump type;

[0048] In response to a link configuration operation for the jump link configuration item, configure the page link to be jumped to in the event of a jump, and generate second jump data indicating the page link;

[0049] Based on the first redirect data and the second redirect data, the page link data included in the check-in configuration data is generated.

[0050] In one possible implementation, the plurality of check-in attribute settings include a make-up check-in task configuration item; the check-in configuration data includes make-up check-in task data; when the attribute configuration module responds to attribute configuration operations for the plurality of check-in attribute settings, configures the page display format of the check-in page component, and generates the check-in configuration data for the check-in page component, the attribute configuration module is used to:

[0051] In response to the supplementary signature configuration operation for the supplementary signature task configuration item, determine the supplementary signature task to be executed and the supplementary signature icon for each supplementary signature date, and generate supplementary signature task data indicating the supplementary signature date and the supplementary signature task corresponding to each supplementary signature date.

[0052] This application embodiment also provides a display device for a check-in page, applied to a mobile terminal, the display device comprising:

[0053] The data acquisition module is used to retrieve, in response to logging into the mobile terminal check-in page, the check-in configuration data that should be displayed on the check-in page component of the mobile terminal check-in page at the current time from the database component of the configuration terminal;

[0054] The page rendering module is used to render the check-in page component onto the mobile terminal check-in page using the check-in configuration data according to the time display format carried by the check-in configuration data; wherein, the time display format includes either weekly display or monthly display.

[0055] In one possible implementation, when the data acquisition module retrieves the check-in configuration data that should be displayed in the check-in page component of the mobile terminal check-in page at the current time point from the database component of the configuration terminal in response to logging into the mobile terminal check-in page, the data acquisition module is used to:

[0056] In response to logging into the mobile terminal check-in page, determine the component identifier of the check-in page component that should be displayed on the mobile terminal check-in page;

[0057] Using the component identifier, the check-in configuration data of the check-in page component is determined by searching the database component of the configuration terminal.

[0058] In one possible implementation, when the page rendering module renders the check-in page component onto the mobile terminal check-in page using the check-in configuration data according to the time display format carried by the check-in configuration data, the page rendering module is used to:

[0059] The check-in configuration data is parsed to determine the checked-in date, the checked-in icon for the checked-in date, the button icon for the check-in button in the check-in page component, the date to be checked in, the check-in icon for the date to be checked in, and the display icon for the reward date;

[0060] Based on the time display format and the current time, determine the target time period for the sign-in page component to be displayed on the sign-in page;

[0061] The system tracks the number of times a user has checked in, the number of dates to be missed, the dates to be missed due, and the dates not checked in during the target time period.

[0062] By combining the checked-in dates, the number of checked-ins, and the unchecked-in dates, the reward dates for the reward nodes that will reward the user within the target time period are determined.

[0063] By combining the time display format, the already checked-in icon, the button icon, the make-up check-in icon, and the display icon, the check-in page components for the target time period are rendered onto the mobile terminal check-in page.

[0064] This application embodiment also provides an electronic device, including: a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, the steps of the check-in page configuration method and / or check-in page display method described above are performed.

[0065] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the above-described check-in page configuration method and / or check-in page display method.

[0066] The check-in page configuration method, display method, and apparatus provided in this application embodiment, in response to a page creation request, jumps to a page editing interface; in response to a component selection operation for the check-in page component, displays the check-in page component in the canvas area, and displays multiple check-in attribute settings for configuring the page display format of the check-in page component in the attribute configuration area; in response to attribute configuration operations for the multiple check-in attribute settings, configures the page display format of the check-in page component, and generates check-in configuration data for the check-in page component; stores the check-in configuration data in a database component, so that the mobile terminal renders the check-in page of the check-in activity through the check-in configuration data of the check-in page component. Thus, when there is a need for check-in page configuration, the configuration of the check-in page can be quickly completed using the configured check-in page component without developers writing code, thereby improving the development speed of the check-in page. Simultaneously, the configuration of related attributes can be customized according to the special design requirements of the check-in page component, and the configuration data can be promptly fed back to the mobile terminal, improving user feedback speed and business configuration efficiency.

[0067] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0068] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0069] Figure 1 A flowchart illustrating a method for configuring a check-in page as provided in an embodiment of this application;

[0070] Figure 2 This is a schematic diagram of a page editing interface provided in an embodiment of this application;

[0071] Figure 3 A flowchart illustrating a method for displaying a check-in page as provided in an embodiment of this application;

[0072] Figure 4 A schematic diagram of the structure of a check-in page configuration device provided in an embodiment of this application;

[0073] Figure 5 A schematic diagram of the structure of a sign-in page display device provided in an embodiment of this application;

[0074] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0075] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. Based on the embodiments of this application, every other embodiment obtained by those skilled in the art without inventive effort falls within the scope of protection of this application.

[0076] In existing software development technologies, when developing web pages for an event, it is usually necessary to combine relevant event information and write a large amount of code to implement the basic design of the web page. However, due to the differences in event content, the content to be displayed on the web page also varies. Therefore, the design requirements for the web pages related to the event content also differ. In the actual development implementation, this approach of creating a check-in page suitable for different users by writing a large amount of code according to their actual needs and usage habits leads to low development efficiency, high development costs, and difficulty in maintenance later.

[0077] Based on this, this application provides a method for configuring a check-in page, which can quickly configure the check-in page and enable the development of the check-in page without developers writing code, thereby reducing the difficulty of check-in page development and increasing the development speed of check-in page.

[0078] Please see Figure 1 , Figure 1 This is a flowchart illustrating a method for configuring a check-in page, as provided in an embodiment of this application. It is applied to a configuration terminal; for example... Figure 1 As shown in the embodiments of this application, the configuration method for the check-in page includes:

[0079] S101. In response to the page creation request, redirect to the page editing interface.

[0080] S102. In response to the component selection operation for the check-in page component, display the check-in page component in the canvas area and display multiple check-in attribute settings for configuring the page display format of the check-in page component in the attribute configuration area.

[0081] S103. Respond to the attribute configuration operation for the multiple check-in attribute settings, configure the page display format of the check-in page component, and generate the check-in configuration data of the check-in page component.

[0082] S104. Store the check-in configuration data in the database component so that the mobile terminal can render the check-in page of the check-in activity through the check-in configuration data of the check-in page component.

[0083] The method for configuring a check-in page provided in this application allows users to enter a page editing interface when there is a need to create a check-in page. The interface allows configuration of the check-in page and enables customization of the page display format by setting check-in attribute settings for the check-in page components in the attribute configuration area. This generates check-in configuration data for the check-in page components and stores it in a database component. This allows mobile terminals to quickly render the check-in page using the stored check-in configuration data, improving both the creation and rendering speeds.

[0084] In step S101, business personnel can send a page creation request to create a check-in page in the configuration terminal, which will redirect to the page editing interface for configuring the check-in page, so that business personnel can complete the configuration of the check-in page in the page editing interface.

[0085] To facilitate business personnel in creating check-in pages, various methods for issuing page creation requests can be configured. For example, a creation request control can be set up so that a page creation request can be issued when a business personnel touch the control. Alternatively, the page creation request can be automatically triggered after a business personnel completes the configuration of a page associated with the check-in page. Or, business personnel can issue page creation requests via voice, text, or other means.

[0086] The page editing interface includes a canvas area, a component list, and an attribute configuration area; the component list displays the sign-in page component.

[0087] The canvas area allows business personnel to clearly understand the display effect of the check-in page; that is, business personnel can clearly understand the display effect of the created check-in page in the canvas area.

[0088] The component list includes a variety of components such as basic components, advanced components, and business components for business users to choose from. When editing the page, business users can drag and drop the selected target components to display them in the canvas area. The component list includes, but is not limited to, at least one of the following: check-in page component, leaderboard component, input box component, text field component, radio button component, checkbox component, dropdown component, cascading selection component, rating component, calendar-time component, slider verification component, form submission component, mini-program jump component, verification code component, ordinary button component, image component, carousel component, text component, video component, background music component, divider component, notification bar component, and navigation bar component.

[0089] The attribute configuration area allows you to set multiple check-in attribute settings. These settings can be used to configure the display effects of the check-in page, such as whether the calendar time component on the check-in page is displayed by month or week, and the display format of the check-in button component.

[0090] For example, please refer to Figure 2 , Figure 2 This is a schematic diagram of a page editing interface provided in an embodiment of this application. Figure 2 As shown, the page editing interface 2a displays a canvas area 2b, a component list 2c, and an attribute configuration area 2d. The component list 2c includes a basic component 2c-1 and an advanced component 2c-2. The basic component 2c-1 displays an input box component, a checkbox component, and a radio button component. When a component is selected, the attribute configuration area 2d displays multiple attribute configuration items that allow for attribute configuration of the selected component.

[0091] When business personnel need to configure a check-in page, they can select the corresponding check-in page component from the component list and complete the configuration of the check-in page component.

[0092] In step S102, in response to the business personnel's selection operation of the sign-in page component in the component list, the sign-in page component is displayed in the canvas area of ​​the page editing interface; at the same time, in order to facilitate the business personnel to configure the sign-in page component, multiple sign-in attribute settings items that can configure the page display format of the sign-in page component are displayed in the attribute configuration area.

[0093] In the solution provided in this application, the response to the component selection operation of the check-in page component can specifically be as follows: when a business user presses the control corresponding to the component selection operation, a selection command for the check-in page component can be triggered. Specifically, the user can issue the selection command for the check-in page component through the control corresponding to the component selection operation and / or a preset key combination. Specifically, the user can select the corresponding control using touch components such as a finger or mouse; or through preset key combinations on the keyboard, such as the Ctrl key, Alt key, and A key. These preset keys can be manually set according to the needs of the business user.

[0094] Component selection operations include any one of the following: swipe, drag, click, double-click, and input.

[0095] Specifically, business users can select the sign-in page component by dragging it from the component list to the canvas area; alternatively, they can select it by clicking on the component; they can also select it by double-clicking; or they can select it by clicking twice, with the selection achieved if both clicks are on the sign-in page component and the canvas area respectively.

[0096] In step S103, business personnel can personalize the check-in display page by displaying multiple check-in attribute settings in the attribute configuration area. Specifically, in response to the attribute configuration operations applied by business personnel to multiple check-in attribute settings, the configuration of each check-in attribute setting is completed, thereby configuring the page display format of the check-in page component and generating the check-in configuration data of the check-in page component.

[0097] Here, the check-in attribute settings include calendar format configuration, reward method configuration, reward content configuration, reward icon configuration, jump type configuration, jump link configuration, and make-up check-in task configuration.

[0098] The configuration options are as follows: Calendar Format Configuration: Configures the time display format of the calendar time component in the check-in page component; Reward Method Configuration: Configures the reward distribution method for each reward during the check-in activity; Reward Content Configuration: Configures the reward content for each reward node during the check-in activity; Reward Icon Configuration: Configures the display icon for the reward date corresponding to each reward node in the calendar time component; Page Jump Type Configuration: Configures the jump method and type for the check-in page; Jump Link Configuration: Configures the page link to be jumped to when a jump occurs; Make-up Check-in Task Configuration: Configures make-up check-in tasks.

[0099] To increase the diversity of display formats for the sign-in page components, a way is provided for business users to set the display format of the calendar time component within the sign-in page components.

[0100] In one embodiment, the plurality of check-in attribute settings include a calendar format configuration item; the check-in configuration data includes calendar display data; step S103 includes: responding to a format attribute configuration operation for the calendar format configuration item, configuring the time display format of the calendar time component in the check-in page component, and generating calendar display data indicating the time display format of the calendar time component.

[0101] In this step, the multiple check-in attribute settings displayed in the attribute configuration area include a calendar format configuration item that configures the display format of the calendar time component. Business users can specify whether the calendar time component in the check-in page component is displayed by week or by month by configuring the calendar format configuration item. Specifically, in response to the format attribute configuration operation applied by the business user to the calendar format configuration item, the time display format of the calendar time component displayed in the check-in page component is configured. Two candidate display formats can be preset: the first candidate display format is displayed by month; the second candidate display format is displayed by week. The candidate display format selected by the business user through the format attribute configuration operation is determined as the time display format of the calendar time component.

[0102] For example, when a business user chooses to display the calendar time component by month, the month to which the current time belongs can be displayed in the check-in page component, using the current time as a reference; when a business user chooses to display the calendar time component by week, the week to which the current time belongs can be displayed in the check-in page component, using the current time as a reference; other display formats can also be set according to the actual situation, which will not be elaborated here.

[0103] In the solution provided in this application, the response to the format attribute configuration operation for the calendar format configuration item can specifically be as follows: when a business user presses the control corresponding to the format attribute configuration operation, a time display format selection command can be triggered. Specifically, the user can issue the time display format selection command through the control corresponding to the format attribute configuration operation and / or a preset key combination. Alternatively, the user can use their finger, mouse, or other touch controls to manipulate the format attribute configuration operation; or they can use preset key combinations on the keyboard, such as the Ctrl key, Alt key, and A key. These preset keys can be manually set according to the business user's needs.

[0104] Formal attribute configuration operations include any one of the following: sliding operation, dragging operation, clicking operation, double-clicking operation, and input operation.

[0105] To ensure users can clearly distinguish the reward dates corresponding to reward nodes during the check-in activity and avoid missing out on rewards, in addition to providing business personnel with the option to set reward content and distribution methods, it is also possible to provide them with display icons that differentiate the reward dates corresponding to reward nodes.

[0106] In one implementation, the plurality of check-in attribute settings include a reward method configuration item, a reward content configuration item, and a reward icon configuration item; the check-in configuration data includes reward configuration data; step S103 includes:

[0107] Step 11: Respond to the method configuration operation for the reward method configuration item, determine the reward distribution method for each reward content during the execution of the check-in activity, and generate first reward data indicating the reward distribution method for each reward content.

[0108] In this step, business personnel can configure the reward distribution method for different reward content in the check-in activity; for example, the reward distribution method for reward content A is to accumulate 3 days of check-in; the reward distribution method for reward content B is to complete task C; the reward distribution method for reward content D is to check in for 3 consecutive days, etc.

[0109] Specifically, in response to the method configuration operation applied by the business personnel to the reward method configuration item, the reward distribution method set by the business personnel to be distributed to users for each reward content during the execution of the check-in activity is determined, and the first reward data indicating the reward distribution method for each reward content is generated.

[0110] Here, multiple reward distribution methods can be pre-set for business personnel. Business personnel can select the reward distribution method for each reward content one by one from multiple reward distribution methods through the method configuration operation, thereby completing the configuration of the reward distribution method for each reward content.

[0111] The operation configuration includes any one of the following: swipe operation, drag operation, click operation, double click operation, and input operation.

[0112] Step 12: Respond to the content configuration operation for the reward content configuration item, determine the reward content of each reward node during the execution of the check-in activity, and generate second reward data indicating the reward content of each reward node.

[0113] In this step, business personnel can also configure the reward content to be given to users at each reward node through content configuration operations; for example, there are 3 reward nodes in the sign-in activity, and the reward content to be given to users at different reward nodes is different. The reward content to be given to users at reward node a is "points"; the reward content to be given to users at reward node b is "gold coins"; the reward content to be given to users at reward node c is "physical rice cooker", etc.

[0114] Specifically, in response to the content configuration operations performed by business personnel on the reward content configuration items, the system determines each reward content to be awarded to the user at each reward node during the execution of the check-in activity, as set by the business personnel, and generates second reward data indicating the reward content of each reward node.

[0115] Here, multiple reward options can be pre-set for business personnel. Business personnel can then select the reward option for each reward node from the multiple reward options through the content configuration operation, thereby completing the configuration of the reward option for each reward node.

[0116] Content configuration operations include any one of the following: swipe, drag, click, double-click, and input.

[0117] Step 13: In response to the icon configuration operation for the reward icon configuration item, determine the display icon for the reward date corresponding to each reward node in the calendar time component, and generate third reward data indicating the display icon for the reward date corresponding to each reward node.

[0118] In this step, business personnel can also configure the display icon of the reward date corresponding to each reward node in the calendar time component through icon configuration. For example, the display icon of the reward date corresponding to the reward node is different from the sign-in icon of the sign-in date that has been completed, and the sign-in icon of the sign-in date that has not been completed.

[0119] Specifically, in response to the icon configuration operation performed by the business personnel on the reward icon configuration item, the display icon of the reward date corresponding to each reward node in the calendar time component set by the business personnel is determined, and third reward data indicating the display icon of the reward date corresponding to each reward node is generated.

[0120] Here, multiple candidate icons can be pre-set for business personnel. Business personnel can select the display icon for the reward date corresponding to each reward node from the multiple candidate icons one by one through the icon configuration operation, thereby completing the display icon configuration for the reward date corresponding to each reward node.

[0121] Icon configuration operations include any one of the following: swipe, drag, click, double-click, and input.

[0122] Step 14: Based on the first reward data, the second reward data, and the third reward data, generate the reward configuration data included in the check-in configuration data.

[0123] When a user completes a task and receives a reward, the system can configure whether the user needs to be redirected to a different page to claim the reward.

[0124] In one implementation, the plurality of check-in attribute settings include a jump type configuration item and a jump link configuration item; the check-in configuration data includes page link data; step S103 includes:

[0125] Step 21: Respond to the type configuration operation for the jump type configuration item, configure the jump method and the jump type when the sign-in page jumps when claiming the reward content of any reward node, and generate first jump data indicating the jump method and the jump type.

[0126] In this step, business personnel can configure whether a user needs to be redirected to another page when claiming the reward content of any reward node, as well as the type of this page redirection. Business personnel can select / input the redirection method for each reward node through the type configuration operation. Specifically, for each reward node, in response to the type configuration operation applied by the business personnel to the redirection type configuration item, the system determines whether the page redirection is required when the user claims the reward content of that reward node, configures the redirection type when a page redirection occurs, and generates the first redirection data that indicates whether a page redirection has occurred and the redirection method and type.

[0127] The redirection method includes either redirection or non-redirection; the redirection type includes any one of the following: internal redirection, external redirection, and redirection via a specific link.

[0128] The type configuration operation includes any one of the following operations: swipe operation, drag operation, click operation, double click operation, and input operation.

[0129] Step 22: Respond to the link configuration operation for the jump link configuration item, configure the page link of the page to be jumped to in the event of a jump, and generate second jump data indicating the page link.

[0130] In this step, if the check-in page involves page redirection, business personnel can configure the page link of the page to be redirected to ensure that users can be redirected to the corresponding page when claiming rewards. For example, business personnel can input the page link of the page to be redirected to through the link configuration operation; or, they can select the page link of the page to be redirected to through the link configuration operation. Specifically, in response to the link configuration operation applied by the business personnel to the redirection link configuration item, when the check-in page redirects, the page link of the page to which the user needs to be redirected is configured, and second redirection data that can indicate the page link of the page to be redirected to is generated.

[0131] Step 23: Based on the first redirect data and the second redirect data, generate the page link data included in the check-in configuration data.

[0132] In one embodiment, the plurality of check-in attribute settings include a make-up check-in task configuration item; the check-in configuration data includes make-up check-in task data; step S103 includes: responding to a make-up check-in configuration operation for the make-up check-in task configuration item, determining the make-up check-in task to be executed and the make-up check-in icon for each make-up check-in date, and generating make-up check-in task data indicating the make-up check-in date and the make-up check-in task corresponding to each make-up check-in date.

[0133] In this step, for the dates that a user did not sign in, the user can be given the opportunity to sign in again. At this time, the business personnel need to set the sign-in task to be executed when the sign-in is made up for the date to be made up. For example, the user can sign in again for the date to be made up after completing the sign-in task F. Specifically, in response to the sign-in configuration operation applied by the business personnel to the sign-in task configuration item, the sign-in task to be executed for each date to be made up is determined.

[0134] Meanwhile, in order to enable users to clearly distinguish between the dates to be retroactively signed and other dates (signed-in dates and unsigned-in dates), business personnel can also select the retroactive sign icon for the dates to be retroactively signed through the retroactive sign configuration operation.

[0135] Finally, supplementary signature task data is generated, which indicates the dates to be supplemented and the supplementary signature tasks corresponding to each date.

[0136] In step S104, after generating the check-in configuration data for the check-in page component, the check-in configuration data can be stored in the database component so that when the mobile terminal has a need to render the check-in page, the check-in configuration data of the check-in page can be obtained by searching the database component, and the check-in configuration data can be used to complete the rendering of the check-in page.

[0137] The check-in page configuration method provided in this application embodiment, in response to a page creation request, jumps to a page editing interface; in response to a component selection operation for the check-in page component, displays the check-in page component in the canvas area, and displays multiple check-in attribute settings for configuring the page display format of the check-in page component in the attribute configuration area; in response to attribute configuration operations for the multiple check-in attribute settings, configures the page display format of the check-in page component, and generates check-in configuration data for the check-in page component; stores the check-in configuration data in a database component, so that the mobile terminal renders the check-in page of the check-in activity through the check-in configuration data of the check-in page component. Thus, when there is a need to configure a check-in page, the configuration of the check-in page can be quickly completed using the configured check-in page component, without requiring developers to write code, thereby improving the development speed of the check-in page.

[0138] Please see Figure 3 , Figure 3 This is a flowchart illustrating a method for displaying a check-in page, as provided in an embodiment of this application. It is applied to mobile terminals; such as... Figure 3 As shown in the embodiment of this application, the method for displaying the check-in page includes:

[0139] S301. In response to logging into the check-in page of the mobile terminal, retrieve the check-in configuration data of the check-in page component that should be displayed on the check-in page at the current time from the database component that configures the page data of the terminal.

[0140] S302. According to the time display format carried in the check-in configuration data, render the check-in page component onto the mobile terminal check-in page using the check-in configuration data.

[0141] The present application provides a method for displaying a check-in page, which, in response to a user logging into a mobile terminal check-in page, retrieves check-in configuration data for a check-in page component to be displayed on the mobile terminal check-in page from a database component of a configuration terminal; and renders the check-in page component onto the mobile terminal check-in page according to a pre-set time display format to improve the rendering speed of the check-in page.

[0142] In step S301, when a user logs into the mobile terminal check-in page, the check-in configuration data of the mobile terminal check-in page can be obtained from the database component on the configuration terminal side that stores the configuration data of each component.

[0143] The check-in configuration data includes a calendar time component representing the target time period to which the current time point belongs.

[0144] In one implementation, step S301 includes: in response to logging into the mobile terminal check-in page, determining a component identifier of the check-in page component that should be displayed on the mobile terminal check-in page; and using the component identifier, determining the check-in configuration data of the check-in page component by searching the database component of the page data of the configured terminal.

[0145] In this step, in response to the user logging into the check-in page, the component identifier of the check-in page component that should be displayed on the mobile terminal check-in page is determined; using the component identifier of the check-in page component, the check-in configuration data of the check-in page component is searched from the database component of the configuration terminal by querying the database component, and the searched check-in configuration data is obtained.

[0146] For the sign-in page component, the calendar time component has different time display formats, which can be displayed by month or by week. Therefore, the time display format should also be taken into account when displaying the sign-in page component.

[0147] In step S302, the check-in page component is rendered onto the user's logged-in check-in page according to the time display format carried by the check-in configuration data. Here, the calendar time component of the check-in page component displayed on the mobile terminal check-in page is displayed according to the time display format. Specifically, when the time display format is displayed by week, the target time period displayed in the calendar time component is one week; when the time display format is displayed by week, the target time period displayed in the calendar time component is one month.

[0148] In one implementation, step S302 includes:

[0149] Step 3021: Parse the check-in configuration data to determine the checked-in date, the checked-in icon for the checked-in date, the button icon for the check-in button in the check-in page component, the date to be checked in, the check-in icon for the date to be checked in, the reward date, and the display icon for the reward date.

[0150] In this step, the obtained check-in configuration data is parsed to determine the check-in dates of the user in the historical check-in process, the check-in icon corresponding to the check-in date, the button icon of the check-in button in the check-in page component, the dates that the user can make up for, the make-up check-in icon for the dates to be made up, and the display icon of the reward date corresponding to the reward node with reward content.

[0151] Step 3022: Determine the target time period for the sign-in page component to be displayed on the sign-in page based on the time display format and the current time.

[0152] In this step, because the time display formats of the calendar time components in the check-in page component are different, the target time period displayed by the check-in page component on the mobile terminal check-in page is not the same. Specifically, it is necessary to combine the preset time display format and the current time to determine the target time period displayed by the check-in page component on the check-in page. If the time display format is displayed by week, then the target time period is the week to which the current time point belongs; if the time display format is displayed by month, then the target time period is the month to which the current time point belongs.

[0153] Step 3023: Calculate the number of times a user has checked in, the number of dates to be made up for, and the number of dates not checked in during the target time period.

[0154] In this step, the statistics are as follows: the dates on which users have checked in, the number of times users have checked in, the dates on which users can make up for missed check-ins, and the dates on which users have not checked in during the target time period. Here, the dates on which users have not checked in can refer to the historical check-in dates on which users cannot make up for missed check-ins, or they can refer to the check-in dates that have not yet been reached.

[0155] Step 3024: Combining the checked-in date, the number of checked-ins, and the unchecked-in date, determine the reward date of the reward node that will reward the user within the target time period.

[0156] In this step, by combining the user's checked-in dates, the number of times the user has checked in, and the unchecked dates the user has not checked in, it is determined whether the user needs to be rewarded within the target time period; if it is determined that the user needs to be rewarded within the target time period, the reward date of the reward node for rewarding the user is determined.

[0157] Step 3025: Combining the time display format, the already checked-in icon, the button icon, the make-up check-in icon, and the display icon, render the check-in page component for the target time period onto the mobile terminal check-in page.

[0158] In this step, according to the time display format, the sign-in page component within the target time period is rendered onto the mobile terminal sign-in page using the sign-in icon for the already signed-in date, the button icon for the button component in the sign-in page component, the sign-in icon for the sign-in date that can be made up, and the display icon for the reward date.

[0159] The check-in page display method provided in this application embodiment, in response to logging into the check-in page of a mobile terminal, retrieves check-in configuration data from the database component of the configuration terminal, specifying the check-in page component to be displayed on the check-in page at the current time. Following the time display format carried by the check-in configuration data, the check-in page component is rendered onto the mobile terminal check-in page using the check-in configuration data. This enables fast rendering of the check-in page.

[0160] Please see Figure 4 , Figure 4 This is a schematic diagram of a configuration device for a check-in page provided in an embodiment of this application. It is applied to a configuration terminal; such as... Figure 4 As shown, the configuration device 400 includes:

[0161] The interface jump module 410 is used to respond to the page creation request and jump to the page editing interface; wherein, the page editing interface includes a canvas area, a component list and an attribute configuration area; the component list displays the sign-in page component;

[0162] The component selection module 420 is used to respond to a component selection operation for the check-in page component, display the check-in page component in the canvas area, and display multiple check-in attribute settings in the attribute configuration area for configuring the page display format of the check-in page component;

[0163] The attribute configuration module 430 is used to respond to attribute configuration operations for the plurality of check-in attribute settings, configure the page display format of the check-in page component, and generate check-in configuration data for the check-in page component;

[0164] The data storage module 440 is used to store the check-in configuration data in the database component so that the mobile terminal can render the check-in page of the check-in activity through the check-in configuration data of the check-in page component.

[0165] Furthermore, the plurality of check-in attribute settings include a calendar format configuration item; the check-in configuration data includes calendar display data; when the attribute configuration module 430 responds to attribute configuration operations for the plurality of check-in attribute settings, configures the page display format of the check-in page component, and generates the check-in configuration data of the check-in page component, the attribute configuration module 430 is used to:

[0166] In response to the format attribute configuration operation for the calendar format configuration item, configure the time display format of the calendar time component in the check-in page component, and generate calendar display data indicating the time display format of the calendar time component; wherein, the time display format includes display by week and display by month.

[0167] Furthermore, the plurality of check-in attribute settings include reward method configuration items, reward content configuration items, and reward icon configuration items; the check-in configuration data includes reward configuration data; when the attribute configuration module 430 responds to attribute configuration operations for the plurality of check-in attribute settings, configures the page display format of the check-in page component, and generates the check-in configuration data of the check-in page component, the attribute configuration module 430 is used to:

[0168] In response to the configuration operation for the reward method configuration item, determine the reward distribution method for each reward item during the execution of the check-in activity, and generate first reward data indicating the reward distribution method for each reward item;

[0169] In response to the content configuration operation for the reward content configuration item, determine the reward content of each reward node during the execution of the check-in activity, and generate second reward data indicating the reward content of each reward node;

[0170] In response to the icon configuration operation for the reward icon configuration item, determine the display icon for the reward date corresponding to each reward node in the calendar time component, and generate third reward data indicating the display icon for the reward date corresponding to each reward node;

[0171] Based on the first reward data, the second reward data, and the third reward data, the reward configuration data included in the check-in configuration data is generated.

[0172] Furthermore, the plurality of check-in attribute settings include jump type configuration items and jump link configuration items; the check-in configuration data includes page link data; when the attribute configuration module 430 responds to attribute configuration operations for the plurality of check-in attribute settings, configures the page display format of the check-in page component, and generates the check-in configuration data of the check-in page component, the attribute configuration module 430 is used to:

[0173] In response to the type configuration operation for the jump type configuration item, configure the jump method and the jump type when the sign-in page jumps when claiming the reward content of any reward node, and generate first jump data indicating the jump method and the jump type;

[0174] In response to a link configuration operation for the jump link configuration item, configure the page link to be jumped to in the event of a jump, and generate second jump data indicating the page link;

[0175] Based on the first redirect data and the second redirect data, the page link data included in the check-in configuration data is generated.

[0176] Furthermore, the plurality of check-in attribute settings include a make-up check-in task configuration item; the check-in configuration data includes make-up check-in task data; when the attribute configuration module 430 responds to attribute configuration operations for the plurality of check-in attribute settings, configures the page display format of the check-in page component, and generates the check-in configuration data of the check-in page component, the attribute configuration module 430 is used to:

[0177] In response to the supplementary signature configuration operation for the supplementary signature task configuration item, determine the supplementary signature task to be executed and the supplementary signature icon for each supplementary signature date, and generate supplementary signature task data indicating the supplementary signature date and the supplementary signature task corresponding to each supplementary signature date.

[0178] The check-in page configuration device provided in this application embodiment, in response to a page creation request, jumps to a page editing interface; in response to a component selection operation for the check-in page component, displays the check-in page component in the canvas area and displays multiple check-in attribute settings for configuring the page display format of the check-in page component in the attribute configuration area; in response to attribute configuration operations for the multiple check-in attribute settings, configures the page display format of the check-in page component and generates check-in configuration data for the check-in page component; stores the check-in configuration data in a database component, so that the mobile terminal renders the check-in page of the check-in activity through the check-in configuration data of the check-in page component. Thus, when there is a need for check-in page configuration, the configuration of the check-in page can be quickly completed using the configured check-in page component, without requiring developers to write code, thereby improving the development speed of the check-in page.

[0179] Please see Figure 5 , Figure 5 This is a schematic diagram of a sign-in page display device provided in an embodiment of this application. It is applied to a mobile terminal; such as... Figure 5 As shown, the display device 500 includes:

[0180] The data acquisition module 510 is used to retrieve, in response to logging into the mobile terminal check-in page, the check-in configuration data that should be displayed on the check-in page component of the mobile terminal check-in page at the current time point from the database component of the configuration terminal;

[0181] The page rendering module 520 is used to render the check-in page component onto the mobile terminal check-in page according to the time display format carried by the check-in configuration data; wherein, the time display format includes either weekly display or monthly display.

[0182] Furthermore, when the data acquisition module 510 is used to retrieve the check-in configuration data that should be displayed in the check-in page component of the mobile terminal check-in page at the current time point from the database component of the configuration terminal in response to logging into the mobile terminal check-in page, the data acquisition module 510 is used to:

[0183] In response to logging into the mobile terminal check-in page, determine the component identifier of the check-in page component that should be displayed on the mobile terminal check-in page;

[0184] Using the component identifier, the check-in configuration data of the check-in page component is determined by searching the database component of the configuration terminal.

[0185] Furthermore, when the page rendering module 520 renders the check-in page component onto the mobile terminal check-in page according to the time display format carried by the check-in configuration data, the page rendering module 520 is used to:

[0186] The check-in configuration data is parsed to determine the checked-in date, the checked-in icon for the checked-in date, the button icon for the check-in button in the check-in page component, the date to be checked in, the check-in icon for the date to be checked in, and the display icon for the reward date;

[0187] Based on the time display format and the current time, determine the target time period for the sign-in page component to be displayed on the sign-in page;

[0188] The system tracks the number of times a user has checked in, the number of dates to be missed, the dates to be missed due, and the dates not checked in during the target time period.

[0189] By combining the checked-in dates, the number of checked-ins, and the unchecked-in dates, the reward dates for the reward nodes that will reward the user within the target time period are determined.

[0190] By combining the time display format, the already checked-in icon, the button icon, the make-up check-in icon, and the display icon, the check-in page components for the target time period are rendered onto the mobile terminal check-in page.

[0191] The sign-in page display device provided in this application embodiment, in response to logging into the mobile terminal sign-in page, retrieves sign-in configuration data from the database component of the configuration terminal, specifying the sign-in page component to be displayed on the mobile terminal sign-in page at the current time. Following the time display format carried by the sign-in configuration data, the device renders the sign-in page component onto the mobile terminal sign-in page using the sign-in configuration data. This enables rapid rendering of the sign-in page.

[0192] Please see Figure 6 , Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 6 As shown, the electronic device 600 includes a processor 610, a memory 620, and a bus 630.

[0193] The memory 620 stores machine-readable instructions executable by the processor 610. When the electronic device 600 is running, the processor 610 and the memory 620 communicate via the bus 630. When the machine-readable instructions are executed by the processor 610, they can perform the operations described above. Figure 1 The steps of the check-in page configuration method in the illustrated method embodiment, and / or the execution as described above. Figure 3 The steps of the sign-in page display method in the method embodiment shown are described in detail in the method embodiment, and will not be repeated here.

[0194] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can perform the above-described actions. Figure 1 The steps of the check-in page configuration method in the illustrated method embodiment, and / or the execution as described above. Figure 3 The steps of the sign-in page display method in the method embodiment shown are described in detail in the method embodiment, and will not be repeated here.

[0195] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0196] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the shown or discussed mutual couplings, direct couplings, or communication connections may be through some communication interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0197] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0198] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0199] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0200] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The scope of protection of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this application. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for configuring a check-in page, characterized in that, The configuration method, applied to a configuration terminal, includes: In response to the page creation request, the user is redirected to the page editing interface; the page editing interface includes a canvas area, a component list, and an attribute configuration area; the component list displays the sign-in page component; In response to a component selection operation on the check-in page component, the check-in page component is displayed in the canvas area, and multiple check-in attribute settings for configuring the page display format of the check-in page component are displayed in the attribute configuration area. These check-in attribute settings include calendar format configuration, reward method configuration, reward content configuration, reward icon configuration, jump type configuration, jump link configuration, and make-up check-in task configuration. The calendar format configuration is used to configure the time display format of the calendar time component in the check-in page component. The reward method configuration is used to configure the reward distribution method for each reward during the execution of the check-in activity. The reward content configuration is used to configure the reward content for each reward node during the execution of the check-in activity. The reward icon configuration is used to configure the display icon for the reward date corresponding to each reward node in the calendar time component. The page jump type configuration is used to configure the jump method and jump type of the check-in page. The jump link configuration is used to configure the page link to be jumped to when a jump action occurs. The make-up check-in task configuration is used to configure make-up check-in tasks. In response to attribute configuration operations for the multiple check-in attribute settings, configure the page display format of the check-in page component and generate check-in configuration data for the check-in page component; The check-in configuration data is stored in the database component so that the mobile terminal can render the check-in page of the check-in activity through the check-in configuration data of the check-in page component.

2. The configuration method according to claim 1, characterized in that, The check-in configuration data includes calendar display data; the response to the attribute configuration operation for the multiple check-in attribute settings configures the page display format of the check-in page component and generates the check-in configuration data for the check-in page component, including: In response to the format attribute configuration operation for the calendar format configuration item, configure the time display format of the calendar time component in the check-in page component, and generate calendar display data indicating the time display format of the calendar time component; wherein, the time display format includes display by week and display by month.

3. The configuration method according to claim 2, characterized in that, The check-in configuration data includes reward configuration data; the response to the attribute configuration operation for the multiple check-in attribute settings configures the page display format of the check-in page component and generates the check-in configuration data for the check-in page component, including: In response to the configuration operation for the reward method configuration item, determine the reward distribution method for each reward item during the execution of the check-in activity, and generate first reward data indicating the reward distribution method for each reward item; In response to the content configuration operation for the reward content configuration item, determine the reward content of each reward node during the execution of the check-in activity, and generate second reward data indicating the reward content of each reward node; In response to the icon configuration operation for the reward icon configuration item, determine the display icon for the reward date corresponding to each reward node in the calendar time component, and generate third reward data indicating the display icon for the reward date corresponding to each reward node; Based on the first reward data, the second reward data, and the third reward data, the reward configuration data included in the check-in configuration data is generated.

4. The configuration method according to claim 1, characterized in that, The check-in configuration data includes page link data; the response to the attribute configuration operation for the multiple check-in attribute settings configures the page display format of the check-in page component and generates the check-in configuration data for the check-in page component, including: In response to the type configuration operation for the jump type configuration item, configure the jump method and the jump type when the sign-in page jumps when claiming the reward content of any reward node, and generate first jump data indicating the jump method and the jump type; In response to a link configuration operation for the jump link configuration item, configure the page link to be jumped to in the event of a jump, and generate second jump data indicating the page link; Based on the first redirect data and the second redirect data, the page link data included in the check-in configuration data is generated.

5. The configuration method according to claim 1, characterized in that, The check-in configuration data includes make-up check-in task data; the response to the attribute configuration operation for the multiple check-in attribute settings configures the page display format of the check-in page component and generates the check-in configuration data for the check-in page component, including: In response to the supplementary signature configuration operation for the supplementary signature task configuration item, determine the supplementary signature task to be executed and the supplementary signature icon for each supplementary signature date, and generate supplementary signature task data indicating the supplementary signature date and the supplementary signature task corresponding to each supplementary signature date.

6. A method for displaying a check-in page, characterized in that, Applied to mobile terminals, the display method includes: In response to logging into the mobile terminal check-in page, the system retrieves check-in configuration data from the database component of the configured terminal, specifying the check-in page component to be displayed on the mobile terminal check-in page at the current time. This check-in configuration data is generated by configuring multiple check-in attribute settings in the attribute configuration area, which are used to configure the page display format of the check-in page component. These attribute settings include calendar format configuration, reward method configuration, reward content configuration, reward icon configuration, jump type configuration, jump link configuration, and make-up check-in task configuration. The calendar format configuration is used to configure... The check-in page component includes the following settings: Time display format in the calendar time component; Reward method configuration item for configuring the reward distribution method for each reward during the check-in activity; Reward content configuration item for configuring the reward content for each reward node during the check-in activity; Reward icon configuration item for configuring the display icon for the reward date corresponding to each reward node in the calendar time component; Page jump type configuration item for configuring the jump method and type of the check-in page; Jump link configuration item for configuring the page link to be jumped to when a jump occurs; and Make-up check-in task configuration item for configuring make-up check-in tasks. According to the time display format carried by the check-in configuration data, the check-in page component is rendered onto the mobile terminal check-in page using the check-in configuration data; wherein, the time display format includes either weekly display or monthly display.

7. The display method according to claim 6, characterized in that, The response to logging into the mobile terminal check-in page involves retrieving check-in configuration data from the database component of the configured terminal, specifying the check-in page component that should be displayed on the mobile terminal check-in page at the current time. This includes: In response to logging into the mobile terminal check-in page, determine the component identifier of the mobile terminal check-in page component that should be displayed on the check-in page; Using the component identifier, the check-in configuration data of the check-in page component is determined by searching the database component of the configuration terminal.

8. The display method according to claim 6, characterized in that, The step of rendering the check-in page component onto the mobile terminal check-in page according to the time display format carried in the check-in configuration data includes: The check-in configuration data is parsed to determine the checked-in date, the checked-in icon for the checked-in date, the button icon for the check-in button in the check-in page component, the date to be checked in, the check-in icon for the date to be checked in, and the display icon for the reward date; Based on the time display format and the current time, determine the target time period for the sign-in page component to be displayed on the sign-in page; The system tracks the number of times a user has checked in, the number of dates to be missed, the dates to be missed due, and the dates not checked in during the target time period. By combining the checked-in dates, the number of checked-ins, and the unchecked-in dates, the reward dates for the reward nodes that will reward the user within the target time period are determined. By combining the time display format, the already checked-in icon, the button icon, the make-up check-in icon, and the display icon, the check-in page components for the target time period are rendered onto the mobile terminal check-in page.

9. A configuration device for a check-in page, characterized in that, The configuration device is applied to a configuration terminal and includes: The interface navigation module is used to respond to a page creation request and navigate to the page editing interface; wherein, the page editing interface includes a canvas area, a component list, and an attribute configuration area; the component list displays the sign-in page component; The component selection module responds to component selection operations for the check-in page component, displays the check-in page component in the canvas area, and displays multiple check-in attribute settings in the attribute configuration area to configure the page display format of the check-in page component. The check-in attribute settings include calendar format configuration, reward method configuration, reward content configuration, reward icon configuration, jump type configuration, jump link configuration, and make-up check-in task configuration. The calendar format configuration is used to configure the time display format of the calendar time component in the check-in page component. The reward method configuration is used to configure the reward distribution method for each reward during the check-in activity. The reward content configuration is used to configure the reward content for each reward node during the check-in activity. The reward icon configuration is used to configure the display icon for the reward date corresponding to each reward node in the calendar time component. The page jump type configuration is used to configure the jump method and type of the check-in page. The jump link configuration is used to configure the page link to be jumped to when a jump action occurs. The make-up check-in task configuration is used to configure make-up check-in tasks. The attribute configuration module is used to respond to attribute configuration operations for the multiple check-in attribute settings, configure the page display format of the check-in page component, and generate the check-in configuration data of the check-in page component. The data storage module is used to store the check-in configuration data in the database component, so that the mobile terminal can render the check-in page of the check-in activity through the check-in configuration data of the check-in page component.

10. A display device for a check-in page, characterized in that, The display device, used in mobile terminals, includes: The data acquisition module, in response to logging into the mobile terminal's check-in page, retrieves check-in configuration data from the database component of the configuration terminal, specifying the check-in page component to be displayed at the current time. This check-in configuration data is generated by configuring multiple check-in attribute settings in the attribute configuration area, which configure the page display format of the check-in page component. These attribute settings include calendar format configuration, reward method configuration, reward content configuration, reward icon configuration, jump type configuration, jump link configuration, and make-up check-in task configuration. The calendar format configuration is used to configure... The configuration options are as follows: **Time Display Format in the Calendar Time Component of the Check-in Page:** The **Reward Method Configuration:** This option configures the reward distribution method for each reward during the check-in activity. The **Reward Content Configuration:** This option configures the reward content for each reward node during the check-in activity. The **Reward Icon Configuration:** This option configures the display icon for the reward date corresponding to each reward node in the Calendar Time Component. The **Page Jump Type Configuration:** This option configures the jump method and type for the check-in page. The **Jump Link Configuration:** This option configures the page link to be jumped to when a jump occurs. The **Make-up Check-in Task Configuration:** This option configures make-up check-in tasks. The page rendering module is used to render the sign-in page component onto the sign-in page according to the time display format carried by the sign-in configuration data; wherein, the time display format includes either weekly display or monthly display.

Images