Intelligent presentation of documents

Abstract

To provide a method, program and an electronic device for providing dynamically updated information associated with a document.SOLUTION: A method includes: receiving, on an electronic device, first information from a vendor; generating a first document including the first information, storing the first document on the electronic device, and receiving an instruction to update a part of the first information from the vendor; and updating the first document with the updated part of the first information, the first document associated with a document notification including the updated part of the first information and a first portion of the first document, automatically displaying, via a display device, the document notification not including a second portion of the first document, receiving an input on the notification via one or more input devices, and displaying a representation of the first document, including the first portion of the first document and the second portion of the first document, via the display device.SELECTED DRAWING: Figure 14

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent No. 61 / 656,931, filed June 7, 2012, and U.S. Patent No. 13 / 843,962, filed March 15, 2013, the contents of which are incorporated herein in their entireties. [Technical Field]

[0002] The present invention relates generally to managing and presenting documents on a display of a computing device. [Background technology]

[0003] Loyalty cards, identification cards, coupons, tickets, boarding passes, and other documents are used by people every day when shopping, identifying themselves, attending events, and traveling. Many of these documents are digitized and stored on mobile computing devices to enable use wherever the mobile computing device is. However, managing and accessing these digitized documents on a mobile computing device can be tedious and time-consuming. Summary of the Invention

[0004] In some implementations, documents can be presented on a display of a computing device based on the context of the computing device. This context can include the current time and / or current location associated with the computing device. The documents can be presented based on the time and / or location associated with the document. Documents can be downloaded and shared between devices. Documents can be dynamically updated based on information provided by the document vendor and / or information from other network-based resources. In some implementations, the various graphical interfaces described herein allow access to various document types in an organized and efficient manner.

[0005] Particular implementations provide at least the following benefits: documents can be presented in anticipation of a user's desire to use the document; documents can be presented in a way that makes them easily accessible; documents can provide dynamically updated information associated with the document so that users can easily access the most current information.

[0006] The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features, aspects, and potential advantages will become apparent from the description, drawings, and claims. [Brief explanation of the drawings]

[0007] [Figure 1] 1 illustrates an embodiment of a system for receiving, storing, and updating documents on a mobile device. [Figure 2] FIG. 1 illustrates an example of a new document interface. [Figure 3] FIG. 1 illustrates an embodiment of a graphical interface for presenting documents based on time and / or location. [Figure 4] FIG. 4 illustrates an embodiment of a graphical interface for presenting a document 402 on a mobile device. [Figure 5] FIG. 1 illustrates an example of a graphical interface for a document management application. [Figure 6] FIG. 1 illustrates an example of a graphical interface for a document management application. [Figure 7] FIG. 1 illustrates an example of a graphical interface for presenting multiple related documents. [Figure 8] FIG. 1 illustrates an example of a graphical interface for presenting multiple related documents. [Figure 9] FIG. 1 illustrates an example of a graphical interface for presenting multiple related documents. [Figure 10] FIG. 1 illustrates an example of a graphical interface for presenting multiple related documents. [Figure 11] FIG. 1 illustrates an example of a graphical interface for presenting multiple related documents. [Figure 12] FIG. 10 is a diagram illustrating an example of a ticket template for an event. [Figure 13] FIG. 10 is a diagram showing an example of an identification card template. [Figure 14] FIG. 10 is a diagram showing an example of a template for a customer point card. [Figure 15] FIG. 10 is a diagram illustrating an example of a discount coupon template. [Figure 16] FIG. 10 is a diagram showing an example of a template of a boarding pass. [Figure 17] FIG. 10 is a diagram showing an example of a template for a general document. [Figure 18] FIG. 1 illustrates an example of a graphical interface for specifying document options. [Figure 19] FIG. 1 illustrates an example of a graphical interface for deleting a document from a mobile device. [Figure 20] FIG. 10 illustrates an example of a graphical interface for deleting a document. [Figure 21] FIG. 1 illustrates a flow diagram of an example process for intelligently presenting document notifications on a mobile device. [Figure 22] FIG. 1 illustrates a flow diagram of an example process for presenting a document on a mobile device. [Figure 23] FIG. 1 illustrates a flow diagram of an example process for receiving and storing a document on a mobile device. [Figure 24] 24 shows a block diagram of an example system architecture that implements the features and processes of FIGS. 1-23. Like reference symbols in each drawing indicate like elements. DETAILED DESCRIPTION OF THE INVENTION

[0008] overview This specification describes various graphical user interfaces (UIs) for implementing various features, processes, and workflows. These GUIs can be presented on a variety of electronic devices, including, but not limited to, laptop computers, desktop computers, computer terminals, television systems, tablet computers, e-readers, and smartphones. One or more such electronic devices can include a touch-sensitive surface. The touch-sensitive surface can process multiple simultaneous input points, including processing data related to the pressure, angle, or position of each input point. Such processing can facilitate multi-finger gestures, including pinching and swiping.

[0009] When this disclosure refers to "selecting" or "selecting" a user interface element within a GUI, these terms are understood to include clicking or "hovering" with a mouse or other input device over a user interface element, touching, tapping, or gesturing with one or more fingers or a stylus over a user interface element. A user interface element may be a virtual button, menu, selector, switch, slider, scrubber, knob, thumbnail, link, icon, radial button, checkbox, or any other mechanism for accepting input from or providing feedback to a user.

[0010] 1 illustrates an embodiment of a system 100 for receiving, storing, and updating documents on a mobile device. For example, the documents in system 100 may include customer loyalty cards, event tickets, vouchers, coupons, boarding passes, identification cards, key cards (e.g., cards for entering a hotel room, a house, a car, etc.), or any other type of document. In some implementations, system 100 may include a mobile device 102. For example, mobile device 102 may be a laptop computer, a smartphone, a feature phone, a tablet computer, or any other type of computing device.

[0011] In some implementations, the mobile device 102 may include applications that a user of the mobile device 102 can use to obtain various documents. For example, the mobile device 102 may include a browser 104. Using the browser 104, a user may access web pages to purchase event tickets, travel passes, and other types of documents. Using the browser 104, a user may access web pages to become a member of customer loyalty programs with various vendors and commercial businesses. Document information 106 generated in such transactions may be downloaded or transferred to the mobile device 102 via the browser 104. For example, information associated with a purchased ticket, boarding pass, or other document may be transferred to the mobile device 102 via the browser 104. Information associated with a customer loyalty card or an account created through membership in a customer loyalty program may be transferred to the mobile device 102 via the browser 104.

[0012] In some implementations, the mobile device 102 may include an application 108. For example, the application 108 may be a client application for a network (e.g., Internet) service that allows a user to download documents. The application 108 may be a client application that allows a user to purchase tickets to an event and download the event tickets to the mobile device 102. The application 108 may be a travel application that allows a user to purchase airline tickets and hotel accommodations. When a user purchases an item through the application 108, document information 106 associated with the purchase may be downloaded to the mobile device 108 via the application 108.

[0013] In some implementations, the mobile device 102 may include an email application 110. For example, instead of receiving the document 106 via the browser 104 or application 108, the mobile device 102 may receive the document information 106 as an email attachment. For example, the browser 104 and / or application 108 may be configured to not allow document downloads. Thus, when a user purchases a document using the browser 104 or application 108, the online vendor may send the user an email with the document information 106 attached.

[0014] In some implementations, the mobile device 102 may include a wireless receiver 114. For example, the wireless receiver 114 may be configured to receive Wi-Fi® signals, Bluetooth® signals, near-field communication signals, or any other type of wireless or radio frequency signal. In some implementations, the wireless receiver 114 may receive information 106 encoded via wireless transmission. For example, a computing device may share document information 106 by encoding the document information 106 into a wireless signal and transmitting the wireless signal to another device. For example, the mobile device 102 may receive document information 106 from another computing device.

[0015] In some implementations, the mobile device 102 may include an image capture device 112. For example, the image capture device 112 may be a digital camera built into the mobile device 102. In some implementations, a user may use the image capture device 112 to capture encoded document information 106 on a physical document. For example, a paper, plastic, or other physical document may have a barcode, a quick response code, a linear barcode, a matrix code, or any other type of code that can be optically scanned. The user may use the image capture device 112 to capture an image of the paper document, and the mobile device 102 may determine the document information 106 based on the captured image. For example, once the image of the document can be captured, optical character recognition software may be used to determine the document information 106.

