Systems and methods for managing relationships, organization, retrieval, and sharing of different types of content accessible on a computing device

Abstract

A system, method, and non-transitory memory are provided that are associated with managing content entries using a computing device. The method includes accessing a content entry from a content source via a link to the content entry, where the content entry is remote to the computing device; adding at least one of a tag, a memo, or a contact to associate with the content entry; posting at least one of a tag, a memo, or a contact associated with the link to the content entry as a record associated with the computing device in a database; and displaying the content entry via the accessed link associated with at least one of the posted tag, memo, or contact.

Description

Technical Field

[0001] This application relates to computing devices such as mobile devices, and the access and management of various content thereof. More specifically, this application is directed to systems and methods related to effectively managing the relationships, organization, acquisition, and sharing of different types of content accessible by computing devices such as mobile devices.

Background Art

[0002] Computing devices, particularly mobile devices (e.g., smartphones), are ubiquitous in today's society, have become integrated and very powerful, continuously improve in execution speed, and hold and / or access an unprecedented amount of different types of "content". For example, email, contacts in an address book / phone book, text (e.g., iPhone (registered trademark) / Android text or native text), direct messaging messages (e.g., WhatsApp, Viber, LinkedIn (registered trademark), etc.), photos, writings, music, videos, calendars and calendar appointments, writings (e.g., iPhone or native writings) and writings of other applications, posts on social networking services (SNS) (e.g., Facebook, etc.), shopping lists / carts from e-commerce services (e.g., Amazon, etc.), Real Simple Syndication (RSS) feeds (e.g., Feedly, Flipboard, etc.), website web pages (e.g., identified via a Uniform Resource Locator or URL), etc., which are hereinafter referred to as "content" or "types of content". However, the integration and management of the aforementioned heterogeneous content is still very primitive, and seamless integration and management that is centralized remains an illusion.

[0003] The types of the foregoing content are generally accessed and managed by various applications associated with the content and executed by a mobile device for searching, accessing, obtaining, and modifying the content, for example, via an application related to the type of the content. Accordingly, various types of content are generally fragmented on the mobile device. Currently, there is no systematic method to centrally and uniformly organize fragmented types of content, such as storing, searching, obtaining, and sharing content on a mobile device, as a specific content entry of a specific content type, so as to achieve seamless integration, organization, management, obtaining, and sharing of the content.

[0004] The integration of specific content related to a mobile device is limited. The native phone book application enables including specific types of content, such as phone number(s) of a contact, email address, company name, building address, date of birth, website uniform resource locator (URL), description, note, photo, and several other types of data, such as incoming call tone, text tone, date (e.g., anniversary), etc., in a contact record (i.e., contact) of the phone book application. A contact and / or its contact record can be associated with a person and / or a business. However, when not included in the contact record, specific types of content identified above, such as photos (stored and accessed by a photo album application), emails of an email application, SNS posts, music or video files of associated application(s), cannot be easily associated with or obtained in relation to the contact.

[0005] More specifically, the address book / phone book and the contacts recorded therein have conventionally presented only basic information such as phone numbers, email addresses, and notes. As described above, the content that can be stored in a contact (e.g., the address book / phone book of an iPhone or Android) is quite limited, and even if an address book / phone book is provided, the user cannot associate or form relationships between various content types and one or more pieces of content, whether it is a personal content story or a business-related content story. For example, the user cannot associate or form relationships (e.g., people and / or businesses) with suitable contacts assigned by the user, or generate or formulate a content story with multiple contacts for various content types accessible by a mobile device, and it cannot notify or provide the user with information regarding a specific contact or group of contacts based on its / their suitable association with various content types.

[0006] Furthermore, current technologies not only cannot generate relationships / associations, but also cannot organize and manage relationships and associations between content types and contacts, cannot obtain unified searchability and acquisition of various content types and one or more contacts related to the content, and furthermore, cannot share various content types and their associations / relationships to those various content types with one or more contacts.

[0007] Therefore, it is desirable to cause a paradigm shift in forming relationships and provide a robust system and method that uses a computing device such as a mobile device to provide functions for centralized management, organization, search, acquisition, and sharing of different types of content (content entries), and in addition, enables the formation and use of story development regarding the relationships of different types of content entries for one contact or multiple contacts, or one or more search terms. SUMMARY OF THE INVENTION

[0008] Systems and methods are provided related to effectively managing the relationships, organization, retrieval, and sharing of different types of content (content entries) accessible by a computing device such as a mobile device.

[0009] According to an embodiment, a method of managing content entries using a computing device is disclosed. The method includes accessing a content entry from a content source via a link to the content entry, wherein the content entry is remote to the computing device, adding at least one of a tag, a memo, or a contact to associate with the content entry, posting at least one of a tag, a memo, or a contact associated with the link to the content entry as a record associated with the computing device's database, and displaying the content entry accessed via a link associated with at least one of the posted tag, memo, or contact.

[0010] In some cases, accessing a content entry from a content source may include receiving a selection of a content type associated with the content entry, receiving a selection of a content source associated with the content type, receiving a selection of the content entry, and returning a link to the content entry.

[0011] The method may further include storing the content entry in a database and returning a link to the content entry stored in the database.

[0012] In some cases, accessing a content entry from a content source may include navigating to a web page in a web browser, performing the sharing function of the web browser in relation to the web page, receiving a selection of a content application in relation to the sharing function, and sharing a link associated with the web page as a link to the content entry with the content application, where the link associated with the web page as the thing to be shared is a link to the content entry.

[0013] In some cases, accessing a content entry from a content source may include receiving a selection of a content type associated with the content entry, receiving a link associated with the web page, and returning the link associated with the web page as a link to the content entry.

[0014] The method may further include generating a story development associated with a link to a content entry. In some examples, generating a story development associated with a link to a content entry includes receiving a selection of an address book content type from a plurality of content types, receiving a contact selected from a plurality of contacts associated with the address book content type, obtaining from a database one or more links to respective content entries associated with each of at least one other content type from the plurality of content types, wherein the link of each respective content entry is associated with the selected contact, obtaining, and generating a story development for the selected contact, wherein the story development includes one or more links to respective content entries associated with each of at least one other content type as obtained, and each respective content entry is accessible via one or more links from one or more content sources remote to the computing device, generating. In other examples, generating a story development associated with a link to a content entry includes receiving search terms, obtaining from a database one or more links to respective content entries associated with each of at least one content type from the plurality of content types, wherein each of the one or more content entries is associated with at least one of tags, notes, contacts, links, or other text data including the search terms, obtaining, and generating a story development for the search terms, wherein the story development includes one or more links to respective content entries associated with each of at least one content type, and each respective content entry is accessible via one or more links from one or more content sources remote to the computing device, generating.In a further example, generating a story progression associated with a link to a content entry includes receiving a selected tag, obtaining from a database one or more links to respective content entries associated with each of at least one content type from a plurality of content types, wherein the links of the respective content entries are associated with the selected tag, obtaining, and generating a story progression for the selected tag, the story progression including one or more links to respective content entries associated with each of at least one content type as obtained, wherein each of the respective content entries is accessible via one or more links from one or more content sources remote to the computing device, generating.

[0015] In some cases, the method can include sharing a content entry with a contact of a second computing device. In some examples, sharing a content entry with a contact of a second computing device includes generating a second record associated with the second computing device in a database, copying a link to the content entry to the second record including at least one of a tag, a memo, or a contact associated with the link, and notifying the contact of the second computing device that the content entry has been shared, wherein the second computing device can display the content entry as accessed via the link associated with at least one of the tag, the memo, or the contact, notifying.

[0016] According to another embodiment, a system for managing content entries is disclosed. The system includes a computing device and a memory device storing instructions that, when executed by the computing device, cause the computing device to perform the following operations. According to a further embodiment, a non-transitory memory storing instructions is disclosed, and the instructions, when executed by a computing device, cause the computing device to perform the following operations related to managing content entries.

[0017] The operations of the system and the non-transitory memory include accessing a content entry from a content source via a link to the content entry, where the content entry is remote to the computing device, adding at least one of a tag, a memo, or a contact to associate with the content entry, posting at least one of a tag, a memo, or a contact associated with the link to the content entry as a record associated with the computing device in a database, and displaying the content entry accessed via a link associated with at least one of the posted tag, memo, or contact.

[0018] In some cases, the operation of accessing a content entry from a content source may include receiving a selection of a content type associated with the content entry, receiving a selection of a content source associated with the content type, receiving a selection of the content entry, and returning a link to the content entry.

[0019] The operations of the system and the non-transitory memory further include storing the content entry in a database and returning a link to the content entry stored in the database.

[0020] In some cases, the operation of accessing a content entry from a content source may include navigating to a web page in a web browser, performing the sharing function of the web browser in relation to the web page, receiving a selection of a content application in relation to the sharing function, and sharing a link associated with the web page as a link to the content entry, where the link associated with the web page as the shared item is a link to the content entry. In other cases, the operation of accessing a content entry from a content source may include receiving a selection of a content type associated with the content entry, receiving a selection of a content source associated with the content type, receiving a link associated with the web page, and returning the link associated with the web page as a link to the content entry.

[0021] The operation of the system and the non - transient memory may further include generating a story progression associated with a link to a content entry. In some examples, the operation of generating a story progression associated with content includes receiving a selection of an address book content type from a plurality of content types, receiving a contact selected from a plurality of contacts associated with the address book content type, obtaining from a database one or more links to respective content entries associated with each of at least one other content type from a plurality of content types, wherein the link for each content entry is associated with the selected contact, obtaining, and generating a story progression for the selected contact, wherein the story progression includes one or more links to respective content entries associated with each of at least one other content type as obtained, and each content entry is accessible via one or more links from one or more content sources remote to the computing device, generating. In other examples, the operation of generating a story progression associated with a link to a content entry includes receiving search terms, obtaining from a database one or more links to respective content entries associated with each of at least one content type from a plurality of content types, wherein each of the one or more content entries is associated with at least one of a tag, a memo, a contact, a link, or other text data including the search terms, obtaining, and generating a story progression for the search terms, wherein the story progression includes one or more links to respective content entries associated with each of at least one content type, and each content entry is accessible via one or more links from one or more content sources remote to the computing device, generating.In other examples, generating a story progression associated with a link to a content entry may include receiving a selected tag, obtaining from a database one or more links to respective content entries associated with each of at least one content type from a plurality of content types, where the links of the respective content entries are associated with the selected tag, and generating a story progression for the selected tag, the story progression including one or more links to respective content entries associated with each of at least one content type as obtained, where each content entry is accessible via one or more links from one or more content sources remote to the computing device.

[0022] The operation of the system and the non-transitory memory may further include sharing a content entry with a contact of a second computing device. In some examples, the operation of sharing a content entry with a contact of a second computing device may include generating a second record associated with the second computing device in the database, copying a link to the content entry to the second record including at least one of a tag, a memo, or a contact associated with the link, and notifying the contact of the second computing device that the content entry has been shared, where the second computing device can display the content entry as accessed via the link associated with at least one of the tag, the memo, or the contact.

