Patent Description:
<CIT> relates to systems, software, and computer implemented methods for providing user interface (UI)-based modifications to adjust and interact with data exchange splits. An example client device can identify a data exchange (DE) associated with at least three entities, the DE associated with a total value. A visualization representing the DE can be presented via a UI and can include a chart comprising the total value of the DE exchange divided into value areas that are each associated with a particular entity. In response to a detection of input associated with a selection of an edge between a first and second value area, the combined value area associated with the first and second value areas can be locked. In response to detected movement input associated with the edge, the relative values of the first and second inside the combined value area can be adjusted in the visualization.

In some implementations, a method for presenting an arc-shaped user interface element includes presenting, on a user interface of a user device, an arc-shaped user interface element that includes a first end, a second end, and an arc spanning from the first end to the second end, wherein the arc represents a total amount, and wherein the user interface is associated with a first user account; detecting, by the user device, a user interaction that indicates a first point on the arc-shaped user interface element; presenting, on the user interface and based on the user interaction, a first arc portion of the arc, spanning from the first end to the first point, in a different visual manner than one or more other arc portions of the arc, wherein the first arc portion represents a first amount, of the total amount, to be associated with the first user account, wherein the one or more other arc portions includes a second arc portion of the arc, spanning from the second end to a second point associated with a second user account, that represents a second amount, of the total amount, associated with the second user account; and transmitting, by the user device and to an account management device, information that identifies the first amount, of the total amount, to be associated with the first user account. The second arc portion is not editable via user interaction with the user interface associated with the first user account.

In some implementations, a non-transitory computer-readable medium storing a set of instructions includes one or more instructions that, when executed by one or more processors of a user device, cause the user device to present, on a user interface associated with a first user account, an arc-shaped element that includes a first end, a second end, and an arc spanning from the first end to the second end, wherein the arc represents a joint pledged contribution amount; detect a user interaction that indicates a first area on the arc-shaped element; present, on the user interface and based on the user interaction, a first arc portion, of the arc, spanning from the first end to the first area, wherein the first arc portion represents a first pledged contribution amount, of the joint pledged contribution amount, to be associated with the first user account, wherein the arc includes a second arc portion, spanning from the second end to a second area associated with a second user account, that represents a second pledged contribution amount, of the joint pledged contribution amount, associated with the second user account; and transmit, to an account management device, information that identifies the first pledged contribution amount to be associated with the first user account. The second arc portion is not editable via user interaction with the user interface associated with the first user account.

In some implementations, a user device includes a memory and one or more processors, communicatively coupled to the memory, configured to present, on a user interface associated with a first user account, an arc-shaped element that includes a first end, a second end, and an arc spanning from the first end to the second end, wherein the arc represents a joint amount associated with the first user account and a second user account; detect a user interaction, with the user device, that indicates a first part of the arc-shaped element; present, on the user interface and based on the user interaction, a first arc portion, of the arc, spanning from the first end to the first part, wherein the first arc portion represents a first pledged amount, of the joint amount, to be associated with the first user account, wherein the arc includes a second arc portion, spanning from the second end to a second part, of the arc-shaped element, associated with the second user account, wherein the second arc portion represents a second pledged amount, of the joint amount, associated with the second user account; and transmit, to another device, information that identifies the first pledged amount to be associated with the first user account. The second arc portion is not editable via user interaction with the user interface associated with the first user account. Thus, according to an aspect, the objective relates to providing an improved user interface with the ability to edit individual contribution. This objective is achieved by the subject-matter of the independent claims. Particular embodiments are defined in the dependent claims.

<FIG> is a flowchart of an example process relating to presentation and The following detailed description of example implementations refers to the accompanying drawings.

Some activities involve two parties that make a collaborative effort to reach a shared goal. For example, parties, such as a parent and a child, a couple, or business partners, may make contributions to a shared monetary savings goal. However, in some cases, the parties may become confused or have disagreements regarding the respective contributions of the parties, and the parties may have difficulty tracking the progress toward the shared goal. Accordingly, a user interface (UI) that allows each party to pledge individual contributions to the shared goal and track the progress of each party toward the shared goal on respective user devices may be beneficial. However, existing techniques for visualizing monetary savings and/or investment goals on a UI are not well suited for multiple users that make contributions to a shared goal. It is desirable for a UI to provide user-friendly way for to visualize and edit the individually pledged contributions of each party, as well as the shared goal.