[0016] In some implementations, document information 106 may include all of the information for generating a document on mobile device 102. For example, document information 106 may include a username, vendor information, a user's account name, and other information for generating a document on mobile device 102. In some implementations, document information 106 may include a document template identifier and data associated with the document template, as described in more detail below.

[0017] In some implementations, only a minimal amount of information is included in the document information 106. For example, the minimal information may include a transaction identifier and a vendor URL (Uniform Resource Locator). The mobile device 102 can access the document vendor server 118 over the network 116 using the vendor URL. The mobile device 102 can send the document information 106 to the document vendor server 118. The document vendor server 118 can use the transaction identifier information included in the document information 106 to identify information associated with the document and provide complete document information to the mobile device 102. Once the mobile device 102 receives the document information from the document vendor server 118, the mobile device can generate the document 102 and store the document 102 in the document database 122. For example, based on the document information received from the vendor server 118, the mobile device 102 can identify a document template and populate the document template with the document information provided by the document vendor server 118, as described in more detail below.

[0018] In some implementations, the documents 102 can be stored on a network device. For example, the document database 122 can be a network or cloud-based database. The mobile device 102 can store the documents 102 on a network device and access the documents 102 from the network device as needed.

[0019] New Document Interface 2 illustrates an example of new document interface 200. For example, as described above, new document interface 200 can be presented when document information is received by mobile device 102. For example, when document information is received from a website via a browser application, the graphical interface of the browser application and new document interface 200 can replace the displayed application on the mobile device display. Similarly, when document information is received via another application, new document interface 200 can replace the displayed application on the mobile device display.

[0020] In some implementations, new document interface 200 can present newly generated document 202. As described below, new document 202 can correspond to a document received on the mobile device and can be generated based on a document template. New document 202 can include vendor-provided data specific to the newly generated document. For example, if new document 202 corresponds to a boarding pass, new document 202 can display airline operation information associated with the boarding pass. If new document 202 is the only document currently stored on the mobile device, new document 202 can be the only document displayed on new document interface 202. If new document 202 is not the only document currently stored on the mobile device, other documents currently stored on the mobile device can also be presented in overlay presentation 204.

[0021] In some implementations, animations may be presented when a new document is added to documents stored on the mobile device. For example, a user may select graphical element 206 to save a new document 202 on the mobile device. In response to selecting graphical element 206, document 202 may animate to appear inserted into overlay presentation 204. For example, document 202 may slide downward on the mobile device display until the new document is inserted within a stack of other documents on the mobile device. In some implementations, selecting graphical element 208 may return a user to a previous application. In response to selecting graphical element 208, new document interface 200 and the application that received the new document may be replaced on the mobile device display. For example, if a user is viewing an email application before new document interface 200 is displayed, selecting graphical element 208 may replace the email application on the display with new document interface 200.

[0022] Intelligent presentation of documents FIG. 3 illustrates an example of a graphical interface 300 for presenting documents based on time and / or location. In one implementation, a document stored on a mobile device can be associated with a time (e.g., a specific day and / or time). A transportation boarding pass can be associated with a departure time and / or boarding time. An event ticket (e.g., a concert ticket, a movie ticket, etc.) can be associated with a start time of the event. A sale coupon can be associated with an expiration date. In one implementation, if the current time is close to a specific time associated with the document, the document can be presented on the graphical interface 300 in anticipation of the user's imminent use. In one implementation, the document can be associated with a time period, or time window, for presenting the document. For example, if the document is a discount coupon with an expiration date, the discount coupon can be associated with a one-week time window that can be presented on the graphical interface 300. The one-week time window can be the one-week period before and at the expiration date of the discount coupon.

[0023] In some implementations, documents stored on a mobile device are associated with locations. For example, discount coupons and customer loyalty cards can be associated with store locations. Boarding passes can be associated with transportation hubs (e.g., airports, bus terminals, train stations, etc.). In some implementations, a document can be displayed when the mobile device detects that its current location is closest to a location associated with a document. For example, if the mobile device's current location is closest to the store location associated with a loyalty card stored on the mobile device, the loyalty card document can be displayed on the graphical interface 300.

[0024] In one implementation, graphical interface 300 may be a locked display for a mobile device. For example, graphical interface 300 may be the interface that is displayed when the mobile device is in a locked state that requires a password or password to access the mobile device's functionality. Graphical interface 300 may be the first interface a user sees when waking the mobile device from a sleep or low-power state.

[0025] In some implementations, the graphical interface 300 can present a document notification 302. For example, the document notification 302 may correspond to an airline boarding pass document stored on the mobile device. The document notification 302 can be presented on the graphical interface 300 when the mobile device detects that it is closest to the location (e.g., airport) and / or time (e.g., boarding time or departure time) associated with the boarding pass document. The document notification 302 can present information associated with the boarding pass document. For example, the document notification 302 can present a summary (e.g., a selected item) or a portion of the information associated with the boarding pass document. The document notification 302 can present, for example, the flight number, gate number, and departure time. The document notification 302 can indicate how many boarding passes are stored on the mobile device. For example, if a family travels together, a boarding pass for each family member can be stored on the mobile device. The number of boarding passes for a particular trip can be indicated, for example, by a graphical element 308.

[0026] In one implementation, a user can select a document notification 302 to display the associated boarding pass document. For example, a user can perform a swipe gesture 310 to display the boarding pass document. In one implementation, a user can drag a graphical element 312 (e.g., a document icon) on the document notification 302 to display the boarding pass document.

[0027] In some implementations, multiple document notifications can be displayed. For example, document notification 302 and document notification 304 can be displayed on graphical interface 300. For example, document notification 304 can correspond to a customer loyalty card for a coffee shop. If the current location of the mobile device is closest to, for example, the address of the coffee shop, document notification 304 can be displayed. Document notification 304 can provide a summary of information associated with the coffee shop's customer loyalty card. For example, if a coffee shop's card can be used to purchase coffee at the coffee shop and the card is associated with an account balance (e.g., $16), the account balance can be displayed on document notification 304. Document notification 304 can display, for example, the nearest coffee shop.

[0028] In one implementation, a user can select a document notification 304 to cause an associated coffee shop document to appear on the mobile device. For example, a user can perform a touch input 314 to swipe downward from the location of the document notification on the mobile device. When the user swipes downward (e.g., by pulling) on ​​the notification, the associated document can be revealed and / or displayed on the mobile device.

[0029] In some implementations, document notifications may be presented near the bottom of the graphical interface 300. For example, document notification 306 may be presented near the bottom of the graphical interface 300. A user may provide touch input 316 (e.g., an upward swipe) to display related documents.

[0030] In some implementations, a document notification can be presented in response to receiving document information updates. For example, when a mobile device receives an update to flight information associated with a boarding pass document, a document notification corresponding to the boarding pass document can be presented on the graphical interface 300. The document notification can present the changed flight information so that the user can be notified of the changes promptly. For example, the changed information can be highlighted using colored text or graphic objects (e.g., icons, animations, etc.) that draw the user's attention to the changed information, as described in more detail below.

[0031] In some implementations, after receiving a selection of a document notification 302, 304, or 306, the user's identity can be verified to ensure that the user is an authorized user of the mobile device and / or the document associated with the selected document notification. For example, the user can be prompted to enter an unlock code or password for the mobile device. After the user enters the correct code or password, the document associated with the selected notification can be presented.

[0032] In some implementations, a mobile device can be configured to verify a user's identity through biometric authentication. In some implementations, a mobile device can be configured to verify a user's identity based on the user's fingerprint. For example, the mobile device can scan a user's fingerprint and compare the scanned fingerprint to previously authenticated fingerprints of authenticated users of the mobile device and / or selected documents. The previously authenticated fingerprints (or biometric data derived from the previously authenticated fingerprints) can be stored on the mobile device or on a remote server. When the mobile device compares fingerprints during the user authentication process, the stored fingerprints can be retrieved from a local or remote storage location.