[0023] These and other objects, goals, and advantages of the present application will become apparent from the following detailed description of exemplary embodiments read in conjunction with the accompanying drawings.

[0024] Some embodiments are shown by way of example and not limitation in the figures of the accompanying drawings.

Brief Description of the Drawings

[0025]

Figure 1

Figure 2

Figure 2A

Figure 2B

Figure 2C

Figure 2D

Figure 2E

Figure 2F

Figure 2G

Figure 2H

Figure 3

Figure 3A

Figure 3B

Figure 3C

Figure 3D

Figure 3E

Figure 4

Figure 5

Figure 6

Figure 6A

Figure 6B

Figure 6C

Figure 6D

Figure 7

Figure 7A

Figure 8

Figure 8A

Figure 8B

Figure 8C

Figure 8D

Figure 9

Figure 9A

Figure 9B

Figure 10

Figure 10A

Figure 10B

Figure 11

[0026] This specification discloses systems and methods related to effectively managing the relationships, organization, acquisition, and sharing of various types of content accessible by computing devices such as mobile devices. In the following description, for the purpose of explanation, numerous specific details are set forth in order to provide a thorough understanding of exemplary embodiments or aspects. However, it will be apparent to those skilled in the art that the exemplary embodiments may be practiced without all of the specific details of the disclosure.

[0027] FIG. 1 shows a flowchart of an exemplary method 100 of associating various contents (content entries) or links to a content (content entry) selected or accessed by a computing device (e.g., a mobile phone, smartphone, etc.) with one or more of tags (plural possible), memos (plural possible), and / or contacts (plural possible), generating a database of a content management application, and / or creating / updating a record of a database in which a selected content (content entry) or a link to the selected or accessed content (content entry) is associated with tags (plural possible), memos (plural possible), and / or contacts (plural possible). The type of content defined above in this specification may be local to a content management application of a mobile device that executes the exemplary method 100 (e.g., stored or accessed by the content management application 316) in some cases, or may be managed by an application external to the content application that executes the exemplary method 100 in other cases.

[0028] In this specification, a link to a specific content (content entry) uniquely identifies the content (content entry) and enables the content management application 316 to receive or access it, for example, via the file name or location of the content (content entry), and / or to uniquely identify or distinguish the specific content (content entry) from other content (content entries) for access by the content management application, regardless of whether it is located on a computing device or outside the computing device. For example, the link can be a hyperlink, a Uniform Resource Locator (URL), or another type of link or methodology that can be used to identify and access content (content entries) of various content types, such as content type 616 shown in FIG. 6A, such as a photograph, video or music file, a writing, a document file (such as a PDF file), a web page, an email, etc.

[0029] For clarity and brevity, the content management application 316 (e.g., referred to as "Tokpee") that manages, organizes, retrieves, and shares the relationships, organization, retrieval, and sharing of different types of content (content entries) according to the disclosure of this application is referred to herein as the "content management application", "content management app", "content application", "content app", or simply the "application".

[0030] The exemplary method 100 begins at operation 102, where the user executes, on a computing device, a content management application 316 that manages, organizes, and associates one or more types of content (content entries) with one or more tags, one or more notes, and / or one or more contacts, among other features described herein.

[0031] In operation 104, if one or more content items (plural possible) (content entries), such as the content entry itself or a link to the content entry, are selected, they are received or accessed from the content source for posting to the content application 316. In particular, content (content entries) that are locally accessible to the computing device on which the content application 316 is executed (e.g., the computing device 402 shown in FIG. 4), such as stored in a computing device or cloud storage associated with the computing device, e.g., iCloud Photos or Google Photos, can be received or accessed via an exemplary method as shown in FIG. 2, while content (content entries) that are external to the computing device on which the application is executed can be received or accessed via an exemplary method as shown in FIG. 3, both of which will be described in more detail below. However, it should be noted that the selection of one or more content items or links to content (such as content entries) received or accessed for posting can be programmatically achieved in other ways as long as the content or link to the content (content entry) can be represented, referenced, accessed, and / or retrieved in the content application 316 for the management of relationships, organization, acquisition, and sharing associated with the content entry in accordance with the systems, methods, and / or methodologies disclosed herein.

[0032] Thereafter, exemplary method 100 proceeds to operation 106 where a determination is made regarding the action the user wishes to perform with respect to the selected content or the link to the selected content (content entry). The user can decide to associate or add one or more contacts, one or more tags, and / or one or more notes with the received or accessed content and / or the link to the content (content entry), as will be described in more detail shortly.

[0033] If it is determined in operation 106 that the user wishes to tag one or more contents or link contents (content entries) with one or more tags (for example, tags that are descriptive terms, symbols, or combinations thereof associated with the content entry), the method proceeds to operation 108, and the user can add one or more tags for association with one or more contents received or accessed in operation 104 or links to one or more contents (content entries). Examples of tagging a content or a link to a content with one or more tags will be described in more detail below with reference to FIGS. 2D and 2F. Next, method 100 proceeds to operation 114, as will be described in more detail later.

[0034] However, if it is determined in operation 106 that the user wishes to add one or more notes (for example, notes that are descriptive phrases, slogans, or sentences (s) associated with the content entry, or combinations thereof) associated with one or more contents or links to contents (content entries), exemplary method 100 proceeds to operation 112, and the user can add one or more notes associated with one or more contents received or accessed in operation 104 or links to contents (content entries). Examples of adding one or more notes associated with a content or a link to a content (content entry) will be described in more detail below with reference to FIGS. 2D and 2G. Next, exemplary method 100 proceeds to operation 114, as will be described in more detail later.

[0035] Finally, if it is determined in operation 106 that the user wishes to associate one or more contents, or links to contents (content entries), with one or more contacts, exemplary method 100 continues to operation 110, where the user can add (select) one or more contacts from a contact list (e.g., address book / phone book) that are associated with one or more contents received or accessed in operation 104 or links to contents (content entries). Examples of selecting one or more contacts associated with a content or a link to a content (content entry) are described in more detail below with reference to FIGS. 2D and 2E. Next, exemplary method 100 continues to operation 114, as will be described more immediately in detail below.

[0036] In operation 114, it is determined whether one or more actions related to the referenced association to the selected content(s) or links (if any) to the selected content(s) (content entries) have been completed, or whether one or more further actions related to the post should be cancelled. If it is determined in operation 114 that one or more further actions related to the post should be cancelled, method 100 continues to operation 118, as will be described more detail below.

[0037] However, if it is determined in operation 114 that one or more actions have not yet been completed, exemplary method 100 continues to operation 106, and one or more of operations 108, 110, and / or 112 may be repeated until it is determined in operation 114 that one or more actions related to the association to the selected content(s) or links (if any) to the selected content(s) (content entries) have been completed.

[0038] Alternatively, if it is determined in operation 114 that one or more actions have been completed, exemplary method 100 continues to operation 116, where the selected content or link to the content (content entry) is posted in association with any contact, tag(s), and / or memo(s). The posting creates the database 406 of the content application 316 and / or updates / creates a record 500 of the database 406 where the content or link to the content (content entry) is associated with one or more tags, one or more memos, and / or one or more contacts. For example, the association can be stored in the exemplary application database 406 of the application server / content provider 404 shown in FIG. 4 as an exemplary record 500 as shown in FIG. 5. Alternatively, the association to the content or link to the content (content entry) can be stored in a computing device (e.g., a mobile device, smartphone, etc.) such as a table, file, etc. As an example, as shown in FIG. 2C, a photo 220D or a link to the photo 220D (content entry) is associated with specific memo(s) 270, tag(s) 262, and contact(s) 246 as shown in FIG. 2H. Thereafter, the association can be managed, e.g., the association can be changed to reference more or fewer content or links to content, and / or one or more associations can be deleted, and / or one or more other associations can be added.

[0039] After that, in operation 118, at least one of the content entries associated with any tags (plural possible), memos (plural possible), and / or contacts (plural possible) that are posted is displayed. In some embodiments, one or more of the aforementioned associations can be immediately updated or applied in relation to the selected photo 220D (content entry) or the selected multiple photos 220A - 220D (content entries) when the association (plural possible) is posted. Or in some other embodiments, one or more of the aforementioned associations can be updated or applied when an update is executed, such as by using the update button 248, as will be described in more detail below with reference to FIG. 2H. Next, method 100 ends in operation 120. As an example, if the association has not been posted previously via operations 106 - 116, the content or the link to the content (content entry) (e.g., photo 220D or the link to photo 220D) can be displayed without any posted associations (e.g., memo (plural possible) 270, tag (plural possible) 262, and / or contact (plural possible) 246 as specifically shown in FIG. 2D). Alternatively, if one or more associations have not been posted previously via operations 106 - 116, the content or the link to the content (content entry) (e.g., photo 220D or the link to photo 220D) can be displayed with any of the posted associations (e.g., memo (plural possible) 270, tag (plural possible) 262, and / or contact (plural possible) 246 as specifically shown in FIG. 2H). In operation 118, the exemplary method 100 ends.

[0040] FIG. 2 shows a flowchart of an exemplary method 200 that returns one or more links to a selected content (content entry) from a selected content source to the exemplary method 100 as shown in FIG. 1. More specifically, the exemplary method 200 returns one or more links to the selected content (content entry) to operation 104 as specifically described above with reference to FIG. 1. The exemplary method 200 starts at operation 202.

[0041] In operation 204, a selection of the content type of content (content entry) for posting is received from a plurality of content types. The content type can be, as described below with reference to FIG. 6A, an address book (contacts), a photo, a writing, a web page, etc. selected from a plurality of content types 616 of the home page 614. For example, a selection of the content type "photo" 616B is received in operation 204. In operation 206, a selection of a content source associated with the selected content type can be received. For example, as shown in FIG. 2B, a selection of the "photo library" 218 is received via the camera button 216 in FIG. 2A, and the photo library is locally located, for example, in a computing device (e.g., the computing device 402 shown in FIG. 4) or cloud storage associated with the computing device (e.g., iCloud Photos or Google Photos). In operation 208, a selection of one or more of the content (content entry) from the selected content source or a link to the content entry is received. One or more content can be selected by the user via the content application 316. For example, a selection of photos 220A to 220D or a link to a photo is received from the photo library (e.g., via user selection) in a computing device (e.g., the computing device 402) or cloud storage associated with the computing device, as shown in FIG. 2C. As an example, the application server / content provider 404 can store the selected photo (content entry) or the link to the selected photo (content entry) in the application database 406, as shown in FIG. 4.

[0042] Thereafter, in operation 210, a determination is made as to whether the selection of content (content entry) from the selected content source has been completed. If it is determined that the selection has not been completed, exemplary method 200 continues with operation 208, and operations 208 - 210 are repeated until it is determined in operation 210 that the selection has been completed. For example, as shown in FIG. 2A, the camera button 216 is selected, and as shown in FIG. 2B, the selection of content source 218 (e.g., photo library) disposed on the computing device or in cloud storage associated with the computing device and associated with the selected content type (e.g., photo 616B) is received, and any additional photos or links to photos selected from the photo library are similarly shown in FIG. 2C. In a similar manner, additional photos (content entries), or links to selected (e.g., via user selection) photos (content entries), can be stored in application database 406 by server / content provider 404.

