Electronic messaging platform that allows users to change the content and attachments of messages after sending

CROSS-REFERENCE TO RELATED APPLICATIONS

0001This application is a continuation of U.S. application Ser. No. 16/384,285, filed Apr. 15, 2019, issuing as U.S. Pat. No. 10,791,083, which is a continuation of U.S. application Ser. No. 15/232,567, filed Aug. 9, 2016, now U.S. Pat. No. 10,291,568. The prior applications are incorporated by reference herein.

FIELD

0002This disclosure is directed to electronic messaging, as well as related devices, systems, and methods.

BACKGROUND

0003Electronic messaging such as email, instant messages, text messages, etc. have become commonplace. Electronic messaging is used, for example, for communicating personal and/or business information. Despite its advantages, electronic messaging has shortcomings which can adversely affect communication and relationships.

SUMMARY

0004Examples described herein relate to managing and/or editing sent electronic messages, as well as related devices, systems, and methods.

0005In one example, a system for editing an electronic message comprises at least one processor, and an application configured to, by the at least one processor, send an electronic message from a sender to a recipient, edit the message after it has been sent to the recipient to create an edited message, retain a relative location of the message in the recipient's inbox while the edited message is created, send the edited message from the sender to the recipient, and place the edited message in the relative location of the message in the recipient's inbox.

0006In some examples, the application is further configured to edit the message by adding at least one attachment to or by removing at least one attachment from the message. In some examples, the application is further configured to edit the message by adding at least one additional recipient to the message. In some examples, the application is further configured to edit the message by editing a subject line of the message.

0007In some examples, the application is further configured to display information about the recipient while the sender is composing, editing, or replying to the message. In some of those examples, the information about the recipient comprises personal information about the recipient. In other such examples, the information about the recipient comprises notes about the recipient that were previously entered by the sender. In other such examples, the information about the recipient comprises information about past or upcoming meetings between the sender and the recipient.

0008In some examples, the application is a messaging application on a smartphone. In some examples, the application is a messaging application on a computer.

0009In another example, a method of editing an electronic message is provided. The method comprises sending an electronic message from a first device of a first user to a second user, editing the message from a second device of the first user, and sending the edited message from the second device of the first user to the second user.

0010In some examples, editing the message includes adding at least one attachment to or removing at least one attachment from the message. In other examples, editing the message includes adding at least one additional recipient to the message.

0011In some examples, the first device is a computer, and the second device is a smartphone. In other examples, the first device is a smartphone, and the second device is a computer. In some examples, the message is an email message.

0012In another example, one or more computer-readable storage media storing computer-executable instructions for editing an electronic message is provided. The computer-readable storage comprises instructions for sending a message from a sender to a recipient, instructions for editing the message after the message has been sent to create an edited message, instructions for retaining a relative location of the message in the recipient's inbox while the edited message is created, instructions for sending the edited message from the sender to the recipient, and instructions for placing the edited message in the relative location of the message in the recipient's inbox.

0013In some examples, the instructions for editing the message include instructions for adding at least one attachment to or removing at least one attachment from the message. In some examples, the instructions for editing the message include instructions for adding at least one recipient to the message. In some examples, the instructions for editing the message include instructions for editing a subject line of the message.

0014The foregoing and other objects, features, and advantages of the invention will become more apparent from the following detailed description, which proceeds with reference to the accompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

0015<figref idref="DRAWINGS">FIG. 1</figref> is a flowchart illustrating an example method of manipulating electronic messages.

0016<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart illustrating an example method of manipulating electronic messages.

0017<figref idref="DRAWINGS">FIGS. 3A-3F</figref> are examples of a user interface demonstrating various features of a system capable of manipulating electronic messages.

0018<figref idref="DRAWINGS">FIG. 4</figref> is a block diagram of an example system capable of manipulating electronic messages.

0019<figref idref="DRAWINGS">FIG. 5</figref> is an example of a user interface demonstrating various features of a system capable of displaying information about a recipient while a user is composing an electronic message.

0020<figref idref="DRAWINGS">FIG. 6</figref> is an example of a user interface demonstrating various features of a system capable of displaying information about events related to a recipient while a user is composing an electronic message.

0021<figref idref="DRAWINGS">FIG. 7</figref> is a diagram of an example computing system in which some described embodiments can be implemented.

0022<figref idref="DRAWINGS">FIG. 8</figref> is an example mobile device that can be used in conjunction with the technologies described herein.

0023<figref idref="DRAWINGS">FIG. 9</figref> is an example cloud-supported environment that can be used in conjunction with the technologies described herein.