[0033] In some implementations, a mobile device can be configured to authenticate a user's identity using facial recognition technology. For example, a mobile device can be configured with a camera that can capture an image of a user's face when the user selects a document. The captured image can be compared to previously authenticated images of the user (or biometric data obtained from previously captured images of the user) to identify the identity of the user who selected the document. The captured image (or biometric data) can be stored on the mobile device or a remote server and accessed when the mobile device compares the captured image with previously authenticated images and / or biometric data.

[0034] In some implementations, biometric authentication can be performed using sensors configured on the mobile device (e.g., a camera, a fingerprint scanner, etc.). In some implementations, biometric authentication can be performed using a touch-sensitive display screen of the mobile device. For example, when a user touches a touchscreen interface of the mobile device, the mobile device can capture the user's fingerprint.

[0035] In some implementations, user authentication / verification using the techniques described above (e.g., password, fingerprint, facial recognition, etc.) can occur in response to a user selecting a document notification or in response to a user selecting a document (e.g., to view the document). In some implementations, user authentication / verification can occur when a user attempts to initiate a transaction using a document stored on a mobile device. For example, when a user attempts to make a purchase using a document, the mobile device can scan the user's fingerprint (or face) to verify that the user is an authorized user of the document before authorizing the purchase or presenting (by displaying, transmitting, etc.) information to facilitate the purchase. In some implementations, biometric authentication / verification can occur passively. For example, when a user makes a document selection using touch input on a touchscreen display, the mobile device can capture the user's fingerprint. Similarly, when a user makes a document selection, the mobile device can capture an image of the user's face. In this manner, passive biometric authentication can occur without the user providing any authentication-specific input. For example, an authentication-specific input may be a user providing a fingerprint as a touch input to a mobile device in response to an authentication / verification prompt presented by the mobile device (e.g., the sole purpose of the touch input is to authenticate the user).

[0036] 4 illustrates an example embodiment of a graphical interface 400 for presenting a document 402 on a mobile device. For example, the graphical interface 400 can be presented in response to a user selecting the document notification 302 in FIG. 3. The document 402 can be, for example, an airline boarding pass document. For example, if document notification 304 or 306 is selected, the graphical interface 400 can present a customer loyalty card document for a coffee shop.

[0037] In one implementation, document 402 can present vendor-provided information associated with document 402. For example, document 402 can present airline-provided information associated with a boarding pass, including airline name, departure gate, passenger name, seat number, flight number, departure time, departure point, arrival time, arrival point, and any other relevant travel information. In one implementation, if multiple boarding passes associated with the same flight are stored on the mobile device, document 402 can include an indication of the number of boarding passes stored on the mobile device (e.g., 1 of 3). If multiple boarding pass documents are present on the mobile device, the user can navigate between the boarding pass documents using input (e.g., touch input, swipe gestures, etc.).

[0038] In some implementations, document 402 may include an optically scannable and / or machine-readable graphical element 404. For example, graphical element 404 may be a two-dimensional barcode or code matrix that is scannable by a barcode reader, camera, and / or other optical scanning device. For example, when a user uses document 402 to board an airplane, airport personnel may scan graphical element 404 to process the boarding pass and obtain information associated with the passenger. In some implementations, near-field communication technology, Bluetooth, and / or other wireless transmission mechanisms may be used to transmit document information to facilitate transactions between users and vendors.

[0039] Document Management Applications 5 illustrates an example of a graphical interface 500 for a document management application. For example, a mobile device may include a document management application. A user may launch the document management application by selecting a graphical element (such as an icon) presented on the user interface of the mobile device. In response to launching the document management application, graphical interface 500 may be presented on the display of the mobile device. If the mobile device currently stores only one document, graphical interface 500 presents the document in a manner similar to graphical interface 400. If the mobile device stores two documents, the two documents may be tiled within graphical interface 500 so that both documents can be fully viewed.

[0040] In some implementations, when three or more documents are stored on a mobile device, the documents can be displayed in an overlapping presentation, as shown in FIG. 5. For example, when several documents are displayed in an overlapping presentation, a portion (e.g., an introduction) of each document can be displayed, which can provide a summary of the information associated with the document. For example, the summary information can include a selection of the most important or useful information associated with each document. This information can include the name of the document's vendor (e.g., the company associated with the document) or other information that a user might want to know by glancing at the displayed portion of the document. For example, account balances, gate numbers, seat numbers, event locations and times, discount offers and discount amounts can be presented within the displayed portion of the document so that a user can quickly determine important information about the document without having to select the document.

[0041] In some implementations, a user can select a displayed portion of a document to display the entire document. For example, graphical interface 500 can display document summaries 502-510. The document summaries can include the most important (e.g., most useful) document information. For example, the document summaries can present information that distinguishes one document from another. Document summaries 502 can correspond to an airline boarding pass document. Document summaries 504 can correspond to a customer loyalty card (e.g., a purchase card) document. Document summaries 506 can correspond to an event ticket (e.g., a concert ticket) document. Document summaries 508 can correspond to an identification document document. Document summaries 510 can correspond to a customer loyalty card document. A user can select document summaries (e.g., document portions) 504 to display the entire portion corresponding to the customer loyalty card document.

[0042] In some implementations, when a user selects a document summary, a video can be presented simultaneously with the presentation of the corresponding document. For example, when a user selects document summary 504, document summary 504 can be moved up and the other document summaries 502, 506, 508, and 510 can be moved down to present the video. The movement of the document summaries is indicated by the dashed arrows in Figure 5. As shown in Figure 6, when document summary 504 is moved up, a full view of the corresponding document can be revealed.

[0043] Other mechanisms or animations can also be implemented to present a full view of a document in response to a document summary being selected. In one implementation, when a user selects a document summary, non-selected documents fade out of view on the mobile device display while the corresponding documents fade in view. In one implementation, non-selected documents slide off to the left or right of the display, revealing the selected document. In another implementation, the selected document summary is shuffled to the front of the presented document summary (e.g., closest to the user). Once the selected document summary reaches the front of the document summary, the entire document can be displayed.

[0044] FIG. 6 illustrates an example of a graphical interface 600 for a document management application. For example, the graphical interface 600 can be displayed in response to a user selecting the document summary 504 in FIG. 5 . The graphical interface 600 shows the animation results triggered by the selection of the document summary 504. For example, the document summaries 502, 504, 506, and 508 not selected by the user can be moved to the bottom of the display for overlapping display. The selected document summary 504 can be moved to the top of the display. An animation can be displayed to show a full view of the document 602 corresponding to the selected document summary 504. The effect of the animation is to simulate a physical card, file, or holder being pulled from a stack of cards, filing cabinet, wallet, or other physical storage mechanism.

[0045] In some implementations, document 602 can display a full view of the information associated with the document. For example, compared to document summary 504, which merely displays selected items of information, document 602 can present all of the information associated with the document. Document 602 can display the document vendor name, account balance, document user / owner name, account number, nearest store location, and other information related to the user's use of the document. In some implementations, document 602 can display image 604. Document 604 can include an image associated with the document's vendor (e.g., logo, trademark, etc.). Image 604 can be configured to present additional information, as described in more detail below.

[0046] In some implementations, document 602 may present a scannable element 606. For example, element 606 may be a linear barcode, a matrix barcode, a quick response code, scannable text, or an optical, machine-readable representation of data. Scannable element 606 may be encoded with data associated with document 602. For example, the encoded data may include a vendor identifier, a vendor URL, a user account number, a transaction number, or other information associated with document 602. Scannable element 606 may be presented to a vendor and scanned with an optical scanning or image capture device. The scannable element may be decoded to extract encoded document information. This encoded document information may be used to obtain a complete set of information associated with the scanned document. For example, as described above with reference to FIG. 1, the vendor URL and account number may be used to contact a vendor server to access account information associated with scanned document 602. Scannable element 606 may, for example, speed and facilitate transactions between a mobile device user and a document vendor.

[0047] View related documentation FIG. 7 illustrates an example graphical interface 700 for presenting multiple related documents. For example, multiple boarding pass documents can be related based on flight number, departure point, and arrival time. Tickets for an event can be related by event and time. Documents can be related based on how they were received. For example, documents received as a result of the same transaction, in the same communication (e.g., email), or at the same time (or nearly so) can be identified as related documents. If a user has multiple related tickets stored on their mobile device, these tickets can be represented on the graphical interface 700 with a single document summary 502 and an indicator 702 that informs the user that there are multiple documents related to the document summary. For example, the document summary 502 can include text indicating that there are three boarding passes available on the mobile device.