[0043] Thereafter, in operation 212, as shown in operation 104 of FIG. 1, a link to the content (content entry) selected from the selected content source is returned in relation to the post. Method 200 ends at operation 214.

[0044] The operations of method 200 are shown using content type "photo" 616B as shown in FIG. 6A for simplicity and clarity, but it should be noted that method 200 is still applicable to other types of content (e.g., including content entries of content type 616 as shown in FIG. 6A, videos, music, writings, document files, web pages, emails, etc.) accessible by computing device 402.

[0045] Figures 2A - 2H show an exemplary page for creating / updating a record 500 in a database 406 of a content application that associates a particular content (content entry) or a link to content (content entry) selected by a computing device 402 with one or more of tags (s), memo (s), and / or contact (s) according to FIGS. 1 and 2.

[0046] In one example, as shown on the exemplary home page 614 shown in FIG. 6A, a user can select a content type "Photo" 616B from multiple content types 616. Thereafter, as shown in FIGS. 2A and 2B, a selection of a content source associated with the selected content type may be received. In particular, as shown in FIG. 2A, when the camera button 216 is selected, the user can then select a photo library 218, as shown in FIG. 2B, as a content source locally located on a computing device (e.g., computing device 402) or cloud storage associated with the computing device (e.g., iCloud Photos or Google Photos). Thereafter, the user can select one or more photos (e.g., content entries or links to content entries) from the selected photo library 218. For example, photos 220A - 220D or links to photos can be selected from the selected photo library 218 of the computing device or cloud storage associated with the computing device as shown in FIG. 2C. Thus, the application server / content provider 404 can store the photo or the link to the photo in the application database 406 as shown in FIG. 4.

[0047] For example, the user selects photo 220D, which is displayed as shown in FIG. 2D. As further shown in FIG. 2D, content application 316 has the ability to associate the selected photo 220D, one or more contacts using contact function 222, one or more tags using tag function 224, and / or one or more notes using note function 226. Further, the user can use delete function 228 to delete a photo or a link to a photo from database 406. Note that content application 316 can obtain, store, and synchronize contacts 618 (content entries) of address book 616A (content type) as shown in FIGS. 6A and 6B with native address book / phone book contacts maintained on a computing device (e.g., computing device 402).

[0048] As shown in FIG. 2E, the user can associate or tag the contacts maintained by the content application 316 with the selected photo 220D. The user can directly type a contact in the input field 230, search for a contact using the search field 232 for any contact found to be displayed at position 237 for selection, use the button 234 to select one or more of the most recently tagged contacts for any of the most recently tagged contacts displayed at position 237 for selection, use the button 236 to select one or more of the contact tags from all the contact tags of the content application for the contact tags for selection displayed at position 237, and / or use the button 242 to select one or more contacts from the address book / phone book for the contact for selection displayed at position 237, thereby entering one or more contacts. When one or more contacts such as Alex Jones and / or John Smith are selected, the user can then use the post button 240 to post the selection of the contacts to the associated photo content. Otherwise, the user can cancel the association using the button 238. When posted, the contacts are associated with the selected photo (e.g., photo 220D), are displayed associated with the selected photo 220D, and thus indicate the association between the contacts at position 246 and the selected photo 220D.

[0049] The above example of tagging is shown in relation to one selected photo 220D (content entry), but it should be noted that tagging is done for all photos (content entries) selected on the page, as shown in FIG. 2C. For example, if photos 220A - 220D (content entries) or a link to a photo (content entry) is selected, the above-described tagging by the content application 316 posts a selection of contacts such as Alex Jones and John Smith to all the selected photos (such as photos 220A - 220D), while any one of the selected photos 220A - 220D (such as photo 220D) is associated with the posted associated contacts and is currently displayed, as particularly shown in FIG. 2E.

[0050] As shown in FIG. 2F, the user can also associate tags maintained by the content application 316 with a selected photo (e.g., photo 220D), or a plurality of selected photos (e.g., photos 220A - 220D). The user can enter one or more tags by directly typing the tag into the input field 250, searching for tags using the search field 252 for the labeled tags for selection displayed at position 237, using the button 254 to select one or more of the most recently selected tags for the selection - labeled tags displayed at position 237, and / or using the button 256 to select one or more tags from all the tags of the content application for the selection - labeled tags displayed at position 237. When a tag such as "bridge" is selected, the user can use the post button 260 to post the tag selection(s) to one photo (content entry) or a plurality of photos (content entries) to which the tag selection(s) are to be associated. Otherwise, the user can cancel the association using the button 258. When posted, the tag(s) are associated with the selected one photo (e.g., 220D) or a plurality of photos (e.g., photos 220A - 220D), and are displayed in association with one of the selected photos 220D or any one of the selected photos 220A - 220D (e.g., photo 220D), thus indicating the association of the selected photo 220D at position 262 with the tag(s). As specifically shown in FIG. 2F, now the contact and the tag are associated with the photo 220D (content entry) at positions 246 and 262 respectively. Similarly, the selected contact and tag are associated with all the selected photos (e.g., 220A - 220D).

[0051] As shown in FIG. 2G, the user can associate a note maintained by the content application 316 with a selected photo (e.g., photo 220D), or a plurality of selected photos (e.g., photos 220A - 220D). The user can input a note, for example, a note that describes the content of a single selected photo (e.g., photo 220D) or the selected photos (e.g., 220A - 220D), by directly typing the text of the note into the note input field 264. When the note as shown in FIG. 2G is completed, the user can then use the post button 268 to post the note to the associated photo 220D (content entry) or the plurality of associated photos 220A - 220D (content entries). Otherwise, the user can cancel the association using the button 266. When posted, the note(s) is associated with the single selected photo 220D or the plurality of associated photos 220A - 220D, and is displayed associated with one of the single selected photo 220D or the selected photos 220A - 220D (e.g., photo 220D), thus showing the association between the photo 220D selected at position 270 and the note(s). As specifically shown in FIG. 2G, now the contact, tag, and note are each associated with the photo 220D (content entry) at positions 246, 262, 270 respectively. Similarly, the selected contact, tag, and note are associated with all of the selected photos (e.g., 220A - 220D).

[0052] As described with reference to FIGS. 2A - 2G, when any one or more of the associations are completed, or when all associations are completed, the associations can be updated or applied with respect to the selected content photo 220D (content entry) or multiple selected photos 220A - 220D (content entries) of the database 406 using the update button 248. In some embodiments, when one or more of the above associations are posted, such as by using the respective posting buttons 240, 260, and / or 268 as particularly shown in FIGS. 2E - 2G, they can be immediately updated or applied with respect to the selected content photo 220D (content entry) or multiple selected photos 220A - 220D (content entries) of the database 406.

[0053] As shown in FIG. 2H, all posted associations are tagged to the photo 220D (content entry) or multiple selected photos 220A - 220D (content entries), while the first selected photo 220A from the multiple selected photos 220A - 220D in FIG. 2C is illustrated in FIGS. 2D - 2H. The associations can be managed, such as being modified and / or updated using the functions 222, 224, 226, and / or 248 as described in more detail above. For example, the deletion of any of the associations of contacts, tags, and / or memos can be performed in the respective input fields 230, 250, 264 using the delete symbol "x" to delete the association. Note that the delete symbol is not shown in relation to the memo input field 264 in FIG. 2G. Further, the content photo 220D can also be deleted (e.g., from the database 406) using, for example, the delete button 228 as particularly shown in FIG. 2H.

[0054] The functionality described above with respect to FIGS. 2A - 2H may be applicable to other types of content (e.g., various types of content entries) accessible by a computing device (e.g., computing device 402). In particular, for the sake of brevity and clarity, the functionality is described using the content type "Photo" 616B as shown in FIG. 6A, but the functionality still applies to other types of content accessible by computing device 402 (e.g., videos, music, scribbles, document files, web pages, emails, etc., including content entries of content type 616 as shown in FIG. 6A).

[0055] FIG. 3 shows a flowchart of another exemplary method 300 that returns a link to a selected content (content entry) from a selected content source to the exemplary method 100 as shown in FIG. 1. More specifically, the exemplary method 300 returns a link to the selected content entry to operation 104 as specifically described above with reference to FIG. 1. The exemplary method 300 begins at operation 302.

[0056] In operation 304, a selection of a content source or content provider associated with the content for posting is received. For example, a news content source (e.g., Fox news) is selected as shown by content provider 414 in FIG. 4. The content source may not be local to the computing device (e.g., computing device 402), but it can be accessed by the computing device 402 via network 418 using, for example, a web browser (e.g., Safari of the Apple iPhone shown in FIG. 4, Chrome of Android™, or any other browser installed on a computing device such as computing device 402). In operation 306, a selection of a specific content (content entry) from the selected content source or a link to the content entry is received. For example, web page 312 is selected from content provider 414 as shown in FIG. 3A. Based on the foregoing example, the user can navigate to or simply access web page 312 of content provider 414 via network 418 using a web browser in accordance with operations 304 and 306. Thereafter, in operation 308, a link to the selected content entry (web page 312) from the selected content source (content provider 414) is returned in relation to the post as shown in operation 104 of FIG. 1.

[0057] For example, as specifically shown in FIGS. 3A and 3B, a Uniform Resource Locator (URL) for a web page 312 (content entry) can be returned to a content application by using a share button 314 to execute the sharing function of a web browser and then selecting from a list of available applications a content application 316 (“Tokpee”), and a link to the content is shared with the content application 316 for that application. Accordingly, a link identifying the web page 312 of the network 418 is returned to operation 104 of the exemplary method 100 as specifically shown in FIG. 1. When selected, the selected content application 316 is executed, where the contacts and tag associations of operations 106, 108, 112 of FIG. 1 can be added. For example, the contacts and tag associations in operations 106, 108 can be added as specifically shown in FIGS. 3D and 3E, respectively. In one example, the memo association in operation 112 of FIG. 1 can be added as shown in FIG. 3C. In particular, the memo association in operation 112 can be extended to include basic information 318 related to a type 318A, a title 318B, a description 318C, and a URL 318D that describe the content entry shared with the content application 316. Method 300 ends at operation 310.

[0058] The operations of method 300 are shown using links to web pages for brevity and clarity, but nevertheless, it should be noted that method 300 may be applicable to other types of content accessible by a computing device 402 via a network 418 (e.g., videos, music, scribbles, document files, emails, etc., including content entries of content type 616 as shown in FIG. 6A).

[0059] Figures 3A - 3E show an exemplary page for creating / updating a record 500 in a database 406 of a content application 316 that associates a specific content (content entry) or a link to content (content entry) selected by a computing device 402 with one or more of the tag(s), memo(s), and / or contact(s) according to FIGS. 1 and 3.

