To help in understanding the present disclosure, a discussion of some example touch gestures is provided. In particular, example touch gestures that may be interpreted as commands to scroll a scrollable UI are described. It should be understood that other touch gestures may be used by a user to input a scroll command. Further, other forms of user inputs (e.g., via a mechanical button, via a mouse, via voice) may be used to input a scroll command.

FIGS. 2A-2C illustrate some example touch inputs that may be used to scroll a scrollable UI that is displayed by the apparatus 100. It should be noted that FIGS. 2A-2C do not illustrate condensing or scrolling of the UI sections, for simplicity.

FIG. 2A illustrates an example swipe gesture 202, indicated by a short black arrow, that travels a relatively short distance and/or is performed at a relatively slow speed. Based on the parameters of the swipe gesture 202 (e.g., relatively short distance and/or relatively slow speed), the touch input is recognized by the apparatus 100 as a command to scroll the UI at a relatively slow scrolling rate 204, indicated by a short white arrow.

FIG. 2B illustrates another example swipe gesture 206, indicated by a long black arrow, that travels a longer distance and/or is performed at a faster speed compared to the swipe gesture 202 of FIG. 2A. Based on the parameters of this swipe gesture 206 (e.g., longer distance and/or faster speed), this touch input is recognized by the apparatus 100 as a command to scroll the UI at a faster scrolling rate 208, indicated by a longer white arrow, compared to the slow scrolling rate 204 of FIG. 2A.

FIG. 2C illustrates another example swipe gesture 210, indicated by multiple arrows, that comprises multiple swipes performed in succession within a defined time duration. In these examples, multiple swipes performed in quick succession (e.g., the start of one swipe being performed within a defined time duration, such as 100 ms, after the end of a preceding swipe) may together be recognized as a single compound swipe gesture 210. Based on the parameters of this swipe gesture 210 (e.g., number of swipes performed), this touch input is recognized by the apparatus 100 as a command to scroll the UI at a scrolling rate 212, indicated by a white arrow, dependent on the number of swipes (e.g., higher scrolling rate for a higher number of swipes performed).

Although FIGS. 2A-2C illustrate vertical swiping gestures to cause vertical scrolling of the UI, it should be understood that swiping gestures may be performed in other directions and may result in scrolling of the UI in other directions (e.g., horizontal scrolling, diagonal scrolling, etc.).

FIG. 3 is a flowchart illustrating an example method 300 that may be implemented by the apparatus 100. For example, the processing unit 102 of the apparatus 100 may execute instructions, stored in the memory 108, for the condensable UI module 112. In other examples, the method 300 may be encoded as part of the instructions for an application that uses a scrollable UI, rather than as a separate module.

At an operation 302, a scrollable UI is outputted, where the UI has a plurality of sections. For example, the processing unit 102 of the apparatus 100 may cause a display device of the apparatus 100 to output the UI. A scrollable UI may be visually and/or logically divided into a plurality of sections, which may be navigated to by scrolling (e.g., vertically and/or horizontally) through the UI. That is, the size of the UI may be larger than the display area of the display device, such that only a portion of the UI may be viewable at any time, and such that a user may input scrolling commands to bring into view section(s) of the UI. Each section of the UI may be individually condensed. In general, each section of the UI may be defined to have an optional heading (e.g., title, section label, etc.) and contents (e.g., textual content, graphical content, etc.). When a section is condensed, the size of the section may be reduced by reducing the area occupied by the contents while keeping the heading (if present) viewable. For example, if a section of the UI has a textual heading and multiple lines of textual content, then the section may be condensed by reducing the textual content to a single line while maintaining the full textual heading. In some examples, reducing the textual content of a condensed section may include simple truncation of the textual content (e.g., so that only the first line of the section is displayed), may include reducing the size of the textual content (e.g., reducing the font size or spacing), may include showing only a summary text (e.g., a summary text may be predefined for the section, such as a subheading; or a summary text may be automatically generated using machine learning or natural language processing techniques), or may include substituting portions of the textual content with abbreviations, among other possibilities. In another example, if a section of the UI has a textual heading and multiple lines of textual content, then the section may be condensed by omitting the textual content completely while maintaining the textual heading. Other such examples will be discussed further below.