DETAILED DESCRIPTION

0000General Considerations

0024This disclosure is set forth in the context of representative embodiments that are not intended to be limiting in any way.

0025As used in this application and in the claims, the singular forms “a,” “an,” and “the” include the plural forms unless the context clearly dictates otherwise. Additionally, the term “includes” means “comprises.”

0026The systems, methods, and apparatus disclosed herein should not be construed as being limiting in any way. Instead, this disclosure is directed toward all novel and non-obvious features and aspects of the various disclosed embodiments, alone and in various combinations and sub-combinations with one another. The disclosed systems, methods, and apparatus are not limited to any specific aspect or feature or combinations thereof, nor do the disclosed systems, methods, and apparatus require that any one or more specific advantages be present or problems be solved. Furthermore, any features or aspects of the disclosed embodiments can be used in various combinations and sub-combinations with one another. Furthermore, as used herein, the term “and/or” means any one item or combination of items in the phrase.

0027Although the operations of some of the disclosed methods are described in a particular, sequential order for convenient presentation, it should be understood that this manner of description encompasses rearrangement, unless a particular ordering is required by specific language set forth below. For example, operations described sequentially may in some cases be rearranged, omitted, or performed concurrently. Moreover, for the sake of simplicity, the attached figures may not show the various ways in which the disclosed systems, methods, and apparatus can be used in conjunction with other systems, methods, and apparatus. Additionally, the description sometimes uses terms like “receive,” “produce,” “identify,” “transform,” “modulate,” “calculate,” “predict,” “evaluate,” “validate,” “apply,” “determine,” “generate,” “associate,” “select,” “search,” and “provide” to describe the disclosed methods. These terms are high-level abstractions of the actual operations that are performed. The actual operations that correspond to these terms can vary depending on the particular implementation and are readily discernible by one of ordinary skill in the art.

0028Some of the disclosed methods can be implemented with computer-executable instructions stored on one or more computer-readable storage media (e.g., non-transitory computer-readable media, such as one or more volatile memory components (such as DRAM or SRAM), or nonvolatile memory components (such as hard drives) and executed on a computer. Any of the computer-executable instructions for implementing the disclosed techniques as well as any data created and used during implementation of the disclosed embodiments can be stored on one or more computer-readable media (e.g., non-transitory computer-readable media). The computer-executable instructions can be part of, for example, a dedicated software application or a software application that is accessed or downloaded via a web browser or other software application (such as a remote computing application). Such software can be executed, for example, on a single local computer (e.g., any suitable commercially-available computer) or in a network environment (e.g., via the Internet, a wide-area network, a local-area network, a client-server network (such as a cloud computing network), or other such network) using one or more network computers.

0029For clarity, only certain selected aspects of the software-based implementations are described. Other details that are well-known in the art are omitted. For example, it should be understood that the disclosed technology is not limited to any specific computer language or program. Likewise, the disclosed technology is not limited to any particular computer or type of hardware. Certain details of suitable computers and hardware are well-known and need not be set forth in detail in this disclosure.

0030Theories of operation, scientific principles, or other theoretical descriptions presented herein in reference to the systems, methods, and apparatus of this disclosure have been provided for the purposes of better understanding and are not intended to be limiting in scope. The systems, methods, and apparatus in the appended claims are not limited to those systems, methods, and apparatus that function in the manner described by such theories of operation.

EXAMPLES

0031Using the systems, methods, and computer-readable media described herein, a user can manipulate (e.g., edit and/or delete) an electronic message sent by the user to a recipient. The user can also determine whether an electronic message has been read by the recipient. Additionally, the user can view information about the recipient (e.g., position, relationship, past and/or upcoming meetings, etc.) while the user is composing the electronic message. These features, as well as others described herein, advantageously allow a user to more accurately, effectively, and efficiently communicate. The features can also reduce mistakes and/or save time, which in turn can reduce stress. Thus, the systems, methods, and computer-readable media described herein and make electronic messaging more enjoyable, efficient, and effective.

0032Electronic messages or messages referred to herein can comprise various formats and/or platforms including email, instant messages (“IM”), text messages (e.g., SMS), and the like. Although examples described herein may refer to a particular platform (e.g., email), the features of the examples can be adapted to one or more other platforms (e.g., IM, text messages, etc.).

0033Examples are described below with reference to <figref idref="DRAWINGS">FIGS. 1-9</figref>.

0034<figref idref="DRAWINGS">FIG. 1</figref> illustrates a method <b>100</b> for manipulating electronic messages. A user can create a message to a recipient by composing a message and/or replying to a message to the user from the recipient. In process block <b>102</b>, the message is delivered from the user to the recipient's “Inbox.” In process block <b>104</b>, the message is displayed, for example, in the user's “Sent” folder. Although not shown in <figref idref="DRAWINGS">FIG. 1</figref>, in other examples, the message can be displayed, for example, in the user's “Sent” folder if the recipient has read the message and/or in the user's “Unread Sent” folder if the recipient has not read the message.

0035The user can select a sent (read and/or unread) message to edit, for example, by clicking or tapping on the message. In process block <b>106</b>, the user input can be received. In process block <b>108</b>, the intent of the user can be determined. For example, it can be determined that the user wants to delete the message. This can be determined, for example, when the user clicks or taps a “Delete” or “Move to trash” icon or button. Upon determining the user's intent to delete the message, the message can be deleted (e.g., removed from the recipient's inbox or other location as though it were never sent), as illustrated in process block <b>110</b>.