Some implementations described herein enable a user device to present, on a UI, an arc-shaped UI element that visually indicates individually pledged contributions of two users, as well as the progress of the users toward a shared goal. For example, in some implementations, the arc-shaped UI element includes a first end, a second end, and an arc spanning from the first end to the second end. The arc represents a total amount of the shared goal. A first arc portion spanning from the first end to a first point on the arc-shaped UI element represents a first amount to be associated with a first user account, and a second arc portion spanning from the second end to a second point on the arc-shaped UI element represents a second amount to be associated with a second user account. The user device presents, on the UI, the first arc portion and the second arc portion in different visual manners from each other and from one or more other arc portions of the arc. This provides a clear, cohesive, and user-friendly visualization of the individually pledged contributions of the two users, as well as the progress toward the total amount of the shared goal.

In some implementations described herein, the user device detects user interaction by the first user that indicates and/or edits the first point on the arc-shaped UI element or user interaction by the second user that indicates and/or edits the second point on the arc-shaped UI element. The user device presents, on the UI, the first arc portion and/or the second arc portion based on the user interaction. This provides the UI with user-friendly controls that allow the users to set and edit the individually pledged contributions while tracking progress toward the total amount of the shared goal. As a result, the user device provides a UI that provides user-friendly visualization and editing of the individually pledged contributions of the users and the progress of the users toward the shared goal. Furthermore, users of different user devices, which may be remote from one another, can receive updates regarding updated pledges and/or contributions of another user.

<FIG> are diagrams of an example <NUM> associated with presentation and control of user interaction with an arc-shaped UI element. As shown in <FIG>, example <NUM> includes user devices, an account management device, and an input device. These devices are described in more detail in connection with <FIG> and <FIG>.

As shown in <FIG>, and by reference number <NUM>, the input device may transmit, to the account management device, account information for establishing a joint account for user A and user B. User A and/or user B may input the account information to the input device via an input component of the input device. The account information may be associated with a joint account for user A and user B to make contributions toward a shared goal. In some implementations, the joint account may be a joint account for user A and user B to make monetary contributions toward a monetary savings goal. As shown in example <NUM>, in some cases, user A may be a parent and user B may be a child. User A and user B may establish a joint account to manage one or more monetary saving goals for user B, to which user A may contribute.

The account information may include a respective user credential for each user. For example, the user credential for a user may include a username and a password associated with that user. In some cases, the user credential for a user may also include dual authentication information, such as a telephone number or email address to be used for dual authentication of the user. In some implementations, the account information may also include contact information, such as an email address, a telephone number, and/or an address, among other examples, for each user. In some implementations, the account information associated with a respective financial account, such as a checking account, a savings account, or a credit card account, for each user. The account management device may receive the account information from the input device, store the account information, and create the joint account for user A and user B.

As further shown in <FIG>, and by reference number <NUM>, user B may login to an application relating to the joint account on user device B. For example, user B may input the user credential associated with user B to user device B. User device B may transmit the user credential associated with user B to the account management device for authentication. The account management device may verify the user credential based on the user credential associated with user B in the stored account information.

As further shown in <FIG>, and by reference number <NUM>, user device B may present a UI via a display of device B (e.g., in a web browser or other application). The UI may be associated with a user account of user B. In some implementations, the account management device, based on verifying the user credential associated with user B, may transmit UI configuration information to user device B, and the UI configuration information may cause user device B to present the UI. As shown by reference number <NUM>, the UI may include a "Set New Goal" mode or UI, in which user B may input a total savings goal and a pledged contribution amount, for user B, via the UI. For example, the UI may enter the "Set New Goal" mode based on user device B detecting a user selection of a selectable UI element of the UI. The UI may present a fillable field for user B to input a total amount for the savings goal. The total amount for the savings goal may be the joint pledged contribution amount for user A and user B. As shown by reference number <NUM>, the UI may include a field that presents the total amount for the savings goal. For example, in <FIG>, the total amount is set to $<NUM>.

As further shown, user device B may present, on the UI, an arc-shaped UI element <NUM> that includes a first end <NUM>, a second end <NUM>, and an arc <NUM> spanning from the first end <NUM> to the second end <NUM>. The arc <NUM> may represent the total amount for the joint contribution of user A and user B. The arc shaped UI element <NUM> may also be referred to herein an "arc-shaped element. " In some implementations, the arc-shaped element may be substantially horseshoe shaped, as shown in <FIG>. For example, the arc-shaped element may be shaped like a horseshoe, a curve, a rounded curve, a portion of a circle, a portion of an ellipse, a portion of an oval, an arc (e.g., an arc of a circle, an arc of an ellipse, or an arc of an oval), an arch, or the like.