[0048] 8 shows an embodiment of a graphical interface 800 for presenting multiple related documents. For example, instead of presenting indicator 703 on document summary 502, interface 800 can present multiple related documents by presenting a stack of indicators 802 for multiple related documents. The number of items in the stacked presentation can correspond to the number of documents associated with document summary 502. Stacked presentation 802 can have the appearance of multiple stacked documents, for example, with the top of each document visible.

[0049] FIG. 9 illustrates an example embodiment of a graphical interface 900 for presenting multiple related documents. For example, document 902 may be one of three related boarding passes. The boarding passes may be related, for example, based on flight number, departure time, and / or departure city. In some implementations, only one of the three related documents is presented at a time. For example, a user may select overview 502 in FIG. 7 or FIG. 8 to display one document (e.g., document 902) corresponding to document overview 502. In some implementations, a user may enter input into document 902 to view the next or previous related document. For example, if there are three related documents, selecting document overview 502 may display the first document (e.g., the first of the three). A user may enter input (e.g., touch input, tapping, or swiping) into document 902 to display the second related document (e.g., the second of the three). A user may enter further input to display the third related document (e.g., the third of the three). For example, a user can navigate between related documents by swiping left (e.g., to display the previous document) or right (e.g., to display the next document) using touch input 904.

[0050] FIG. 10 illustrates an example of a graphical interface 1000 for presenting multiple related documents. In one implementation, document summaries for the related documents can be grouped on the graphical interface 1000. For example, document summaries 1002, 1004, and 1006 may correspond to boarding pass documents for the same flight. Instead of providing a single document summary and multiple document indicators, as in FIG. 7, or instead of presenting an overlaid display, as in FIG. 8, the related document summaries 1002, 1004, and 1006 can be individually displayed and grouped on the graphical interface 1000. In one implementation, when multiple related document summaries are displayed, the mobile device can automatically determine distinctive characteristics (e.g., most significant differences) for each related document to display on the document summary. For example, each boarding pass is associated with a different passenger. Thus, the passenger name for each boarding pass can be presented on the corresponding document summary to assist the user in distinguishing between the related document summaries 1002, 1004, and 1006. To view the corresponding document, the user can select document overview 1002, 1004, or 1006 to display the corresponding document, where selecting document overview 1002, 1004, or 1006 causes the corresponding boarding pass document to be displayed.

[0051] In some implementations, when a user selects one of the grouped document summaries 1002, 1004, or 1006, an animation may be presented to show the selected document. For example, this animation may be similar to the animation described with reference to FIG. 5. When a user selects document summary 1004, document summary 1004 may move to the top of the display. Non-selected document summaries 1002, 1006, 504, 506, 508, 510 may move to the bottom of the display. The dashed arrows in FIG. 10 indicate the movement of the document summaries. While the animation (e.g., the movement of the document summaries) is occurring, a full view of the document corresponding to document summary 1004 may be shown, as shown in FIG. 11.

[0052] FIG. 11 illustrates an embodiment of a graphical interface 1100 for presenting a selected document. For example, the graphical interface 1100 may be presented in response to the selection of document summary 1004. Document 1102 may correspond to the selected document summary 1004 in FIG. 10. The unselected document summaries 1002, 1006, and 504 may be displayed in an overlay presentation at the bottom of the graphical interface 1100. If a user wants to view other documents related to document 1102 (e.g., the documents corresponding to document summaries 1002 and 1006), the user may provide an input on the graphical interface 1100 to select document summary 1002 or 1006. In response to the selection of document summary 1002 or 1006, the corresponding documents may be displayed on the graphical interface 1100 in a manner similar to document 1102.

[0053] In some implementations, selecting document summary 1002, 1006, or 504 can cause an animation to be presented on graphical interface 1100. For example, when document summary 1006 is selected, document 1102 can be animated and moved down into an overlaid presentation of document summaries 1002, 1006, and 504 until only the document summary (e.g., document summary 1004) of document 1102 is visible. Document summary 1006 can be moved up to reveal the document corresponding to document summary 1006 until a full view of the corresponding document is displayed, similar to document 1102. In this manner, the graphical interface 1100 can animate as if switching or swapping between the two documents.

[0054] Document Templates In some implementations, a document can be presented on a mobile device display according to a predefined document template. For example, the document template can specify the appearance of the document and the location and type of information displayed on the document. The document template can specify the look and feel of the document in portrait and / or landscape orientations. For example, a document can have different layouts for portrait and landscape orientations. Different document types can be associated with different document templates with different appearances, allowing a user to quickly identify the type of document presented on the mobile device display based on its appearance. When document information is received from a document vendor, the information can include information identifying the document template used to generate the document on the mobile device. The document template can be identified by a template identifier or by document type data included in the vendor-provided document information. As discussed above in Figures 1-11, the document template can determine the look and feel of the document presented on the graphical interface.

[0055] Vendor-provided document information can include data, color schemes, images, and other information to be presented on the document for generating the document on a mobile device. For example, each document template can include data fields that can be populated with vendor-provided data. In some implementations, a vendor can dynamically update data for a document. For example, when account information (e.g., account balance), flight information (e.g., flight number, departure time, boarding time), or event data (e.g., time, date, or venue) changes, the corresponding document stored on the mobile device can be updated to reflect the changed information.

[0056] In some implementations, documents and / or document templates can be configured to present information provided by other network (e.g., Internet) resources. For example, a boarding pass document template can include data fields for departure and arrival locations. A boarding pass document template can be configured to display weather, traffic, or other information associated with the departure and arrival locations, as described below. In some implementations, a user can select location information displayed on a document and / or document template (e.g., select text describing a location) to invoke a map display corresponding to the selected location.

[0057] In some implementations, similar documents are automatically modified to present distinctive characteristics to allow users to distinguish between the documents. For example, if a user has two or more customer loyalty cards from the same vendor, the customer loyalty card documents can automatically be set to different colors, images, or other characteristics that the user can use to distinguish between the customer loyalty cards. In some implementations, documents are automatically updated to present seasonal or holiday themes. For example, documents can be automatically updated to present images of fireworks, stars and stripes, or other images around the Fourth of July.

[0058] In some implementations, documents and / or document templates can be configured to present optically scannable objects to facilitate transactions between users and vendors. For example, a document can include a linear barcode, a two-dimensional matrix barcode, a quick response code, scannable text, or other scannable graphics. The optically scannable objects can be encoded with document information that can be decoded by an optical scanner. The decoded information can be used to facilitate transactions between users and vendors. For example, the decoded information can include ticket information, account information, user identification information, flight information, and any other information necessary to conduct a particular transaction.

[0059] In some implementations, documents and / or document templates can be configured to allow document information to be transmitted wirelessly between a user device and a vendor device. For example, near-field communication technology, Bluetooth, and / or other wireless transmission technology can be used to transmit document information from a user device to a vendor system to facilitate a transaction between a user and a vendor.

[0060] FIG. 12 illustrates an example of an event ticket template 1200. In some implementations, the event ticket template can define the appearance of an event ticket document. For example, the event ticket document can correspond to a movie ticket, a concert ticket, or a ticket for admission to any other type of event. The event ticket template's appearance can include, for example, a cutout 1202 at the top of the document. Data fields displayed on the event ticket template can include the event name, the name of the event organizer or vendor, the venue, the location, and the date and time of the event. If seating is designated, the event ticket can specify seating information. The event ticket template 1200 can include an area for presenting an image 1204. For example, the image 1204 can display an image associated with the event or an image associated with the vendor or organizer. The event ticket 1200 can include a scannable object 1206. For example, the scannable object 1206 can be an optical, machine-readable graphic encoded with document information, as described above. The event ticket template 1200 can include a graphical element 1208 for presenting configuration options. For example, a user can select graphical element 1208 to bring up graphical interface 1800 of FIG.