0036Alternatively, it can be determined that the user wants to edit the message. This can be determined, for example, when the user clicks or taps an “Edit” or “Revise” icon or button or when the user clicks or taps on the directly on the message such as on the “To” line, the “Subject” line, and/or in the “Body” of the message. Upon determining the user's intent to edit the message, the message can be edited, as illustrated in process block <b>112</b>.

0037Once the message is edited, the user's intent can be determined, as illustrated in process block <b>114</b>. Upon determining that the user's intent is to send the revised or edited message, the message is delivered to the recipient, as illustrated in process block <b>116</b>. The user can repeat the process until satisfied with the message.

0038In some examples, the recipient is not notified of a change to the message. As such, the user can correct mistakes, delete inadvertent messages, etc. without alerting the recipient that such changes have occurred.

0039In some examples (e.g., <figref idref="DRAWINGS">FIG. 1</figref>), the user can edit messages that have been read by the recipient (e.g., messages in a “Sent” folder) and/or messages that have not been read by the recipient (e.g., messages in an “Unread Sent” folder). In other examples (e.g., <figref idref="DRAWINGS">FIG. 2</figref>), a user can only edit messages that has not been read by a recipient (e.g., messages in the “Unread Sent” folder).

0040<figref idref="DRAWINGS">FIG. 2</figref> illustrates a method <b>200</b> for manipulating unread electronic messages. In process block <b>202</b>, a message is delivered from a user to a recipient's inbox. In process block <b>204</b>, a determination of whether the recipient has read the message is made. If the message has been read by the recipient, the message is displayed in the user's “Sent” folder, as illustrated in process block <b>206</b>. If the message has not been read by the recipient, the message is displayed in the user's “Unread Sent” folder, as illustrated by process block <b>208</b>.

0041The user can select an unread sent message to edit, for example, by clicking or tapping on the message. In process block <b>210</b>, the user input can be received. In process block <b>212</b>, the intent of the user can be determined. For example, it can be determined that the user wants to delete the message. This can be determined, for example, when the user clicks or taps a “Delete” or “Move to trash” icon or button. Upon determining the user's intent to delete the message, the message can be deleted (e.g., removed from the recipient's inbox or other location as though it were never sent), as illustrated in process block <b>214</b>.

0042Alternatively, it can be determined that the user wants to edit the message. This can be determined, for example, when the user clicks or taps an “Edit” or “Revise” icon or button or when the user clicks or taps on the directly on the message such as on the “To” line, the “Subject” line, and/or in the “Body” of the message. Upon determining the user's intent to edit the message, the message can be edited, as illustrated in process block <b>214</b>.

0043Once the message is edited, the user's intent can be determined, as illustrated in process block <b>218</b>. Upon determining that the user's intent is to send the revised or edited message, the message is delivered to the recipient, as illustrated in process block <b>220</b>.

0044A message can be manipulated in various ways. For example, a user can delete the message, add recipients (e.g., To, Cc; Bcc; etc.), edit (e.g., delete, change, and/or add) text in the body of the message, and/or add and/or remove attachments.

0045In some examples (e.g., methods <b>100</b>, <b>200</b>), the user's sent folder can show each message that is sent (e.g., each revised message or iteration) even though the recipient's inbox only shows the most recent message. For example, if the user sends a message to a recipient and then edits the message and resends it three additional times, the user's sent folder can display 4 messages (i.e., the original message and three edited messages) and the recipient's inbox will only show one message (i.e., the most recent version of the message). In other examples, the user's sent folder and the recipient's inbox can only display the most recent version of the message.