As further shown in <FIG>, and by reference number <NUM>, user device B may detect a user interaction that indicates a point <NUM> on the arc-shaped element. As used herein, the indicated point <NUM> may be a point on the arc-shaped element, an area on the arc-shaped element, or a part of the arc-shaped element. In some implementations, user device B may detect user interaction with a slidable UI element <NUM>, presented in or on the arc-shaped element in the UI, to slide the slidable UI element <NUM> to the indicated point <NUM> on the arc-shaped element. An arc portion <NUM> spanning from the second end <NUM> to the indicated point <NUM> may represent a pledged contribution amount for user B. User device B may determine the amount of the pledged contribution for user B based on the length of the arc portion <NUM> spanning from the second end <NUM> to the indicated point <NUM> and the total length of the arc <NUM> spanning from the first end <NUM> to the second end <NUM>. For example, user device B may determine the amount of the pledged contribution for user B such that the ratio of the pledged contribution for user B to the total amount of the joint contribution is equal to the ratio of the length of the arc portion <NUM> to the total length of the arc <NUM>.

User device B may present the pledged contribution for user B in one or more fields on the UI. As shown by reference number <NUM>, the UI may present the pledged amount for user B in a field that shows the pledged amount for the user that is logged in and for which the UI is being displayed (e.g., user B in <FIG>). Additionally, or alternatively, as shown by reference number <NUM>, the UI may include a field that shows the pledged contribution for user B and is not dependent on the user that is logged in and for which the UI is being displayed. In the example of <FIG>, the pledged amount for user B is $<NUM> of the total goal of $<NUM>. In some implementations, user device B may update the field(s) showing the pledged amount for user B as the user interaction indicating the point <NUM> on the arc-shaped element is detected to allow user B to select a desired pledged contribution. For example, user B may slide the slidable UI element <NUM> away from the second end <NUM> (e.g., clockwise in <FIG>) along the arc <NUM> to increase the amount of the pledged contribution, or user B may slide the slidable UI element <NUM> towards the second end <NUM> (e.g., counter-clockwise in <FIG>) along the arc <NUM> to decrease the amount of the pledged contribution. In this case, user device B may update the field(s) showing the pledged contribution for user B to show the amount change as user B slides the slidable element <NUM> along the arc <NUM>.

Based on the user interaction indicating the point <NUM> on the arc-shaped element, user device B may present the arc portion <NUM> representing the pledged contribution for user B on the UI in a different visual manner than one or more other arc portions (e.g., a differential arc portion <NUM>, described below) of the arc-shaped element. For example, user device B may present the arc portion representing the pledged contribution for user B on the UI using a particular visual attribute, such as a color, a fill pattern, or a shading, that is different from visual attributes used for other arc portions. Other arc portions on the arc-shaped element may include, for example, an arc portion representing a pledged contribution of user A and/or a differential arc portion <NUM> representing a difference between the total amount of the goal and the combined pledged contributions of user A and user B. In the example of <FIG>, the arc-shaped element does not yet include an arc portion representing a pledged contribution for user A. Accordingly, the differential arc portion <NUM> in <FIG> includes a remaining portion of the arc other than the arc portion representing the pledged contribution for user B. In some implementations, an arc portion representing the pledged contribution for user A may not be editable via user interaction when the UI is associated with the user account of user B (e.g., when user B is logged in).

In some implementations, the slidable UI element <NUM> may only appear on the UI when a user interaction with the UI and/or the arc-shaped element is detected, and may disappear from the UI when the user interaction with the UI and/or the arc-shaped element ends. An example of the UI after the slidable UI element disappears (or is hidden or removed from the UI) is shown in <FIG>. Additionally, or alternatively, the slidable UI element <NUM> may be displayed on the UI until the user finalized and/or submits their contribution.

As further shown in <FIG>, and by reference number <NUM>, user device B may transmit, to the account management device, information that identifies the total amount for the goal and the pledged contribution amount for user B. For example, user device B may transmit the information to the account management device based on detecting a user interaction with a UI element on the UI. As shown by reference number <NUM>, the account management device may store the information that identifies the total amount for the goal and the pledged contribution amount for user B in a data structure. For example, the account management device may store, in the data structure, an account number (or other account identifier) associated with the joint account for user A and user B (e.g., "<NUM>" in <FIG>), a savings goal identifier (ID) associated with the particular savings goal for user A and user B (e.g., "Goal <NUM>" in <FIG>), information identifying the total amount for the goal (e.g., $<NUM> in <FIG>), information identifying the pledged contribution for user A (e.g., $<NUM> in <FIG>), and information identifying the pledged contribution for user B (e.g., $<NUM> in <FIG>).

As shown in <FIG>, and by reference number <NUM>, user A may login to the application relating to the joint account on user device A. For example, user A may input the user credential associated with user A to user device A. User device A may transmit the user credential associated with user A to the account management device for authentication. The account management device may verify the user credential based on the user credential associated with user A in the stored account information. In some implementations, user device A may be a different user device from user device B. In some implementations, user device A may be the same user device as user device B.