[0060] In an example related to receiving an association of a specific content (content entry) 104 and a memo of operation 112 in FIG. 1, the user can select the content type "Web" 616D from a plurality of content types 616 as shown in the exemplary home page 614 of FIG. 6A, and can select to add a specific web page (content entry) associated with the content type via a selector (not shown). When a web page (content entry) is selected and added, a blank page similar to the page shown in FIG. 3C is displayed to the user. The user can input basic information 318 for a specific content entry (e.g., a news web page) from a specific content source or provider (e.g., Fox News), such as a title 318B, a description 318C, and a URL 318D. The content type 318A of the basic information 318 can be automatically displayed as "Web" based on the previous content type selection or can be pre - input, and / or can be omitted from the page of FIG. 3C. Thereafter, the content entry can be posted using a post selector (upper right of the page).

[0061] In another example related to receiving an association of a specific content (content entry) 104 and the memo of operation 112 in FIG. 1, the user can select a news content source or provider 414 (e.g., Fox news) by using a web browser, etc., and can navigate to a specific content web page 312 (content entry) from the content provider 414, or, as particularly shown in FIG. 3A, enter the address of the web page 312 into the web browser to simply access the web page 312 of the content provider 414. Then, as shown in FIGS. 3A and 3B, the user clicks the share button 314 of the web browser, and then selects a content application 316 ("Tokpee") from the list of available applications to share a link (URL) to the content entry (web page 312) with the content application ("Tokpee") 316. When the content application 316 is selected and executed, the page shown in FIG. 3C is displayed, and the user can then enter the title 318B and description 318C of the web page 312. The content type 318A can be automatically entered as "web" based on the content type and / or content source. Similarly, the link to the web page 312 (content entry) shared with the content application 316 can also be automatically entered (e.g., URL 318D). Thereafter, the content entry can be posted using the post selector (upper right of the page).

[0062] In any of the foregoing examples, the association of one or more contacts can be added via the contact function 222, as shown in FIG. 3D, and the association of one or more tags can be added via the tag function 224, as shown in FIG. 3E. The association of contacts and tags is described in detail with respect to FIGS. 2E and 2F, and as shown in FIGS. 3A - 3E, their descriptions are incorporated herein in their entirety as if they were fully described herein with respect to the content (e.g., web page 312). As shown in FIG. 3C, the association of a memo can be extended to include basic information 318, wherein it should be noted that the basic information related to the type, title, and description describes the content entry (web page 312) that is shared with the content application 316.

[0063] The foregoing functionality shown in FIGS. 3A - 3E may be applicable to other types of content (e.g., various types of content entries) accessible by a computing device (e.g., computing device 402) across the network 418. In particular, for the sake of brevity and clarity, the functionality is described using the content type "web" 616D as shown in FIG. 6A, but it should be noted that the functionality is still applicable to other types of content accessible by the computing device 402 (e.g., including content entries of the content type 616 as shown in FIG. 6A, videos, music, writings, document files, emails, etc.).

[0064] FIG. 4 shows a block diagram of an exemplary system 400 for managing the relationships, organization, acquisition, and sharing of different types of content (content entries) accessible by one or more computing devices (e.g., computing devices 402, 403), such as mobile devices, smartphones, or other computing devices (e.g., personal computers, laptops, etc.). The exemplary system 400 includes exemplary computing devices 402, 403, an application server / content provider system 404 including an application database 406, and one or more content providers 408 - 416. Although only some exemplary computing devices 402, 403 are shown in FIG. 4, it should be noted that the system 400 may include multiple different computing devices capable of performing the functionality described herein. The application server / content provider 404 of the system 400 and the content providers 408 - 416 may be considered to provide different types of content (content entries) in relation to the content sources accessible by the computing devices 402, 403 in connection with the functions and / or methodologies specifically described herein.

[0065] The computing devices 402, 403, the application server / content provider 404, and the content providers 408 - 416 can communicate via a network 418. The network can be the Internet, a wide area network (WAN), a local area network (LAN), and various combinations thereof, and / or other conventional network technologies (e.g., satellite), and / or technologies not yet developed and / or deployed. One or more computing devices (e.g., computing device 402 or 403) can generally connect to the network 418 via a wired or wireless connection, such as Wi-Fi or cellular technology, which may include 4G, 5G, LTE, etc., and / or wired / wireless technologies not yet developed and / or deployed.

[0066] Computing devices 402, 403 can be any electronic device (such as a mobile device) that can be connected to a network 418 (such as the Internet, WAN, LAN, etc.), and in particular, can be a smartphone or tablet computer (such as an iPhone, iPad (registered trademark), etc.) that can be connected to the network 418 via a wired or wireless connection using one or more of the aforementioned technologies. In some embodiments, one or more of the computing devices 402, 403 can also be a conventional computer such as a desktop computer or a laptop computer.

[0067] Computing devices 402, 403 can execute a content management application 316, which provides effective management of the relationships, organization, acquisition, and sharing of different types of content (content entries) accessible by the computing devices 402, 403. In some embodiments, the content management application 316 can be an application that is fully resident on the computing device (e.g., computing device 402 or computing device 403) and is self - contained when performing the functions described herein (e.g., without communicating with the application server / content provider 404 and / or the application database 406). In other embodiments, the content management application 316 can be an application that is resident on the computing devices 402, 403, which can call specific functions via an API provided by the application server / content provider 404, or can be an application that is partially or fully resident on the application server / content provider 404.

[0068] The application server / content provider 404 includes or can access an application database 406. The application server 404 can receive and execute calls from computing devices 402, 403 via an API or the like to perform the methods, functions, and / or operations related to other methods described herein. The application database 406 can store, associate, organize, retrieve, and share specific content (content entries) or links to content entries, such as contacts, photos, web pages, etc., accessible by the application 316 shown and described herein. More specifically, the database 406 can store relationship records 500 that can be used to associate content (content entries) or content links (links to content entries) with specific information and other content or information managed by the application 316. Exemplary database records 500 will be described in more detail below with reference to FIG. 5. In some embodiments, the database 406 can be stored locally on a computing device (e.g., computing device 402 or computing device 403), can be locally accessible by the computing device (e.g., via a direct wired / wireless connection), or can be directly accessible by the computing device via the network 418 (e.g., without communicating with the application server / content provider 404), and the content management application 316 can thus perform the functions described herein by communicating with such an application database 406.

[0069] The one or more content providers 408-416 can include one or more email providers 408 (e.g., Gmail, Hotmail, etc.), one or more video service providers 410 (e.g., YouTube™, Apple TV, etc.), one or more online shopping and / or auction providers 412 (e.g., Amazon, eBay, etc.), one or more news providers 414 (e.g., CNN, Fox news, etc.), and one or more social media providers 416 (e.g., Facebook, Twitter, etc.). It should be noted that the foregoing list of content providers is not exhaustive, and the system 400 can include and / or be readily extended to accommodate the types of content (content entries) listed, as well as one or more additional types of content providers and / or additional types of content (content entries), such as additional content providers for the exemplary content types shown in the home page 614 of FIG. 6A.

[0070] FIG. 5 is an exemplary record 500 of an exemplary database 406 of a content application 316 used to manage the relationships, organization, acquisition, and sharing of different types of content (content entries) accessible by computing devices 402, 403. The exemplary record 500 may be maintained in the application database 406 and may include fields such as a content link 502 for the content (content entry), basic information 504 associated with the content entry (e.g., type, title, description, and URL, as well as any additional information such as creation / access date, etc.), one or more tags 506 associated with the content entry, one or more contacts 508 associated with the content entry, and one or more notes 510 associated with the content entry, and may be related. In some embodiments, the note field 510 may maintain the basic information 504 associated with the content entry, and the basic information 504 may be omitted. Multiple records may be maintained for different content entries or links to content entries managed by the application 316 of a computing device (e.g., computing device 402).

[0071] FIG. 6 shows a flowchart of an exemplary method 600 for generating a story expansion in relation to a selected content entry (e.g., contact 620) of a selected content type (e.g., address book 616A) selected from a plurality of content types 616, as shown in FIGS. 6A and 6B.

[0072] In operation 602, exemplary method 600 begins and related application 316 is executed. In operation 604, a selection of a content type (e.g., address book 616A) for search and / or retrieval is received from a plurality of content types 616 managed by content application 316. For example, a user can select address book 616A managed by related application 316 from home page 614 as particularly shown in FIG. 6A. In operation 606, a list of content entries (e.g., contacts 618) associated with the selected content type (e.g., address book 616A) is displayed. For example, contacts 618 are displayed from address book 616A as particularly shown in FIG. 6B.

[0073] In operation 608, a selection of a content entry is received. For example, a user can select a particular content entry (e.g., contact 620) managed by related application 316, and the selection can be achieved by selecting a content entry (e.g., contact 620) from the list of displayed content entries (e.g., contacts 618), or by searching for a contact of a particular content entry (e.g., contact 620) from the list of available content entries (e.g., contacts 618) (e.g., full / partial text search), followed by search function 622 and selecting a content entry (e.g., contact 620) from the results of the search (not shown) as described in more detail with reference to FIG. 6B.

[0074] Subsequently, in operation 610, a story expansion is generated for the selected content entry (e.g., contact 620), which includes one or more other content types (e.g., photo 616B) and their related content (e.g., photos 220B and 220D), which are associated with and / or related to the selected content entry (e.g., contact 620), as will be described in more detail with reference to FIGS. 6C and 6D. For example, for the selected content entry (e.g., contact 620), other content types and their related content are retrieved and displayed in the generated story expansion, as described in more detail with reference to FIG. 6A, e.g., photo content (e.g., photos 220B, 220D) associated with photo 618B of the content type, writing content related to writing 616C of the content type, web content related to web 618D of the content type, shopping content (e.g., web page) related to shopping 618I of the content type, video content related to video 618G of the content type, file content related to file 618K of the content type, and any other content type and the content related to that content type.

[0075] As specifically shown in FIG. 6C, the story expansion content can be summarized to glimpse the content types related to the content entry (e.g., contact 620) for which the story expansion was generated and their associated content. Method 600 ends at operation 612.

[0076] Note that the story development can be generated for any other selected content entry of the content type, which can be selected from a plurality of content types 616 as particularly shown in FIG. 6A. For example, the story development can be generated for a specific selected photo from the content type photo 616B, or a specific selected writing from the content type writing 616C,..., a specific selected video from the content type video 616G,..., or a specific selected email from the content type email 616L, etc. The content types related to and constituting the story development of the selected content type may be different based on the initially selected content type, that is, the story development of photos, writings, videos, emails, etc. may include different content types and their associated content. However, the important point to note is that each story development of the selected content type includes at least one content type and its associated content.

[0077] FIGS. 6A - 6D show exemplary pages for generating story developments related to selected content entries of selected content types from a plurality of content types according to FIG. 6.

[0078] When the user executes the content application 316, a home page 614 is displayed as particularly shown in FIG. 6A. In one example, the user can select a content type (e.g., address book 616A) from a plurality of content types 616 managed by the content application 316. Thus, as shown in FIG. 6B, a list of content entries (e.g., contacts 618) associated with the selected content type (e.g., address book 616A) is displayed. As further shown in FIG. 6B, the user can select a specific content entry (e.g., contact 620) from the list of contacts in the address book 616A or search for a specific contact (e.g., using a full / partial search) from the list of available contacts using the search function 622. The total number of content entries (contacts) is shown as reference number 624 in FIG. 6B. Note that a similar page for content entries can be displayed in relation to other content types 616 that may be selected, enabling user selection of content entries as described.