0046For example, <figref idref="DRAWINGS">FIGS. 3A-3C</figref> illustrate an example user interface <b>300</b>. Referring to <figref idref="DRAWINGS">FIG. 3A</figref>, the user interface <b>300</b> can comprise an “Unread Sent” folder or list <b>302</b> and a message display <b>304</b>. As shown in the folder <b>302</b> and the message display <b>304</b>, User <b>1</b> sent a first message <b>306</b> to User <b>2</b> at 1:01 PM (i.e., displayed as 13:01 in the message display <b>304</b>). The first message <b>306</b> from User <b>1</b> to User <b>2</b> contains a “typo” (i.e., “documents” is incorrectly spelled “documentss”). The first message <b>306</b> also refers to an attachment, but the first message <b>306</b> does not include an attachment. Typical messaging platforms would require User <b>1</b> to send another message (or two) to User <b>2</b> in order to correct the typo and/or include the referenced attachment.

0047The messaging platform described herein, however, advantageously allows User <b>1</b> to edit the first message <b>306</b> to User <b>2</b> without an additional message appearing in User <b>2</b>'s inbox. This can be accomplished, for example, by clicking on the first message <b>306</b>, which allows User <b>1</b> to edit the first message <b>306</b>. User <b>1</b> can then fix the typo and include the referenced attachment. User <b>1</b> can then send a revised, second message <b>308</b> to User <b>2</b>, as shown in <figref idref="DRAWINGS">FIG. 3B</figref>.

0048<figref idref="DRAWINGS">FIG. 3B</figref> shows that in the second message <b>308</b> the typo has been corrected and a first attachment (illustrated as “Attachment_1.pdf” in <figref idref="DRAWINGS">FIG. 3B</figref>) has been included. <figref idref="DRAWINGS">FIG. 3B</figref> also shows that the folder <b>302</b> only has one message from User <b>1</b> to User <b>2</b>. The second message <b>308</b> shows that the message was at 1:01 PM even though it was revised and sent at 1:04 PM as shown by timestamp <b>310</b>. As a result, when User <b>2</b> reads the second message <b>308</b> there is no indication that User <b>1</b> sent the first message <b>306</b>.

0049<figref idref="DRAWINGS">FIG. 3C</figref> shows a third message <b>312</b> which is a revised version of the second message <b>308</b>. Compared to the second message <b>308</b>, the third message <b>312</b> has been edited to change “document” to “documents” in the body of the third message <b>312</b> and to include a second attachment (e.g., illustrated as “Attachment_1.docx” in <figref idref="DRAWINGS">FIG. 3C</figref>). The third message <b>312</b> shows that the message was at 1:01 PM even though it was revised and sent at 1:07 PM as shown by timestamp <b>314</b>.

0050<figref idref="DRAWINGS">FIG. 3D</figref> shows a fourth message <b>316</b> which is separate from and subsequent to the messages <b>306</b>, <b>308</b>, <b>312</b>. For example, the message display <b>304</b> and the timestamp <b>318</b> illustrate that the fourth message <b>316</b> was sent at 1:12 PM.

0051<figref idref="DRAWINGS">FIGS. 3E-3F</figref> illustrates a fifth message <b>320</b> which is a revised version of the third message <b>312</b>. Compared to the third message <b>312</b>, the fifth message <b>320</b> changes the Subject from “Email <b>1</b>” to “Email <b>3</b>” and adds User <b>3</b> as a “To” recipient and User <b>4</b> (<figref idref="DRAWINGS">FIG. 3F</figref>) as a “Cc” recipient. The fifth message <b>320</b> was sent at 1:15 PM as illustrated by timestamp <b>322</b>, but the message <b>320</b> still indicates that the message was sent at 1:01 PM (i.e., the time that the first message <b>306</b> was sent). As also shown in <figref idref="DRAWINGS">FIGS. 3E-3F</figref>, the fifth message <b>320</b> retains the position of the third message <b>312</b> relative to the other messages (e.g., the fourth message <b>316</b>) in the folder <b>302</b>.