As further shown in <FIG>, and by reference number <NUM>, user device A may transmit, to the account management device, a request for information identifying the total amount of the joint contribution goal, information identifying the pledged contribution amount for user B, and/or UI configuration information. As shown by reference number <NUM>, the account management device may transmit, to user device A, a response including the information identifying the total amount of the joint contribution goal, the information identifying the pledged contribution amount for user B, and/or the UI configuration information.

As further shown in <FIG>, and by reference number <NUM>, user device A may present a UI via a display of device A (e.g., in a web browser or other application). The UI may be associated with a user account of user A. In some implementations, the UI configuration information received from the account management device may cause user device A to present the UI. The UI may include the arc-shaped element <NUM> described above in connection with the UI presented on user device B. As shown by reference number <NUM>, the UI may include a "View/Edit Existing Goal" mode or UI, in which the UI presents the arc-shaped element <NUM> that visually indicates the total amount of the goal and the pledged contribution amount for user B. In the "View/Edit Existing Goal" mode, user A may input a pledged contribution amount via the UI. Additionally, or alternatively, user A may edit the total amount of the goal. In some implementations, the UI may enter the "View/Edit Existing Goal" mode based on user device A detecting a user selection of a selectable UI element in the UI. User device A may present, on the UI, the total amount for the goal and the pledged contribution amount for user B based on the information identifying the total amount for the goal and the pledged contribution amount for user B received from the account management device.

As further shown in <FIG>, and by reference number <NUM>, user device A may detect a user interaction that indicates a point <NUM> on the arc-shaped element <NUM>. As used herein, the indicated point <NUM> may be a point on the arc-shaped element, an area on the arc-shaped element, or a part of the arc-shaped element. In some implementations, user device A may detect user interaction with a slidable UI element, presented in or on the arc-shaped element in the UI, as described above in connection with user device B. The point <NUM> indicated by the user interaction detected by user device A may be referred to herein as the "first point. " The point <NUM> that is indicated by the user interaction detected by user device B, as described above in connection with <FIG>, may be referred to herein as the "second point. " As further shown, an arc portion <NUM> spanning from the first end <NUM> to the first point <NUM> may represent the pledged contribution amount for user A. The arc portion <NUM> that represents the pledged contribution amount for user A may be referred to herein as the "first arc portion. " The arc portion <NUM> that represents the pledged contribution amount for user B, as described above in connection with <FIG>, may be referred to herein as the "second arc portion. " User device A may determine the amount of the pledged contribution for user A based on the length of the first arc portion <NUM> and the total length of the arc <NUM> spanning from the first end <NUM> to the second end <NUM>. For example, user device A may determine the amount of the pledged contribution for user A such that the ratio of the pledged contribution for user A to the total amount of the joint contribution is equal to the ratio of the length of the first arc portion <NUM> to the total length of the arc <NUM>.

User device A may present the pledged contribution amount for user A in one or more fields on the UI. As shown by reference number <NUM>, the UI may present the pledged amount for user A in a field that shows the pledged amount for the user that is logged in and for which the UI is being displayed (e.g., user A in <FIG>). Additionally, or alternatively, as shown by reference number <NUM>, the UI may include a field that shows the pledged contribution for user A and is not dependent on the user that is logged in and for which the UI is being displayed. In the example of <FIG>, the pledged amount for user A is $<NUM> of the total goal of $<NUM>. In some implementations, user device A may update the field(s) showing the pledged amount for user A as the user interaction indicating the first point <NUM> on the arc-shaped element <NUM> is detected to allow user A to select a desired pledged contribution amount. For example, user A may slide the slidable UI element away from the first end <NUM> (e.g., counter-clockwise in <FIG>) along the arc <NUM> to increase the amount of the pledged contribution, or user A may slide the slidable UI element towards the first end <NUM> (e.g., clockwise in <FIG>) along the arc <NUM> to decrease the amount of the pledged contribution. In this case, user device A may update the field(s) showing the pledged contribution for user A to show the amount change as user A slides the slidable element along the arc <NUM>.

Based on the user interaction indicating the first point <NUM> on the arc-shaped element <NUM>, user device A may present the first arc portion <NUM> on the UI in a different visual manner than the second arc portion <NUM>, and/or one or more other arc portions, such as the differential portion <NUM>. For example, user device A may present the first arc portion <NUM> on the UI using a first visual attribute, and user device A may present the second arc portion <NUM> on the UI using a second visual attribute that is different from the first visual attribute. As shown in <FIG>, the differential arc portion <NUM> spans from the first point <NUM> to the second point <NUM> and represents a difference between the total amount for the goal and a sum of a first contribution amount for user A and a second contribution amount for user B. The UI may present the differential arc portion <NUM> using a third visual attribute that is different from both the first visual attribute and the second visual attribute.

