US-12625954-B1 - Dynamic adaptation of identity related user interface

US12625954B1US 12625954 B1US12625954 B1US 12625954B1US-12625954-B1

Abstract

An Account Booking Location (ABL) is computed from a login request to access an account of a user. The ABL corresponds to an asset of a partner entity that initiated the account. A UI element corresponding to the ABL is pushed from a repository to a cache for a UI rendering and a rendering service composes a rendering instruction using the cached data to cause a brand-specific UI to be rendered on a device of the user. When a second login request from a second user also corresponds to the ABL, the cached data is reused to compose a second rendering instruction such that the second rendering instruction causes the brand-specific UI to be rendered on a second device. When a control mechanism is configured to cause a feature to be rendered in an ABL agnostic manner, the rendering instruction is modified to include the feature on the brand-specific UI.

Inventors

Manohar Perumal
Russell Dean Brandon
Soma Nagasundaram
Sandeep Butapati
Rachel Yuen Lynn Tan
Arnab Bhattacharjee
Loree Winstanley

Assignees

U.S. BANK NATIONAL ASSOCIATION

Dates

Publication Date: 20260512
Application Date: 20250505

Claims (20)

1 . A computer-implemented method comprising: computing an Account Booking Location (ABL) from a login request to access an account of a first user, wherein the ABL comprises an identifier assigned to an asset of a partner entity, the identifier corresponding to a location of a site where the partner entity first created the account, and where the account is considered to be located; pushing from a repository to a cache to form cached data, on demand for a UI rendering responsive to the request, a User Interface (UI) element corresponding to the ABL; causing, responsive to the pushing, a rendering service to compose a rendering instruction using the cached data such that the rendering instruction causes a first brand-specific UI to be rendered on a device associated with the first user; reusing, responsive to a second login request from a second user wherein the second login request also corresponds to the ABL, the cached data to compose a second rendering instruction such that the second rendering instruction causes the first brand-specific UI to be rendered on a second device associated with the second user; and further causing, responsive to a determination that a control mechanism is configured to cause a feature to be rendered in an ABL agnostic manner, the rendering service to modify the rendering instruction such that the feature is included on the first brand-specific UI.
2 . The computer-implemented method of claim 1 , wherein the control mechanism is configured to control a rendering of a subset of a set of features on any UI that is rendered by the rendering service regardless of any correspondence with any particular partner entity.
3 . The computer-implemented method of claim 1 , wherein the control mechanism is configured to be enabled responsive to a detection of a first event by an event detection component, wherein the rendering service modifies the rendering instruction only when the control mechanism is enabled.
4 . The computer-implemented method of claim 1 , further comprising: configuring the control mechanism to be disabled responsive to a second detection of a second event by the event detection component at a future time; and causing the rendering service to cease modifying the rendering instruction such that the feature is omitted from the first brand-specific UI subsequent to the second detection.
5 . The computer-implemented method of claim 1 , further comprising: associating a second control mechanism with a second feature that is to be rendered in the ABL agnostic manner; determining that the second control mechanism is disabled; causing, responsive to the second control mechanism being disabled, the rendering service to omit the second feature from the rendering instruction.
6 . The computer-implemented method of claim 1 , wherein a function code associated with the feature is configured to cause a rendering of the feature regardless of the control mechanism, and wherein the rendering of the feature is controlled by a toggling of the control mechanism relative to the feature.
7 . The computer-implemented method of claim 1 , further comprising: configuring a code of the control mechanism such that the control mechanism can be associated with a subset of a set of features; and further configuring the code of the control mechanism such that the subset of features can be toggled between a rendering mode and a non-rendering mode using the control mechanism.
8 . A computer program product comprising one or more non-transitory computer readable storage media, and program instructions collectively stored on the one or more computer readable storage media, the program instructions executable by a set of one or more processors to cause the set of one or more processors to perform operations comprising: computing an Account Booking Location (ABL) from a login request to access an account of a first user, wherein the ABL comprises an identifier assigned to an asset of a partner entity, the identifier corresponding to a location of a site where the partner entity first created the account, and where the account is considered to be located; pushing from a repository to a cache to form cached data, on demand for a UI rendering responsive to the request, a User Interface (UI) element corresponding to the ABL; causing, responsive to the pushing, a rendering service to compose a rendering instruction using the cached data such that the rendering instruction causes a first brand-specific UI to be rendered on a device associated with the first user; reusing, responsive to a second login request from a second user wherein the second login request also corresponds to the ABL, the cached data to compose a second rendering instruction such that the second rendering instruction causes the first brand-specific UI to be rendered on a second device associated with the second user; and further causing, responsive to a determination that a control mechanism is configured to cause a feature to be rendered in an ABL agnostic manner, the rendering service to modify the rendering instruction such that the feature is included on the first brand-specific UI.
9 . The computer program product of claim 8 , wherein the control mechanism is configured to control a rendering of a subset of a set of features on any UI that is rendered by the rendering service regardless of any correspondence with any particular partner entity.
10 . The computer program product of claim 8 , wherein the control mechanism is configured to be enabled responsive to a detection of a first event by an event detection component, wherein the rendering service modifies the rendering instruction only when the control mechanism is enabled.
11 . The computer program product of claim 8 , further comprising: configuring the control mechanism to be disabled responsive to a second detection of a second event by the event detection component at a future time; and causing the rendering service to cease modifying the rendering instruction such that the feature is omitted from the first brand-specific UI subsequent to the second detection.
12 . The computer program product of claim 8 , further comprising: associating a second control mechanism with a second feature that is to be rendered in the ABL agnostic manner; determining that the second control mechanism is disabled; causing, responsive to the second control mechanism being disabled, the rendering service to omit the second feature from the rendering instruction.
13 . The computer program product of claim 8 , wherein a function code associated with the feature is configured to cause a rendering of the feature regardless of the control mechanism, and wherein the rendering of the feature is controlled by a toggling of the control mechanism relative to the feature.
14 . The computer program product of claim 8 , further comprising: configuring a code of the control mechanism such that the control mechanism can be associated with a subset of a set of features; and further configuring the code of the control mechanism such that the subset of features can be toggled between a rendering mode and a non-rendering mode using the control mechanism.
15 . The computer program product of claim 8 , wherein the stored program instructions are stored in a computer readable storage device in a data processing system, and wherein the stored program instructions are transferred over a network from a remote data processing system.
16 . The computer program product of claim 8 , wherein the stored program instructions are stored in a computer readable storage device in a server data processing system, and wherein the stored program instructions are downloaded in response to a request over a network to a remote data processing system for use in a computer readable storage device associated with the remote data processing system, further comprising: program instructions to meter use of the program instructions associated with the request; and program instructions to generate an invoice based on the metered use.
17 . A computer system comprising a set of one or more processors and one or more computer readable storage media, and program instructions collectively stored on the one or more computer readable storage media, the program instructions executable by the set of one or more processors to cause the processor to perform operations comprising: computing an Account Booking Location (ABL) from a login request to access an account of a first user, wherein the ABL comprises an identifier assigned to an asset of a partner entity, the identifier corresponding to a location of a site where the partner entity first created the account, and where the account is considered to be located; pushing from a repository to a cache to form cached data, on demand for a UI rendering responsive to the request, a User Interface (UI) element corresponding to the ABL; causing, responsive to the pushing, a rendering service to compose a rendering instruction using the cached data such that the rendering instruction causes a first brand-specific UI to be rendered on a device associated with the first user; reusing, responsive to a second login request from a second user wherein the second login request also corresponds to the ABL, the cached data to compose a second rendering instruction such that the second rendering instruction causes the first brand-specific UI to be rendered on a second device associated with the second user; and further causing, responsive to a determination that a control mechanism is configured to cause a feature to be rendered in an ABL agnostic manner, the rendering service to modify the rendering instruction such that the feature is included on the first brand-specific UI.
18 . The computer system of claim 17 , wherein the control mechanism is configured to control a rendering of a subset of a set of features on any UI that is rendered by the rendering service regardless of any correspondence with any particular partner entity.
19 . The computer system of claim 17 , wherein the control mechanism is configured to be enabled responsive to a detection of a first event by an event detection component, wherein the rendering service modifies the rendering instruction only when the control mechanism is enabled.
20 . The computer system of claim 17 , further comprising: configuring the control mechanism to be disabled responsive to a second detection of a second event by the event detection component at a future time; and causing the rendering service to cease modifying the rendering instruction such that the feature is omitted from the first brand-specific UI subsequent to the second detection.