[0079] When a user selects a content entry (e.g., contact 620), the content application 316 generates a story expansion for the selected content entry (e.g., contact). In particular, the story expansion includes information about the content entry (e.g., the name, phone number, etc. of contact 620) as shown on the pages in FIGS. 6C and 6D, and one or more content types that were previously associated with and / or related to the selected content entry (e.g., contact 620), and the content associated therewith. For example, for the selected contact 620, content entries of other content types are retrieved using record 500 of the application database 406, including photo content type 618B and associated content photos 220B, 220D, written content type 616C and associated written content, web content type 618D and associated web content, shopping content type 618I and associated shopping content (e.g., web page), video content type 618G and associated video content, file content type 618K and associated file content (e.g., file), and as particularly shown in FIG. 6A, any other content type of content type 616 and its associated content, etc., are displayed as generated in the story expansion. For example, as shown in FIGS. 6C and 6D, only a specific content type 626 from content type 616 is associated with the content entry (e.g., contact 620), and thus is only shown in the story expansion for the selected contact 620.

[0080] As shown particularly in the story progression of FIG. 6C, content types 626 and their content are shown in summary or in total, and a glimpse of the story of the content types and their content associated with the content entry (e.g., contact 620) for which the story progression was generated is shown. If a content type includes multiple content, note that only some may be shown for clarity, and the rest are viewable by the user by clicking "Show All" in FIGS. 6C and 6D. For example, the user can click "Show All" for content type photo 618B, and if it is associated with, for example, contact 620, all content entries (e.g., photos) associated with the content entry (e.g., contact 620) are shown, such as photos 220A - 220D as shown in FIG. 2C. Further, the user can return to the home page 614 using the home page button 628, or can follow the page trail and return using the back link (e.g., "<") at the top of the pages in FIGS. 6B - 6D.

[0081] Finally, with the search function 617 (e.g., upper right) shown in FIG. 6A, the user can search for one or more search terms from the text data associated with the content entries of content type 616 managed by the application 316, and generate a story progression related to or associated with the search terms across multiple content types 616 and their associated content entries, as will be described in more detail below with reference to FIGS. 7 and 7A.

[0082] FIG. 7 shows a flowchart of an exemplary search method 700 that performs a search for text data associated with content entries of content type 616 managed by content application 316 using application database 406 and generates a story expansion associated with the search terms of the search. The story expansion includes content entries of the content type resulting from the search. The exemplary method 700 begins at operation 702, and as shown in FIG. 6A, the user clicks on search function 617 and a search is performed in database 406 or on a computing device (e.g., computing device 402) for all content entries associated with content type 616 maintained by content application 316. In response, a page 712 is displayed, as particularly shown in FIG. 7A.

[0083] At operation 704, search terms are received for performing a search of the text data associated with the content entries of content type 616 managed by content application 316. As an example, the user enters the search term "conservative" in search field 718 of page 712 and then presses the return key or clicks on the search glass to perform the search, as shown in FIG. 7A. Thus, at operation 706, a search is performed of the content of content type 616 maintained by application 316 of application database 406, e.g., a search of any text data indicated by or associated with the content entries of content type 616 (e.g., tags, memos, any text data of contacts, and basic information such as the type of link to the content entry, title, description, and search for search terms of the URL address).

[0084] Subsequently, in operation 708, a story expansion associated with the search term is generated, and the story expansion includes content (content entries) of all content types that contain the search term in the text information associated with the content. For example, page 712 displays a story expansion 720 that includes a content type web 618D and related content entries (e.g., web pages) associated by the tag "conservative", as shown in FIG. 7A. Page 712 may include all content (content entries) of all content types that contain the search term in the text data of the content entry, such as any content entry of content type 616, as shown by page 614 in FIG. 6A. It should be noted that the exemplary method 700 ends at operation 710.

[0085] FIG. 7A shows an exemplary page 712 that performs an exemplary search of content (e.g., content entries) of one or more content types 616 managed by content application 316 and generates a story expansion 720 that includes one or more content entries obtained from the search. In one embodiment, the search can be performed on all content entries of all content types 616, as shown in FIG. 6A. In another embodiment, the search can be performed on all content entries (e.g., contacts) of a specific content type (e.g., address book 616A), as specifically shown in FIG. 6A. In this regard, page 712 includes a selection of the type of search to be performed, such as a search of all content 714 of the content application 316 (e.g., content entries of content type 616), or a search of content associated with a specific content type (e.g., contacts) 716. As shown on page 712, a search of all content of the content application is selected at selection 714, and a search of content associated with a specific content type (e.g., contacts) is selected at selection 716.

[0086] When a search type is selected, search terms associated with the search terms can be entered into the search field 718, and as shown in FIG. 7A, the Enter key can be pressed or the search glass can be clicked to execute the search. The search terms to be searched can be included in any one or more text data (text fields) of tags, memos, contacts, and / or basic information, the type, title, and description associated with the content entry, and / or can be included in the link to the content entry (for example, included in or associated with the URL for the content entry).

[0087] In an example of searching for content and generating a story development related to the search terms, the user enters "conservative" in the search field 718 and executes the search as shown in FIG. 7A (for example, pressing Return or clicking the search glass). The search is performed, for example, by searching for any text information indicated by the content (content entry) of different content types (for example, including tags, memos, contacts, and basic information, the type, title, description, and address of the link to the content entry). Accordingly, a story development associated with the search terms is generated, and the story development includes all content types and content entries for each of the content types, and includes the search terms in any text information associated with the content entry. For example, page 712 displays a story development 720 that includes the content type web 618D and an associated content entry (for example, a web page) associated by the tag "conservative" as shown in FIG. 7A. Similarly, the story development 720 can include one or more other content entries of the content type 616 as shown in FIG. 6A. For example, the generated story development 720 can include photos, writings, SNS posts, files, emails, etc., which can include the search terms in the text data.

[0088] The user can select by clicking on a content type (web), title (such as Foxnews or Newsmax), or tag (such as "conservative"), thereby generating a further story expansion associated with the first available contact containing the clicked content type, title, or tag, as shown, for example, in FIGS. 6C and 6D. Further, when any link of the story expansion 720 (such as a Foxnews link or a Newsmax link) is clicked, the application 316 can then open the content indicated by the clicked link, for example, open the web page indicated by the Newsmax link in a web browser.

[0089] Accordingly, if the user decides to perform a search for a specific content entry (such as a contact) by selection of the search 716, the content application 316 enables the user to select a contact (such as contact 620) via a page 616A of FIG. 6B, for example, and then enables a search of the content entry of the selected contact to be performed against the search terms entered into the search field 718, as already explained above. Accordingly, the search results are story expansions such as the story expansion 720 associated with the contact related to the search terms.

[0090] FIG. 8 shows a flowchart of an exemplary method 800 for generating a story expansion from content (such as a content entry) associated with another story expansion, where the story expansion has a shared content history.

[0091] In operation 802, exemplary method 800 begins. In operation 804, a selection of a content type is received from a plurality of content types for search / retrieval. For example, as particularly shown in FIG. 6A, the user selects photo 616B from content type 616. In operation 806, there are displayed content entries associated with the selected content type. For example, page 818 displays content entries (e.g., photos) as shown in FIG. 8A. In operation 808, a selection of a content entry is received. For example, as shown in FIG. 8A, a content entry (e.g., photo 220B) is selected.

[0092] In operation 810, contacts and / or tags that are tagged or associated with the selected content entry (e.g., photo 220B) are displayed in relation to the selected content entry. For example, tag "Ranking" 624 and several contacts "Alex Jones" and "John Smith" are tagged to photo 220B, shown as respective numbers 620 and 622, and are displayed associated with photo 220B. In operation 812, a selection of tagged data such as contacts 620, 622 or tag 624 is received from the displayed content entry 220B.

[0093] After that, in operation 814, a story expansion is generated for the selected tagged data that includes content (e.g., content entries) associated with at least one content type. In one example, when a contact 620 or contact 820 in FIG. 8B is selected, a story expansion for the selected contact 620 that includes content entries associated with at least one content type, or a story expansion for the selected contact 820 is generated. For example, the story expansion for contact 620 is shown in FIGS. 6C and 6D, and the story expansion for contact 820 is shown in FIGS. 8C and 8D. In particular, the story expansion for contact 620 includes the associated contact information, content type and a specific set of associated content entries, and a summary of the story as shown in FIGS. 6C and 6D, while the story expansion for contact 820 includes the associated contact information, content type and another specific set of associated content entries, and a summary of the story as shown in FIGS. 8C and 8D. Note that since content entries (e.g., photo 220B) are associated with several contacts 620, 820, the aforementioned contacts have a shared content history that includes, for example, shared content entries (e.g., photo 220B). Note that content entries of various content types can constitute the shared history between contacts 620, 820. Further note that the aforementioned story expansions for contacts 620, 820 have a shared content history.

[0094] In another example, when tag 624 in FIG. 8B is selected, a story progression is generated for the selected tag 624 that includes content (content entries) associated with at least one content type tagged with the selected tag 624. For example, photos 220A and 220B shown in FIG. 8A are associated with the common tag "ranking" between them, and thus, in addition to any other content entries associated with tag "ranking" 624, can be retrieved (not shown) in connection with the generation of the story progression for tag "ranking" 624, and the content entries can be of different content types 616 as particularly shown in FIG. 6A. Note that the content types and associated content forming the generated story progression are not exhaustive and / or are not limited to the aforementioned photos, and thus, any other content of application 316 tagged with tag 624 can be retrieved, and in this way, a story progression for tag 624 can be formed. Note that the aforementioned story progressions for contacts 620, 820 and the story progression for tag 624 have a shared content history.

[0095] FIGS. 8A-8D show exemplary pages for generating a story progression from content entries associated with another story progression, and the story progression has a shared content history according to FIG. 8.

[0096] In one example, a user can select photo 616B from other content types 616, particularly as shown in FIG. 6A. Application 316 presents page 818 that displays photos 220A-220D, particularly as shown in FIG. 8A. As an example, the user can select photo 220B from the photos displayed on page 818.

[0097] As shown in FIG. 8B, any contacts 620, 820 and / or any tags 624 that are tagged to or associated with the selected photo 220B are displayed in relation to the photo 220B. By way of example, the user can select the contact 620 from the photo 220B.

[0098] As specifically shown in FIGS. 6C and 6D, a story expansion is generated for the selected contact 620, and the story expansion includes various contents associated with at least one content type, for example, content types 618B, 616C, 618D…, 618K. Since the photo 220B is the shared content of the content type photo 616 among the contacts 620 and 820, the user can instead select the contact 820 from the photo 220B in FIG. 8B, and the story expansion is generated for the selected contact 820 as specifically shown in FIGS. 8C and 8D.