In some implementations, the second arc portion <NUM> representing the pledged contribution for user B may not be editable via user interaction when the UI is associated with the user account of user A (e.g., when user A is logged in). In some implementations, the account management device, based on receiving and verifying the user credential associated with user A, may transmit information that indicates an end or a side of the arc-shaped element that is associated with user A. For example, the information may indicate that the first end <NUM> of the arc-shaped element is associated with user A. The information may be included in the UI configuration information. In this case, the UI configuration information may cause user device A to allow user A to interact with the side or end of the arc-shaped element associated with user A and prevent user A from interacting with the side or end of the arc-shaped element not associated with user A. Similarly, the account management device may transmit, to user device B, information that indicates an end or a side that is associated with user B (e.g., the second end <NUM>) based on receiving and verifying the user credential associated with user B.

As shown in <FIG>, and by reference number <NUM>, user device A may transmit, to the account management device, information that identifies the pledged contribution amount for user A. For example, user device A may transmit the information to the account management device based on detecting a user interaction with a UI element on the UI. As shown by reference number <NUM>, the account management device may store the information that identifies the pledged contribution amount for user A in a data structure, such as the data structure described above in connection with <FIG>.

As shown in <FIG>, and by reference number <NUM>, user A may interact with user device A to login to the application associated with the joint account, as described elsewhere herein. User device A may present the UI including the arc-shaped element <NUM>. As shown by reference number <NUM>, the UI may include an "Edit Planned Contribution" mode or UI, in which user A may edit a previously stored pledged contribution amount for user A via the UI. In some implementations, the UI may enter the "Edit Planned Contribution" mode based on user device A detecting a user selection of a selectable UI element in the UI. In some implementations, the "Edit Planned Contribution" mode may be a sub-mode of the "View/Edit Existing Goal" mode. In this case, the UI may present the selectable UI element for entering the "Edit Planned Contribution" while in the "View/Edit Existing Goal" mode. Although operations described in connection with <FIG> are described in connection with the "Edit Planned Contribution" mode and in connection with User A, one or more of these operations may be performed in connection with the "View/Edit Existing Goal" mode (described above in connection with <FIG>) and/or in connection with User B.

As further shown in <FIG>, and by reference number <NUM>, user device A may detect a user interaction that indicates an adjusted first point <NUM> on the arc-shaped element <NUM>. For example, user A may interact with the slidable UI element described above to adjust the pledged contribution amount for user A. User device A may update the first arc portion <NUM> based on the adjusted first point <NUM> and determine the adjusted pledged contribution amount for user A based on the length of the updated first arc portion <NUM>. In some implementations, user device A may detect that the updated first arc portion <NUM> overlaps with the second arc portion <NUM>. For example, user device A may detect that the adjusted first point <NUM> indicated by the user interaction is located closer to the second end <NUM> of the arc-shaped element than is the second point <NUM> (e.g., a distance between the adjusted first point <NUM> and the second end <NUM> is smaller than a distance between the second point <NUM> and the second end <NUM>). In this case, the updated first arc portion <NUM> may include a portion <NUM> of the second arc portion <NUM> between the first point <NUM> and the second point <NUM>, and may also include an entirety <NUM> of the arc <NUM> other than the second arc portion <NUM> (e.g. a portion of the arc <NUM> between the second point <NUM> and the first end <NUM>).

Based on detecting that the updated first arc portion <NUM> overlaps with the second arc portion <NUM>, user device A may determine that the sum of the adjusted pledged contribution amount for user A, represented by the updated first arc portion <NUM>, and the pledged contribution amount for user B, represented by the second arc portion <NUM>, exceeds the total joint contribution amount. For example, as shown in <FIG>, the adjusted contribution amount for user A is $<NUM>, the contribution amount for user B is $<NUM>, and the sum of the contribution amounts for user A and user B ($<NUM>) exceeds the total amount of $<NUM> for the goal. As shown by reference number <NUM>, in some implementations, user device A may update the total amount for the goal and present the updated total amount on the UI. For example, user device A may update the total amount for the goal to an updated joint pledge contribution amount that is the sum of the pledged contribution amounts for user A and user B (e.g., $<NUM> in <FIG>). Alternatively, user device A may maintain the prior total amount for the goal, and may provide an indication of an additional amount beyond the total amount. Referring to the example of <FIG>, user device A may indicate that the total amount for the goal is still $<NUM>, and that there is an additional amount of $<NUM>. The additional amount may be used toward the goal or may be reallocated to a different goal. In this example, user device A may indicate the total amount and the additional amount, such as "Total Goal: $<NUM> + $<NUM> Extra.

In some implementations, user device A may present, on the UI and/or on the arc-shaped element, an indication that the sum of the pledged contribution amounts exceeds the total amount for the goal. For example, user device A may present the updated first arc portion <NUM>, including the portion <NUM>, on the UI using the first visual attribute associated with the first arc portion <NUM>. In some implementations, user device A may present a visual marking <NUM>, on the arc <NUM> (e.g., on the arc-shaped element), representing the second point <NUM> in order to visualize the amount of overlap between the updated first arc portion <NUM> and the second arc portion <NUM>.

