CN112328143B - Button activation method and device - Google Patents
Button activation method and device Download PDFInfo
- Publication number
- CN112328143B CN112328143B CN202011367666.2A CN202011367666A CN112328143B CN 112328143 B CN112328143 B CN 112328143B CN 202011367666 A CN202011367666 A CN 202011367666A CN 112328143 B CN112328143 B CN 112328143B
- Authority
- CN
- China
- Prior art keywords
- button
- sub
- interactive
- service
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 230000004913 activation Effects 0.000 title claims abstract description 32
- 230000002452 interceptive effect Effects 0.000 claims abstract description 127
- 230000001960 triggered effect Effects 0.000 claims abstract description 32
- 238000012544 monitoring process Methods 0.000 claims abstract description 8
- 230000000694 effects Effects 0.000 claims description 49
- 230000009191 jumping Effects 0.000 claims description 5
- 230000001747 exhibiting effect Effects 0.000 claims 2
- 230000003213 activating effect Effects 0.000 abstract description 8
- 230000008569 process Effects 0.000 description 27
- 238000013461 design Methods 0.000 description 14
- 230000000007 visual effect Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 238000011161 development Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003086 colorant Substances 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
- G06F3/0482—Interaction with lists of selectable items, e.g. menus
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
- G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The application provides a button activating method, which comprises the following steps: monitoring user operation of a user aiming at a target interface comprising a plurality of service scenes; the target interface comprises an interactive button; the button activation state of the interactive button comprises a plurality of button sub-states; the button sub-states respectively correspond to different service scenes; determining a target service scene triggered by a user based on the monitored user operation; and switching the interactive button to a button sub-state corresponding to the target service scene. The application can expand the business semantics of the button activation state.
Description
Technical Field
The present application relates to the field of computer applications, and in particular, to a button activation method and apparatus.
Background
In a traditional mobile terminal application, an interactive button provided in a user interface can be generally used as an entrance for a user to finish a subsequent business process; for example, taking the "payment button" provided in the payment application as an example, when the user needs to complete a payment transaction through the payment application, the "payment button" needs to be triggered, such as by "clicking", to initiate a subsequent payment process. In order to guide the user to complete the subsequent business process through the interactive button, the developer usually designs different button states for the interactive button to express different business semantics in the development stage of the application. However, with the increasing complexity of the service scenario of the mobile terminal, the existing button state is single, so that the actual service requirement cannot be met gradually.
Disclosure of Invention
The application provides a button activating method which is applied to a client, and comprises the following steps:
monitoring user operation of a user aiming at a target interface comprising a plurality of service scenes; the target interface comprises an interactive button; the button activation state of the interactive button comprises a plurality of button sub-states, and the plurality of button sub-states respectively correspond to different service scenes;
determining a target service scene triggered by a user based on the monitored user operation;
and switching the interactive button to a button sub-state corresponding to the target service scene.
Optionally, the target interface is preconfigured with service options corresponding to the service scene;
the determining the target service scene triggered by the user based on the monitored user operation comprises the following steps:
determining target service options selected by a user in the target interface based on the monitored user operation;
And determining the service scene corresponding to the target service option as the target service scene triggered by the user.
Optionally, different button sub-states are respectively preconfigured with different button switching special effects;
The switching the interactive button to the button sub-state corresponding to the target service scene includes:
acquiring a button switching special effect preconfigured for a button sub-state corresponding to the target service scene;
and playing the button switching special effect at a position corresponding to the interactive button, and switching the interactive button to a button sub-state corresponding to the target service scene when the button switching special effect playing is finished.
Optionally, the method further comprises:
after the interactive button is switched to the button sub-state corresponding to the target service scene, determining whether the user triggers the interactive button or not based on the monitored user operation;
if the user triggers the interactive button, jumping to a service interface corresponding to the target service scene to finish a subsequent service flow;
wherein, different business scenes correspond to different business interfaces respectively.
Optionally, the different button sub-states respectively correspond to different button styles.
The application also provides a button activating device which is applied to a client, and the device comprises:
The monitoring module monitors user operation of a user aiming at a target interface comprising various service scenes; the target interface comprises an interactive button; the button activation state of the interactive button comprises a plurality of button sub-states, and the plurality of button sub-states respectively correspond to different service scenes;
the determining module is used for determining a target service scene triggered by the user based on the monitored user operation;
and the switching module is used for switching the interactive button to a button sub-state corresponding to the target service scene.
Optionally, the target interface is preconfigured with service options corresponding to the service scene;
The determination module:
determining target service options selected by a user in the target interface based on the monitored user operation;
And determining the service scene corresponding to the target service option as the target service scene triggered by the user.
Optionally, different button sub-states are respectively preconfigured with different button switching special effects;
the switching module is used for:
acquiring a button switching special effect preconfigured for a button sub-state corresponding to the target service scene;
and playing the button switching special effect at a position corresponding to the interactive button, and switching the interactive button to a button sub-state corresponding to the target service scene when the button switching special effect playing is finished.
Optionally, the determining module further:
after the interactive button is switched to a button sub-state corresponding to the target service scene, determining whether the interactive button is triggered by a user based on the monitored user operation;
if the user triggers the interactive button, jumping to a service interface corresponding to the target service scene to finish a subsequent service flow;
wherein, different business scenes correspond to different business interfaces respectively.
Optionally, the different button sub-states respectively correspond to different button styles.
In the present application, the activation state of the button may be further configured to be a plurality of sub-states respectively corresponding to different service scenarios based on the actual kind of service scenario contained in the target interface; when a user triggers a certain service scene under the service flow corresponding to the button, the button can be immediately switched to a sub-state corresponding to the service scene;
The system can distinguish the business scene triggered by the user by looking at different sub-states presented by the button, so that the business semantics conveyed by the activation state of the button can be further expanded, the adaptability of the button to different business scenes can be remarkably improved, and the button can meet more diversified business scenes.
Drawings
FIG. 1 is a flow chart of a button activation method according to an embodiment of the present application;
FIG. 2 is a schematic diagram showing a scenario of triggering payment via a "payment interface" according to an embodiment of the present application;
FIG. 3 is a schematic diagram of another embodiment of the present application showing triggering of a payment scenario via a "payment interface";
FIG. 4 is a logical block diagram of a button activation apparatus according to an embodiment of the present application;
fig. 5 is a hardware architecture diagram of a client carrying the button activating device according to an embodiment of the present application.
Detailed Description
In conventional button-state designs, the button state of the interactive button is typically designed to be both "active" and "inactive".
By active state, it is meant that the interactive button is in an operable state. When the business flow corresponding to the interactive button meets the triggering condition, the interactive button can be switched to an activated state; for example, in one embodiment shown, the interactive button may be highlighted or the color of the button changed to indicate that the interactive button is currently in an operational state. In this way, the user can be guided to "click" on the interactive button, completing the subsequent business process.
By inactive state it is meant that the interactive button is in an inoperable state. When the business flow corresponding to the interactive button does not meet the triggering condition, the interactive button is kept in a non-activated state consistently; for example, in one embodiment shown, the interactive button may be consistently maintained in gray to indicate that the interactive button is currently in an inoperable state. In this way, the user may be prevented from "clicking" on the interactive button.
In practical application, for an interactive button, the corresponding business process is often unique; for example, a "payment button" provided by a payment client is typically used only to trigger a payment business process; however, a business process corresponding to a certain interactive button may include multiple business scenarios. In the traditional button state design, the difference of the button states of the interactive buttons on the service scene is not considered; therefore, when a specific service scenario under a service flow corresponding to an interactive button satisfies a trigger condition, the interactive button is usually only switched to an active state by default. And the single activation state obviously cannot convey more business semantics, so that the system cannot accurately distinguish specific business scenes.
For example, taking the example of a "pay button" provided to the user by the payment client, the "pay button" is typically used to trigger a payment business process; however, in practical applications, even a payment business process triggered by the same "payment button" may possibly contain multiple different payment scenarios; for example, "order payment scenario," "loving lunch donation payment scenario," and so forth; when the "payment button" is in an active state, it is generally only possible to communicate that the payment business process corresponding to the "payment button" has satisfied the business semantics of the trigger condition, and the system cannot accurately distinguish which payment scenario under the payment business process has currently satisfied the trigger condition.
Therefore, the traditional button state design has the defect that the button state is single and more business semantics cannot be transmitted.
In view of this, the present application aims to propose a button state design scheme for further subdividing the activation state of a button based on a business scenario.
When implemented, the activation state of the button may be further configured to correspond to multiple sub-states of different business scenarios, respectively, based on the actual type of business scenario contained in the target interface; when a user triggers a certain service scene under the service flow corresponding to the button, the button can be immediately switched to a sub-state corresponding to the service scene;
In the application, the system can distinguish the business scene triggered by the user by looking at different sub-states presented by the button, so that the business semantics conveyed by the activation state of the button can be further expanded, the adaptability of the button to different business scenes can be obviously improved, and the button can meet more diversified business scenes.
The present application is described below by way of specific embodiments and in connection with specific application scenarios.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating a button activating method applied to a client according to an embodiment of the present application; the method performs the steps of:
Step 101, monitoring user operation of a user aiming at a target interface comprising a plurality of business scenes; the target interface comprises an interactive button; the button activation state of the interactive button comprises a plurality of button sub-states; the button sub-states respectively correspond to different service scenes;
Step 102, determining a target service scene triggered by a user based on the monitored user operation;
And step 103, switching the interactive button to a button sub-state corresponding to the target service scene.
The client may refer to any form of client software capable of providing related services to a user; such as a web client, or an APP application.
The target interface specifically refers to a related service interface provided by the client side to a user; wherein, the target interface can comprise a plurality of business scenes;
For example, taking the above-mentioned client as a payment client, in this case, the above-mentioned target interface may specifically be a payment interface containing multiple payment scenarios, through which a user may trigger different payment scenarios such as "order payment", "loving lunch donation", and the like.
The interactive button may be an interactive button provided in the service interface for triggering a related service flow. The user may trigger the interactive button, such as by "clicking", to initiate a business process corresponding to the interactive button.
For example, taking the client as a payment client, in this case, the target interface may specifically be a "payment interface", the interaction button may be a "payment button" provided in the payment interface, and the user may trigger the "payment button" by, for example, clicking, to initiate a subsequent payment procedure, and complete the related payment service.
The service scenario specifically refers to a specific service type contained in a service flow corresponding to the interactive button; in practical application, under the service flow corresponding to the interactive button, multiple service scenes can be included; the user can trigger different service scenes in the target page by executing different user operations in the target page.
For example, taking the interactive button as a "payment button" and the business process as a "payment process" triggered by the "payment button", even though the payment business process is triggered by the same "payment button", different payment scenarios such as "order payment", "loving lunch donation" and the like may be included. In this scenario, the user may perform different user operations in the "payment interface" to trigger different payment scenarios, such as "order payment scenario", "love lunch donation payment scenario", etc., respectively.
In the application, in order to realize the further expansion of the service semantics conveyed by the interactive button, a button state design idea is provided for further dividing the activation state of the button into a plurality of sub-states.
The technical scheme of the application is described in detail below through three stages of sub-state division, service scene triggering and active state switching.
1) Partitioning of sub-states
In the application, when the developer designs the button state of the interactive button, on the basis of the traditional button state design, the activation state of the interactive button can be further subdivided based on the actual types of the contained business scenes under the corresponding business flow of the interactive button, and the activation state of the interactive button is divided into a plurality of button sub-states.
Wherein, for each divided button sub-state, the sub-state can respectively correspond to one service scene under the service flow corresponding to the interactive button; an independent button sub-state can be defined for each service scenario.
The number of button sub-states in which the activation state of the interactive button is finally divided depends on the type of the service scene included in the service flow corresponding to the interactive button, and is not particularly limited in the application; in practical applications, those skilled in the art can perform custom configuration on the types of service scenarios and the number of button sub-states that are finally divided based on the actual service requirements.
For example, taking the above business process as an example of a "payment process" triggered by the "payment button", a developer may divide the "payment process" into different "payment scenarios" based on actual business requirements; for example, "order payment scenario," "donation payment scenario," "daily payment scenario," and so forth; then is under the "payment flow" the various payment scenarios involved are those that, a button sub-state is defined respectively.
It should be emphasized that the "activation state" of the interactive buttons described in the present application will not be a single button state, as compared to conventional button state design concepts. But rather a set of "active states" consisting of several button sub-states together; for each button sub-state, an independent "active state". When the interactive button is switched to any one of the sub-states, the interactive button is indicated to be in an operable state currently.
Different business scenes under the business processes corresponding to the interactive buttons are respectively corresponding to different button sub-states, so that different business semantics can be accurately transmitted through the different button sub-states, further different business scenes can be intuitively distinguished, and in practical application, different visual designs can be respectively carried out according to the different button sub-states.
In the application, the visual design for differentiating different button sub-states can specifically comprise two parts of differential design on the special effect of button switching and differential design on the button style:
In one embodiment shown, different button switching effects may be configured for different button sub-states, respectively. The button switching special effect refers to a button display effect which needs to be played at a position corresponding to the interactive button when the interactive button is switched to a corresponding button sub-state.
The specific display content and display mode of the button switching special effect are not particularly limited in the application, and in practical application, a person skilled in the art can perform custom configuration based on practical requirements;
For example, in practical application, the button switching special effects may be dynamic changes of colors of the interactive buttons, switching animations played in a specific area around the interactive buttons or the like.
In the illustrated embodiment, different button styles may also be configured for different button sub-states, respectively. The button style refers to basic attributes such as color, size, shape, text on the button, etc. presented by the interactive buttons. That is, in the present application, when the interactive button is switched to different button sub-states, the color, size, shape, text on the button, etc. of the interactive button may be different, and thus the interactive button may exhibit a differentiated display effect in different button sub-states.
The specific type of button style configured for each button sub-state is not particularly limited in the present application, and in practical application, a person skilled in the art may also perform custom configuration based on actual requirements.
By means of the method, different button switching special effects or button patterns are respectively configured for different button sub-states, so that when the interactive buttons are switched among the different button sub-states, a differentiated visual effect can be displayed, and the different button sub-states can be intuitively distinguished.
When the method is implemented, in an initial state, a state identifier can be respectively configured for each button sub-state, and a scene identifier can be respectively configured for various business scenes contained in the business process corresponding to the interactive button.
After the above allocation process is completed, the state identifier of each button sub-state and the scene identifier of the service scene corresponding to the button sub-state can be mapped and stored based on the configuration of the developer, so as to generate a corresponding configuration file.
The developer can develop the execution codes related to the button switching special effects and the button styles in the background for each button sub-state based on a specific development language (for example, java language for an android system and object C language for an IOS system), and then package the developed execution codes into a visual component for the client to call.
Finally, the packaged visual components and the state identifiers of the corresponding button sub-states can be mapped and stored, so that the client can quickly retrieve relevant visual components to execute and call based on the state identifiers of the button sub-states.
At this time, based on the actual types of the included service scenes under the service flow corresponding to the interactive button, the initialization configuration process of further subdividing the activation state of the interactive button is completed.
2) Triggering of business scenarios
In the application, the client can monitor the user operation of the user aiming at the target interface and judge whether the monitored user operation is a preset operation or not so as to identify the target service scene triggered by the user.
When the user triggers the service scene, the user operation executed in the target interface may include any type of user operation capable of triggering the related service scene;
For example, taking a terminal device on which the client is mounted as a touch screen terminal device, the user operation may include any form of touch operation for the target interface by the user; such as a click operation, a long press operation, a slide operation, a special gesture operation, and the like.
When the method is realized, the client can respectively define a preset operation for triggering the current service scene according to each service scene; when the client monitors the user operation of the user aiming at the target interface, the monitored user operation can be matched with the defined preset operation for triggering each service scene; when the monitored user operation matches any preset operation, the client can immediately trigger the service scene corresponding to the preset operation and continue to execute the subsequent button state switching flow.
In the illustrated embodiment, in order to implement quick triggering of various service scenarios under the service flow corresponding to the interactive button, a plurality of service options corresponding to each service scenario may be provided in the target interface. In this case, the preset operation for triggering each service scenario may be a selection operation for a service option corresponding to each service scenario.
When the method is realized, the client can still monitor the user operation of the user aiming at the target interface and judge whether the monitored user operation is the selected operation aiming at each service option provided in the target interface; if the monitored user operation is the selection operation of any service option in the target interface, the service option can be immediately selected at the moment, the service scene corresponding to the service option is triggered, the subsequent process is executed, and the interactive button is switched to the button sub-state corresponding to the service scene.
In this case, the user can not only select the corresponding service option in the target interface, but also quickly trigger the service scene corresponding to the service option; and when the user triggers the corresponding service scene by selecting the service option, and switches the interactive button to the button sub-state corresponding to the service scene, the user can also reselect the service option in the target interface to complete the quick switching between different button sub-states.
In addition to the service options corresponding to each service scenario described above, the service options corresponding to each service scenario may be set on the same target interface with the interactive button, or may be set on other interfaces than the target interface in practical application; that is, in the present application, the service options corresponding to each service scenario may be provided on the target interface simultaneously with the interactive button, or may be provided on different interfaces.
For example, in one implementation, the business options corresponding to each business scenario may be provided in a separate "scenario selection" interface; after the user selects the corresponding service option, the client can execute a service jump to the target interface, and then complete the subsequent switching process of button sub-states in the target interface.
3) Switching of active states
In the application, when the client determines the target service scene triggered by the user by monitoring the user operation of the user on the target interface, the subsequent process of switching the interactive button to the activated state can be completed based on the button sub-state pre-configured for the target service scene.
When the method is realized, the client can call related configuration files by taking the scene identification of the target service scene as a query index, and query the state identification of the button sub-state configured for the target service scene; after the state identifier of the button sub-state configured for the target service scene is queried, the client can further use the state identifier as a query index to query the relevant visual component developed by the developer, acquire the button switching special effect and the button style preconfigured for the button sub-state, and play the button switching special effect at the position corresponding to the interactive button. When the button switching special effect playing is finished, the client can also switch the button style of the interactive button based on the button style preconfigured for the button sub-state. When the button style switching is completed, the interactive button is successfully switched to the button sub-state.
In the application, after the interactive button is successfully switched to the button sub-state corresponding to the target service scene triggered by the user by executing the switching process, the interactive button is in an operable state at the moment, and the user can start the subsequent service flow corresponding to the target service scene by further triggering the operation button.
When the method is implemented, the client can define a preset operation for triggering the interactive button aiming at the interactive button; for example, the preset operation may specifically be a "click operation" for the above-mentioned interactive button. The client can monitor the user operation of the user on the target page in the background, and can trigger the service flow corresponding to the target service scene immediately after the click operation of the user on the interactive button is monitored.
It should be noted that, because there may be a certain difference in the service execution flow due to different service scenarios, the developer may configure different service interfaces for different service scenarios respectively. I.e. for each service option preconfigured in the above-mentioned target interface, a different service interface will be respectively corresponding.
The "different service interfaces" described above may refer to completely different service interfaces with different page addresses (such as URL addresses) corresponding to different service scenes, or may refer to the same page address of the service interface corresponding to the different service scenes, but the page contents displayed in the interfaces under the different service scenes are different.
In this case, after the client monitors the click operation of the user on the interactive button, the client may trigger the service flow corresponding to the target service scenario immediately, jump to the service interface corresponding to the target service scenario, and complete the subsequent service flow.
In this way, on the one hand, the user can trigger the interactive button to switch between different button sub-states by selecting different service options; moreover, when the interactive button is switched between different button sub-states, different button switching special effects are respectively played, so that stable transition between the different button sub-states can be realized by playing the different button switching special effects.
On the other hand, the user can trigger the interactive button to switch between different button sub-states by selecting different service options, and after the switching of the button sub-states is completed, if the user further triggers the interactive button, the user can jump to different service interfaces to execute the subsequent service flow corresponding to the service scene triggered by the user.
Therefore, the application further subdivides the activation state of the interactive button according to the category of the service scene, and can further expand the service semantics conveyed by the activation state of the interactive button, so that the interactive button can adapt to diversified service scenes.
The technical solutions in the above embodiments are described in detail below in connection with specific application scenarios.
In this example, the client may be a "payment client"; the target interface may be a "payment interface"; the interactive button may be an "immediate payment" button provided by the payment interface to the user. The payment process corresponding to the "immediate payment" button may further include: "loving lunch donation payment scenario" and "order payment scenario". The activation states of the "pay immediate" button described above are divided into "button sub-state 1" and "button sub-state 2".
Wherein, the payment scene of the love lunch donation corresponds to the button sub-state 2; the "order payment scenario" corresponds to "button sub-state 2". The button switching effect configured for the "button sub-state 1" is "button switching effect 1"; the button switch effect configured for the "button sub-state 2" is "button switch effect 2".
Referring to fig. 2, fig. 2 is a schematic diagram illustrating a scenario of triggering payment through a "payment interface" in the present example.
As shown in fig. 2, in the "payment interface", a user option corresponding to the "love lunch donation payment scenario" may be provided by default. The "pay immediate" button may be in an inoperable inactive state in an initial state.
With continued reference to fig. 2, the user may enter a payment amount by clicking on the entry box where "transfer amount" is located, completing "order payment". When the client monitors the click operation of the user on the input box where the transfer amount is located and obtains the payment amount input by the user, the client can trigger an order payment scene in the payment interface immediately, and play the button switching special effect 1 at the position corresponding to the button for immediate payment. When the play of the button switching special effect 1 is finished, the button of the immediate payment is switched to the button sub-state 1, and the button of the immediate payment is switched from the inoperable state to the operable state.
In this case, the user may initiate the flow of subsequent order payments by continuing to trigger the "immediate payment" described above, completing the payment of the order.
Referring to fig. 3, fig. 4 is a schematic diagram illustrating another triggering of a payment scenario through a "payment interface" according to the present embodiment.
As shown in fig. 3, after the "order payment scenario" is triggered, the user may also trigger the "payment scenario for loving lunch donation" in the "payment interface" by selecting the user option corresponding to the "payment scenario for loving lunch donation" described above, so as to complete the switching of the "immediate payment" button from the "button sub-state 1" to the "button sub-state 2".
With continued reference to fig. 3, when the client monitors the "selection operation" of the user option of the user for the "payment scene for loving lunch donation", the "payment scene for loving lunch donation" may be triggered immediately, and the "button switching special effect 2" is played at the position corresponding to the "immediate payment" button.
For example, the "button switch special effect 2" shown in fig. 3 is a "pay immediate" button that changes color dynamically in the left-to-right direction and outputs a presentation special effect of a heart-shaped icon around the button.
When the "button switch special effect 2" play is finished, the "pay immediately" button is switched to "button sub-state 2". At this time, the above-mentioned "immediate payment" button is still in an operable state.
In this way, the user can quickly trigger different payment scenes through the payment interface to switch the immediate payment button to different button sub-states; in addition, the button for immediate payment can convey different business semantics through different visual presentation effects under different button sub-states.
As can be seen from the above embodiments, the button state design scheme provided by the present application can further configure the activation state of the button to be respectively corresponding to multiple sub-states of different service scenarios based on the actual types of the service scenarios included in the target interface; when a user triggers a certain service scene under the service flow corresponding to the button, the button can be immediately switched to a sub-state corresponding to the service scene;
The system can distinguish the business scene triggered by the user by looking at different sub-states presented by the button, so that the business semantics conveyed by the activation state of the button can be further expanded, the adaptability of the button to different business scenes can be remarkably improved, and the button can meet more diversified business scenes.
The application also provides an embodiment of the device corresponding to the embodiment of the method.
Referring to fig. 4, the present application proposes a button activating device 40 applied to a client; referring to fig. 5, the hardware architecture of the client carrying the button activating device 40 generally includes a CPU, a memory, a nonvolatile memory, a network interface, an internal bus, and the like; taking a software implementation as an example, the button activating device 40 may be generally understood as a computer program loaded in a memory, and the logic device formed by combining software and hardware after the CPU runs, where the device 40 includes:
A monitoring module 401, configured to monitor user operations of a user for a target interface including multiple service scenarios; the target interface comprises an interactive button; the button activation state of the interactive button comprises a plurality of button sub-states, and the plurality of button sub-states respectively correspond to different service scenes;
a determining module 402, configured to determine a target service scenario triggered by the user based on the monitored user operation;
And the switching module 403 switches the interaction button to a button sub-state corresponding to the target service scene.
In this example, the target interface is preconfigured with service options corresponding to the service scenario;
the determination module 402:
determining target service options selected by a user in the target interface based on the monitored user operation;
And determining the service scene corresponding to the target service option as the target service scene triggered by the user.
In this example, different button sub-states are respectively preconfigured with different button switching special effects;
the switching module 403:
acquiring a button switching special effect preconfigured for a button sub-state corresponding to the target service scene;
and playing the button switching special effect at a position corresponding to the interactive button, and switching the interactive button to a button sub-state corresponding to the target service scene when the button switching special effect playing is finished.
In this example, the determining module 402 further:
after the interactive button is switched to a button sub-state corresponding to the target service scene, determining whether the interactive button is triggered by a user based on the monitored user operation;
if the user triggers the interactive button, jumping to a service interface corresponding to the target service scene to finish a subsequent service flow;
wherein, different business scenes correspond to different business interfaces respectively.
In this example, different button sub-states correspond to different button styles, respectively.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present application. Those of ordinary skill in the art will understand and implement the present application without undue burden.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.
The foregoing description of the preferred embodiments of the application is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the application.
Claims (12)
1. A button activation method, applied to a client, the method comprising:
Monitoring user operation of a user aiming at a target interface comprising a plurality of service scenes; the target interface comprises an interactive button; the button activation state of the interactive button comprises a plurality of button sub-states, and the plurality of button sub-states respectively indicate service semantics corresponding to different service scenes;
determining a target service scene triggered by a user based on the monitored user operation;
and switching the interactive button to a button sub-state for indicating the business semantics corresponding to the target business scene.
2. The method of claim 1, the target interface preconfigured with business options corresponding to the business scenario;
the determining the target service scene triggered by the user based on the monitored user operation comprises the following steps:
determining target service options selected by a user in the target interface based on the monitored user operation;
And determining the service scene corresponding to the target service option as the target service scene triggered by the user.
3. The method of claim 1, wherein different button sub-states are respectively preconfigured with different button switching effects;
The switching the interactive button to the button sub-state corresponding to the target service scene includes:
acquiring a button switching special effect preconfigured for a button sub-state corresponding to the target service scene;
and playing the button switching special effect at a position corresponding to the interactive button, and switching the interactive button to a button sub-state corresponding to the target service scene when the button switching special effect playing is finished.
4. The method of claim 3, the button switch special effects for exhibiting business semantics of the button sub-state indication; the button switching special effect comprises the dynamic change of the color of the interactive button and/or switching animation played in the area corresponding to the interactive button.
5. The method of claim 1, the method further comprising:
after the interactive button is switched to the button sub-state corresponding to the target service scene, determining whether the user triggers the interactive button or not based on the monitored user operation;
if the user triggers the interactive button, jumping to a service interface corresponding to the target service scene to finish a subsequent service flow;
wherein, different business scenes correspond to different business interfaces respectively.
6. The method of claim 1, wherein different button sub-states correspond to different button styles, respectively.
7. A button activation apparatus for use with a client, the apparatus comprising:
The monitoring module monitors user operation of a user aiming at a target interface comprising various service scenes; the target interface comprises an interactive button; the button activation state of the interactive button comprises a plurality of button sub-states, and the plurality of button sub-states respectively indicate service semantics corresponding to different service scenes;
the determining module is used for determining a target service scene triggered by the user based on the monitored user operation;
And the switching module is used for switching the interactive button to a button sub-state for indicating the business semantics corresponding to the target business scene.
8. The apparatus of claim 7, the target interface preconfigured with business options corresponding to the business scenario;
The determination module:
determining target service options selected by a user in the target interface based on the monitored user operation;
And determining the service scene corresponding to the target service option as the target service scene triggered by the user.
9. The apparatus of claim 7, different button sub-states are respectively preconfigured with different button switch special effects;
the switching module is used for:
acquiring a button switching special effect preconfigured for a button sub-state corresponding to the target service scene;
and playing the button switching special effect at a position corresponding to the interactive button, and switching the interactive button to a button sub-state corresponding to the target service scene when the button switching special effect playing is finished.
10. The apparatus of claim 9, the button switch special effects for exhibiting business semantics of the button sub-state indication; the button switching special effect comprises the dynamic change of the color of the interactive button and/or switching animation played in the area corresponding to the interactive button.
11. The apparatus of claim 7, the determination module further to:
after the interactive button is switched to a button sub-state corresponding to the target service scene, determining whether the interactive button is triggered by a user based on the monitored user operation;
if the user triggers the interactive button, jumping to a service interface corresponding to the target service scene to finish a subsequent service flow;
wherein, different business scenes correspond to different business interfaces respectively.
12. The apparatus of claim 7, wherein different button sub-states correspond to different button styles, respectively.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011367666.2A CN112328143B (en) | 2017-04-14 | 2017-04-14 | Button activation method and device |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710244791.6A CN107422943B (en) | 2017-04-14 | 2017-04-14 | Button activation method and device |
| CN202011367666.2A CN112328143B (en) | 2017-04-14 | 2017-04-14 | Button activation method and device |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710244791.6A Division CN107422943B (en) | 2017-04-14 | 2017-04-14 | Button activation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112328143A CN112328143A (en) | 2021-02-05 |
| CN112328143B true CN112328143B (en) | 2024-06-21 |
Family
ID=60424167
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710244791.6A Active CN107422943B (en) | 2017-04-14 | 2017-04-14 | Button activation method and device |
| CN202011367666.2A Active CN112328143B (en) | 2017-04-14 | 2017-04-14 | Button activation method and device |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710244791.6A Active CN107422943B (en) | 2017-04-14 | 2017-04-14 | Button activation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN107422943B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113156827B (en) * | 2021-04-02 | 2023-06-20 | 中国科学院计算技术研究所 | Intelligent device control method and system based on semantics |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104715309A (en) * | 2013-12-11 | 2015-06-17 | 阿里巴巴集团控股有限公司 | Service control method and device |
Family Cites Families (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7444599B1 (en) * | 2002-03-14 | 2008-10-28 | Apple Inc. | Method and apparatus for controlling a display of a data processing system |
| US20040217991A1 (en) * | 2003-04-30 | 2004-11-04 | International Business Machines Corporation | Method and apparatus for dynamic sorting and displaying of listing data composition and automating the activation event |
| US8686991B2 (en) * | 2007-09-26 | 2014-04-01 | Autodesk, Inc. | Navigation system for a 3D virtual scene |
| CN102789351B (en) * | 2011-05-20 | 2015-03-18 | 腾讯科技（深圳）有限公司 | Method and device for switching browsed interfaces |
| CN102207872B (en) * | 2011-06-04 | 2014-08-06 | 中国移动通信集团内蒙古有限公司 | Method and system for customizing Web UI (User Interface) control according to user requirements |
| CN104660797B (en) * | 2013-11-25 | 2019-06-18 | 中兴通讯股份有限公司 | Operation processing method and device |
| JP6259368B2 (en) * | 2013-11-28 | 2018-01-10 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカＰａｎａｓｏｎｉｃ Ｉｎｔｅｌｌｅｃｔｕａｌ Ｐｒｏｐｅｒｔｙ Ｃｏｒｐｏｒａｔｉｏｎ ｏｆ Ａｍｅｒｉｃａ | Control method of mobile terminal |
| CN103761041A (en) * | 2014-01-13 | 2014-04-30 | 联想(北京)有限公司 | Information processing method and electronic device |
| CN105094576B (en) * | 2014-04-21 | 2018-05-08 | 北京奇虎科技有限公司 | Application scenarios switching method and apparatus |
| CN104598112B (en) * | 2015-01-23 | 2019-01-18 | 小米科技有限责任公司 | Button interaction method and apparatus |
| CN104601821B (en) * | 2015-01-30 | 2018-09-21 | 江苏中航伟业电子科技发展有限公司 | A method of realizing terminal traffic control |
| CN106547461B (en) * | 2015-09-23 | 2021-11-09 | 小米科技有限责任公司 | Operation processing method, device and equipment |
| CN105607851A (en) * | 2015-12-18 | 2016-05-25 | 上海逗屋网络科技有限公司 | Scene control method and device for touch terminal |
| CN106028101A (en) * | 2016-05-19 | 2016-10-12 | 广州视源电子科技股份有限公司 | Screen display method and system for key function icons |
| CN106371699A (en) * | 2016-08-31 | 2017-02-01 | 天脉聚源(北京)传媒科技有限公司 | Press button color regulating method and device |
-
2017
- 2017-04-14 CN CN201710244791.6A patent/CN107422943B/en active Active
- 2017-04-14 CN CN202011367666.2A patent/CN112328143B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104715309A (en) * | 2013-12-11 | 2015-06-17 | 阿里巴巴集团控股有限公司 | Service control method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107422943A (en) | 2017-12-01 |
| CN112328143A (en) | 2021-02-05 |
| CN107422943B (en) | 2020-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3279763B1 (en) | Method for controlling display and electronic device | |
| CN107957831B (en) | Data processing method, device and processing equipment for displaying interface content | |
| CN108229939B (en) | Method, device and equipment for sending and receiving electronic red packets | |
| CN111589163B (en) | Ranking list processing method, terminal equipment, server and storage medium | |
| CN109260713B (en) | Virtual object remote assistance operation method and device, storage medium and electronic equipment | |
| CN107357544B (en) | Display method, display device, intelligent terminal and computer readable storage medium | |
| CN109726539B (en) | Application starting method, device, terminal and storage medium | |
| CN105072258B (en) | Scene modes of mobile terminal switching method, device and mobile terminal | |
| CN114779987B (en) | Method, device, terminal and storage medium for displaying content | |
| CN113286204A (en) | Information display method and device, computer equipment and computer readable storage medium | |
| EP2947567A1 (en) | User interface text appearance customization | |
| CN108984089B (en) | Touch operation method and device, storage medium and electronic equipment | |
| CN111708471B (en) | Control processing method and related device | |
| CN107632853A (en) | A kind of method for information display and device | |
| CN109992227A (en) | User interface display control method, device, terminal and computer storage medium | |
| CN109144447A (en) | Split screen window adjusting method, device, storage medium and electronic equipment | |
| CN106204695B (en) | Editing method and device of 3D animation | |
| CN112328143B (en) | Button activation method and device | |
| CN112187624B (en) | Message reply method and device and electronic equipment | |
| CN113262472A (en) | Processing method and device of option control, processor and electronic device | |
| CN109101164A (en) | Application display method, device, storage medium and electronic equipment | |
| CN112619147A (en) | Game equipment replacing method and device and terminal device | |
| CN111694626B (en) | Application jump method, device, terminal and storage medium | |
| CN112083994A (en) | Notification message processing method and device | |
| CN111408134A (en) | Display control method and device for secondary confirmation, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40045917 Country of ref document: HK |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |