WO2017174989A1

WO2017174989A1 - Dynamic user interfaces in a data processing system

Info

Publication number: WO2017174989A1
Application number: PCT/GB2017/050959
Authority: WO
Inventors: Seema SACHDEV; Raj HUNDAL; Ruchir Rodrigues
Original assignee: Barclays Bank Plc
Priority date: 2016-04-06
Filing date: 2017-04-06
Publication date: 2017-10-12
Also published as: GB2549126A

Abstract

Systems and methods are described for providing a user interface for devices in a data processing system. The user interface comprises at least one user-operable control element having a plurality of different operating modes, wherein said user-operable control element is configured based on profile data related to the user, to selectively actuate one of said operating modes of said user-operable control element based on a profile characteristic of the user. A control instruction is generated from a portable computing device, by receiving information associated with a tilt angle of the device from one or more sensors and calculating a tilt state of the device, determining that the tilt state of the device is at, or exceeds, a defined tilt threshold, generating, in response to the determination, a control instruction, and transmitting the control instruction to a remote server.

Description

Dynamic User Interfaces in a Data Processing System

Field of the Invention

[0001] This invention relates generally to methods and systems facilitating online interactions by users in a networked system, and more particularly to a graphical user interface (GUI) for computing devices in a data processing system.

Background

[0002] Systems for facilitating online interactions by users using computing devices in a networked system are generally known. What is desired is a system facilitating intuitive, flexible, configurable and user-appropriate GUI for mobile devices in a data processing system, particularly devices that are associated with defined parent-child relationships.

Summary of the Invention

[0003] Aspects of the present invention are set out in the accompanying claims.

[0004] According to one aspect, the present invention provides a method of providing a user interface comprising at least one user-operable control element having a plurality of different operating modes, wherein one of said operating modes is selectively actuated for the or each user-operable control element based on a determined characteristic of the user.

[0005] In another aspect, the present invention provides a method of generating a transaction instruction from a portable computing device, comprising receiving information associated with a tilt angle of the device from one or more sensors and calculating a tilt state of the device, determining that the tilt state of the device is at, or exceeds, a defined tilt threshold, generating, in response to the determination, a control instruction, and transmitting the control instruction to a remote server.

[0006] In other aspects, there are provided systems and apparatus configured to perform the methods as described above. In a further aspect, there is provided a computer program comprising machine readable instructions stored thereon arranged to cause a programmable device to perform the methods as described above. Brief Description of the Drawings

[0007] There now follows, by way of example only, a detailed description of embodiments of the present invention, with references to the figures identified below.

[0008] Figure 1 is a block diagram showing the main components of a monetary value transfer system according to embodiments of the invention.

[0009] Figure 2 is a block diagram of an example of a mobile device on which one or more of the functions of the embodiments may be implemented.

[0010] Figure 3, which comprises Figures 3A to 3B, is a flow diagram illustrating the main processing steps performed by the system of Figure 1 to facilitate GUI configuration according to an embodiment.

[0011] Figure 4, which comprises Figures 4A to 4F, schematically illustrates an exemplary sequence of display screens output by the parent mobile device during the process of Figure 3.

[0012] Figure 5, which comprises Figures 5A to 5D, schematically illustrates an exemplary plurality of display screens of varying GUI complexities, as output by the child mobile device.

[0013] Figure 6 is a flow diagram illustrating the main processing steps performed by the system of Figure 1 to process a transaction in response to gesture-based control according to an embodiment.

[0014] Figure 7, which comprises Figures 7A to 7E, schematically illustrates an exemplary sequence of display screens output by the parent and child mobile devices during the process of Figure 6.

[0015] Figure 8 is a block diagram of an example of a computer system on which one or more of the functions of components in the system of Figure 1 may be implemented. Description of Embodiments

[0016] Figure 1 shows a system 1 including a data processing server 3 configured to facilitate a transfer of monetary value between a parent user and an associated child user using respective mobile computing devices 5, 7, according to an embodiment of the present invention. In this embodiment, the parent user and associated child user are registered with the server 3 and a respective account 9a, 9b is established for each user on the server 3. The child account 9b may be a sub-account of the parent account 9a, or may be a separate account 9b that is linked to the parent account 9a. The parent account 9a may be associated with a plurality of child accounts 9b. The account data may be stored in one or more secure databases 11 accessible by the server 3. User information for the registered users may include user identifiers (e.g. name, e-mail address, mobile device number, address, etc.), transaction records, account balance, security data, etc. In this embodiment, the child account 9b also includes profile data 13, such as the child's date of birth, parental control settings (e.g. configurable transaction limits), savings goals, task lists, etc. The profile data 13 may instead be stored as a linked profile account separate from the parent and child accounts 9a, 9b.

[0017] The parent and child mobile devices 5, 7 may be any suitable portable electronic device such as a cellular device, a smartphone, a tablet computer, etc. that includes software and/or hardware components to communicate with the server 3 over a data network 15. The parent and child mobile devices 5, 7 include respective mobile applications 17 to provide access functionality to the respective accounts 9, including electronic value transfer functionality as described below. The mobile applications 17 may also include electronic wallet functionality to initiate mobile payments using an associated account. The mobile applications 11 may be secured to operate in one of a parent- or child- mode by an authorised user, for example by verifying a corresponding secret PIN or passcode set up by the parent user during a registration process. In this exemplary embodiment, the parent account 9a is associated with the parent mobile application 17a and the child account 9b is associated with the child mobile application 17b, for example during the registration process in which the parent-user verifies that they are authorised to access the parent account 9a, and the parent and/or child user verifies that they are authorised to access the child account 9b. The parent mobile device 3 runs the mobile application 11a in the parent-mode that enables the parent user to receive and configure the profile data 13 of the associated child account 9b and to generate an instruction for a value transfer transaction, in communication with a mobile application gateway 19 of the server 3. The server 3 processes requests to retrieve and modify account data 9 via an account configuration system 21, and initiates the value transfer transaction via a transaction processing system 23 to debit the parent account 15a and credit the associated child account 15b. The transaction processing system 23 may be of a conventional type, and will not be described further. The value transfer transaction may be conducted while the devices are connected (online) or disconnected (offline) from other system components.

[0018] In an embodiment, the parent mobile device 5 includes one or more tilt sensors 31 (also commonly referred to as accelerometers or orientation sensors), to detect and track the movements of the mobile device 5. The mobile application 17a running in parent-mode may be configured to determine that a predefined movement pattern or gesture (e.g. a tilt down) of the device 5 is performed as an input command for the mobile application to initiate the value transfer transaction. The tilt sensors 31 may be of a conventional type, and will not be described further.

[0019] In an embodiment, the mobile applications 17 are configured to dynamically determine and display a graphical user interface (GUI) in the child-mode based on the child's profile data 13 retrieved from the child account 9b, as described below. The mobile applications 17 include a database storing a plurality of predefined default profiles 25, each default profile 25 defining a respective plurality of predefined user interface (Ul) control elements 27 and default values or parameters for an associated Ul level or state 29. The individual Ul control elements 27 may include interactive GUI entities corresponding to features and functionality associated with the child account 9b. The default profiles 25 may be stored at the server 3 and retrieved by the mobile applications 17 via the data network 15.

[0020] The parent mobile device 3 and the child mobile device 5 may each comprise a mobile device as shown in Figure 2, including a network interface 33 for communication with the data network 15, a contactless (e.g. Bluetooth ( TM), Near-Field Communication (NFC), etc.) communication interface 34 for communication with a corresponding contactless communication terminal (not shown), and a processor 35 for running applications such as the secure mobile application 17. Data 37, such as the default profile database 25, may be stored in memory 39. The user may interact with the mobile device via an input device 41 and a display 43 (which may be a touchscreen device). Additional components may be included, such as a microphone, a speaker, a camera and/or a GPS receiver etc., which are not shown.

GUI Configuration Process

[0021] Figure 3 shows a computer-implemented GUI configuration process of the present embodiment, using the parent mobile device 5, in the context of a journey during which the parent device automatically determines that a more complex GUI can be applied to the associated child's device based on the child's profile data. Reference is also made to Figure 4, which comprises Figures 4A to 4F, schematically illustrating exemplary display screens output by the mobile application 17a of the parent mobile device 5 during this configuration process.

[0022] As shown in Figure 3, the process begins at step S3-1 where the parent mobile device 5, running the mobile application 17a in the parent-mode, verifies the parent user's identity. For example, the parent-user may be prompted to input their secret PIN or passcode that was created during the app registration process. The mobile application 17 may be configured to allow selection of one of a plurality of registered users for verification and use in the corresponding mode of operation. At step S3-3, the parent mobile device 5 transmits a request to the server 3 for the stored profile data 13 from the (or each) child account 9b associated with the parent account 9a of the parent mobile device 5. The request may include data identifying the child account 9b. At step S3-5, the account configuration system 21 receives the data request via the mobile application gateway 19, and in response, retrieves the child's profile data 13 from the account database 11, and transmits the retrieved profile data 13 to the parent mobile device 5. In this embodiment, the profile data 13 includes the child's date of birth, for example as provided during the account registration process, and a current Ul level assigned to the child account 9b based on the child's age. An exemplary predefined scale of Ul levels and associated target age ranges is set out in the table below:

[0023] At step S3-7, the parent mobile device 5 automatically determines that the current Ul level assigned to the child account 9b can be changed (e.g. increased to the next Ul level), based on the child's profile data 13. For example, the mobile application 17a may determine the child's current age from the date of birth in the profile data 13 compared to the current date, and identify the appropriate Ul level for that child's age from the predefined scale. When it is determined that the Ul level can be changed, then at step S3-9, the parent mobile device 5 outputs a prompt for the parent-user to manage the child's profile data 13. For example, Figure 4A shows a display screen 51a that is displayed by the mobile application 17a running in the parent-mode, including an app notification or alert 53a, and a text prompt 53b adjacent a Ul control element (e.g. a button) 55 that is selectable by the user to access the manage profile functionality. At step S3-11, the parent mobile device 5 receives user input to access the manage profile functionality of the mobile application 17a. Figures 4B and 4C show a subsequent display screen 51b that is displayed by the mobile application 17a in response to user input to access the manage profile functionality, including information 57 on the recommended next Ul level for the child, as well as the current set of parent-mode control elements 59-1 corresponding to configured features and functionality available to the child mobile device 7 according to the current Ul level assigned to the child account 9b (Stage 2B in the illustrated example). Optionally, the parent mobile device 5 may be configured to output a preview 61 of the next Ul level applied to the child account 9b and an additional button for the user to confirm the change, for example as shown in Figure 4D.

[0024] At step S3-13, the parent mobile device 5 receives user input to confirm the change to the new Ul level and in response, transmits data identifying the new Ul level to the server 3, at step S3-15. At step S3-17, the account configuration system 21 receives the data identifying the new Ul level from the mobile application 17a via the mobile application gateway 19 and updates the Ul level stored in the child's profile data 13. At step S3-19, the parent mobile device 5 retrieves the Ul control elements 27 predefined for the new Ul level 29, from the default profiles database 25. An example hierarchy of Ul levels with associated features/functionality, options, parameters, settings, operating modes and default Ul control elements is set out below, corresponding to the above scale of Ul levels. The child's profile data 13 includes data identifying the configured options, parameters, settings and/or operating modes for the Ul control elements of the Ul level assigned to the child.

[0025]

Feature/Functionalitv Stage 1

View Balance • Virtual representation of account balance based on transaction record

Spending • Not Available

Rewards • Virtual sticker book/chart for predefined and/or parent- user defined tasks

Feature/Functionalitv Stage 2A

View Balance • Virtual representation of account balance based on

transaction record

Spending • Not Available

Saving Goals • Multiple goals (up to 3)

• Progress bar of saved amount against goal

Chores • List of predefined and/or parent-user defined tasks with complete/incomplete status, and associated reward value

• Allow interaction to complete a listed task Feature/Functionalitv Stage 2B

View Balance • Detailed virtual representation of account balance,

consisting individual coin tokens with numerical denominations, based on transaction record

Spending • Take cash via parent

• Daily limit (£20)

Saving Goals • Multiple goals (up to 5)

• Progress bar of saved amount against goal

• Allow interaction to add coin tokens (monetary value)

against each goal

• Create new goal

• Allow interaction to complete a listed task

• Send image/photo of completed chore for parent to

review and approve via parent device

Feature/Functionalitv Stage 3

View Balance • Text-based account balance

• Account summary and transaction record

• Linked card balance and/or available credit

Spending • Take cash via parent

• Daily limit (£50)

• Add prepaid card

Saving Goals • Multiple goals (no limit)

• Progress bar of saved amount against goal

• Allow interaction to add and withdraw monetary value

against each goal

• Create new goal

• Allow interaction to complete a listed task

• Send image/photo of completed chore for parent to

review and approve via parent device

[0026] At step S3-21, the parent mobile device 5 configures the retrieved Ul control elements 27 based on the child's profile data 13. For example, a user-operable control panel may be defined for the saving goals functionality, the panel having different operating modes corresponding to the Ul levels set out above. One of the operating modes is selectively actuated for the control panel, in this instance based on new Ul level, and individual Ul components of the control panel may be configured based on profile data 13 related to the child's saving goals. At step S3-23, the parent mobile device 5 outputs the user interface with the configured Ul control elements 27 to the display 43. Figures 4E and 4F show a subsequent display screen 51c that is displayed by the mobile application 17a in response to user input to access the manage profile functionality, including a notification 65 that a new Ul level is set for the child, with the default set of parent-mode control elements 59-2 corresponding to default features and functionality available to the child mobile device 7 according to the new Ul level (Stage 3 in the illustrated example). As shown in Figure 4F, a greater number of parent-mode control elements 59-2 are available to the parent user for the child's new Ul level compared to the previous display screen 51b shown in Figure 4C, in order to facilitate configuration of the corresponding child-mode control elements and parameters that will be applied to the child mobile device 7.

[0027] At step S3-25, the parent mobile device 5 may receive parent user input to modify the child's profile data using one or more of the configured Ul control elements. For example, the parent user may configure, toggle and/or override the default options, parameters, settings and/or operating modes for one or more of the Ul control elements 27 of the assigned Ul level 29. At step S3-27, the parent mobile device 5 may transmit the child's updated profile data 13, including all of the configuration changes from step S3-25, back to the server 3. The parent mobile device 5 may instead be configured to transmit data identifying changes to the profile data 13 as received from the server at step S3-5. At step S3-29, the account configuration system 21 receives the updated profile data 13 from the parent mobile device 5 via the mobile application gateway 19, and stores/updates the profile data 13 in the child account 13 to complete the configuration process.

[0028] The server 3 subsequently responds to an access request from the child mobile device 7 running the mobile application 17b in the child-mode, by retrieving and transmitting the child's profile data 13 to the child mobile device 7 at step S3-31. At step S3-33, the child mobile device 7 retrieves data identifying the assigned Ul level from the received profile data 13. At step S3-35, the child mobile device 7 retrieves the Ul control elements 27 that are predefined for the assigned Ul level 29, from the default profiles database 25, similar to step S3-19 above. At step S3-37, the child mobile device 7 configures the retrieved Ul control elements 27 based on the child's profile data 13, similar to step S3-21 above. At step S3-39, the child mobile device 7 outputs the user interface with the configured Ul control elements 27 to the display 43.

[0029] Figure 5, which comprises Figures 5A to 5D, shows exemplary display screens 71 of varying interaction complexity corresponding to the exemplary scale of Ul levels described above, as output by the mobile application 17 in the child-mode. For example, Figure 5A shows a display screen 71a corresponding to Stage 1, including a first button 73a to access the virtual representation of the child's account balance consisting individual user-selectable coin tokens based on transaction record (e.g. a virtual inside view of a piggy bank/money box), and a second button 75a to access the virtual sticker book/chart. Figure 5B shows a display screen 71b corresponding to Stage 2A, including the inside view of the virtual representation of the child's account balance consisting the individual user-selectable coin tokens based on transaction record, a savings goal panel 75b including a progress bar indicating the saved amount against the target for a particular savings goal, and a button or panel 77a to access the interactive task list. Figure 5C shows a display screen 71c corresponding to Stage 2B, including a dynamic rendered view of the child's account balance, consisting individual user-selectable coin tokens with numerical denominations, based on transaction record, a similar savings goal panel 75c including a progress bar indicating the saved amount against the target for each of a plurality of savings goals and further including a first button 79a to allow the child-user to add monetary value to a particular savings goal, and a second button 81a to allow the child-user to add details of a new savings goal. The display screen 71c also includes a button or panel 77b to access the interactive task list with the Ul control elements and configured parameters for Stage 2B. Figure 5D shows a display screen 71d corresponding to Stage 3, including an account balance panel 73d with the text-based account balance, a link to view account summary and transaction record details, and the balance against limit of a linked prepaid card. The display screen 71d also includes a savings goal panel 75d and a button or panel 77c to access the interactive task list, with the Ul control elements and configured parameters for Stage 3.

[0030] In this way, the electronic value exchange system 1 is configured to efficiently, dynamically and effectively facilitate control of a mobile device in a defined parent-child relationship to generate and output a flexible, configurable and user-appropriate GUI. The child user interface may include one or more user-selectable control element having a plurality of different default operating modes, whereby the system is configured to dynamically and efficiently actuate a selected one of the operating modes for the or each user-operable control element, based on a determined characteristic of the user. Gesture Control

[0031] Figure 6 shows a computer-implemented gesture-based control process of the present embodiment, using the parent mobile device 5, in the context of a journey during which the parent mobile device 5 is used to initiate a transfer of monetary value from the parent account 9a to a child account 9b associated with a child mobile device 7. Reference is also made to Figure 7, which comprises Figures 7A to 7E, schematically illustrating exemplary display screens output by the mobile application 17 of the mobile devices 5,7 during this control process.

[0032] As shown in Figure 6, the process begins at step S6-1 where the parent mobile device 5, running the mobile application 17a in the parent-mode, receives user input to initiate a new transaction between the nominated parent account 9a and the associated child account 9b. For example, referring to the example home display screen 51a of the associated child shown in Figure 4A, the parent user may select a button 91 on the display screen 51a, to initiate the transaction functionality of the present embodiment. At step S6-3, the parent mobile device 5 prompts the user to input details of the transaction, in this example a monetary value to be transferred from the nominated parent account 9a to the associated child account 9b. Figure 7A shows an exemplary display screen 93 illustrating a child-friendly input panel 95 consisting of user-selectable virtual representations of a plurality of coin denominations. In this way, the child user may observe the parent user accumulating the input amount 97 to be transferred, in representations of real-world units 99 of the monetary value 97, for example as shown in Figure 7B.

[0033] At step S6-5, the parent mobile device 5 determines if the predefined movement pattern or gesture is performed as an input gesture command for the mobile application 17a to initiate the value transfer transaction. For example, the predefined gesture may be a tilt down of the device 5 from the upright/viewing orientation past a defined tilting angle. The parent mobile device 5 may be configured to wait for the input gesture command within a predefined time period. In response to determining that the input gesture command is received, the parent mobile device 5 generates a control message including data defining a transaction instruction to transfer the defined amount to the identified child account, at step S6-7. The control message also includes data defining the constituent monetary units as input by the parent user. The parent mobile device 5 may generate and output a dynamic animation sequence 101 of virtual representations of the constituent monetary units of the transferred amount falling off the display screen along the detected tilt angle, for example as shown in Figure 7C. At step S6-9, the parent mobile device 5 transmits the generated control message to the server 3.

[0034] At step S6-11, the transaction processing system 23 of the server 3 receives the control message from the parent mobile device 5 via the mobile application gateway 19, and identifies the transaction instruction and details (e.g. amount, recipient) from the received data. At step S6-13, the transaction processing system 23 processes the transaction to debit the parent account 15a and credit the associated child account 15b with the identified amount. At step S6-15, the transaction processing system 23 transmits a notification message to the mobile application 17b of the child mobile device 7, including transaction details identifying the completed transaction and the constituent monetary units of the transferred amount. At step S6-17, the child mobile device 7, running the mobile application 17b in the child-mode, identifies the transaction details from the received data and prompts the user to "accept" the transferred monetary value into the child's account, for example as shown in the exemplary display screen 103a of Figure 7D. The mobile application 17b may be running on the child mobile device 7 in a background mode of operation, whereby the mobile application 17b is activated in response to receiving the notification message from the server 3. The child mobile device 7 is also configured to generate and output an animation sequence 105 of virtual representations of the constituent monetary units of the transferred amount falling into the child's virtual piggy bank/money box, for example as shown in the exemplary display screen 103b of Figure 7E.

Computer Systems

[0035] The entities described herein, such as the mobile application gateway 19, account configuration system 21 and transaction processing system 23, may be implemented by one or more computer systems such as computer system 1000 as shown in Figure 8. Embodiments of the present invention may be implemented as programmable code for execution by such computer systems 1000. After reading this description, it will become apparent to a person skilled in the art how to implement the invention using other computer systems and/or computer architectures.

[0036] Computer system 1000 includes one or more processors, such as processor 1004. Processor 1004 may be any type of processor, including but not limited to a special purpose or a general-purpose digital signal processor. Processor 1004 is connected to a communication infrastructure 1006 (for example, a bus or network). Various software implementations are described in terms of this exemplary computer system. After reading this description, it will become apparent to a person skilled in the art how to implement the invention using other computer systems and/or computer architectures.

[0037] Computer system 1000 also includes a user input interface 1003 connected to one or more input device(s) 1005 and a display interface 1007 connected to one or more display(s) 1009. Input devices 1005 may include, for example, a pointing device such as a mouse or touchpad, a keyboard, a touchscreen such as a resistive or capacitive touchscreen, etc. After reading this description, it will become apparent to a person skilled in the art how to implement the invention using other computer systems and/or computer architectures, for example using mobile electronic devices with integrated input and display components.

[0038] Computer system 1000 also includes a main memory 1008, preferably random access memory (RAM), and may also include a secondary memory 610. Secondary memory 1010 may include, for example, a hard disk drive 1012 and/or a removable storage drive 1014, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. Removable storage drive 1014 reads from and/or writes to a removable storage unit 1018 in a well-known manner. Removable storage unit 1018 represents a floppy disk, magnetic tape, optical disk, etc., which is read by and written to by removable storage drive 1014. As will be appreciated, removable storage unit 1018 includes a computer usable storage medium having stored therein computer software and/or data.

[0039] In alternative implementations, secondary memory 1010 may include other similar means for allowing computer programs or other instructions to be loaded into computer system 1000. Such means may include, for example, a removable storage unit 1022 and an interface 1020. Examples of such means may include a program cartridge and cartridge interface (such as that previously found in video game devices), a removable memory chip (such as an EPROM, or PROM, or flash memory) and associated socket, and other removable storage units 1022 and interfaces 1020 which allow software and data to be transferred from removable storage unit 1022 to computer system 1000. Alternatively, the program may be executed and/or the data accessed from the removable storage unit 1022, using the processor 1004 of the computer system 1000.

[0040] Computer system 1000 may also include a communication interface 1024. Communication interface 1024 allows software and data to be transferred between computer system 1000 and external devices. Examples of communication interface 1024 may include a modem, a network interface (such as an Ethernet card), a communication port, a Personal Computer Memory Card International Association (PCMCIA) slot and card, etc. Software and data transferred via communication interface 1024 are in the form of signals 1028, which may be electronic, electromagnetic, optical, or other signals capable of being received by communication interface 1024. These signals 1028 are provided to communication interface 1024 via a communication path 1026. Communication path 1026 carries signals 1028 and may be implemented using wire or cable, fibre optics, a phone line, a wireless link, a cellular phone link, a radio frequency link, or any other suitable communication channel. For instance, communication path 1026 may be implemented using a combination of channels.

[0041] The terms "computer program medium" and "computer usable medium" are used generally to refer to media such as removable storage drive 1014, a hard disk installed in hard disk drive 1012, and signals 1028. These computer program products are means for providing software to computer system 1000. However, these terms may also include signals (such as electrical, optical or electromagnetic signals) that embody the computer program disclosed herein.

[0042] Computer programs (also called computer control logic) are stored in main memory 1008 and/or secondary memory 1010. Computer programs may also be received via communication interface 1024. Such computer programs, when executed, enable computer system 1000 to implement embodiments of the present invention as discussed herein. Accordingly, such computer programs represent controllers of computer system 1000. Where the embodiment is implemented using software, the software may be stored in a computer program product 1030 and loaded into computer system 1000 using removable storage drive 1014, hard disk drive 1012, or communication interface 1024, to provide some examples.

[0043] Alternative embodiments may be implemented as control logic in hardware, firmware, or software or any combination thereof.

Alternative Embodiments

[0044] It will be understood that embodiments of the present invention are described herein by way of example only, and that various changes and modifications may be made without departing from the scope of the invention.

[0045] For example, in the embodiments described above, the data processing server includes the transaction processing system and the account configuration system. It will be appreciated that the transaction processing system may be implemented as a separate server from the account configuration system, communicatively coupled via the data network.

[0046] Reference in this specification to "an embodiment" are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. In particular, it will be appreciated that aspects of the above discussed embodiments can be combined to form further embodiments. Similarly, various features are described which may be exhibited by some embodiments and not by others. Yet further alternative embodiments may be envisaged, which nevertheless fall within the scope of the following claims.

Claims

1. A method of providing a user interface comprising at least one user-operable control element having a plurality of different operating modes, wherein said user- operable control element is configured based on profile data related to the user, to selectively actuate one of said operating modes of said user-operable control element based on a profile characteristic of the user.

2. The method of claim 1, wherein the characteristic is a computed age of the user.

3. The method of claim 1 or 2, wherein data defining the plurality of operating modes for the or each user-operable control element is stored in a database.

4. The method of claim 3, wherein the database stores data defining a predefined default configuration of the or each user-operable control element, and wherein the default configuration is modified based on retrieved profile data related to the user.

5. The method of any preceding claim, wherein the user interface is generated and output by a mobile device.

6. The method of any preceding claim, further comprising storing data defining a control state of the second device, which control state defining said selectively actuated operating mode for the or each user-operable control element, wherein said control state is configurable by the first device.

7. The method of any preceding claim, wherein the data defining a control state of the second device is stored in a remote database.

8. The method of any preceding claim, further comprising storing data defining a parent-child relationship between first and second mobile devices.

9. The method of any preceding claim, wherein the first mobile device is associated with a parent account and the second mobile device is associated with a child sub-account of the parent account.

10. A method of generating a control instruction from a portable computing device, comprising:

receiving information associated with a tilt angle of the device from one or more sensors and calculating a tilt state of the device;

determining that the tilt state of the device is at, or exceeds, a defined tilt threshold;

generating, in response to the determination, a control instruction; and transmitting the control instruction to a remote server.

11. The method of claim 10, further comprising generating and outputting dynamic feedback in response to the calculated tilt state of the device.

12. A system comprising means for performing the method of any one of claims 1 to 11.

13. A storage medium comprising machine readable instructions stored thereon for causing a computer system to perform a method in accordance with any one of clai ms l to ll.