In some implementations, user device A may display a prompt asking user A to confirm the selection of the adjusted first point <NUM> in a case in which the sum of the pledged contribution amounts exceeds the total amount for the goal. In this case, user device A may change the total amount for the goal to an updated total amount (e.g., an updated joint pledged contribution) based on receiving a user input that confirms the selection. In some implementations, user device A may initially present the updated arc portion <NUM> on the UI as an arc portion spanning from the first end <NUM> to the second point <NUM>, and may then present the updated first arc portion <NUM> including the portion <NUM> (e.g., between the first point <NUM> and the second point <NUM>) and the entirety <NUM> of the arc <NUM> other than the second arc portion <NUM> based on receiving the user input that confirms the selection. In some implementations, user device A may present the updated first arc portion <NUM> on the UI using the first visual attribute associated with the first arc portion <NUM>. As further shown, user device A may present the visual marking <NUM> representing the second point <NUM> using a visual attribute that is different from the first visual attribute. In some implementations, user device A may present the visual marking <NUM> using the second visual attribute used for the second arc potion <NUM> to indicate that the visual marking <NUM> indicates the second point <NUM> that is at an end of the second arc portion <NUM>. Alternatively, user device A may present the first arc portion <NUM> using a first visual attribute, may present the second arc portion <NUM> using a second visual attribute, and may present the visual marking <NUM> using a third visual attribute.

In some implementations, the UI may not permit the combined pledged contribution amounts for user A and user B to exceed to the total amount for the goal. In this case, user device A, based on detecting that the adjusted first point <NUM> is located closer to the second end <NUM> than is the second point <NUM>, may set the adjusted first point <NUM> to the same point as the second point <NUM>. That is, user device A may set the pledged contribution amount for user A to be equal to a difference between the total amount for the goal (e.g., the joint pledged contribution) and the pledged contribution amount for user B.

As further shown in <FIG>, and by reference number <NUM>, user device A may transmit, to the account management device, the updated pledged contribution amount for user A. In some implementations, user device A may transmit, to the account management device, the updated total amount for the goal in cases in which the adjustment to the updated pledged contribution amount for user A results in updating the total amount for the goal.

As shown in <FIG>, and by reference number <NUM>, the UI may include a "Transfer Funds" mode or UI in which a user may indicate an actual amount to contribute from a financial account associated with the user. As shown by reference number <NUM>, user device A may detect a user interaction that indicates a third point <NUM> on the first arc portion <NUM>. As further shown, a third arc portion spanning <NUM> from the first end <NUM> to the third point <NUM> may represent the actual amount, of the pledged contribution amount for user A, contributed to the total goal amount from the financial account associated with user A. By indicating the third point <NUM> and setting the third arc portion <NUM>, user A may indicate, via the UI, an amount to be transferred from the financial account associated with user A. For example, as shown in <FIG>, the actual amount to be transferred from the financial account associated with user A is $<NUM>. The UI may present the third arc portion <NUM> in a visual manner different from the first arc portion <NUM> (e.g., a remaining portion of the first arc portion <NUM> that represents a pledged, but not contributed, amount). For example, the UI may present the third arc portion <NUM> using a third visual attribute that is different from the first visual attribute associated with the first arc portion <NUM>. The third visual attribute may also be different from the second visual attribute associated with the second arc portion <NUM>, a visual attribute associated with a differential arc portion, and/or a visual attribute associated with the visual marking <NUM>.

User B may indicate, via the UI, an amount to transfer from a financial account associated with user B similarly to as described above for user A. As shown, user device A may present, on the UI, a fourth arc portion <NUM> spanning from the second end <NUM> to a fourth point <NUM> (or area, part, or the like) of the second arc portion <NUM>. The fourth arc portion <NUM> represents an actual amount contributed to the total amount for the goal from the financial account associated with user B. The UI may present the fourth arc portion <NUM> using a fourth visual attribute that is different from the second visual attribute associated with the second arc portion <NUM>. The fourth visual attribute may also be different from the first visual attribute associated with the first arc portion <NUM>, the third visual attribute associated with the third arc portion <NUM>, the visual attribute associated with the differential arc portion, and/or the visual attribute associated with the visual marking <NUM>.

As further shown in <FIG>, and by reference number <NUM>, user device A may transmit, to the account management device, an instruction to transfer funds from the financial account associated with user A. User device A may transmit the instruction to transfer the amount represented by the third arc portion <NUM> of the UI (e.g., $<NUM> in <FIG>) based on detecting the user interaction setting the amount to be transferred. The instructions to transfer the funds may include instructions to transfer the funds from the financial account associated with user A to the joint account for user A and user B or to transfer the funds to the financial account associated with user B.