0052<figref idref="DRAWINGS">FIG. 4</figref> illustrates a system <b>400</b> configured for composing and/or sending messages as illustrated by process block <b>402</b> and for editing and/deleting messages as illustrated by process block <b>404</b>. The system <b>400</b> can be configured to interact with a plurality of devices (e.g., computers, smartphones, tablets, etc.) and can be configured such that a user can compose and/or send a message from one device (e.g., a computer) and edit and/or delete the message from another device. For example as shown in <figref idref="DRAWINGS">FIG. 4</figref>, User <b>1</b> can use a computer <b>408</b> and/or a smartphone <b>410</b> to compose and/or send a message to User <b>2</b> who can view and/or reply to the message (illustrated in process block <b>406</b>) on a computer <b>412</b>. User <b>1</b> can also use the computer <b>408</b> and/or the smartphone <b>410</b> to edit and/or delete the message to User <b>2</b>. As such, the system <b>400</b> provides significant advantages over typical systems which only allow users to edit a message on the device from which the message was sent.

0053<figref idref="DRAWINGS">FIG. 5</figref> illustrates a user interface <b>500</b>. The user interface <b>500</b> can comprise a message display <b>502</b> and an information display <b>504</b>. The information display <b>504</b> can be displayed when a user is composing, editing, and/or replying to a message. A user can access the information display, for example, by clicking or touching a “Notes” icon or button in the message display <b>502</b>. The information display <b>504</b> can include information and/or notes about a recipient of the message. For example, the notes can include birthday, family information (e.g., names of partner and/or children), anniversary, things to notice, topics to avoid, follow-up topics, topics to always mention, as well as a general notes section.