A UI may be divided into sections based on natural logical divisions in the UI. For example, if the UI is for viewing a structured document (e.g., in a text editing/reading application) having headings, each heading may define a respective section of the UI. In another example, if the UI is for an image gallery application where images are sorted chronologically or by category (e.g., categorized by person(s) appearing in each image), the UI may be naturally divided into sections by day/month/year (e.g., sections defined by year, then subsections defined by month, and further subsections defined by day) or by category. In another example, if the UI is for a calendar application, the UI may be divided into sections by day/week/month/year (e.g., sections defined by year, then subsections defined by month, further subsections defined by week, and yet further subsections defined by day). In another example, if the UI is for a fillable form, each heading of the form may define a respective section of the UI. Other such examples of scrollable UIs having multiple sections are considered to be within the scope of the present disclosure.

At an operation 304, a command is received to scroll the UI at a first scrolling rate. For example, the processing unit 102 may receive a signal (e.g., via the I/O interface 104) corresponding to an input command to scroll the UI at a first scrolling rate.

In some examples, the first scrolling rate may be dependent on parameters of the received signal corresponding to the input command. In examples where the received signal is received from a touch-sensitive device, the received signal may indicate a swipe gesture having detected parameters (e.g., detected speed, distance, acceleration and/or number of swipes). Then the first scrolling rate may correspond to at least one of the parameters of the detected swipe gesture (e.g., the first scrolling rate is faster for a faster swipe speed, a larger swipe distance, a greater swipe acceleration and/or a greater number of successive swipes within a defined time duration). In examples where the received signal is received from a mouse device, the first scrolling rate may correspond to a speed, acceleration and/or distance of mouse movement.

In some examples, the first scrolling rate may be predefined and not dependent on parameters of the received signal. For example, if the received signal is received from a keyboard device (e.g., user presses a scroll button), the first scrolling rate may be a fixed rate that is maintained as long as the scroll button is held down.

At an operation 306, in response to the first scrolling rate exceeding a defined first threshold, one or more sections of the UI are condensed. The section(s) of the UI that are condensed may be predefined (e.g., by the developer or designer of the UI), based on the scrolling direction (e.g., if UI is scrolled to bring bottom sections of UI into view, upper sections of the UI may be condensed, and vice versa; if UI is scrolled to bring rightmost sections of UI into view, leftmost sections of the UI may be condensed, and vice versa), based on the content of the sections (e.g., sections containing graphical elements are condensed; or sections that do not require user input are condensed), etc. The condensed section(s) of the UI may be condensed during execution of the command to scroll the UI (i.e., during the time that the UI is still scrolling).

Condensing a section of the UI results in the section occupying a smaller area of the display screen of the apparatus 100. This may be achieved by, for example, reducing the size and/or quality (e.g., resolution) of images in the content of the section, omitting images and other graphical elements from the content of the section, reducing the font of text in the content of the section, reducing the number of lines of text in the content of the section, replacing some or all of the textual content of the section with abbreviations or a summary text, reducing the overall size of the section (e.g., similar to “zooming out” of the section), changing the arrangement of content in the section (e.g., rearranging a grid of images, sometimes referred to as a “gallery” view, into a single row that is horizontally scrollable, sometimes referred to as a “filmstrip” view), removing interactive elements (e.g., user-selectable options, input fields, drop-down menus, etc.) from the content of the section (such that the section becomes a “read-only” section), or replacing input field with information retrieved from a user profile, among other possibilities.

In some examples, the section(s) may be condensed in a stepwise manner, in which the section(s) are condensed by a first amount (e.g., contents condensed by 25%) if the first scrolling rate is in a first range above the first threshold, and condensed by a second greater amount (e.g., contents condensed by 50%) if the first scrolling rate is in a second higher range above the first threshold. In other examples, the condensed section(s) of the UI may be condensed by an amount that is continuous or semi-continuous and proportionate to the first scrolling rate. For example, the amount by which the first scrolling rate exceeds the first threshold may be mapped or normalized to a value in the continuous range of 0.0 to 1.0, and the section(s) of the UI may be condensed by a percentage corresponding to the mapped or normalized value.

