CN112328143A - Button activation method and device - Google Patents
Button activation method and device Download PDFInfo
- Publication number
- CN112328143A CN112328143A CN202011367666.2A CN202011367666A CN112328143A CN 112328143 A CN112328143 A CN 112328143A CN 202011367666 A CN202011367666 A CN 202011367666A CN 112328143 A CN112328143 A CN 112328143A
- Authority
- CN
- China
- Prior art keywords
- button
- service
- sub
- interactive
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 64
- 230000004913 activation Effects 0.000 title claims abstract description 31
- 230000002452 interceptive effect Effects 0.000 claims abstract description 127
- 230000001960 triggered effect Effects 0.000 claims abstract description 31
- 238000012544 monitoring process Methods 0.000 claims abstract description 9
- 230000000694 effects Effects 0.000 claims description 46
- 230000008569 process Effects 0.000 claims description 40
- 238000013461 design Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 7
- 230000000007 visual effect Effects 0.000 description 6
- 230000004069 differentiation Effects 0.000 description 3
- 238000011161 development Methods 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
- 230000003213 activating effect Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 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
- 230000003993 interaction Effects 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 238000012800 visualization Methods 0.000 description 1
Images
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
Abstract
The application provides a button activation method, comprising 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 various 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 method and the device can expand the service semantics of the button activation state.
Description
Technical Field
The present application relates to the field of computer applications, and in particular, to a method and an apparatus for activating a button.
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 complete a subsequent business process; for example, taking a "payment button" provided in the payment application as an example, when a user needs to complete a payment transaction through the payment application, the "payment button" needs to be triggered by means such as "clicking" to start 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 increasingly complicated service scenarios on the mobile side, the existing button state is single, and thus the actual service requirements cannot be met gradually.
Disclosure of Invention
The application provides a button activation method, which is applied to a client side 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 scenarios;
the determining a target service scenario triggered by the user based on the monitored user operation includes:
determining a target business option selected in the target interface by the user 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 a button sub-state corresponding to the target service scenario includes:
acquiring a button switching special effect pre-configured for a button sub-state corresponding to the target service scene;
and playing the button switching special effect at the position corresponding to the interactive button, and switching the interactive button to a button sub-state corresponding to the target service scene when the playing of the button switching special effect is finished.
Optionally, the method further includes:
determining whether a user triggers the interactive button based on monitored user operation after the interactive button is switched to a button sub-state corresponding to the target service scene;
if the user triggers the interactive button, skipping to a service interface corresponding to the target service scene to complete a subsequent service process;
wherein, different service scenes correspond to different service interfaces respectively.
Alternatively, wherein the different button sub-states correspond to different button styles, respectively.
The present application further proposes a button activation device for a client, the device comprising:
the monitoring module monitors 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;
the determining module is used for determining a target service scene triggered by a 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 scenarios;
the determination module:
determining a target business option selected in the target interface by the user 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:
acquiring a button switching special effect pre-configured for a button sub-state corresponding to the target service scene;
and playing the button switching special effect at the position corresponding to the interactive button, and switching the interactive button to a button sub-state corresponding to the target service scene when the playing of the button switching special effect is finished.
Optionally, the determining module further:
determining whether a user triggers the interactive button based on the monitored user operation after the interactive button is switched to a button sub-state corresponding to the target service scene;
if the user triggers the interactive button, skipping to a service interface corresponding to the target service scene to complete a subsequent service process;
wherein, different service scenes correspond to different service interfaces respectively.
Alternatively, wherein the different button sub-states correspond to different button styles, respectively.
In the present application, the activation state of the button may be further configured to be a plurality of sub-states corresponding to different business scenarios, respectively, based on the actual kind of business scenario contained in the target interface; when a user triggers a certain service scene under the service process corresponding to the button, the button can be immediately switched to a sub-state corresponding to the service scene;
the system can distinguish the service scene triggered by the user by checking different sub-states presented by the button, so that the service semantics transmitted by the activated state of the button can be further expanded, the adaptability of the button to different service scenes can be obviously improved, and the button can meet more diversified service scenes.
Drawings
FIG. 1 is a flow chart illustrating a method for button activation according to one embodiment of the present application;
FIG. 2 is a schematic diagram illustrating a payment scenario triggered via a "payment interface" according to an embodiment of the present application;
FIG. 3 is a schematic diagram illustrating another scenario of payment triggered via a "payment interface" according to an embodiment of the present application;
FIG. 4 is a logical block diagram of a button activation device according to one embodiment of the present application;
fig. 5 is a hardware architecture diagram of a client carrying the button activation device according to an embodiment of the present application.
Detailed Description
In the conventional button state design, the button state of the interactive button is generally designed to be in two types, namely an "activated state" and an "inactivated state".
By activated, it is meant that the interactive button is in an operable state. When the business process corresponding to the interactive button meets the triggering condition, the interactive button can be switched to an activated state; for example, in one illustrated embodiment, the interactive button may be highlighted or the color of the button changed to indicate that the interactive button is currently in an operable state. In this way, the user can be guided to click the interactive button to complete the subsequent business process.
By inactive state, it is meant that the interactive button is in an inoperable state. When the business process corresponding to the interactive button does not meet the triggering condition, the interactive button is kept in an inactive state; for example, in one illustrated embodiment, the interactive button may be uniformly 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 transaction flow; however, the business process corresponding to an interactive button may include a plurality of business scenarios. In the traditional button state design, the difference of the button state of the interactive button in a service scene is not considered; therefore, when a specific service scenario under the service flow corresponding to the interactive button satisfies the trigger condition, the interactive button is usually only switched to the activated state by default. However, a single activated state obviously cannot convey more service semantics, so that the system cannot accurately distinguish a specific service scene.
For example, taking a "payment button" provided by the payment client facing the user as an example, the "payment button" is generally used for triggering a payment business process; however, in practical applications, even a payment business process triggered by the same "payment button" may include a plurality of different payment scenarios; for example, "order payment scenario", "payment scenario for love lunch donations", etc.; when the "payment button" is in an activated state, it is usually only possible to convey that the payment service flow corresponding to the "payment button" already satisfies the service semantic of the trigger condition, but the system cannot accurately distinguish which payment scenario under the payment service flow currently satisfies the trigger condition.
Therefore, the traditional button state design has the defects that the button state is single and more business semantics cannot be transmitted.
In view of the above, the present application is directed to provide a button state design scheme for further subdividing the activation state of a button based on a service scenario.
In implementation, the activation state of the button may be further configured to correspond to a plurality of sub-states of different business scenarios, respectively, based on the actual category of the business scenario contained in the target interface; when a user triggers a certain service scene under the service process corresponding to the button, the button can be immediately switched to a sub-state corresponding to the service scene;
according to the method and the system, the service scene triggered by the user can be distinguished by checking different sub-states presented by the button, so that the service semantics transmitted by the activated state of the button can be further expanded, the adaptability of the button to different service scenes can be obviously improved, and the button can meet more diversified service scenes.
The present application is described below with reference to specific embodiments and specific application scenarios.
Referring to fig. 1, fig. 1 is a diagram illustrating a button activation method applied to a client according to an embodiment of the present application; the method performs the steps of:
and 103, switching the interactive button to a button sub-state corresponding to the target service scene.
The client can be generally referred to client software in any form and capable of providing related services for users; such as a web client, or an APP application.
The target interface is a related service interface provided by the client side facing to the user; wherein, the target interface can comprise a plurality of service scenes;
for example, taking the client as a payment client as an example, in this case, the target interface may be a payment interface including multiple payment scenarios, and the user may trigger different payment scenarios such as "order payment", "love lunch donation", and the like through the payment interface.
The interactive button may be an interactive button provided in the service interface for triggering a related service process. The user may trigger the interactive button by, for example, "clicking" to initiate the business process corresponding to the interactive button.
For example, taking the client as a payment client as an example, 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 means of "clicking" for example, to start a subsequent payment process, so as to complete a related payment service.
The service scene specifically refers to a specific service type included in the service flow corresponding to the interactive button; in practical application, the service process corresponding to the interactive button can include a plurality of service scenes; the user can trigger different service scenes in the target page by executing different user operations in the target page.
For example, taking the above-mentioned interactive button as a "payment button" and the above-mentioned business process as a "payment process" initiated by triggering the above-mentioned "payment button" as an example, even a payment business process triggered by the same "payment button" may include different payment scenarios such as "order payment", "love lunch donation", and the like. In this scenario, the user may perform different user operations in the "payment interface" to trigger different payment scenarios, such as the "order payment scenario" and the "payment scenario for love lunch donation", respectively.
In the application, in order to realize the activated state of the interactive button, the conveyed business semantics are further expanded, and a button state design idea of further dividing the activated state of the button into multiple sub-states is provided.
The technical scheme of the present application is described in detail below through three stages, namely, the division of sub-states, the triggering of a service scenario, and the switching of an active state.
1) Partitioning of sub-states
In the application, when a developer designs a button state for an interactive button, the developer can further subdivide the activation state of the interactive button based on the actual type of a service scene contained in a service flow corresponding to the interactive button on the basis of the traditional button state design, and divide the activation state of the interactive button into a plurality of button sub-states.
Wherein, for each divided button sub-state, it can correspond to a service scene under the service flow corresponding to the interactive button; i.e. an independent button substate can be defined for each service scenario.
The number of the button sub-states which are finally divided into the activated states of the interactive buttons depends on the types of the service scenes under the service flow corresponding to the interactive buttons, and is not particularly limited in the application; in practical applications, those skilled in the art can configure the types of the service scenarios and the number of the finally divided button sub-states in a customized manner based on actual service requirements.
For example, still taking the service flow as the "payment flow" triggered to be started by the "payment button" as an example, the developer may divide the "payment flow" into different "payment scenarios" based on actual service requirements; for example, an "order payment scenario", "contribution payment scenario", "daily payment scenario", etc.; then, a button sub-state is respectively defined for various payment scenes contained in the payment process.
It is emphasized that the "activated state" of the interactive button described in this application, in contrast to conventional button state design considerations, will no longer be a single button state. But rather a set of "active states" consisting of several button states together; for each button sub-state, there is a separate "activated state". That is, when the interactive button is switched to any one of the sub-states, it indicates that the interactive button is currently in an operable state.
The interactive buttons are arranged on the main body, and the interactive buttons are arranged on the main body, wherein different button sub-states respectively correspond to different service scenes under the service process corresponding to the interactive buttons, so that different service semantics can be accurately conveyed through the different button sub-states to visually distinguish the different service scenes.
In this application, carry out the visual design of differentiation to different button sub-states, specifically can include the differentiation design on the button switches the special effect to and the differentiation design two parts on the button pattern:
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 that 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 the display mode of the special effect switched by the button are not particularly limited in the application, and in practical application, a person skilled in the art can perform custom configuration based on actual requirements;
for example, in practical applications, the button switching special effect may be a dynamic change such as a color of an interactive button, a switching animation played at a position of the interactive button or in a specific area around the interactive button, and so on.
In the illustrated embodiment, different button styles may also be provided for different button substates. The button style refers to basic properties such as color, size, shape, and text on the button presented by the interactive button. That is, in this application, when switching the above-mentioned interactive button to different button sub-states, the characters etc. on the colour, size, shape, the button of this interactive button can all have the difference, and then under different button sub-states, above-mentioned interactive button can demonstrate differentiated bandwagon effect.
The specific type of the button style configured for each button substate is not particularly limited in this application, and in practical applications, those skilled in the art may perform custom configuration based on actual requirements.
Through the mode, different button switching special effects or button styles are respectively configured for different button sub-states, so that the interactive buttons can show differentiated visual effects when being switched between different button sub-states, and different button sub-states can be visually distinguished.
In the implementation, in the initial state, a state identifier may be configured for each button substate, and a scene identifier may be configured for each service scene included in the service flow corresponding to the interactive button.
After the distribution 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 a developer, and a corresponding configuration file is generated.
And the developer can develop execution codes related to the button switching special effect and the button style respectively for each button sub-state in the background based on a specific development language (such as java language for an android system and object C language for an IOS system), and then encapsulate the developed execution codes into a visualization component for the client to call.
Finally, the encapsulated visual components and the state identifiers of the corresponding button sub-states can be mapped and stored, so that the client can quickly retrieve the related visual components to execute and call based on the state identifiers of the button sub-states.
At this time, based on the actual type of the service scene included in the service flow corresponding to the interactive button, the initialization configuration process of further subdividing the activated state of the interactive button is completed.
2) Triggering of a service scenario
In the application, the client may monitor a user operation of the user for the target interface, and determine whether the monitored user operation is a preset operation, so as to identify a target service scenario triggered by the user.
When a user triggers a service scene, the user operation executed in the target interface may include any type of user operation capable of triggering a related service scene;
for example, taking a terminal device equipped with the client as a touch screen terminal device as an example, the user operation may include any form of touch operation of a user on the target interface; such as a tap operation, a long press operation, a slide operation, a special gesture operation, etc.
When the method is implemented, 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 is matched with any one preset operation, the client can immediately trigger a service scene corresponding to the preset operation and continue to execute a subsequent process of switching the button state.
In an embodiment shown, in order to implement quick triggering of various service scenarios in a service flow corresponding to the interactive button, a plurality of service options corresponding to the service scenarios may be provided in the target interface. In this case, the preset operation for triggering each service scenario may be a selected operation for the service option corresponding to each service scenario.
When the method is implemented, 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 selection operation aiming at each service option provided in the target interface; if the monitored user operation is the selection operation aiming at any service option in the target interface, the service option can be selected immediately at the moment, the service scene corresponding to the service option is triggered, then the subsequent process is executed, and the interactive button is switched to the button sub-state corresponding to the service scene.
Therefore, in this case, the user can quickly trigger the service scene corresponding to the service option by selecting the corresponding service option in the target interface; 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.
It should be noted that, in addition to the service options corresponding to the service scenes described above, the service options corresponding to the service scenes may be set on the same target interface as the interactive buttons, and in practical applications, the service options corresponding to the service scenes may also be set on other interfaces besides the target interface; that is, in the present application, the service options corresponding to each service scenario may be set in the target interface simultaneously with the interactive buttons, or may be set in different interfaces respectively.
For example, in one implementation, the service options corresponding to each service scenario may be set to an independent "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 the button sub-state in the target interface.
3) Active state switching
In this application, after the client determines a target service scenario triggered by a user by monitoring user operation of the user for the target interface, a subsequent process of switching the interactive button to an activated state may be completed based on a button substate preconfigured for the target service scenario.
When the method is implemented, the client can use the scene identifier of the target service scene as a query index, call a related configuration file, and query the state identifier of the button sub-state configured for the target service scene; after querying the state identifier of the button sub-state configured for the target service scene, the client may further use the state identifier as a query index, query a related visual component developed and completed by a developer, obtain a button switching special effect and a button style preconfigured for the button sub-state, and then play the button switching special effect at a 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 pre-configured for the button sub-state. When the button style switching is completed, the interactive button is successfully switched to the button 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, and the user can further trigger the operation button to start a subsequent service process corresponding to the target service scene.
When the method is implemented, the client may define a preset operation for triggering the interactive button for the interactive button; for example, the preset operation may be specifically a "click operation" for the interactive button. And the client can continue to monitor the user operation of the user for the target page in the background, and can immediately trigger the service process corresponding to the target service scene after monitoring the 'click operation' of the user for the interactive button.
It should be noted that, because different service scenarios may have a certain difference in the service execution flow, the developer may configure different service interfaces for different service scenarios. That is, for each service option pre-configured in the target interface, different service interfaces will be respectively corresponding.
The above-described "different service interfaces" may refer to service interfaces with different service scenes and completely different corresponding page addresses (e.g., URL addresses), or may refer to service interfaces with the same page address corresponding to different service scenes, but the page contents displayed in the interfaces in different service scenes are different.
In this case, after the client monitors the "click operation" of the user for the interactive button, the client may immediately trigger the service flow corresponding to the target service scenario, and jump to the service interface of the target service scenario, thereby completing the subsequent service flow.
By the mode, on one hand, a 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 played respectively, so that stable transition between 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 a subsequent service process corresponding to a service scene triggered by the user.
Therefore, the button state for further subdividing the activation state of the interactive button relates to the idea based on the type of the service scene, and the service semantics transmitted by the activation state of the interactive button can be further expanded, so that the interactive button can adapt to diversified service scenes.
The technical solutions in the above embodiments are described in detail below with reference to 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 "pay immediate" button may further include: the payment scene of the love lunch donation and the order payment scene. The activated state of the "immediate payment" button is divided into "button substate 1" and "button substate 2".
Wherein, the payment scene of the love lunch donation corresponds to the button sub-state 2; the "order Payment scenario" corresponds to the "button substate 2". The button switch special effect configured for the "button substate 1" is "button switch special effect 1"; the button switch effect configured for the "button substate 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 this example.
As shown in fig. 2, in the "payment interface", a user option corresponding to the "payment scenario for love lunch donations" may be provided by default. The "pay-as-you-go" button, in its initial state, may be in an inoperable, inactive state.
With continued reference to FIG. 2, the user may enter the payment amount by clicking on the "transfer amount" input box to complete the "order payment". And when the client monitors the click operation of the user on the input box where the transfer amount is located, and acquires the payment amount input by the user, the order payment scene can be immediately triggered in the payment interface, and the button switching special effect 1 is played at the position corresponding to the immediate payment button. When the 'button switching special effect 1' playing is finished, the 'immediate payment' button is switched to a 'button sub-state 1', and meanwhile, the 'immediate payment' button is switched from an inoperable state to an operable state.
In this case, the user may initiate a subsequent order payment process by continuing to trigger the "immediate payment" process described above, thereby completing the order payment.
Referring to fig. 3, fig. 4 is a schematic diagram illustrating another scenario of triggering payment through a "payment interface" in this example.
As shown in fig. 3, after the "order payment scenario" is triggered, the user may also trigger the "payment scenario for love lunch donation" in the "payment interface" by selecting the user option corresponding to the "payment scenario for love lunch donation" to complete the switching of the "immediate payment" button from the "button sub-state 1" to the "button sub-state 2".
Referring to fig. 3, when the client monitors the "selection operation" of the user option for the "payment scene for love lunch donation" by the user, the "payment scene for love lunch donation" may be triggered immediately, and the "button switching special effect 2" is played at a position corresponding to the "immediate payment" button.
For example, the "button switch effect 2" shown in fig. 3 is a "pay-for-immediately" button that dynamically changes color in a left-to-right direction and outputs a presentation effect of a heart icon around the button.
When the "button switch special effect 2" playback ends, the "immediate payment" button described above is switched to the "button substate 2". At this point, the "pay immediate" button is still operable.
Therefore, by the mode, the user can quickly trigger different payment scenes through the payment interface and switch the immediate payment button to different button sub-states; moreover, the 'pay immediately' button can convey different business semantics through differentiated 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 a plurality of sub-states respectively corresponding to 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 process corresponding to the button, the button can be immediately switched to a sub-state corresponding to the service scene;
the system can distinguish the service scene triggered by the user by checking different sub-states presented by the button, so that the service semantics transmitted by the activated state of the button can be further expanded, the adaptability of the button to different service scenes can be obviously improved, and the button can meet more diversified service scenes.
Corresponding to the method embodiment, the application also provides an embodiment of the device.
Referring to fig. 4, the present application provides a button activation apparatus 40 applied to a client; referring to fig. 5, the hardware architecture of the client carrying the button activation device 40 generally includes a CPU, a memory, a non-volatile memory, a network interface, an internal bus, and the like; in the case of a software implementation, the button activation device 40 can be generally understood as a computer program loaded in a memory, and a logic device formed by a combination of software and hardware after being executed by a CPU, wherein the button activation device 40 includes:
the monitoring module 401 monitors 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 a user based on the monitored user operation;
the switching module 403 is configured to switch the interactive button to a button sub-state corresponding to the target service scenario.
In this example, the target interface is preconfigured with service options corresponding to the service scenes;
the determination module 402:
determining a target business option selected in the target interface by the user 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 the example, different button sub-states are respectively preconfigured with different button switching special effects;
the switching module 403:
acquiring a button switching special effect pre-configured for a button sub-state corresponding to the target service scene;
and playing the button switching special effect at the position corresponding to the interactive button, and switching the interactive button to a button sub-state corresponding to the target service scene when the playing of the button switching special effect is finished.
In this example, the determining module 402 further:
determining whether a user triggers the interactive button based on the monitored user operation after the interactive button is switched to a button sub-state corresponding to the target service scene;
if the user triggers the interactive button, skipping to a service interface corresponding to the target service scene to complete a subsequent service process;
wherein, different service scenes correspond to different service interfaces respectively.
In this example, different button sub-states correspond to different button styles, respectively.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention 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 invention 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 will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (12)
1. A button activation method applied to a client side 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 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 corresponding to the target service scene.
2. The method of claim 1, the target interface preconfigured with service options corresponding to the service scenario;
the determining a target service scenario triggered by the user based on the monitored user operation includes:
determining a target business option selected in the target interface by the user 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, different button sub-states each preconfigured with different button switch special effects;
the switching the interactive button to a button sub-state corresponding to the target service scenario includes:
acquiring a button switching special effect pre-configured for a button sub-state corresponding to the target service scene;
and playing the button switching special effect at the position corresponding to the interactive button, and switching the interactive button to a button sub-state corresponding to the target service scene when the playing of the button switching special effect is finished.
4. The method of claim 3, wherein the button switch special effect is used to expose business semantics of the button sub-state indication.
5. The method of claim 3, further comprising:
determining whether a user triggers the interactive button based on monitored user operation after the interactive button is switched to a button sub-state corresponding to the target service scene;
if the user triggers the interactive button, skipping to a service interface corresponding to the target service scene to complete a subsequent service process;
wherein, different service scenes correspond to different service interfaces respectively.
6. The method of claim 1, wherein the 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 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;
the determining module is used for determining a target service scene triggered by a 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.
8. The apparatus of claim 7, the target interface preconfigured with service options corresponding to the service scenario;
the determination module:
determining a target business option selected in the target interface by the user 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 each preconfigured with different button switch special effects;
the switching module:
acquiring a button switching special effect pre-configured for a button sub-state corresponding to the target service scene;
and playing the button switching special effect at the position corresponding to the interactive button, and switching the interactive button to a button sub-state corresponding to the target service scene when the playing of the button switching special effect is finished.
10. The apparatus of claim 9, the button switch special effect to expose business semantics of the button sub-state indication.
11. The apparatus of claim 8, the determination module further to:
determining whether a user triggers the interactive button based on the monitored user operation after the interactive button is switched to a button sub-state corresponding to the target service scene;
if the user triggers the interactive button, skipping to a service interface corresponding to the target service scene to complete a subsequent service process;
wherein, different service scenes correspond to different service interfaces respectively.
12. The device of claim 7, wherein the different button sub-states correspond to different button patterns, respectively.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011367666.2A CN112328143A (en) | 2017-04-14 | 2017-04-14 | Button activation method and device |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011367666.2A CN112328143A (en) | 2017-04-14 | 2017-04-14 | Button activation method and device |
| CN201710244791.6A CN107422943B (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 (1)
| Publication Number | Publication Date |
|---|---|
| CN112328143A true CN112328143A (en) | 2021-02-05 |
Family
ID=60424167
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011367666.2A Pending CN112328143A (en) | 2017-04-14 | 2017-04-14 | Button activation method and device |
| CN201710244791.6A Active CN107422943B (en) | 2017-04-14 | 2017-04-14 | Button activation method and device |
Family Applications After (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) | CN112328143A (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 (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| CN102789351A (en) * | 2011-05-20 | 2012-11-21 | 腾讯科技（深圳）有限公司 | Method and device for switching browsed interfaces |
| US20150145435A1 (en) * | 2013-11-28 | 2015-05-28 | Panasonic Intellectual Property Corporation Of America | Control method of mobile device |
| CN104715309A (en) * | 2013-12-11 | 2015-06-17 | 阿里巴巴集团控股有限公司 | Service control method and device |
| CN105094576A (en) * | 2014-04-21 | 2015-11-25 | 北京奇虎科技有限公司 | Switching method and device for application scenarios |
| CN105607851A (en) * | 2015-12-18 | 2016-05-25 | 上海逗屋网络科技有限公司 | Scene control method and device for touch terminal |
| US20160342302A1 (en) * | 2015-01-23 | 2016-11-24 | Xiaomi Inc. | Method and device for interacting with button |
| CN106371699A (en) * | 2016-08-31 | 2017-02-01 | 天脉聚源(北京)传媒科技有限公司 | Press button color regulating method and device |
Family Cites Families (8)
| 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 |
| US20090083669A1 (en) * | 2007-09-26 | 2009-03-26 | Autodesk, Inc. | Navigation system for a 3d virtual scene |
| 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 |
| CN103761041A (en) * | 2014-01-13 | 2014-04-30 | 联想(北京)有限公司 | Information processing method and electronic device |
| 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 |
| CN106028101A (en) * | 2016-05-19 | 2016-10-12 | 广州视源电子科技股份有限公司 | Screen display method and system for key function icon |
-
2017
- 2017-04-14 CN CN202011367666.2A patent/CN112328143A/en active Pending
- 2017-04-14 CN CN201710244791.6A patent/CN107422943B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| CN102789351A (en) * | 2011-05-20 | 2012-11-21 | 腾讯科技（深圳）有限公司 | Method and device for switching browsed interfaces |
| US20150145435A1 (en) * | 2013-11-28 | 2015-05-28 | Panasonic Intellectual Property Corporation Of America | Control method of mobile device |
| CN104715309A (en) * | 2013-12-11 | 2015-06-17 | 阿里巴巴集团控股有限公司 | Service control method and device |
| CN105094576A (en) * | 2014-04-21 | 2015-11-25 | 北京奇虎科技有限公司 | Switching method and device for application scenarios |
| US20160342302A1 (en) * | 2015-01-23 | 2016-11-24 | Xiaomi Inc. | Method and device for interacting with button |
| CN105607851A (en) * | 2015-12-18 | 2016-05-25 | 上海逗屋网络科技有限公司 | Scene control method and device for touch terminal |
| CN106371699A (en) * | 2016-08-31 | 2017-02-01 | 天脉聚源(北京)传媒科技有限公司 | Press button color regulating method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107422943B (en) | 2020-10-20 |
| CN107422943A (en) | 2017-12-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108027706B (en) | Application interface display method and terminal equipment | |
| US10572647B2 (en) | Touchscreen unlocking method and apparatus | |
| JP6211721B2 (en) | Button interaction method, apparatus, program, and recording medium | |
| EP3316112A1 (en) | Split screen display method and apparatus, computer program and recording medium | |
| JP7138804B2 (en) | INTERFACE DISPLAY METHOD AND DEVICE, TERMINAL AND COMPUTER PROGRAM | |
| CN108229939B (en) | Method, device and equipment for sending and receiving electronic red packets | |
| CN109260713B (en) | Virtual object remote assistance operation method and device, storage medium and electronic equipment | |
| CN105072258B (en) | Scene modes of mobile terminal switching method, device and mobile terminal | |
| TW201909602A (en) | Image transmission method and device based on instant communication | |
| CN104571874B (en) | The method and apparatus of switching at runtime keyboard background | |
| WO2019047728A1 (en) | Method for opening shortcut function, device, mobile terminal, and storage medium | |
| KR20130096576A (en) | Apparatus and method for creating a shortcut menu and mobile device including the apparatus | |
| CN105430183B (en) | A kind of method and mobile terminal of mobile terminal switching account | |
| CN111708471B (en) | Control processing method and related device | |
| EP2947567A1 (en) | User interface text appearance customization | |
| EP3236355B1 (en) | Method and apparatus for managing task of instant messaging application | |
| CN111767108A (en) | Application program label generation method, application interface display method and device | |
| CN111494935A (en) | Method and device for controlling virtual object in game | |
| CN106095285B (en) | Operation execution method and device | |
| CN111124668A (en) | Memory release method and device, storage medium and terminal | |
| CN111538574B (en) | Task stack management method, device, terminal and storage medium | |
| CN107422943B (en) | Button activation method and device | |
| CN110837317A (en) | Method, device and equipment for preventing user from mistakenly touching on display interface | |
| CN105589627B (en) | Shortcut menu display method, shortcut menu display device and terminal | |
| CN112619147A (en) | Game equipment replacing method and device and terminal device |
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 |