0054<figref idref="DRAWINGS">FIG. 6</figref> illustrates a user interface <b>600</b>. The user interface <b>600</b> can comprise a message display <b>602</b> and an information display <b>604</b>. The information display <b>604</b> can be displayed when a user is composing, editing, and/or replying to a message. A user can access the information display <b>604</b>, for example, by clicking or touching an “Agenda” icon or button in the message display <b>602</b>. The information display <b>604</b> can include information about previous and/or upcoming events or meetings related to a recipient of the message. For example, the user can enter details about upcoming meetings, and the details can be displayed in the information display <b>604</b>. In particular examples, the information display <b>604</b> can also include other meeting information such as title, start and end date, start and finish time, reoccurrence (e.g., daily, weekly, monthly, yearly), location (which, in some examples, can be integrated with mapping software and/or a mapping service, priority (e.g., very high, high, medium, low), alerts (e.g., at time of the event, 5 minutes before, 30 minutes before, a hour before, a day before, a week before, etc.), description of the meeting, and/or the contacts involved.

0000Computing Systems

0055<figref idref="DRAWINGS">FIG. 7</figref> depicts a generalized example of a suitable computing system <b>700</b> in which the described innovations may be implemented. The computing system <b>700</b> is not intended to suggest any limitation as to scope of use or functionality, as the innovations may be implemented in diverse general-purpose or special-purpose computing systems. For example, the computing devices <b>308</b>, <b>312</b> can be configured similar to the computing system <b>700</b>.

0056With reference to <figref idref="DRAWINGS">FIG. 7</figref>, the computing system <b>700</b> includes one or more processing units <b>710</b>, <b>715</b> and memory <b>720</b>, <b>725</b>. In <figref idref="DRAWINGS">FIG. 7</figref>, this basic configuration <b>730</b> is included within a dashed line. The processing units <b>710</b>, <b>715</b> execute computer-executable instructions. A processing unit can be a general-purpose central processing unit (CPU), processor in an application-specific integrated circuit (ASIC), or any other type of processor. In a multi-processing system, multiple processing units execute computer-executable instructions to increase processing power. For example, <figref idref="DRAWINGS">FIG. 7</figref> shows a central processing unit <b>710</b> as well as a graphics processing unit or co-processing unit <b>715</b>. The tangible memory <b>720</b>, <b>725</b> may be volatile memory (e.g., registers, cache, RAM), non-volatile memory (e.g., ROM, EEPROM, flash memory, etc.), or some combination of the two, accessible by the processing unit(s). The memory <b>720</b>, <b>725</b> stores software <b>780</b> implementing one or more innovations described herein, in the form of computer-executable instructions suitable for execution by the processing unit(s).

0057A computing system may have additional features. For example, the computing system <b>700</b> includes storage <b>740</b>, one or more input devices <b>750</b>, one or more output devices <b>760</b>, and one or more communication connections <b>770</b>. An interconnection mechanism (not shown) such as a bus, controller, or network interconnects the components of the computing system <b>700</b>. Typically, operating system software (not shown) provides an operating environment for other software executing in the computing system <b>700</b>, and coordinates activities of the components of the computing system <b>700</b>.

0058The tangible storage <b>740</b> may be removable or non-removable, and includes magnetic disks, magnetic tapes or cassettes, CD-ROMs, DVDs, or any other medium which can be used to store information and which can be accessed within the computing system <b>700</b>. The storage <b>740</b> stores instructions for the software <b>780</b> implementing one or more innovations described herein.

0059The input device(s) <b>750</b> may be a touch input device such as a keyboard, mouse, pen, or trackball, a voice input device, a scanning device, or another device that provides input to the computing system <b>700</b>. For video encoding, the input device(s) <b>750</b> may be a camera, video card, TV tuner card, or similar device that accepts video input in analog or digital form, or a CD-ROM or CD-RW that reads video samples into the computing system <b>700</b>. The output device(s) <b>760</b> may be a display, printer, speaker, CD-writer, or another device that provides output from the computing system <b>700</b>.

0060The communication connection(s) <b>770</b> enable communication over a communication medium to another computing entity. The communication medium conveys information such as computer-executable instructions, audio or video input or output, or other data in a modulated data signal. A modulated data signal is a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media can use an electrical, optical, RF, or other carrier.

0061The innovations can be described in the general context of computer-executable instructions, such as those included in program modules, being executed in a computing system on a target real or virtual processor. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Computer-executable instructions for program modules may be executed within a local or distributed computing system.

0062The terms “system” and “device” are used interchangeably herein. Unless the context clearly indicates otherwise, neither term implies any limitation on a type of computing system or computing device. In general, a computing system or computing device can be local or distributed, and can include any combination of special-purpose hardware and/or general-purpose hardware with software implementing the functionality described herein.

0063For the sake of presentation, the detailed description uses terms like “determine” and “use” to describe computer operations in a computing system. These terms are high-level abstractions for operations performed by a computer, and should not be confused with acts performed by a human being. The actual computer operations corresponding to these terms vary depending on implementation.

0000Mobile Device

0064<figref idref="DRAWINGS">FIG. 8</figref> illustrates a generalized an example of a mobile device <b>800</b> in which the described innovations may be implemented. For example, the smartphone <b>310</b> can be configured similar to the mobile device <b>800</b>.

0065The mobile device <b>800</b> can include a variety of optional hardware and software components, shown generally at <b>802</b>. Any components <b>802</b> in the mobile device can communicate with any other component, although not all connections are shown, for ease of illustration. The mobile device can be any of a variety of computing devices (e.g., cell phone, smartphone, handheld computer, Personal Digital Assistant (PDA), etc.) and can allow wireless two-way communications with one or more mobile communications networks <b>804</b>, such as a cellular, satellite, or other network.

0066The illustrated mobile device <b>800</b> can include a controller or processor <b>810</b> (e.g., signal processor, microprocessor, ASIC, or other control and processing logic circuitry) for performing such tasks as signal coding, data processing, input/output processing, power control, and/or other functions. An operating system <b>812</b> can control the allocation and usage of the components <b>802</b> and support for one or more application programs <b>814</b>. The application programs can include common mobile computing applications (e.g., email applications, calendars, contact managers, web browsers, messaging applications), or any other computing application. Functionality <b>813</b> for accessing an application store can also be used for acquiring and updating application programs <b>814</b>.

0067The illustrated mobile device <b>800</b> can include memory <b>820</b>. Memory <b>820</b> can include non-removable memory <b>822</b> and/or removable memory <b>824</b>. The non-removable memory <b>822</b> can include RAM, ROM, flash memory, a hard disk, or other well-known memory storage technologies. The removable memory <b>824</b> can include flash memory or a Subscriber Identity Module (SIM) card, which is well known in GSM communication systems, or other well-known memory storage technologies, such as “smart cards.” The memory <b>820</b> can be used for storing data and/or code for running the operating system <b>812</b> and the applications <b>814</b>. Example data can include web pages, text, images, sound files, video data, or other data sets to be sent to and/or received from one or more network servers or other devices via one or more wired or wireless networks. The memory <b>820</b> can be used to store a subscriber identifier, such as an International Mobile Subscriber Identity (IMSI), and an equipment identifier, such as an International Mobile Equipment Identifier (IMEI). Such identifiers can be transmitted to a network server to identify users and equipment.

0068The mobile device <b>800</b> can support one or more input devices <b>830</b>, such as a touchscreen <b>832</b>, microphone <b>834</b>, camera <b>836</b>, physical keyboard <b>838</b> and/or trackball <b>840</b> and one or more output devices <b>850</b>, such as a speaker <b>852</b> and a display <b>854</b>. Other possible output devices (not shown) can include piezoelectric or other haptic output devices. Some devices can serve more than one input/output function. For example, touchscreen <b>832</b> and display <b>854</b> can be combined in a single input/output device.

0069The input devices <b>830</b> can include a Natural User Interface (NUI). An NUI is any interface technology that enables a user to interact with a device in a “natural” manner, free from artificial constraints imposed by input devices such as mice, keyboards, remote controls, and the like. Examples of NUI methods include those relying on speech recognition, touch and stylus recognition, gesture recognition both on screen and adjacent to the screen, air gestures, head and eye tracking, voice and speech, vision, touch, gestures, and machine intelligence. Other examples of a NUI include motion gesture detection using accelerometers/gyroscopes, facial recognition, 3D displays, head, eye, and gaze tracking, immersive augmented reality and virtual reality systems, all of which provide a more natural interface, as well as technologies for sensing brain activity using electric field sensing electrodes (EEG and related methods). Thus, in one specific example, the operating system <b>812</b> or applications <b>814</b> can comprise speech-recognition software as part of a voice user interface that allows a user to operate the device <b>800</b> via voice commands. Further, the device <b>800</b> can comprise input devices and software that allows for user interaction via a user's spatial gestures, such as detecting and interpreting gestures to provide input to a gaming application.

0070A wireless modem <b>860</b> can be coupled to an antenna (not shown) and can support two-way communications between the processor <b>810</b> and external devices, as is well understood in the art. The modem <b>860</b> is shown generically and can include a cellular modem for communicating with the mobile communication network <b>804</b> and/or other radio-based modems (e.g., Bluetooth <b>864</b> or Wi-Fi <b>862</b>). The wireless modem <b>860</b> is typically configured for communication with one or more cellular networks, such as a GSM network for data and voice communications within a single cellular network, between cellular networks, or between the mobile device and a public switched telephone network (PSTN).

0071The mobile device can further include at least one input/output port <b>880</b>, a power supply <b>882</b>, a satellite navigation system receiver <b>884</b>, such as a Global Positioning System (GPS) receiver, an accelerometer <b>886</b>, and/or a physical connector <b>890</b>, which can be a USB port, IEEE 1394 (FireWire) port, and/or RS-232 port. The illustrated components <b>802</b> are not required or all-inclusive, as any components can be deleted and other components can be added.

0000Cloud-Supported Environment

0072<figref idref="DRAWINGS">FIG. 9</figref> illustrates a generalized example of a suitable cloud-supported environment <b>900</b> in which described embodiments, techniques, and technologies may be implemented. In the example environment <b>900</b>, various types of services (e.g., computing services) are provided by a cloud <b>910</b>. For example, the cloud <b>910</b> can comprise a collection of computing devices, which may be located centrally or distributed, that provide cloud-based services to various types of users and devices connected via a network such as the Internet. The implementation environment <b>900</b> can be used in different ways to accomplish computing tasks. For example, some tasks (e.g., processing user input and presenting a user interface) can be performed on local computing devices (e.g., connected devices <b>930</b>, <b>940</b>, <b>950</b>) while other tasks (e.g., storage of data to be used in subsequent processing) can be performed in the cloud <b>910</b>.

0073In example environment <b>900</b>, the cloud <b>910</b> provides services for connected devices <b>930</b>, <b>940</b>, <b>950</b> with a variety of screen capabilities. Connected device <b>930</b> represents a device with a computer screen <b>935</b> (e.g., a mid-size screen). For example, connected device <b>930</b> could be a personal computer such as desktop computer, laptop, notebook, netbook, or the like. Connected device <b>940</b> represents a device with a mobile device screen <b>945</b> (e.g., a small size screen). For example, connected device <b>940</b> could be a mobile phone, smart phone, personal digital assistant, tablet computer, and the like. Connected device <b>950</b> represents a device with a large screen <b>955</b>. For example, connected device <b>950</b> could be a television screen (e.g., a smart television) or another device connected to a television (e.g., a set-top box or gaming console) or the like. One or more of the connected devices <b>930</b>, <b>940</b>, <b>950</b> can include touchscreen capabilities. Touchscreens can accept input in different ways. For example, capacitive touchscreens detect touch input when an object (e.g., a fingertip or stylus) distorts or interrupts an electrical current running across the surface. As another example, touchscreens can use optical sensors to detect touch input when beams from the optical sensors are interrupted. Physical contact with the surface of the screen is not necessary for input to be detected by some touchscreens. Devices without screen capabilities also can be used in example environment <b>900</b>. For example, the cloud <b>910</b> can provide services for one or more computers (e.g., server computers) without displays.

0074Services can be provided by the cloud <b>910</b> through service providers <b>920</b>, or through other providers of online services (not depicted). For example, cloud services can be customized to the screen size, display capability, and/or touchscreen capability of a particular connected device (e.g., connected devices <b>930</b>, <b>940</b>, <b>950</b>).

0075In example environment <b>900</b>, the cloud <b>910</b> provides the technologies and solutions described herein to the various connected devices <b>930</b>, <b>940</b>, <b>950</b> using, at least in part, the service providers <b>920</b>. For example, the service providers <b>920</b> can provide a centralized solution for various cloud-based services. The service providers <b>920</b> can manage service subscriptions for users and/or devices (e.g., for the connected devices <b>930</b>, <b>940</b>, <b>950</b> and/or their respective users).

0000Example Implementations

0076Although the operations of some of the disclosed methods are described in a particular, sequential order for convenient presentation, it should be understood that this manner of description encompasses rearrangement, unless a particular ordering is required by specific language set forth below. For example, operations described sequentially may in some cases be rearranged or performed concurrently. Moreover, for the sake of simplicity, the attached figures may not show the various ways in which the disclosed methods can be used in conjunction with other methods.

0077Any of the disclosed methods can be implemented as computer-executable instructions or a computer program product stored on one or more computer-readable storage media and executed on a computing device (e.g., any available computing device, including smart phones or other mobile devices that include computing hardware). Computer-readable storage media are any available tangible media that can be accessed within a computing environment (e.g., one or more optical media discs such as DVD or CD, volatile memory components (such as DRAM or SRAM), or nonvolatile memory components (such as flash memory or hard drives)). By way of example and with reference to <figref idref="DRAWINGS">FIG. 7</figref>, computer-readable storage media include memory <b>720</b> and <b>725</b>, and storage <b>740</b>. By way of example and with reference to <figref idref="DRAWINGS">FIG. 8</figref>, computer-readable storage media include memory and storage <b>820</b>, <b>822</b>, and <b>824</b>. The term computer-readable storage media does not include signals and carrier waves. In addition, the term computer-readable storage media does not include communication connections (e.g., <b>770</b>, <b>860</b>, <b>862</b>, and <b>864</b>).

0078Any of the computer-executable instructions for implementing the disclosed techniques as well as any data created and used during implementation of the disclosed embodiments can be stored on one or more computer-readable storage media. The computer-executable instructions can be part of, for example, a dedicated software application or a software application that is accessed or downloaded via a web browser or other software application (such as a remote computing application). Such software can be executed, for example, on a single local computer (e.g., any suitable commercially available computer) or in a network environment (e.g., via the Internet, a wide-area network, a local-area network, a client-server network (such as a cloud computing network), or other such network) using one or more network computers.

0079For clarity, only certain selected aspects of the software-based implementations are described. Other details that are well known in the art are omitted. For example, it should be understood that the disclosed technology is not limited to any specific computer language or program. For instance, the disclosed technology can be implemented by software written in C++, Java, Perl, JavaScript, Adobe Flash, or any other suitable programming language. Likewise, the disclosed technology is not limited to any particular computer or type of hardware. Certain details of suitable computers and hardware are well known and need not be set forth in detail in this disclosure.

0080Furthermore, any of the software-based embodiments (comprising, for example, computer-executable instructions for causing a computer to perform any of the disclosed methods) can be uploaded, downloaded, or remotely accessed through a suitable communication means. Such suitable communication means include, for example, the Internet, the World Wide Web, an intranet, software applications, cable (including fiber optic cable), magnetic communications, electromagnetic communications (including RF, microwave, and infrared communications), electronic communications, or other such communication means.

0081The disclosed methods, apparatus, and systems should not be construed as limiting in any way. Instead, the present disclosure is directed toward all novel and nonobvious features and aspects of the various disclosed embodiments, alone and in various combinations and sub combinations with one another. The disclosed methods, apparatus, and systems are not limited to any specific aspect or feature or combination thereof, nor do the disclosed embodiments require that any one or more specific advantages be present or problems be solved.

0082The technologies from any example can be combined with the technologies described in any one or more of the other examples. In view of the many possible embodiments to which the principles of the disclosed technology may be applied, it should be recognized that the illustrated embodiments are only examples of the technology and should not be taken as limiting the scope of the present disclosure. Rather, the scope of the invention is defined by the following claims.