In some examples, if the UI includes a section with a sub-section, condensing a section may involve omitting (i.e., hiding) the sub-section (and also any sub-sub-sections within the sub-section), such that only the higher-level section is shown. In some examples, condensing a section of the UI in this manner may enable the UI to be changed from a granular view to a higher-level view. For example, if the UI provides information in chronological sections (e.g., the UI for a calendar application may provide events information sorted by date), the UI may display per-year events at a highest-level section, per-month events at a next-higher-level sub-section, and per-day events at a lowest-level sub-section. Thus, condensing the UI may involve hiding more granular, lower-level chronological sub-sections so that higher-level chronological sections are displayed (e.g., the calendar UI may be originally displaying events on a per-day basis, then condensed to display events on a per-month basis).

Optionally, the operation 306 may include an operation 308 to provide a UI element (e.g., a selectable option, a prompt, etc.) that the user may interact with to enable condensing of the section(s) of the UI. For example, after determining that the first scrolling rate exceeds the first threshold but before condensing the section(s) of the UI, a UI element may be displayed in the UI, which the user may select in order to cause the section(s) of the UI to be condensed.

Optionally, if at least one condensed section of the UI includes one or more input fields, the operation 306 may include an operation 310 to automatically complete the one or more input fields of at least one condensed section of the UI. For example, if an input field of a condensed section requires user input of data that is already stored in the memory 108 of the apparatus 100, the relevant data may be identified (e.g., based on the label assigned to an input field), retrieved from the memory 108 and automatically inputted into the input field. In another example, if the input field has a default value (which may be defined by the developer or designer of the UI), the default value may be automatically inputted into the input field. In this way, condensing the section may result in a condensed section that displays a summary of data that is already available (i.e., without requiring further user input). The condensed section may thus become a read-only version (i.e., without enabled input fields or other elements requiring or permitting user input) of the original section. In some examples, an input field of a condensed section may be automatically completed using data that is retrieved from an external system (i.e., external to the apparatus 100). For example, if the apparatus 100 is in communication with a network server or a software platform (e.g., the UI displayed by the apparatus 100 is the manner in which the network server or software platform receives input from and provides output to the user), condensing the section may involve the apparatus 100 automatically querying the network server or software platform for the relevant data to complete the input field. The condensed section may then be condensed such that the inputted data is displayed (e.g., in a smaller font) in place of a larger input field, or the condensed section may be condensed such that only the heading of the section is displayed together with a label indicating that the section has been completed.

In some examples, if the condensed section includes at least one particular input field that cannot be automatically completed using data that is already available (e.g., the input field requires data that is not contained in a user profile, or the input field does not have a defined default value), the particular input field may remain incomplete and available for user input even after condensing the section. That is, the section may be condensed so that a first input field is automatically completed and replaced with the completed data value where the data is available (or retrievable) while a second input field that cannot be automatically completed may remain displayed (despite the first input field having been removed). In some examples, condensing the section in which the second input field remains incomplete may cause the section to be condensed in a way that the second input field (that still requires user input) is positioned at or close to a focus area of the display screen. In the present disclosure, a focus area of the screen refers to an area of the screen in which a user's gaze or attention is expected to naturally fall or in which a user's gaze or attention has been detected to be currently focused at (e.g., using eye gaze detection algorithms). For example, if the focus area of the display screen is defined (or detected) to be in the top third of the screen, then condensing the section may involve automatically replacing the first input field with the available data and further positioning the condensed section such that the second input field is in the top third of the screen. In this way, condensing the UI section may enable more efficient and/or intuitive user interaction by focusing the user's attention on the input field that requires their input. This may be particularly useful, for example, in scenarios where the UI is being displayed by an apparatus 100 having limited screen size or where the UI includes many input fields but most of which can be automatically completed (e.g., such that it is difficult for the user to identify which input fields actually require their attention). In some examples, positioning an input field at or close to a focus area of the display screen may include automatically enabling or selecting the input field so as to direct further input (e.g., keystrokes from a real or virtual keyboard) to the input field.