[0061] FIG. 13 illustrates an example of an identification card template 1300. In one implementation, the identification card template 1300 includes a graphical element 1302 that visually distinguishes it from other documents. For example, the graphical element 1302 may appear as a hole near the top of the identification card document, making the identification card resemble a physical identification card (e.g., a badge) that we wear around our necks or attach to our clothing. The identification card template 1300 may include data fields for providing a name, an identification number, and an identification issuer (e.g., an employer, a government agency). The identification card template 1300 may include an image 1304 associated with a person associated with the identification card document. For example, the image 1304 may be a photograph of the person's face.

[0062] FIG. 14 shows an example of a customer loyalty card template 1400. For example, the customer loyalty card template may include the vendor / store name, the customer name, the customer authentication number, and / or the location of the nearest store. In some implementations, the customer loyalty card may function as a store credit card or a store shopping card. For example, a customer may transfer money to an account associated with a store shopping card and use the money to purchase items at the store associated with the card. In some implementations, the customer loyalty card template 1400 may include an account balance data field 1402. For example, the account balance data field 1402 may display the account balance (e.g., available funds) for a store credit card or a store shopping card. In some implementations, the account balance displayed on the customer loyalty card may be dynamically updated. For example, the balance displayed in the account balance field may be updated as the user spends money, deposits money into, or makes payments with the account associated with the customer loyalty card.

[0063] For example, a vendor's server can notify a user's mobile device that a change has occurred to the user's account, the mobile device can request a data update in response to the change notification, and the data presented on the customer loyalty card can be updated to reflect the changed information. In some implementations, updated or recently changed information can be presented and highlighted using a text color (e.g., red) that is different from the text color (e.g., black) used for other data displayed on the customer loyalty card document. In some implementations, updated or recently changed information can be highlighted by presenting a graphical element (not shown) that indicates that the information has changed. For example, the changed information or data can be highlighted by drawing a line around the changed information or by presenting an icon or other graphical element to draw the user's attention to the changed information.

[0064] FIG. 15 shows an example of a discount coupon template 1500. In one implementation, the discount coupon template 1500 can define the appearance of a discount coupon document. For example, a discount coupon document can correspond to a coupon for a discount on an item purchased from a vendor or store. The appearance of an event ticket template can include, for example, a ragged, jagged, or perforated edge 1502 at the top of the document to differentiate the discount coupon document from other documents. The discount coupon template 1500 can include data fields for providing the vendor / store name, the nearest store location, and / or expiration dates and conditions associated with the discount coupon.

[0065] The discount coupon template 1500 may include a data field 1504 for presenting discount information. For example, the discount information may include a special discount (e.g., $5 off) or a percentage discount (e.g., 25% off) that a user can receive by purchasing an item through a vendor or store. In some implementations, the discount information may be dynamically updated by the vendor. For example, a discount coupon may initially offer a 10% discount. After one week, it may offer a 20% discount. As the vendor offers more (or less) discounts, the vendor may notify the user's mobile device that the information associated with the discount coupon document has changed, and the mobile device may update the document information to present the updated or changed discount. As noted above, the changed information may be highlighted to attract the user's attention.

[0066] FIG. 16 illustrates an example boarding pass template 1600. For example, boarding pass template 1600 can provide data fields for presenting boarding pass document information. Boarding pass document information can include, for example, airline name, flight number, gate number, seat number, departure point, departure time, boarding time, arrival point, and / or arrival time. Boarding pass template 1600 can specify where the document information is displayed when the boarding pass document is presented. In some implementations, boarding pass document information can be dynamically updated. For example, if there is a flight change (e.g., a scheduled flight is delayed or canceled), the information displayed on the boarding pass is automatically updated to reflect the change. For example, if the flight number, departure time, boarding time, gate number, seat number, arrival time, etc. change, the data presented in the respective fields of boarding pass template 1600 is updated.

[0067] Boarding pass template 1600 may include dynamic information regions 1602 and 1604. For example, information region 1602 may present information (e.g., traffic, weather) associated with the flight's departure location. Information region 1604 may present information (e.g., traffic, weather, etc.) associated with the flight's arrival location. Information in dynamic information regions 1602 and 1604 may be obtained from various network (e.g., Internet) resources (e.g., weather, traffic websites, etc.). Dynamic information regions 1602 and 1604 may be dynamically updated, for example, as the information changes.

[0068] FIG. 17 illustrates an example of a generic document template 1700. For example, generic document template 1700 can be used to determine the submission of documents that do not fit into one of the document categories described above with respect to FIGS. 12-18. Vendors can provide document information that can be inserted into the various data fields provided by generic document template 1700. In some implementations, vendors can specify their own document formats. For example, document formats can be specified using HTML (Hyper Markup Language). In this way, document vendors can provide vendor-specific document layouts with customized look and feel.

[0069] FIG. 18 illustrates an example of a graphical interface 1800 for specifying document options. For example, the graphical interface 1800 may be invoked and displayed when a user selects the graphical element 1208 in FIGS. 12-17. The graphical interface 1800 may include a graphical element 1802 for turning automatic document updates on and off. For example, if a user turns on automatic document updates, the mobile device receives notifications from the vendor when information associated with the associated document changes. The mobile device may then update the document information associated with the document and present the information in one of the user interfaces described above. For example, the updated information may be highlighted to reflect what information has changed. If a user turns off automatic document updates, the document will no longer be automatically received. For example, the user may need to take some action on the document (e.g., display the document) to receive document updates.

[0070] Graphical interface 1800 may include a graphical element 1804 for specifying whether a document should be presented on a lock screen (e.g., graphical interface 300) of a mobile device. For example, a user may select graphical element 1804 to turn off lock screen document notifications. When a user turns off lock screen notifications, document notifications are no longer displayed on the lock screen of the mobile device. A user may select graphical element 1804 to turn on lock screen document notifications. When a user turns on lock screen notifications, document notifications are displayed on the mobile device as described with reference to FIG. 3.

[0071] FIG. 19 illustrates an example of a graphical interface 1900 for deleting a document from a mobile device. For example, the graphical interface 1900 may correspond to the graphical interface 500 of FIG. 5. The graphical interface 1900 may include a graphical element 1902 for invoking an edit mode for the graphical interface 1900. For example, a user may select the graphical element 1902 to display graphical elements 1904-1912 (e.g., a delete button). Alternatively, a user may provide input in the form of a touch gesture (e.g., a swipe gesture) on an individual document to enable editing of the particular document. For example, a user may provide a swipe gesture on a document overview 1914 to reveal the graphical element 1904. A user may also select the graphical element 1902 again to cause the graphical elements 1904-1912 to disappear from the display. A user may also provide touch input (e.g., tapping) to the graphical interface 1900 on an area not associated with the graphical elements 1904-1912 to remove the graphical elements 1904-1912 from the display. In one implementation, a user can select one of the graphical elements 1904-1912 to cause the corresponding document to be deleted.

[0072] FIG. 20 shows an example embodiment of a graphical interface 2000 for deleting a document. For example, the graphical elements may be invoked by selecting graphical elements 1904-1912 in FIG. 19. Graphical interface 2000 may display document 2002, which may correspond to the document selected for deletion in graphical interface 1900 of FIG. 19. A user may delete document 2002 by selecting graphical element 2004. A user may cancel the deletion of document 2002 by selecting graphical element 2006.

[0073] In one implementation, an animation may be presented when a user selects to delete a document. For example, as document 2002 moves across graphical interface 2000 and attempts to enter graphical element 2008, a document shredder animation may be presented. For example, graphical element 2008 may have the appearance of a document shredder. As document 2002 enters graphical element 2008, document 2002 appears to be shredded into strips or small pieces of paper, thereby simulating the destruction of document 2002. In one implementation, the document shredder animation is presented while the mobile device vibrates.

[0074] In some implementations, when document 2002 is deleted, an animation of a fire may be displayed. For example, the animation may make document 2002 appear to be set on fire, causing document 2002 to appear to be burned. Document 2002 may burn to ashes and disappear from the bottom of graphical interface 200. In some implementations, other document destruction animations (e.g., exploding, crumpling into a ball, dropping into a trash can, ripping, etc.) may be presented.

[0075] Process Example 21 shows a flow diagram of an example process 2100 for intelligently presenting document notifications on a mobile device. In step 2102, documents can be stored on the mobile device. For example, the mobile device can store documents corresponding to boarding passes, customer loyalty cards, identification cards, event tickets, key cards, credit cards, and / or any other type of document.