[0099] It should be noted that although the story expansions of the contacts 620 and 820 are partially different, the aforementioned story expansions can be said to overlap in specific content or have a specific shared content history. For example, the story expansion of the contact 620 is shown in FIGS. 6C and 6D, and the story expansion of the contact 820 is shown in FIGS. 8C and 8D. As shown in the aforementioned figures, the photos 220B and 220D are associated with the contacts 620 and 820, and thus, the aforementioned contacts 620, 820 overlap in the photos 220B and 220D or have a specific shared content history. It should be further noted that other contents of various content types can overlap and thus can be included in the shared content history of multiple contacts.

[0100] In another example, referring to the story development of contact 620 as shown in FIGS. 6C and 6D, which can be generated as described herein, the user can select photo 220B of content type 618B. Upon selection, the page of FIG. 8B is presented for the selected photo 220B, showing the associated contacts 620 and 820, as well as the associated tags 624. As an example, the user can select contact 820, and thus the story development of contact 820 can be generated as described herein and as particularly shown in FIGS. 8C and 8D.

[0101] The generation of story development using shared content is shown using photos for simplicity and clarity, but note that any other shared content of content type 616 (e.g., content entry) as shown in FIG. 6A can similarly overlap in the shared content history of the various story developments generated as disclosed herein. Thus, the shared content can be used for the generation and switching of various story developments that include the shared content.

[0102] FIG. 9 shows an exemplary method 900 of sharing a selected content entry from a content application 316 of one computing device 402 as associated with a selected contact with a content application 316 of another computing device 403, which includes zero or more tagged contacts, tags, and / or notes associated with the selected content entry.

[0103] Method 900 begins at operation 902, where a user executes content management and relationship application 316 (e.g., tokpee) on computing device 402. At operation 904, a selection of a content type of content (e.g., a content entry) for sharing is received from a plurality of available content types. For example, the content types can be contacts, photos, writings, web pages, etc., as described herein with reference to content types 616 of content management application 316, as particularly shown in FIG. 6A. For example, as shown in FIG. 6A, a selection of content type "photo" 616B is received.

[0104] At operation 906, content entries associated with the selected content type are displayed. For example, photos 220A - 220D or links to these photos are received from application server / content provider 404, and the photos or links to the photos are stored in application database 406, as shown in FIG. 4. At operation 908, a selection of a content entry is received from the displayed content entries. For example, the user can select photo 220D, as particularly shown in FIG. 2C. In this regard, it should be noted that, as described herein with reference to FIGS. 2A - 2H, content photo 220D can be tagged with zero or more associations, or be tagged. For example, photo 220D shown in FIG. 2D has no associations tagged to photo 220D, while photo 220D shown in FIG. 2H includes various posted associations tagged to content photo 220D, including contact 246, tag 262, and memo 270.

[0105] In operation 910, a selection to share a selected content entry (e.g., photo 220D) with one or more contacts is received. For example, as specifically shown in FIG. 2H, the user can select share button 244. In operation 912, a list of contacts available for sharing photo 220D is displayed. For example, as specifically shown in FIGS. 6B and 9A, a list of contacts 618 in address book 616A can be displayed. In operation 914, a selection of at least one contact is received from the list of contacts 618. For example, as specifically shown in FIG. 9A, any one or several of contacts 902, 904, 620 of contacts 618 can be selected. In operation 916, an instruction to share the selected content entry (e.g., photo 220D) with the at least one selected contact is received. For example, a share instruction can be indicated by selection of share button 906 at the bottom of the contact list, or sharing can be cancelled by selection of cancel button 908 as specifically shown in FIG. 9A.

[0106] In operation 918, the selected content entry is copied to the shared item content type 616M of at least one of the selected contacts (for example, the contacts can be associated with the computing device 403, and as specifically shown in FIG. 6A, other contacts can be associated with each computing device of the system 400), and includes zero or more of the tagged contacts, tags, or notes of the selected content entry. For example, the selected content entry and any associations tagged to the content entry (e.g., photo 220D) can be copied to the application database 406 of the application server / content provider 404 in relation to the computing device of the selected contact (e.g., the computing device 403 associated with a particular contact). Further, zero or more of the tagged contacts, tags, or notes of the selected content entry can also be associated with the copied content entry and copied to the application database 406. In operation 920, at least one of the selected contacts is notified that specific information of a specific content type has been shared. For example, the notification can be sent to the computing device 403 (e.g., an email message, a text message, or another type of message or notification). In one embodiment, the notification (e.g., a text message) can include a link to automatically execute the content application 316 on the computing device 403, or if the content application 316 is not yet installed, install it first and then execute the content application 316, and then automatically select the content type "shared item" 616M and request to automatically display the content entry on the computing device 403. Finally, in operation 922, the status of the sharing with at least one contact can be shown to the user of the computing device 402 as specifically shown in FIG. 6B. The exemplary method 900 ends in operation 924.

[0107] Figures 9A and 9B show an exemplary page that shares a selected content entry from content application 316 of one computing device 402 as being associated with a selected contact with content application 316 of another computing device 403, which includes one or more tagged contacts, tags, and / or notes associated with the selected content entry according to FIG. 9. For example, the selected content entry can be shared by a user of computing device 402 of system 400 with a user of computing device 403 as particularly shown in FIG. 4.

[0108] When a user executes a content management and relationship application (e.g., tokpee) 316 on computing device 402, the home page 616 of content application 316 is displayed as shown in FIG. 6A. Next, the user can select a content type (e.g., photo 616B) from a plurality of content types such as content types 616A - 616L. For example, the user can select the content type "photo" 616B.

[0109] After the "photo" content type is selected, a photo or a link to 220A - 220D is received at computing device 402 from application server / content provider 404, or selected if the photo is stored on mobile device 402. The user can select a content entry (e.g., a photo) from content type photos 616B such as photo 220D from among the plurality of displayed photos and share it with a contact as particularly shown in FIG. 2C. As described herein with reference to FIGS. 2A - 2H, one or more associations can be tagged to content photo 220D. For example, the photo 220D shown in FIG. 2D has no tagged associations, while the photo 220D shown in FIG. 2H includes various tagged associations including contacts, tags, and / or notes.

[0110] When a content entry (e.g., a photo) is selected, as shown in FIG. 2H, photo 220D can be displayed. To share photo 220D with a contact, the user can select share button 244 as shown in FIG. 2H. Selecting share button 244 can display a list of contacts 618 available for sharing photo 220D, as shown in FIGS. 6B and 9A. The user can select at least one contact from the list of contacts 618, such as contacts 902, 904, and 620, as particularly shown in FIG. 9A. The user can give a command to share the content entry (e.g., photo 220D) with one or more selected contacts by selecting share button 906, or can give a command to cancel the sharing by selecting cancel button 908, which can be given at the bottom of list 618, as particularly shown in FIG. 9A.

[0111] Upon receiving the aforementioned sharing command, the selected content entry (e.g., photo 220D) or the link to the content entry is copied by the application server / content provider 404 to the shared item content type 616M of at least one selected contact along one or more of the tagged associations. For example, the selected photo 220D or the link to photo 220D is copied to the application database 406 for the selected contact (e.g., the selected contact 620 is associated with the computing device 403, and the other selected contacts are associated with each computing device of the exemplary system 400 as shown in FIG. 4). More specifically, multiple contacts may be associated with multiple respective computing devices, and each device (e.g., computing device 403) can not only install / run the content application 316, but also obtain and display a copy of the content entry (e.g., photo 220D) shared by the computing device 402 along with various tagged associations including contacts, tags, and / or notes.

[0112] After copying the content entry (e.g., photo 220D) or the link to the content entry, the application server / content provider 404 notifies at least one selected contact that specific content has been shared with the at least one contact. For example, the application server / content provider 404 sends a notification notifying the contact associated with each computing device (e.g., the selected contact associated with the computing device 403), and the notification can be an email message, a text message, or another type of message. Finally, the status of sharing with at least one contact is shown to the user on the computing device 402 regardless of whether the sharing was successful. An exemplary display is shown in FIG. 9B, which indicates that the sharing of content with the selected contact was successful.

[0113] Sharing has been described in relation to a particular content entry (e.g., photo 220D) and associations that may be associated with the content entry. Note that any content entry of content type 616 shown in FIG. 6A can be shared with each computing device (such as computing device 403) whose contact is selected to receive the content entry to be shared, along with the associated associations, from computing device 402.

[0114] FIG. 10 shows an exemplary method 1000 for accessing a content entry shared with a contact according to FIGS. 9, 9A, and 9B, and includes one or more tagged associations, such as contacts, tags, and / or notes associated with the selected content entry. For example, a content entry (e.g., photo 220D) was shared by a user of computing device 402 with a selected contact (user) of computing device 403.

[0115] Method 1000 begins at operation 1002, where a user of computing device 403 (e.g., a selected contact) receives a notification (e.g., a text message) from application server / content provider 404 (e.g., via the sharing feature from computing device 402), indicating that the user has received shared content (e.g., a content entry). At operation 1006, content management and relationship application 316 (e.g., tokpee) is executed on the computing device. If the application is not installed, the user is prompted to install application 316 on computing device 403, and then content application 316 is executed. For example, when content application 316 is executed, home page 614 may be displayed to the user, and as shown in FIG. 6A, content type 616 is displayed. At operation 1008, a selection of a content type for an item shared from multiple content types is received. For example, shared item 616M of content type is selected from multiple content types 616 displayed on home page 614, as particularly shown in FIG. 6A. At operation 1010, shared content entry 1016 (e.g., shared photo 220D) includes one or more of the contact, tag, or memo of the content entry and is displayed on computing device 403. For example, a shared content entry (e.g., a photo) as displayed on computing device 403 is shown in FIG. 10B. In one embodiment, the execution of content application 316 and the selection of content type 616M result in the display of content entry 1016 (e.g., shared photo 220D), which can be achieved by the user's selection, e.g., manually executing content application 316, selecting content type 616M, and thus, as particularly shown in FIG. 10B, the display of shared content entry 1016 (e.g., shared photo 220D).In another embodiment, the execution of content application 316, and the selection of content type 616M and the display of content entry 1016 can be automatically performed by the user via the selection of a link provided in a notification (e.g., a text message) received at computing device 403. In operation 1012, exemplary method 1000 ends.

[0116] FIGS. 10 and 10B show an exemplary page accessing content entry 1016 shared with at least one contact according to FIGS. 9, 9A, and 9B, and include one or more tagged associations, such as contacts, tags, and / or notes associated with the selected content entry 1016. For example, the shared content entry 1016 (e.g., shared photo 220D) was shared by the user of computing device 402 with a selected contact (user) of computing device 403.

[0117] As shown in FIG. 10A, a user (e.g., a selected contact) of computing device 403 receives a notification (e.g., a text message) 1014 from application server / content provider 404 (e.g., via the sharing function from computing device 402), which indicates that the user has received shared content (e.g., a content entry). In one embodiment, message 1014 includes a link that can be selected by the user of computing device 403. When the link is selected, content application 316 is automatically executed on computing device 403, and content type "Shared Item" 616M is automatically selected from content type 616, and as a result, content entry 1016 (e.g., photo 220D shared by computing device 402) is automatically displayed on computing device 403 and may include one or more of the contact, tags, or notes of the content entry shared by the user of computing device 402 as shown in FIG. 10B. As described above, if the application is not installed on computing device 403, the user may be prompted to install application 316 on computing device 403 and then execute content application 316 to display content entry 1016 (e.g., photo 220D shared by computing device 402).