In some other examples, the condensed section may be condensed such that all input fields are omitted, even if there is an input field that cannot be automatically completed using available or retrievable data. The heading of such a condensed section may optionally be displayed with a label indicating that the section is incomplete.

Regardless of whether performing the operation 306 includes performing the optional operation 308 and/or optional operation 310, optional operation 312 or optional operation 314 may follow the operation 306.

At the optional operation 312, in response to determining that scrolling of the UI has decreased in rate from the first scrolling rate (i.e., scrolling has slowed down) or that scrolling of the UI has stopped, the condensed section(s) of the UI may be automatically expanded.

Expansion of the condensed section(s) may involve performing an operation that reverses the condensing operation that was performed at the operation 306.

For example, if the condensed section(s) were condensed in a stepwise manner, expansion may be also in a stepwise manner (e.g., expanded to 50% when the scrolling rate of the UI drops below a first threshold, then expanded to 100% when the scrolling of the UI has stopped). In another example if the condensed section(s) were condensed in a continuous manner proportionate to the first scrolling rate, the condensed section(s) may be expanded in a continuous manner proportionate to the decrease in the rate of scrolling of the UI (e.g., corresponding to a normalized rate of scrolling).

In some examples, expanding the condensed section(s) may be performed only after the scrolling rate of the UI has decreased below a defined threshold (which may or may not be different from the first threshold that is used in the operation 306). The threshold for determining whether the condensed section(s) should be expanded may be lower than the threshold used to determine whether the section(s) should be condensed. This hysteresis effect may be used to help provide a smoother user experience (e.g., avoiding quick succession of condensing/expanding section(s)). In some examples, expanding the condensed section(s) may be performed only after the scrolling rate of the UI has decreased in rate from the first scrolling rate for at least a defined time period or scrolling has stopped for at least a defined time period, to help provide a smoother user experience.

In some examples, inertial scrolling may be used to scroll the UI. Inertial scrolling is commonly used in cases where touch inputs (e.g., swipe gestures) are used to scroll the UI. However, inertial scrolling may also be used where other types of inputs are used (e.g., using a scroll button). Inertial scrolling (which may also be referred to as kinetic scrolling, scroll coasting, or scrolling momentum) refers to scrolling of a UI that continues when the user input that causes the scrolling is released and that gradually decays until the scrolling is stopped. This type of scrolling may be considered to mimic the physical effect of, for example, giving a short push to a piece of paper where the paper will slide and then slow to a stop (in this scenario, the scrolling of the UI mimics the piece of paper sliding away from or towards the user). In some examples, inertial scrolling may be designed to closely mimic real-world physics, such as the case where the scrolling rate of the UI and the gradual decay of the scrolling rate depend on the distance, speed, angle and/or acceleration of the detected touch input. In other examples, inertial scrolling may not be true to real-world physics, and may simply be a form of scrolling that gradually decays in rate (rather than stopping abruptly) when the scrolling input is released.

FIG. 4 illustrates a simplified example of how inertial scrolling using touch input may be used to scroll a UI. It should be noted that FIG. 4 does not illustrate condensing of the UI sections, for simplicity.

In FIG. 4, a simplified UI is displayed by the apparatus 100. A user performs a swipe gesture 402, indicated by a long black arrow. Based on the parameters of this swipe gesture 402, this touch input is recognized by the apparatus 100 as a command to scroll the UI at a first scrolling rate 404, indicated by a white arrow. When the swipe gesture 402 ends (and other input to scroll the UI is absent), there is a decay in the scrolling of the UI so that after a short time (indicated as t1) the UI is scrolled at a slower scrolling rate 406 (indicated by a shorter white arrow) and after further time (indicated as t2) scrolling of the UI has stopped. As discussed, above, one or more sections of the UI may be condensed when the first scrolling rate 404 exceeds a first threshold and the condensed section(s) may be expanded in response to the scrolling of the UI decreasing to the slower scrolling rate 406.

In some examples, instead of or in addition to automatically expanding the condensed section(s) in response to a decrease in the scrolling rate or a cessation of the scrolling of the UI, a UI element may be provided so that the user may manually select one or more condensed sections to expand. For example, when a section of the UI is condensed at the operation 306, a UI element may be provided at or near the heading of the condensed section that the user may select to expand the condensed section back to its full size. The condensed section may remain condensed, even after scrolling of the UI has slowed or stopped, until the UI element is selected to expand the condensed section. This may enable a user to manually select which condensed section is of interest to view in full.

In some examples, expanding a condensed section may cause the section to be expanded such that the content of the expanded section is displayed in a way that reflects the state of the content prior to the section having been condensed. For example, if the user had navigated to a certain location in the content (e.g., had scrolled down partway in the content), the certain location may be saved as a checkpoint. Then, when the section is expanded again, the content may be automatically displayed at the checkpoint location (e.g., in the middle of the content in the section, rather than at the start of the content).

In some examples, expansion of a condensed section may cause the section to be expanded such that the expanded section is displayed in a way that a particular portion of the expanded section is positioned in a defined or detected focus area of the screen. For example, if the section includes an input field that requires user input (e.g., the input field could not be automatically completed using available data) then when the section is expanded the section may be positioned such that the input field requiring user input is positioned within the focus area of the screen. It should be noted that if there are other input fields that have been automatically completed using available (or retrievable) data when the section was previously condensed, then those input fields may be displayed with the data already filled in when the section is expanded.

In some examples, if the condensed section is expanded in response to user selection (e.g., a user manually selects the heading of the condensed section or selects a UI element provided at or near the heading), the user may be provided with an additional option to expand the section at the checkpoint location or to expand the section at the start of the section. In some examples, a preview of the checkpoint location may be displayed (e.g., a portion of textual content or a thumbnail of graphical content corresponding to the checkpoint location), to enable the user to be informed of the checkpoint location prior to the user making a selection to expand the section at the checkpoint location.

Following optional operation 312, the method 300 may return to the operation 304 to receive another command to scroll the UI.

Returning to the operation 306, optional operation 314 may follow the operation 306.

At the optional operation 314, a command is received to scroll the UI at a second scrolling rate that is higher than the first scrolling rate. For example, the processing unit 102 may receive another signal (e.g., via the I/O interface 104) corresponding to an input command to scroll the UI at the second scrolling rate.

The command to scroll the UI at the second scrolling rate may be received via the same input modality as the command to scroll the UI at the first scrolling rate (received at the operation 304). For example, if a touch input is used to scroll the UI at a first scrolling rate (e.g., using a first swipe gesture having a first speed, distance and/or acceleration), then another touch input may be used to scroll the UI at a faster second scrolling rate (e.g., using a second swipe gesture having a greater second speed, distance and/or acceleration).

At an optional operation 316 following the optional operation 314, in response to determining that the second scrolling rate exceeds a second threshold (that is higher than the first threshold considered at the operation 306), one or more sections of the UI are further condensed.

This further condensation of the section(s) of the UI may include further condensing one or more sections of the UI that had already been partially condensed in response to the first scrolling rate. For example, at the operation 306, when it is determined that the first scrolling rate exceeds the first threshold, section(s) of the UI may be condensed to a first semi-condensed state. A semi-condensed state may be a state in which a second has its content reduced in size (e.g., reduced to occupy only 50% of the original area, or having large graphical elements removed from the content) but the content has not been completely omitted. When, at the operation 316, it is determined that the second scrolling exceeds the second higher threshold, the one or more of the semi-condensed section(s) may be further condensed to a second fully-condensed state in which only the heading of the section is preserved while the content is not displayed. It should be noted that not necessarily all of the semi-condensed section(s) may be further condensed (e.g., if a semi-condensed section does not have any graphical elements to remove then that section may not be further condensed).

In another example, in the semi-condensed state, a first category of visual elements may be omitted from the condensed section(s) of the UI. For example, large visual elements, such as images, UI buttons or animation may be omitted in the semi-condensed state. Then, when one or more of the semi-condensed section(s) are further condensed in response to the second scrolling rate exceeding the second higher threshold, a second category of visual elements may be further omitted (in addition to the already omitted first category of visual elements). The second category of visual elements may be smaller than those of the first category, for example text or small icons may be in the second category of visual elements. The different categories of visual elements that may be omitted/displayed in different condensed states may be predefined (e.g., by a designer or developer of the UI), may be a set default (e.g., set by the manufacturer of the apparatus 100), or may be determined dynamically (e.g., based on number of visual elements, based on which visual elements occupy the most area, based on which visual elements require more processing power to render, etc.), among other possibilities.