As described above, user A may be a parent and user B may be a child. In some implementations, the UI presented on user device A may include a selectable field, such as a check box, that the parent may select to indicate that the remaining/outstanding portion of the parent's contribution (or user A's contribution) be auto-transferred to the account associated with the child (or user B) or the joint account when the child (or user B) reaches their pledged contribution. In this case, when the field is selected, user device A or user device B may automatically transmit an instruction to transfer the remaining funds for the parent's contribution (or user A's contribution) based on a determination that the actual contribution from the child (or user B) is equal to the pledged contribution from child (or user B).

Although implementations are described herein in connection with presentation and control of user interaction with an arc-shaped UI element, techniques described herein may be used for presentation and control of user interaction with UI elements having other shapes. For example, in some implementations, the UI element may have a vertical line or bar shape, a horizontal line or bar shape, or another shape. In some implementations, the UI element may have two ends and a connector portion spanning between the two ends. Respective portions (e.g., first and second portions) spanning from each of the two ends may represent the respective contributions of two users. Other portions of the UI element (e.g., a third portion, a fourth portion, and/or a differential portion) may be used similarly to in the implementations described above. Using the techniques described herein, a user device may present, on a UI, an arc-shaped UI element (or a UI element with another shape) that provides user-friendly visualization and editing of the individually pledged contributions of two users and the progress of the users toward a shared goal.

<FIG> is a diagram of an example environment <NUM> in which systems and/or methods described herein may be implemented. As shown in <FIG>, environment <NUM> may include one or more user devices <NUM>, an account management device <NUM>, an input device <NUM>, and a network <NUM>. Devices of environment <NUM> may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections.

The user device(s) <NUM> includes one or more devices capable of receiving, generating, storing, processing, and/or providing information associated with presentation of and control of user interaction with an arc-shaped UI element, as described elsewhere herein. The user device(s) <NUM> may include a communication device and/or a computing device. For example, the user device(s) <NUM> may include a wireless communication device, a mobile phone, a user equipment, a laptop computer, a tablet computer, a desktop computer, a gaming console, a set-top box, a wearable communication device (e.g., a smart wristwatch, a pair of smart eyeglasses, a head mounted display, or a virtual reality headset), or a similar type of device.

The account management device <NUM> includes one or more devices capable of receiving, generating, storing, processing, providing, and/or routing information associated with presentation of and control of user interaction with an arc-shaped UI element, as described elsewhere herein. The account management device <NUM> may include a communication device and/or a computing device. For example, the account management device <NUM> may include a server, such as an application server, a client server, a web server, a database server, a host server, a proxy server, a virtual server (e.g., executing on computing hardware), or a server in a cloud computing system. In some implementations, the server device <NUM> includes computing hardware used in a cloud computing environment. In some implementations, the account management device <NUM> stores information associated with a financial account, such as a bank account, a credit account, or the like.

The input device <NUM> includes one or more devices capable of receiving, generating, storing, processing, and/or providing information associated with creating or modifying a user account, as described elsewhere herein. The input device <NUM> may include a communication device and/or a computing device. For example, the input device <NUM> may include a wireless communication device, a mobile phone, a user equipment, a laptop computer, a tablet computer, a desktop computer, a gaming console, a set-top box, a wearable communication device (e.g., a smart wristwatch, a pair of smart eyeglasses, a head mounted display, or a virtual reality headset), or a similar type of device. In some implementations, the input device <NUM> and the user device <NUM> may be the same device. For example, the input device <NUM> may be a user device associated with user A (e.g., user device A), a user device associated with user B (e.g., user device B), as described elsewhere herein.

The network <NUM> includes one or more wired and/or wireless networks. For example, the network <NUM> may include a cellular network, a public land mobile network, a local area network, a wide area network, a metropolitan area network, a telephone network, a private network, the Internet, and/or a combination of these or other types of networks. The network <NUM> enables communication among the devices of environment <NUM>.

<FIG> is a diagram of example components of a device <NUM>, which may correspond to the user device(s) <NUM>, the account management device <NUM>, and/or the input device <NUM>. In some implementations, the user device(s) <NUM>, the account management device <NUM>, and/or the input device <NUM> may include one or more devices <NUM> and/or one or more components of device <NUM>. As shown in <FIG>, device <NUM> may include a bus <NUM>, a processor <NUM>, a memory <NUM>, a storage component <NUM>, an input component <NUM>, an output component <NUM>, and a communication component <NUM>.