[0118] In another embodiment, after receiving a notification (e.g., a text message) 1014 from the application server / content provider 404 (e.g., via the sharing function from the computing device 402), the user can manually execute the content management application 316 on the computing device 403. When the content application 316 is executed, the home page 614 can display a content type 616, as particularly shown in FIG. 6A. The user can manually select a "shared item" 616M of the content type from a plurality of content types 616, as particularly shown in FIG. 6A. Next, a shared content entry 1016 (e.g., a shared photo 220D) 1016 is displayed, which may include one or more of the contact, tag, or memo of the content entry shared by the user of the computing device 402.

[0119] FIG. 11 is a block diagram of an exemplary embodiment of a general computer system 1100. The computer system 1100 may include a set of instructions executable to cause the computer system 1100 to execute any one or more of the methods or computer-based functions disclosed herein in FIGS. 1 - 10B. The computer system 1100, or any portion thereof, may operate as a stand-alone device or may be further connected to other computer systems or peripheral devices, for example, using a network or other connection. For example, the computer system 1100 may be the computing device 402 or the computing device 403 capable of executing the content management and relationship application 316 (e.g., tokpee), and may be further connected to other systems and devices such as the application server / content provider 404 and the application database 406, and the content providers 408 - 416 via a network such as the network 418.

[0120] In addition, the computer system 1100 may be implemented as, or incorporated into, various devices such as a personal computer (PC), a tablet PC, a personal digital assistant (PDA), a computing device or mobile device (e.g., a smartphone), a palmtop computer, a laptop computer, a desktop computer, a communication device, a control system, a web appliance, or any other machine capable of executing (over time or otherwise) a set of instructions that specify actions to be taken by that machine. Further, although a single computer system 1100 is shown, the term "system" shall also be construed to include any collection of systems or subsystems that individually or jointly execute a set of instructions, or multiple sets of instructions, to perform one or more computer functions.

[0121] As shown in FIG. 11, the computer system 1100 may include a processor 1102, e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both. Further, the computer system 1100 may include a main memory 1104 and a static memory 1106 that can communicate with each other via a bus 1126. As shown, the computer system 1100 may further include a video display unit 1110 such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, or a cathode ray tube (CRT). Further, the computer system 1100 may include an input device 1112 such as a keyboard, and a cursor control device 1114 such as a mouse. The computer system 1100 may also include a disk drive (or solid state) unit 1116, a signal generation device 1122 such as a speaker or remote control, and a network interface device 1108.

[0122] In certain embodiments or aspects, as shown in FIG. 11, the disk drive (or solid state) unit 1116 may include one or more instruction sets 1120, e.g., a computer-readable medium 1118 into which software can be embedded. Further, the instructions 1120 may embody one or more of the methods or logics described herein. In certain embodiments or aspects, the instructions 1120 may be fully or at least partially present in the main memory 1104, the static memory 1106, and / or within the processor 1102 during execution by the computer system 1100. The main memory 1104 and the processor 1102 may also include a computer-readable medium.

[0123] In alternative embodiments or aspects, dedicated hardware embodiments such as application specific integrated circuits, programmable logic arrays, and other hardware devices can be constructed to implement one or more of the methods described herein. Applications that may include the apparatus and systems of various embodiments or aspects can broadly include various electronic and computer systems. One or more of the embodiments or aspects described herein can implement functions using related control and data signals that can communicate between and through modules in two or more specifically interconnected hardware modules or devices, or as part of an application specific integrated circuit. Accordingly, the system encompasses software, firmware, and hardware embodiments.

[0124] According to various embodiments or aspects, the methods described herein can be implemented by a software program tangibly embodied on a processor-readable medium and executable by a processor. Further, in exemplary non-limiting embodiments or aspects, the embodiments can include distributed processing, component / object distributed processing, and parallel processing. Alternatively, virtual computer system processing can be constructed to implement one or more of the methods or functions described herein.

[0125] It is also contemplated that a computer-readable medium includes instructions 1120, or receives and executes instructions 1120 in response to a propagated signal, so that a device connected to network 1124 can communicate voice, video, or data via network 1124. Further, instructions 1120 can be transmitted or received over network 1124 via network interface device 1108.

[0126] Although the computer-readable medium is shown as a single medium, the term "computer-readable medium" includes a single medium or multiple media that store one or more sets of instructions, such as a centralized or distributed database, and / or associated caches and servers. The term "computer-readable medium" also includes any medium that can store, encode, or propagate a set of instructions for execution by a processor, or any medium that can cause a computer system to perform any one or more of the methods or operations disclosed herein.

[0127] In certain non-limiting, exemplary embodiments or aspects, the computer-readable medium may include solid-state memory such as a memory card or other package that houses one or more non-volatile read-only memories. Further, the computer-readable medium can be random access memory or other volatile, rewritable memory. Further, the computer-readable medium can include magneto-optical or optical media such as a disk or tape or other storage device to capture carrier signals such as signals communicated across a transmission medium. Digital file attachments to an electronic mail or other built-in information archive or set of archives can be considered a distribution medium equivalent to a tangible storage medium. Thus, any one or more of a computer-readable medium or distribution medium on which data or instructions can be stored, and other equivalents and successor media, are included herein.

[0128] According to various embodiments or aspects, the methods described herein can be implemented as one or more software programs executed by a computer processor. Dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays, and other hardware devices can also be constructed to implement the methods described herein. Additionally, alternative software implementations including, but not limited to, distributed processing or component / object distributed processing, parallel processing, or virtual machine processing can be constructed to implement the methods described herein.

[0129] It should also be noted that the software implementing the disclosed methods can optionally be stored on a tangible storage medium such as a magnetic medium such as a disk or tape, a magneto-optical or optical medium such as a disk, or a solid state medium such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other rewritable (volatile) memories. The software can also utilize signals that contain computer instructions. A digital file attachment to an electronic mail or other internal information archive or set of archives is considered a distribution medium equivalent to a tangible storage medium. Accordingly, the tangible storage media or distribution media enumerated herein, as well as other equivalents and successor media on which the software embodiments of the present specification can be stored, are included herein.

[0130] Systems and methods have been described that relate to effectively managing the relationships, organization, retrieval, and sharing of various types of content accessible by a computing device such as a mobile device. Specific exemplary embodiments or aspects have been described, but it is clear that various modifications and changes may be made to these embodiments or aspects without departing from the broader scope of the invention. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a limiting sense. The accompanying drawings, which form a part hereof, illustrate by way of example and not of limitation, specific embodiments or aspects in which the subject matter may be practiced. The illustrated embodiments or aspects are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments or aspects may be utilized and derived therefrom, whereby structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Accordingly, the embodiments for carrying out the invention are not to be construed in a limiting sense, and the scope of various embodiments or aspects is defined only by the appended claims, together with the full scope of equivalents to which the claims are entitled.

[0131] Such embodiments or aspects of the subject matter of the invention, if more than one are actually disclosed, may be referred to herein, individually and / or collectively, by the term "invention" for convenience only and without any intention of voluntarily limiting the scope of this application to any single invention or inventive concept. Accordingly, it should be recognized that, although specific embodiments or aspects are shown and described herein, all arrangements calculated to achieve the same purpose may be substituted for the specific embodiments or aspects shown. The disclosure is intended to cover any adaptations or variations of the various embodiments or aspects. Combinations of the above-described embodiments or aspects, as well as other embodiments or aspects not specifically described herein, will be apparent to those skilled in the art upon review of the above description.

[0132] The abstract is provided to comply with 37 CFR § 1.72(b) and enables the reader to quickly grasp the nature and gist of the technical disclosure. It is submitted with the understanding that it is not used to interpret or limit the scope or meaning of the claims.

[0133] In the description of the above-described embodiments or aspects, for the purpose of rationalizing the disclosure, various features are grouped together in a single embodiment. The present method of disclosure should not be construed as reflecting that the claimed embodiments or aspects have more features than are explicitly recited in the respective claims. Rather, as reflected in the following claims, the subject matter of the invention is not in all of the features of a single disclosed embodiment or aspect. Thus, the following claims are incorporated by reference into the detailed description herein, and each claim stands on its own as a separate exemplary embodiment or aspect. It is contemplated that the various embodiments or aspects described herein can be combined or grouped in different combinations that are not explicitly described in the forms for carrying out the invention. Further, it is further contemplated that claims covering such different combinations can likewise stand on their own as separate exemplary embodiments or aspects that can be incorporated into the forms for carrying out the invention.

Claims

1. A method for managing content entries using a computing device, comprising: accessing the content entry from a content source via a link to the content entry, wherein the content entry is remote to the computing device; adding at least one of a tag, a memo, or a contact to associate with the content entry; posting at least one of the tag, the memo, or the contact associated with the link to the content entry as a record associated with the computing device in a database; and displaying the content entry as accessed via the link associated with at least one of the tag, the memo, or the contact posted as such.

2. The method according to claim 1, wherein accessing the content entry from the content source comprises: receiving a selection of a content type associated with the content entry; receiving a selection of the content source associated with the content type; receiving a selection of the content entry; and returning the link to the content entry.

3. The method according to claim 2, further comprising storing the content entry in the database and returning the link to the content entry stored in the database.

4. The method according to claim 1, wherein accessing the content entry from the content source comprises: navigating to a web page in a web browser; executing a sharing function of the web browser in relation to the web page; receiving a selection of a content application in relation to the sharing function; and sharing a link associated with the web page with the content application, wherein the link associated with the web page as shared is the link to the content entry.

5. ​ The method according to claim 4, further comprising receiving at least one type, title, and description of the web page associated with the link as being shared with the content application.

6. accessing the content entry from the content source, receiving a selection of a content type associated with the content entry, receiving a link associated with a web page, and returning the link associated with the web page as the link to the content entry, the method according to claim 1.

7. The method according to claim 6, further comprising receiving at least one of a type, title, and description of the web page associated with the received link.

8. The content entry includes one or more of a web page, music, video, file, social networking service (SNS) post, real simple syndication (RSS) feed, photo, written note, email, or direct messaging (DM) message, the method according to claim 1.

9. The method according to claim 1, further comprising generating a story expansion associated with a link to the content entry.

10. Generating the story expansion associated with the link to the content entry includes receiving a selection of an address book content type from a plurality of content types, receiving a contact selected from a plurality of contacts associated with the address book content type, obtaining from the database one or more links to respective content entries each associated with at least one other content type from the plurality of content types, wherein the links to the respective content entries are associated with the selected contact, the obtaining, and Generating the story development for the selected contact, wherein the story development includes one or more links to the respective content entries associated with each of the at least one other content type as obtained, and each of the respective content entries is accessible via the one or more links from one or more content sources remote to the computing device, the generating, as included in the method of claim 9.