In some examples, further condensation of one of more sections of the UI may include condensing section(s) that had not been condensed in response to the first scrolling rate exceeding the first threshold. For example, when the first scrolling rate is determined to exceed the first threshold (at the operation 306), only one section of the UI may be condensed (e.g., if the UI is being scrolled down to view lower sections of the UI, only the uppermost section of the section may be condensed at first); and when the second scrolling rate is determined to exceed the second higher threshold (at the operation 316), additional or all sections of the UI may be condensed (e.g., if the UI is scrolled down even faster, all sections of the UI except the bottommost section may be condensed).

Other such manner of further condensing section(s) of the UI in response to the second scrolling rate exceeding the second higher threshold may be implemented.

In some examples, if the second scrolling rate exceeds a maximum scrolling rate, a UI element (e.g., a selectable option, a prompt, etc.) may be provided that the user may interact with to cause the UI to be scrolled to the topmost (or bottommost, leftmost, rightmost, etc. depending on the direction of scrolling) section of the UI, or that the user may interact with to display a table of contents, for example.

Following the optional operation 316, the method 300 may proceed to optional operation 312 or may return to operation 304.

Although FIG. 3 illustrates operations for condensing section(s) of the UI in response to first and second scrolling rates, it should be understood that the method 300 may be similarly extended to enable further condensing of section(s) of the UI in response to third, fourth, etc. scrolling rates that differ from the first and the second scrolling rates. For example, optional operations 314 and 316 may be performed to even further condense one or more sections of the UI in response to an even faster third scrolling rate that exceeds a third threshold that is higher than the second threshold.

In some examples, in addition to or instead of further condensing section(s) of the UI in response to a second scrolling rate that exceeds a second higher threshold, the section(s) of the UI may be condensed proportionate to the amount by which the scrolling rate of the UI exceeds the first threshold. For example, the operation 306 may involve not only determining that the first scrolling rate exceeds the first threshold but also the amount by which the first scrolling rate exceeds the first threshold. The condensed section(s) may then be condensed by an amount proportionate to the amount by which the first scrolling rate exceeds the first threshold. Then, if the user provides further input to scroll the UI faster (e.g., performs another faster swipe gesture), the scrolling rate of the UI is increased and the condensed section(s) may be further condensed proportionate to the increase in scrolling rate.

Some example implementations of the method 300 are now discussed. Examples are illustrated in which a command to scroll the UI is inputted using certain input modalities (e.g., touch inputs), however it should be understood that other input modalities for inputting a scroll command (e.g., via a mechanical button, via a mouse, etc.) may be used. These examples are provided only for the purpose of illustration and are not intended to be limiting.

FIGS. 5A and 5B illustrate an example implementation of the method 300 in which, when one or more sections of the UI are condensed and the condensed section(s) include input fields, the input fields are automatically completed (e.g., as described above).

As shown in FIG. 5A, the apparatus 100 displays a UI (in this example, a UI for a checkout process, which may be provided by an online shopping application for example) having multiple sections 502, 504, 506, namely a delivery address input section 502, a shipping method selection section 504 and a payment selection section 506. Each of the sections 502, 504, 506 includes at least one input field (e.g., a text input field, a selection button, etc.) requiring using input. As shown in FIG. 5A, a swipe gesture 510 is detected as touch input, which is processed as a signal corresponding to an input command to scroll the UI at a first scrolling rate 520 as indicated in FIG. 5B (e.g., the first scrolling rate may be based on the detected parameters of the swipe gesture 510). In response to determining that the first scrolling rate 520 exceeds a first threshold, the sections 502, 504, 506 of the UI are condensed as shown in FIG. 5B.