[0076] In step 2104, a current location of the mobile device and / or a current time may be determined. For example, the current location of the mobile device may be determined based on GNSS data, detector data, wireless communication data, or any other type of data that can be used to obtain a geographic location of the mobile device. The current time may be determined based on a clock on the mobile device.

[0077] In step 2106, documents can be identified based on a current location and / or time. For example, each document can be associated with one or more locations. A customer loyalty card can be associated with a company that operates multiple stores. Store locations can be downloaded to the mobile device along with the document. In some implementations, only the nearest (e.g., within one mile or within five miles) store locations are stored on the mobile device. The mobile device can use the store location information to identify documents associated with locations closest to the mobile device. In some implementations, documents can be associated with a time (e.g., date and time). For example, a document may have an expiration date. The mobile device can use date and / or time information associated with a document to identify documents associated with dates and / or times close to the current time.

[0078] In some implementations, documents can be identified based on usage patterns. For example, a mobile device can track when and / or where a document is most frequently used by a user. If the mobile device determines that the current location of the mobile device is in a location where a document is frequently used, the mobile device can present a document notification to allow the user to quickly access the document at that location. Similarly, if the current time corresponds to a time when a document is frequently used, the mobile device can present a document notification to allow the user to quickly access the document.

[0079] In step 2108, the identified document may be presented on a display of the mobile device. A document notification may be presented on a display of the mobile device when the mobile device is near a location associated with a document. A document notification may be presented on a display of the mobile device when the current time approaches a date / time associated with a document. In some implementations, the identified document may be presented on a lock screen of the mobile device. For example, a document notification corresponding to the identified document may be displayed on a lock screen of the mobile device to allow a user to quickly access the document from the lock screen interface.

[0080] User input associated with a document may be received at step 2110. For example, a user may select a document notification presented on the lock screen of a mobile device to cause the corresponding document to be displayed at step 2112. Details of process 2100 are further described with reference to Figures 1-20 above.

[0081] 22 is a flow diagram of an example process 2200 for presenting a document on a mobile device. At step 2202, a document can be stored on the mobile device. For example, the mobile device can store documents corresponding to boarding passes, customer loyalty cards, identification cards, event tickets, key cards, credit cards, and / or any other type of document.

[0082] In step 2204, the mobile device may receive a call to a document management interface. For example, a user may call a document management application on the mobile device to view documents stored on the mobile device. In step 2206, the mobile device may display the stored documents. For example, the mobile device may display the documents as described above with reference to FIGS. 3-19.

[0083] In step 2208, the mobile device may receive a document selection. For example, a user may provide input selecting a document summary, causing the mobile device to present a full view of the associated document in step 2210. Details of process 2200 are further described with reference to Figures 1-20 above.

[0084] 23 is a flow diagram of an example process 2300 for receiving and storing documents on a mobile device. In step 2302, document information may be received by the mobile device. For example, the mobile device may receive the document information from a website via a browser. The mobile device may receive the document information from a vendor server via a client application stored on the mobile device. The mobile device may receive the document information via email. The mobile device may receive the document information via wireless communication (e.g., near field communication, Bluetooth, Wi-Fi, etc.). The mobile device may receive the document information, for example, via an ad hoc (e.g., device-to-device) network connection.

[0085] The document information may be generated and transferred as a result of a transaction between a device user and a document vendor. The transaction may be a purchase transaction. For example, a user may purchase a boarding pass, a ticket to an event, or other document. The transaction may be a membership transaction. For example, a user may become a member of a customer loyalty program. Once the transaction is complete, the vendor may transmit the document information to the user.

[0086] At step 2304, a document can be generated based on the received document information. In some implementations, the document information can include all of the information necessary to generate the document on the mobile device. For example, vendor-provided document information can include all of the information necessary to identify a document template and insert data into the document template. In some implementations, the document information can include only the minimum amount of information necessary to retrieve the entire set of document information from the vendor's server. For example, the minimum amount of information can include a transaction identifier, an account identifier, a user identifier, or other information that can be used to retrieve the document information from the vendor's server. Once the identifier (e.g., a transaction identifier) ​​is received, the mobile device can access the vendor server and download the complete information for the document. Once the mobile device has the complete set of document information, the mobile device can generate the document. The document can then be stored on the mobile device at step 2306. Details of process 2300 are further described with reference to FIGS. 1-20 above.

[0087] System architecture example Figure 24 shows a block diagram of an example computing device 2400 capable of implementing the features and processes of Figures 1-23. The computing device 2400 may include a memory interface 2402, one or more data processors, image processors, and / or central processing units 2404, and a peripherals interface 2406. The memory interface 2402, the one or more processors 2404, and / or the peripherals interface 2406 may be separate components or may be integrated into one or more integrated circuits. The various components within the computing device 2400 may be connected by one or more communication buses or signal lines.

[0088] Sensors, devices, and subsystems may be connected to the peripherals interface 2406 to facilitate numerous functions. For example, a motion sensor 2410, a light sensor 2412, and a proximity sensor 2414 may be connected to the peripherals interface 2406 to facilitate orientation, lighting, and proximity functions. Other sensors 2416, such as a Global Navigation Satellite System (GNSS) (e.g., a GPS receiver), temperature sensors, biometric sensors, or other detection devices, may also be connected to the peripherals interface 2406 to facilitate related functions.

[0089] A camera subsystem 2420 and optical sensor 2422 (e.g., a charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) optical sensor) may be utilized to facilitate camera functions such as recording photographs and video clips. The camera subsystem 2420 and optical sensor 2422 may be used, for example, to perform facial recognition analysis and to collect images of a user for use during user authentication.

[0090] Communications functions may be facilitated through one or more wireless communication subsystems 2424, which may include radio frequency receivers and transmitters and / or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of the communications subsystem 2424 may depend on the communications network over which the computing device 2400 is intended to operate. For example, the computing device 2400 may include a communications subsystem 2424 designed to operate on a GSM network, a GPRS network, an EDGE network, a Wi-Fi or WiMax network, or a Bluetooth network. In particular, the wireless communication subsystem 2424 may include a hosting protocol to enable the device 100 to be configured as a base station for other wireless devices.

[0091] The audio subsystem 2426 may be connected to a speaker 2428 and a microphone 2430 to facilitate voice-enabled functions such as speaker recognition, voice replication, digital recording, and telephone functions. The audio subsystem 2426 may be configured to facilitate processing of voice commands to invoke the features and processes described above with reference to Figures 1-23.

[0092] The input / output subsystem 2440 can include a touch surface controller 2442 and / or other input controllers 2444. The touch surface controller 2442 can be connected to a touch surface 2446. The touch surface 2446 and touch surface controller 2442 can detect contact, movement, or interruption using any of a number of touch detection technologies, including, for example, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch surface 2446.

[0093] Other input controller 2444 may be coupled to other input / control devices 2448, such as one or more buttons, rocker switches, thumbwheels, infrared ports, USB ports, and / or pointer devices such as a stylus. One or more buttons (not shown) may include up / down buttons for controlling the volume of speaker 2428 and / or microphone 2430.

[0094] In one implementation, pressing the button for a first duration can unlock the touch surface 2446, and pressing the button for a second duration, longer than the first duration, can turn power on or off to the computing device 2400. Pressing the button for a third duration can activate a voice control or voice command module, which allows a user to speak commands into the microphone 2430 and have the device carry out the verbal commands. A user can customize the functionality of one or more buttons. The touch surface 2446 can be used to implement, for example, virtual or software buttons and / or a keyboard.

[0095] In some implementations, computing device 2400 can present recorded audio files, such as MP3, AAC, and MPEG files, and / or video files. In some implementations, computing device 2400 can include MP3 player functionality, such as an iPod®. Accordingly, computing device 2400 includes a 36-pin connector compatible with an iPod. Other input / output and control devices can also be used.

[0096] The memory interface 2402 can be coupled to memory 2450. The memory 2450 can include high-speed random access memory and / or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and / or flash memory such as NAND or NOR types. The memory 2450 can store an operating system 2452, such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks.