11. The method of claim 10, wherein the story development includes a total including the number of one or more content entries associated with each of at least one other content type as obtained in relation to the story development generated for the selected contact.

12. Generating the story development associated with the link to the content entry comprises Receiving search terms, Obtaining from the database one or more links to the respective content entries associated with each of at least one content type from a plurality of content types, wherein each of the one or more content entries is associated with at least one of the tag, the memo, the contact, the link, or other text data including the search terms, the obtaining, and Generating the story development for the search terms, wherein the story development includes one or more links to the respective content entries associated with each of the at least one content type, and each of the respective content entries is accessible via the one or more links from one or more content sources remote to the computing device, the generating, as included in the method of claim 9.

13. The method of claim 12, wherein the story development includes a total including the number of one or more content entries associated with each of at least one content type as obtained in relation to the story development generated for the selected search terms.

14. Generating the story development associated with the link to the content entry comprises Receiving a selected tag, obtaining from the database one or more links to respective content entries associated with each of at least one content type from a plurality of content types, wherein the links of the respective content entries are associated with the selected tag, said obtaining, and generating a story expansion for the selected tag, the story expansion including the one or more links to the respective content entries associated with each of the at least one content type as obtained, each of the respective content entries being accessible via the one or more links from one or more content sources remote to the computing device, said generating, the method of claim 9.

15. The method of claim 14, wherein the story expansion includes a total including the number of one or more content entries associated with each of the at least one content type as obtained in relation to the story expansion generated for the selected tag.

16. The method of claim 1, further comprising sharing the content entry with a contact of a second computing device.

17. Sharing the content entry with the contact of the second computing device comprises generating a second record associated with the second computing device in the database, copying the link to the content entry to the second record including at least one of the tag, the memo, or the contact associated with the link, and notifying the contact of the second computing device that the content entry has been shared, the second computing device being able to display the content entry accessed via the link associated with at least one of the tag, the memo, or the contact, said notifying, the method of claim 16.

18. A system for managing content entries, comprising a computing device, A non-transitory memory storing instructions, which, when executed by the computing device, cause the computing device to access the content entry from a content source via a link to the content entry, wherein the content entry is remote to the computing device, the accessing, add at least one of a tag, a memo, or a contact to associate with the content entry, post at least one of the tag, the memo, or the contact associated with the link to the content entry as a record associated with the computing device of the database, and display the content entry accessed via the link associated with at least one of the tag, the memo, or the contact posted, the system causing the operations to be performed.

19. The operation of accessing the content entry from the content source receives a selection of a content type associated with the content entry, receives a selection of the content source associated with the content type, receives a selection of the content entry, and returns the link to the content entry, the system according to claim 18.

20. The operation stores the content entry in the database, and further includes returning the link to the content entry stored in the database, the system according to claim 19.

21. The operation of accessing the content entry from the content source navigates to a web page in a web browser, executes a sharing function of the web browser in relation to the web page, receives a selection of a content application in relation to the sharing function, and shares a link associated with the web page with the content application, wherein the link associated with the web page as shared is the link to the content entry, the sharing, the system according to claim 18.

22. The system according to claim 21, further comprising receiving at least one type, title, and description of the web page associated with the link as being shared with the content application.

23. The operation of receiving the selection of the content entry associated with the content source is receiving a selection of a content type associated with the content entry, receiving a link associated with a web page, and returning the link associated with the web page as the link to the content entry, the system according to claim 18.

24. The operation further comprises receiving at least one of a type, title, and description of the web page associated with the received link, the system according to claim 23.

25. The content entry includes one or more of a web page, music, video, file, social networking service (SNS) post, Really Simple Syndication (RSS) feed, photo, note, email, or direct messaging (DM) message, the system according to claim 18.

26. The operation further comprises generating a story expansion associated with the link to the content entry, the system according to claim 18.

27. The operation of generating the story expansion associated with the link to the content entry is receiving a selection of an address book content type from a plurality of content types, receiving a contact selected from a plurality of contacts associated with the address book content type, obtaining from the database one or more links to respective content entries each associated with at least one other content type from the plurality of content types, wherein the links to the respective content entries are associated with the selected contact, the obtaining, and Generating the story development for the selected contact, the story development including one or more links to respective content entries associated with each of the at least one other content type as acquired, each of the respective content entries being accessible via the one or more links from one or more content sources remote to the computing device, the generating, the system of claim 26

28. The system of claim 27, wherein the story development includes a total including the number of one or more content entries associated with each of at least one other content type as acquired in relation to the story development generated for the selected contact.

29. The operation of generating the story development associated with the link to the content entry Receiving search terms Obtaining from the database one or more links to respective content entries associated with each of at least one content type from a plurality of content types, each of the one or more content entries being associated with at least one of the tag, the memo, the contact, the link, or other text data including the search terms, the obtaining, and Generating the story development for the search terms, the story development including one or more links to respective content entries associated with each of at least one content type, each of the respective content entries being accessible via the one or more links from one or more content sources remote to the computing device, the generating, the system of claim 26

30. The system of claim 29, wherein the operation of generating the story development includes a total including the number of one or more content entries associated with each of at least one content type as acquired in relation to the story development generated for the selected search terms.

31. The operation of generating the story development associated with the link to the content entry comprises: Receiving a selected tag; Obtaining from the database one or more links to respective content entries associated with each of at least one content type from a plurality of content types, wherein the links of the respective content entries are associated with the selected tag, said obtaining, and Generating the story development for the selected tag, the story development including the one or more links to the respective content entries associated with each of the at least one content type as obtained, each of the respective content entries being accessible via the one or more links from one or more content sources remote to the computing device, said generating, the system of claim 26.

32. The operation of generating the story development includes a total including the number of one or more content entries associated with each of the at least one content type as obtained in relation to the story development generated for the selected tag, the system of claim 31.

33. The operation further includes sharing the content entry with a contact of a second computing device, the system of claim 18.

34. The operation of sharing the content entry with the contact of the second computing device comprises: Generating a second record associated with the second mobile device of the database; Copying the link to the content entry to the second record including at least one of the tag, the memo, or the contact associated with the link, and Notifying the contact of the second computing device that the content entry has been shared, wherein the second computing device can display the content entry accessed via the link, which is associated with at least one of the tag, the memo, or the contact, the notifying, the system according to claim 33.

35. A non-transitory memory storing instructions that, when executed by a computing device, cause the computing device to perform operations associated with managing content entries using a mobile device, the operations including: Accessing the content entry from a content source via a link to the content entry, wherein the content entry is remote to the computing device, the accessing; Adding at least one of a tag, a memo, or a contact for association with the content entry; Posting at least one of the tag, the memo, or the contact associated with the link to the content entry as a record associated with the computing device of the database; and Displaying the content entry accessed via the link associated with at least one of the tag, the memo, or the contact as posted, the non-transitory memory.

36. The operation of accessing the content entry from the content source includes: Receiving a selection of a content type associated with the content entry; Receiving a selection of the content source associated with the content type; Receiving a selection of the content entry; and Returning the link to the content entry, the non-transitory memory according to claim 35.

37. The operation further includes: Storing the content entry in the database; and Returning the link to the content entry stored in the database, the non-transitory memory according to claim 36.

38. The operation of accessing the content entry from the content source includes: Navigating to a web page in a web browser, Performing a sharing function of the web browser in relation to the web page, Receiving a selection of a content application in relation to the sharing function, and Sharing a link associated with the web page with the content application, wherein the link associated with the web page as the one to be shared is the link to the content entry, the sharing, the non-transitory memory according to claim 35.

39. The non-transitory memory according to claim 38, wherein the operation further includes receiving at least a type, a title, and a description of the web page associated with the link to be shared with the content application.

40. The operation of accessing the content entry from the content source Receiving a selection of a content type associated with the content entry, Receiving a link associated with a web page, and Returning the link associated with the web page as the link to the content entry, the non-transitory memory according to claim 35.

41. The non-transitory memory according to claim 40, wherein the operation further includes receiving at least one of a type, a title, and a description of the web page associated with the received link.

42. The content entry includes one or more of a web page, music, video, file, social networking service (SNS) post, Really Simple Syndication (RSS) feed, photo, writing, email, or direct messaging (DM) message, the non-transitory memory according to claim 35.

43. The non-transitory memory according to claim 35, wherein the operation further includes generating a story expansion associated with the link to the content entry.

44. The operation of generating the story expansion associated with the link to the content entry Receiving a selection of an address book content type from a plurality of content types, Receiving a contact selected from a plurality of contacts associated with the address book content type, Obtaining, from the database, one or more links to respective content entries associated with each of at least one other content type from the plurality of content types, wherein the links of the respective content entries are associated with the selected contact, the obtaining, and Generating the story development for the selected contact, the story development including the one or more links to the respective content entries associated with each of the at least one other content type as obtained, each of the respective content entries being accessible via the one or more links from one or more content sources remote to the computing device, the generating, comprising the non-transitory memory of claim 43. **Claim 45** The story development includes a total including the number of one or more content entries associated with each of at least one other content type as obtained in relation to the story development generated for the selected contact, comprising the non-transitory memory of claim 44. **Claim 46** The operation of generating the story development associated with the link to the content entry Receiving search terms, Obtaining, from the database, one or more links to respective content entries associated with each of at least one content type from the plurality of content types, each of the one or more content entries being associated with at least one of the tag, the memo, the contact, the link, or other text data including the search terms, the obtaining, and Generating the story development for the search terms, the story development including the one or more links to the respective content entries associated with each of at least one content type, each of the respective content entries being accessible via the one or more links from one or more content sources remote to the computing device, the generating, comprising the non-transitory memory of claim 43. **Claim 47** The operation of generating the story development includes a total including the number of one or more content entries associated with each of at least one content type as obtained in relation to the story development generated for the selected search term, the non - transient memory according to claim 46.

48. The operation of generating the story development associated with the link to the content entry includes receiving a selected tag, obtaining from the database one or more links to respective content entries associated with each of at least one content type from a plurality of content types, wherein the link of each respective content entry is associated with the selected tag, the obtaining, and generating the story development for the selected tag, wherein the story development includes the one or more links to the respective content entries associated with each of the at least one content type as obtained, and each respective content entry is accessible via the one or more links from one or more content sources remote to the computing device, the generating, the non - transient memory according to claim 43.

49. The operation of generating the story development includes a total including the number of one or more content entries associated with each of at least one content type as obtained in relation to the story development generated for the selected tag, the non - transient memory according to claim 48.

50. The operation further includes sharing the content entry with a contact of a second computing device, the non - transient memory according to claim 35.

51. The operation of sharing the content entry with the contact of the second computing device includes generating a second record associated with the second computing device in the database, copying the link to the content entry to the second record including at least one of the tag, the memo, or the contact associated with the link, and Notifying the contact of the second computing device that the content entry has been shared, wherein the second computing device can display the content entry accessed via the link, which is associated with at least one of the tag, the memo, or the contact, the non-transitory memory according to claim 50, comprising the notifying.

Images