Description

RELATED APPLICATION The present application is a Continuation-In-Part of U.S. patent application Ser. No. 19/081,261, titled DYNAMIC ADAPTATION OF IDENTITY RELATED USER INTERFACE, and filed on Mar. 17, 2025. BACKGROUND User Interface (UI) refers to the visual elements of a product (e.g., a physical or virtual product, such as an application (“app”) or system with which one or more users interact in or with a computing environment. Typically, a UI includes UI components (components or elements), such as buttons, icons, menus, text fields, and many other types of components that facilitate user interaction and information presentation. Thus, a UI can include components both for receiving input from a user and for providing output to the user. In some instances, a single component can both provide information to a user and receive input. UI is primarily concerned with how the user interacts with a software or system, and designing a UI involves designing these components to be functional and visually appealing. User experience (UX) is the overall experience a user has when using a UI, especially in terms of how easy or satisfying the UI is to use. UX can be described in terms of single UI components, the overall experience of interacting with an entire UI, or the overall experience of using a product or system to achieve a task. UX encompasses everything from the usability and accessibility of a system to the emotions a user feels when interacting with the UI. Where UI is concerned with the visual design of a website, page, or screen of a software, UX is concerned more with how the UI works, how intuitive the flow and function implemented by the UI feels, how efficiently tasks can be completed using the UI, and how enjoyable the process is to a user. A product or system having an improved UI or a UX can result in the product or system having technical advantages over other products or systems lacking such improvements. Such technical advantages can include one or more aspects selected from the group consisting of: improved battery life, lower power consumption, decreased use of processing resources, decreased use of networking resources, improved accessibility, other advantages, or combinations thereof. In addition to UI components, a UI also includes UI content. UI content includes text, graphics, images, multimedia, or links to these types of data. UI content appears in a user interface to guide users, provide information, and manage or enhance the user's experience within an application or website. Some examples of UI content include-textual content, headings & titles, labels, tooltips & hints, error messages, notifications & alerts, visual content, icons & graphics, illustrations & images, videos & animations, interactive content, forms & inputs, sliders & carousels, modals & pop-ups, and many others. One aspect of a UI-UX design is branding. UI content is an important consideration in designing the UX, to ensure that users can recognize the entity they are interacting with via the UI, the relationship they have with the entity, and distinguish the tasks they are performing via the UI. Branding of a UI is the changing, adapting, differentiating, selecting, and presentation of UI elements, UI content, or both, to reflect a name, type, or identity of an entity, or the source or target of the information being exchanged via the UI with an entity that is represented on the UI. A Content Management System (CMS) is a platform used for creating, managing, and modifying digital content. ADOBE EXPERIENCE MANAGER (AEM) from ADOBE is a CMS solution that manages UI content and other UI assets and streamlines the design workflow for UI-UX developers. SUMMARY The present disclosure includes inventive concepts relating generally to generating code for a graphical user interface, such as methods, systems, and computer programs for dynamic adaptation of identity related user interface. The illustrative embodiments provide for dynamic adaptation of identity related user interface. An embodiment includes computing an Account Booking Location (ABL) from a login request to access an account of a first user, wherein the ABL corresponds to an asset of a partner entity that initiated the account. The embodiment further includes pushing from a repository to a cache to form cached data, on demand for a UI rendering responsive to the request, a UI element corresponding to the ABL. The embodiment further includes causing, responsive to the pushing, a rendering service to compose a rendering instruction using the cached data such that the rendering instruction causes a first brand-specific UI to be rendered on a device associated with the first user. The embodiment further includes reusing, responsive to a second login request from a second user wherein the second login request also corresponds to the ABL, the cached data to compose a second rendering instruction such that the second rendering instruction causes the first brand-specif