[0097] Operating system 2452 may include instructions for handling basic system services and for performing hardware-dependent tasks. In some implementations, operating system 2452 may be a kernel (e.g., a UNIX kernel). In certain implementations, operating system 2452 may include instructions for providing intelligent presentation of documents. For example, operating system 2452 may implement the document notification features described with reference to FIGS. 1-23.

[0098] Memory 2450 may also store communications instructions 2454 to facilitate communications with one or more additional devices, one or more computers, and / or one or more servers. Memory 2450 may include graphic user interface instructions 2456 for facilitating graphic user interface processing, sensor processing instructions 2458 for facilitating sensor-related processing and functions, telephony instructions 2460 for facilitating telephony-related processes and functions, electronic messaging instructions 2462 for facilitating electronic messaging-related processes and functions, web browsing instructions 2464 for facilitating web browsing-related processes and functions, media processing instructions 2466 for facilitating media processing-related processes and functions, GNSS / navigation instructions 2468 for facilitating GNSS and navigation-related processes and functions, and / or camera instructions 2470 for facilitating camera-related processes and functions.

[0099] The memory 2450 may store other software instructions 2472 to facilitate other processes and functions, such as security and / or authentication processes and functions, as described above with reference to Figures 1-23. For example, the software instructions may include instructions for receiving, generating, storing, and presenting documents, as described above with reference to Figures 1-23.

[0100] Memory 2450 may also store other software instructions (not shown), such as web video instructions for facilitating web video related processes and functions and / or web shopping instructions for facilitating web shopping related processes and functions. In one implementation, media processing instructions 2466 are divided into audio processing instructions and video processing instructions to facilitate audio processing related processes and functions and video processing related processes and functions, respectively. Activation records and an International Mobile Equipment Identity (IMEI) 2474, or similar hardware identification number, may also be stored in memory 2450.

[0101] Each of the above-identified instructions and applications may correspond to a set of instructions for performing one or more of the functions described above. These instructions need not be implemented as separate software programs, procedures, or modules. Memory 2450 may include additional or fewer instructions. Furthermore, various functions of computing device 2400 may be implemented in hardware and / or software, including one or more signal processing circuits and / or application-specific integrated circuits.

[0102]

[0010] Therefore, in accordance with the above, certain embodiments of the present disclosure relate to a method including storing one or more documents on a computing device, determining a context for the computing device, identifying at least one of the one or more documents for presentation on a display of the computing device based on the context, and presenting the at least one identified document on the display of the computing device. Additionally or alternatively to one or more of the above-disclosed embodiments, in certain embodiments, determining the context for the computing device includes determining a current time, the method further including comparing the current time with one or more preset times associated with the one or more documents, each document associated with the at least one preset time, and identifying at least one identified document based on the comparison. Additionally or alternatively to one or more of the above-disclosed embodiments, in certain embodiments, determining the context for the computing device includes determining a current location of the computing device, the method further including comparing the current location with one or more preset locations associated with the one or more documents, each document associated with the at least one preset location, and identifying at least one identified document based on the comparison. In addition to or as an alternative to one or more of the embodiments disclosed above, in some embodiments, presenting the at least one identified document includes presenting the at least one identified document on a display of the computing device when the device is in a locked state. In addition to or as an alternative to one or more of the embodiments disclosed above, in some embodiments, presenting the at least one identified document includes presenting a summary of the at least one identified document on a display of the computing device.Additionally or alternatively to one or more embodiments disclosed above, in some embodiments, the method further includes receiving user input selecting at least one identified document and presenting an optical machine-readable representation of data associated with the at least one identified document on a display of the computing device. Additionally or alternatively to one or more embodiments disclosed above, in some embodiments, the document corresponds to a ticket for an event. Additionally or alternatively to one or more embodiments disclosed above, in some embodiments, the document corresponds to a boarding pass. Additionally or alternatively to one or more embodiments disclosed above, in some embodiments, the document corresponds to a business customer document. Additionally or alternatively to one or more embodiments disclosed above, in some embodiments, the document corresponds to identification material associated with a user of the computing device. Additionally or alternatively to one or more embodiments disclosed above, in some embodiments, the document corresponds to a coupon.

[0103] Some embodiments of the present disclosure relate to a method that includes storing a plurality of documents on a mobile device, presenting summaries associated with the plurality of documents on a display of the mobile device, receiving from a user a selection of a summary corresponding to a particular one of the plurality of documents, and presenting the particular document on the display of the mobile device in response to receiving the selection. Additionally or alternatively to one or more of the embodiments disclosed above, in some embodiments, presenting summaries associated with the plurality of documents includes presenting the documents in an overlaid presentation. Additionally or alternatively to one or more of the embodiments disclosed above, in some embodiments, presenting the particular document includes presenting an animation that moves non-selected documents to an edge of the display. Additionally or alternatively to one or more of the embodiments disclosed above, in some embodiments, presenting the particular document includes presenting an optical, machine-readable representation of data associated with the particular document on the display of the mobile device. In addition to or as an alternative to one or more of the embodiments disclosed above, in some embodiments, the particular document belongs to a group of related documents, and presenting the particular document includes presenting one of the documents in the group, and the method further includes receiving an input to display another document in the group of related documents while presenting the particular document, and presenting the other document in the group on a display of the mobile device. In addition to or as an alternative to one or more of the embodiments disclosed above, in some embodiments, the display is a touch-sensitive display, and the input to display the other document includes a touch input to the touch-sensitive display. In addition to or as an alternative to one or more of the embodiments disclosed above, in some embodiments, the method further includes receiving an input to delete the particular document, and presenting an animation that appears to cut the particular document.In addition to or as an alternative to one or more of the above-disclosed embodiments, in some embodiments the method includes vibrating the mobile device while presenting the cut animation.

[0104] Certain embodiments of the present disclosure relate to a non-transitory computer-readable medium including one or more sequences of instructions that, when executed by one or more processors, cause one or more documents to be stored on a computing device, determine a context for the computing device, identify at least one of the one or more documents for presentation on a display of the computing device based on the context, and present the at least one identified document on a display of the computing device. Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, the instructions for determining the context of the computing device include instructions for determining a current time, the instructions for comparing the current time with one or more preset times associated with the one or more documents, each document associated with the at least one preset time, and identifying at least one identified document based on the comparison. Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, the instructions for determining the context of the computing device include instructions for determining a current location of the computing device, the instructions for comparing the current location with one or more preset locations associated with the one or more documents, each document associated with the at least one preset location, and identifying at least one identified sentence based on the comparison. In addition to or as an alternative to one or more of the embodiments disclosed above, in some embodiments, the instructions for causing presentation of the at least one identified document include instructions for causing presentation of the at least one identified document on a display of the computing device when the device is in a locked state. In addition to or as an alternative to one or more of the embodiments disclosed above, in some embodiments, the instructions for causing presentation of the at least one identified document include instructions for causing presentation of a summary of the at least one identified document on a display of the computing device.Additionally or alternatively to one or more of the above-disclosed embodiments, in some embodiments, the instructions cause receiving user input selecting at least one identified document and presenting an optical, machine-readable representation of data associated with the at least one identified document on a display of the computing device. Additionally or alternatively to one or more of the above-disclosed embodiments, in some embodiments, the document corresponds to a ticket for an event. Additionally or alternatively to one or more of the above-disclosed embodiments, in some embodiments, the document corresponds to a boarding pass. Additionally or alternatively to one or more of the above-disclosed embodiments, in some embodiments, the document corresponds to a business customer document. Additionally or alternatively to one or more of the above-disclosed embodiments, in some embodiments, the document corresponds to an identification document associated with a user of the computing device. Additionally or alternatively to one or more of the above-disclosed embodiments, in some embodiments, the document corresponds to a coupon.