Bus <NUM> includes a component that enables wired and/or wireless communication among the components of device <NUM>. Processor <NUM> includes a central processing unit, a graphics processing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, a field-programmable gate array, an application-specific integrated circuit, and/or another type of processing component. Processor <NUM> is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor <NUM> includes one or more processors capable of being programmed to perform a function. Memory <NUM> includes a random access memory, a read only memory, and/or another type of memory (e.g., a flash memory, a magnetic memory, and/or an optical memory).

Storage component <NUM> stores information and/or software related to the operation of device <NUM>. For example, storage component <NUM> may include a hard disk drive, a magnetic disk drive, an optical disk drive, a solid state disk drive, a compact disc, a digital versatile disc, and/or another type of non-transitory computer-readable medium. Input component <NUM> enables device <NUM> to receive input, such as user input and/or sensed inputs. For example, input component <NUM> may include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system component, an accelerometer, a gyroscope, and/or an actuator. Output component <NUM> enables device <NUM> to provide output, such as via a display, a speaker, and/or one or more light-emitting diodes. Communication component <NUM> enables device <NUM> to communicate with other devices, such as via a wired connection and/or a wireless connection. For example, communication component <NUM> may include a receiver, a transmitter, a transceiver, a modem, a network interface card, and/or an antenna.

Device <NUM> may perform one or more processes described herein. For example, a non-transitory computer-readable medium (e.g., memory <NUM> and/or storage component <NUM>) may store a set of instructions (e.g., one or more instructions, code, software code, and/or program code) for execution by processor <NUM>. Processor <NUM> may execute the set of instructions to perform one or more processes described herein. In some implementations, execution of the set of instructions, by one or more processors <NUM>, causes the one or more processors <NUM> and/or the device <NUM> to perform one or more processes described herein. In some implementations, hardwired circuitry may be used instead of or in combination with the instructions to perform one or more processes described herein.

<FIG> is a flowchart of an example process <NUM> associated with presentation of and control of user interaction with an arc-shaped user interface element. In some implementations, one or more process blocks of <FIG> may be performed by a user device (e.g., user device <NUM>). In some implementations, one or more process blocks of <FIG> may be performed by another device or a group of devices separate from or including the user device, such as account management device <NUM> and/or input device <NUM>. Additionally, or alternatively, one or more process blocks of <FIG> may be performed by one or more components of device <NUM>, such as processor <NUM>, memory <NUM>, storage component <NUM>, input component <NUM>, output component <NUM>, and/or communication component <NUM>.

As shown in <FIG>, process <NUM> may include presenting, on a user interface associated with a first user account, an arc-shaped element that includes a first end, a second end, and an arc spanning from the first end to the second end, wherein the arc represents a joint amount (block <NUM>). As further shown in <FIG>, process <NUM> may include detecting a user interaction that indicates a first area on the arc-shaped element (block <NUM>). As further shown in <FIG>, process <NUM> may include presenting, on the user interface and based on the user interaction, a first arc portion, of the arc, spanning from the first end to the first area, wherein the first arc portion represents a first amount, of the joint amount, to be associated with the first user account, and wherein the arc includes a second arc portion, spanning from the second end to a second area associated with a second user account, that represents a second amount, of the joint amount, associated with the second user account (block <NUM>). As further shown in <FIG>, process <NUM> may include transmitting information that identifies the first amount to be associated with the first user account (block <NUM>).

Modifications may be made in light of the above disclosure or may be acquired from practice of the implementations.

Although particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various implementations. As an example, "at least one of: a, b, or c" is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiple of the same item.

Claim 1:
A method for presenting an arc-shaped user interface element (<NUM>), the method comprising:
presenting, on a user interface of a user device (<NUM>), an arc-shaped user interface element (<NUM>) that includes a first end (<NUM>), a second end (<NUM>), and an arc (<NUM>) spanning from the first end (<NUM>) to the second end (<NUM>), wherein the arc (<NUM>) represents a total amount, and wherein the user interface is associated with a first user account;
detecting, by the user device (<NUM>), a user interaction that indicates a first point (<NUM>) on the arc-shaped user interface element (<NUM>);
presenting, on the user interface and based on the user interaction, a first arc portion (<NUM>) of the arc (<NUM>), spanning from the first end (<NUM>) to the first point (<NUM>), in a different visual manner than one or more other arc portions of the arc (<NUM>),
wherein the first arc portion (<NUM>) represents a first amount, of the total amount, to be associated with the first user account,
wherein the one or more other arc portions includes a second arc portion (<NUM>) of the arc (<NUM>), spanning from the second end (<NUM>) to a second point (<NUM>) associated with a second user account, that represents a second amount, of the total amount, associated with the second user account; and
transmitting, by the user device (<NUM>) and to an account management device (<NUM>), information that identifies the first amount, of the total amount, to be associated with the first user account,
wherein the second arc portion (<NUM>) is not editable via user interaction with the user interface associated with the first user account.