In FIG. 5B, the sections 502, 504, 506 have been condensed (i.e., the condensed size of each of the sections 502, 504, 506 in FIG. 5B occupies a smaller area of the display screen compared to the original size of the corresponding sections 502, 504, 506 in FIG. 5A). In this example, a UI element 508 has been added to the heading of each of the condensed sections 502, 504, 506, which provides a selectable option to expand the condensed section.

The input fields of the delivery address input section 502 has been automatically completed with available user data such as the user's preferred shipping address; the input field of the shipping method selection section 504 has been automatically completed with selection of a default value such as a free shipping option; and the input field payment selection section 506 has been automatically completed with available user data such as selection of a credit card payment and the user's stored credit card number. The data that is used to complete the input fields of the condensed sections 502, 504, 506 may be retrieved from local memory 108 of the apparatus (e.g., the memory 108 may cache data that the user has previously inputted into similar input fields) and/or may be retrieved from an external system such as a network server or a software platform. For example, if the UI is used to complete a checkout transaction on an e-commerce platform, the apparatus 100 may query the e-commerce platform for user data (e.g., preferred shipping address, preferred shipping method, preferred payment method, etc.) stored in a user profile maintained by the platform. The platform may provide the apparatus 100 with the user data in response to the query, which the apparatus 100 may use to automatically complete the input fields of the condensed sections 502, 504, 506.

Condensing of the sections 502, 504, 506 decreases the area occupied by the sections 502, 504, 506 such that other section(s) of the UI may be brought into view. In this example, additional sections 512 and 514 are brought into view, namely a sign-up section 512 and an order summary section 514. Notably, the sign-up section 512 includes an input field (in this example, a checkbox) that cannot be automatically completed (e.g., the user profile does not include information indicating whether the user would like to automatically sign up to newsletters). Thus, the input field of the sign-up section 512 remains incomplete and is not replaced by automatically retrieved data (unlike the sections 502, 504, 506). In some examples, in response to determining that the first scrolling rate 520 exceeds the first threshold, in addition to condensing the sections 502, 504, 506 the UI may also be automatically positioned such that the sign-up section 512 (which is a section having an input field that still requires user input) is positioned in a focus area of the display screen (e.g., in the top half or top third of the display screen, or in a portion of the screen where an eye gaze estimation algorithm has detected the user's gaze to be focused).

Thus, as illustrated by the example of FIGS. 5A and 5B, examples of the present disclosure may simplify a user's interactions with an apparatus 100 by condensing sections of a UI and automatically completing input fields of the condensed sections, in response to a scrolling command. Further, in some examples, the user's attention may be more efficiently drawn to an input field that requires their input. In this way, the limited display screen of the apparatus 100 may be used more efficiently, and the number of user interactions (and the use of computer resources required to process such interactions) may be reduced.

FIGS. 6A-6C illustrate another example implementation of the method 300 in which, one or more sections of the UI are condensed and expanded proportionate to the scrolling rate of the UI (e.g., as described above). Further, FIGS. 6A-6C illustrate and example in which inertial scrolling is implemented.

As shown in FIG. 6A, the apparatus 100 displays a UI (in this example, a UI for viewing a structured document, such as a “Frequently Asked Questions” page which may be provided by an online website) having multiple sections 602, 604, 606, each corresponding to a respective section of the document (e.g., each corresponding to a respective question). Each of the sections 602, 604, 606 includes a heading (e.g., a question) and text content (e.g., an answer to the question). As shown in FIG. 6A, a swipe gesture 650 is detected as touch input, which is processed as a signal corresponding to an input command to scroll the UI at a first scrolling rate 660 as indicated in FIG. 6B (e.g., the first scrolling rate may be based on the detected parameters of the swipe gesture 650).

The UI is scrolled up, as shown in FIG. 6B, to bring into view lower sections of the UI (which were previously hidden) and higher sections of the UI become hidden. In this example, higher sections 602, 604 which were displayed in FIG. 6A have been scrolled out of view while lower sections 608 to 618 have been scrolled into view. At the same time, in response to determining that the first scrolling rate 660 exceeds a first threshold, the sections 606 to 618 of the UI are condensed.

In this example, the first scrolling rate 660 is at a sufficiently high rate (e.g., the scrolling rate 660 exceeds the first threshold by a large amount; or the scrolling rate