[0105] Certain embodiments of the present disclosure relate to a non-transitory computer-readable medium including one or more sequences of instructions that, when executed by one or more processors, cause a computing device to store a plurality of documents, present summaries associated with the plurality of documents on a display on the computing device, receive a selection of a summary corresponding to a particular one of the plurality of documents, and, in response to receiving the selection, present the particular document on a display of a mobile device. Additionally or alternatively to one or more of the above-disclosed embodiments, in some embodiments, the instructions for presenting summaries associated with the plurality of documents include instructions for presenting the documents in an overlaid presentation. Additionally or alternatively to one or more of the above-disclosed embodiments, in some embodiments, the instructions for presenting the particular document include instructions for presenting an animation that moves non-selected documents to an edge of the display. Additionally or alternatively to one or more of the above-disclosed embodiments, in some embodiments, the instructions for presenting the particular document include instructions for presenting an optical, machine-readable representation of data associated with the particular document on a display of the mobile device. Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, the particular document belongs to a group of related documents, and the instructions to present the particular document include instructions to present one of the documents in the group, and while presenting the particular document, receive an input to display another document in the group of related documents, causing the other document in the group to be presented on a display of the mobile device. Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, the display is a touch-sensitive display, and the input to display the other document includes a touch input to the touch-sensitive display. Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, the instructions receive an input to delete the particular document, causing an animation to be presented that appears to cut the particular document.Additionally or alternatively to one or more of the above disclosed embodiments, in some embodiments, the instructions cause the mobile device to vibrate while causing an animation of a document shredder to be presented.

[0106] Certain embodiments of the present disclosure relate to a system comprising one or more processors and a computer-readable medium comprising one or more sequences of instructions that, when executed by the one or more processors, cause one or more documents to be stored on a computing device, determine a context for the computing device, identify at least one of the one or more documents based on the context for presentation on a display of the computing device, and present at least one of the identified documents on a display on the computing device. In addition to or as an alternative to one or more of the above-disclosed embodiments, in certain embodiments, the instructions for determining the context of the computing device include instructions for determining a current time, the instructions for comparing the current time with one or more preset times associated with the one or more documents, each document associated with at least one preset time, and identifying the at least one identified document based on the comparison. Additionally or alternatively to one or more of the above-disclosed embodiments, in some embodiments, the instructions for determining a context of the computing device include instructions for determining a current location of the computing device, the instructions for comparing the current location with one or more preset locations associated with one or more documents, each document associated with at least one preset location, and identifying at least one identified document based on the comparison. Additionally or alternatively to one or more of the above-disclosed embodiments, in some embodiments, the instructions for presenting the at least one identified document include instructions for presenting the at least one identified document on a display of the computing device when the device is in a locked state. Additionally or alternatively to one or more of the above-disclosed embodiments, in some embodiments, the instructions for presenting the at least one identified document include instructions for presenting a summary of the at least one identified document on a display of the computing device.Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, the instructions cause receiving user input selecting at least one identified document and presenting, on a display of the computing device, an optical, machine-readable representation of data associated with the at least one identified document. Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, the document corresponds to a ticket to an event. Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, the document corresponds to a boarding pass. Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, the document corresponds to a business customer document. Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, the document corresponds to an identification document associated with a user of the computing device. Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, the document corresponds to a coupon.

[0107] Some embodiments of the present disclosure relate to a system comprising one or more processors and a computer-readable medium comprising one or more sequences of instructions that, when executed by the one or more processors, cause a computer to store a plurality of documents on a computing device, present summaries associated with the plurality of documents on a display on the computing device, receive a selection of a summary corresponding to a particular one of the plurality of documents, and, in response to receiving the selection, present the particular document on a display of a mobile device. Additionally or alternatively to one or more of the embodiments disclosed above, in some embodiments, the instructions for presenting summaries associated with the plurality of documents include instructions for presenting the documents in an overlaid presentation. Additionally or alternatively to one or more of the embodiments disclosed above, in some embodiments, the instructions for presenting the particular document include instructions for presenting an animation that moves non-selected documents to an edge of the display. Additionally or alternatively to one or more of the embodiments disclosed above, in some embodiments, the instructions for presenting the particular document include instructions for presenting an optical, machine-readable representation of data associated with the particular document on a display of the mobile device. Additionally or alternatively to one or more of the embodiments disclosed above, in some embodiments, the particular document belongs to a group of associated documents, and the instructions to present the particular document include instructions to present one of the documents in the group, and while presenting the particular document, receive an input to display another document in the group of related documents, causing the other document in the group to be presented on a display of the mobile device. Additionally or alternatively to one or more of the embodiments disclosed above, in some embodiments, the display is a touch-sensitive display, and the input to display the other document includes a touch input to the touch-sensitive display. Additionally or alternatively to one or more of the embodiments disclosed above, in some embodiments, the instructions receive an input to delete the particular document, causing an animation to be presented that makes it appear as if the particular document has been cut.Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, the instructions vibrate the mobile device while presenting the cutting animation. Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, the method further includes, in response to receiving the selection, biometrically authenticating the user as an authorized user of the specific document, and presenting the specific document on a display of the mobile device when the user is verified as an authorized user of the specific document. Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, biometrically authenticating the user includes capturing a fingerprint of the user proximate to receiving the selection and comparing the captured fingerprint with an authenticated fingerprint of an authorized user of the specific document. Additionally or alternatively to one or more of the disclosed embodiments above, in some embodiments, biometrically authenticating the user includes capturing an image of the user proximate to receiving the selection and comparing the captured image with an authenticated image of an authorized user of the specific document.

Claims

1. 1. A method comprising:

1. An electronic device in communication with a display device and one or more input devices, comprising: receiving first information from a vendor; generating and storing a first document including the first information on the electronic device; receiving instructions from a vendor to update the portion of the first information while the first document is stored on the electronic device; In response to receiving an indication of updating the portion of the first information, updating the first document with the updated portion of the first information; automatically displaying via the display device a document notification associated with the first document, the document notification including the updated portion of the first information and a first portion of the first document, but not a second portion of the first document; receiving input for the document notification via the one or more input devices while displaying the document notification; in response to receiving the input, displaying via a display device a representation of the first document, the representation including the first portion of the first document and the second portion of the first document; A method comprising:

2. the document notification visually highlighting the updated portion of the first information. The method of claim 1.

3. visually highlighting the updated portion of the first information by surrounding the updated portion of the first information with a graphical element; The method of claim 2.

4. the first document is associated with a purchasing account, the portion of the first information is a balance of the purchasing account, and the updated portion of the first information is an updated balance of the purchasing account. The method of claim 1.

5. the first document is associated with a trip, the portion of the first information is trip information, and the updated portion of the first information is updated trip information; The method of claim 1.

6. the first document is associated with a user definition for enabling or disabling the updating of the first information; The method of claim 1.

7. After viewing the document notice, displaying, via a display device, a document management user interface; a first representation of the first document, the first representation of the first document including a first portion of the first document and not including a second portion of the first document; displaying the document management user interface including a first representation of a second document stored on the electronic device, the first representation of the second document including a first portion of the second document and excluding a second portion of the second document; receiving input for the first representation of the first document via the one or more input devices while displaying the document management user interface and while displaying the first representation of the first document; In response to receiving the input, displaying via the display device a second representation of the first document including a first portion of the first document and a second portion of the first document, the second portion of the first document including the updated portion of the first information; and further comprising: The method of claim 1.

8. a third document and a fourth document are further stored on the electronic device; the third document and the fourth document are related; the document management user interface includes the first representation of the first document, the first representation of the second document, a summary of the third document, and a stacked presentation associated with the third document and the fourth document. The method of claim 7.

9. receiving, via the one or more input devices, an input selecting the summary of the third document while displaying the document management user interface including the first representation of the first document, the first representation of the second document, the summary of the third document, and the stacked presentation associated with the third document and the fourth document; displaying, via the display device, a third representation of the third document that differs from the summary of the third document in response to receiving the input selecting the summary of the third document; The method of claim 8 further comprising:

10. receiving input for the third representation of the third document via the one or more input devices while displaying the third representation of the third document; displaying, via the display device, a fourth representation of the fourth document in response to receiving the input for the third representation of the third document; 10. The method of claim 9, further comprising:

11. the input to the third representation of the third document is a swipe input; The method of claim 10.

12. One or more programs which, when executed by one or more processors of an electronic device in communication with a display device and one or more input devices, cause the electronic device to perform the method of any one of claims 1 to 11.

13. 1. An electronic device comprising: one or more processors; a memory containing instructions, a memory, the instructions, when executed by the one or more processors, causing the electronic device to perform the method of any one of claims 1 to 11; , an electronic device.

Images