Live greetings

Systems, methods, and apparatuses disclose an electronic greeting card application for creating, editing, distributing, and viewing electronic greeting cards on a portable computing device, wherein the electronic greeting card displays animations and permits users to customize the card by way of adding a message, signature, photo, and sound recording.

FIELD OF THE INVENTION

The general inventive concepts relate to electronic greeting cards and, more particularly, to systems, methods, and apparatuses for creating, editing, distributing, and viewing electronic greeting cards on a portable computing device.

BACKGROUND

Greeting cards have been a staple in human communications for centuries. However, the concept of sending greetings via electronic medium is a relatively new phenomenon. Despite the advances in technology, “electronic” greeting cards have been largely limited to desktop computing platforms.

Lately, electronic greeting cards have been implemented as part of mobile applications in portable computing devices. One example of such implementation is disclosed in U.S. patent application Ser. No. 13/460,045, entitled “SYSTEMS, METHODS AND APPARATUSES FOR CREATING, EDITING, DISTRIBUTING, AND VIEWING ELECTRONIC GREETING CARDS,” which is hereby incorporated by reference in full.

However, there is a need to provide for systems, methods, and apparatuses which allow a user to create, edit, view, and distribute electronic greeting cards on portable computing devices without sacrificing some of the unique features of paper greeting cards, while at the same time utilizing the technical features that are only available in an electronic medium.

BRIEF SUMMARY

The general inventive concepts contemplate systems, methods, and apparatuses for creating, editing, distributing, and viewing electronic greeting cards on a portable computing device, wherein the electronic greeting card displays animations and permits users to customize the card by way of adding a message, signature, photo, and sound recording. By way of example, to illustrate various aspects of the general inventive concepts, several exemplary embodiments of systems, methods, and/or apparatuses are disclosed herein.

Additional features and advantages will be set forth in part in the description that follows, and in part will be obvious from the description, or may be learned by practice of the embodiments disclosed herein. It is to be understood that both the foregoing brief summary and the following detailed description are exemplary and explanatory only and are not restrictive of the embodiments disclosed herein.

DETAILED DESCRIPTION

The embodiments disclosed herein will now be described by reference to some more detailed embodiments, with occasional reference to the accompanying drawings. These embodiments may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the embodiments to those skilled in the art.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which these embodiments belong. The terminology used in the description herein is for describing particular embodiments only and is not intended to be limiting of the embodiments. As used in the specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.

The following are definitions of exemplary terms used throughout the disclosure. Both singular and plural forms of all terms fall within each meaning:

“Computer” or “computing device” or “processing unit” as used herein includes, but is not limited to, any programmed or programmable electronic device, microprocessor, or logic circuit that can store, retrieve, and process data.

“Portable computing devices” include, but are not limited to, computing devices that combine the powers of a conventional computer in portable environments. Exemplary portable computing devices include portable computers, tablet computers, internet tablets, Personal Digital Assistants (PDAs), ultra mobile PCs (UMPCs), carputers (typically installed in automobiles), wearable computers, and smartphones. The term “portable computing device” can be used synonymously with the terms “computer” or “computing device” or “processing unit.”

“Web browser” as used herein, includes, but is not limited to, software for retrieving and presenting information resources on the World Wide Web. An information resource may be a web page, an image, a video, a sound, or any other type of electronic content.

“Software” or “computer program” as used herein includes, but is not limited to, one or more computer or machine readable and/or executable instructions that cause a computer, a portable computing device, microprocessor, logic circuit, or other electronic device to perform functions, actions, and/or behave in a desired manner. The instructions may be embodied in various forms such as routines, algorithms, modules or programs, including separate applications or code from dynamically linked libraries. Software may also be implemented in various forms such as a stand-alone program, an app, a mobile application, a function call, a servlet, an applet, instructions stored in a memory or any other computer readable medium, part of an operating system or other type of executable instructions. It will be appreciated by one of ordinary skill in the art that the form of software is dependent on, for example, requirements of a desired application, the environment it runs on, and/or the desires of a designer/programmer or the like.

“Mobile application” as used herein, includes, but is not limited to, applications that run on smart phones, tablet computers, and other mobile or portable computing devices. The terms “mobile application” or “mobile app” or “software application” or “application” or “app” can be used synonymously with “software” or “computer program” or “application software.” Mobile applications allow users to connect to services that are traditionally available on the desktop or notebook platforms. Typically, these services access the Internet or intranet or cellular or wireless fidelity (Wi-Fi) networks, to access, retrieve, transmit and share data.

“Network” as used herein, includes, but is not limited to, a collection of hardware components and computers or machines interconnected by communication channels that allow sharing of resources and information, including without limitation, the worldwide web or Internet. A network maybe “wireless,” “wired,” or a combination of wired and wireless networks.

“Server” as used herein, includes, but is not limited to, a computer or a machine or a device on a network that manages network resources. The general term “server” may include specific types of servers, such as a Web Server, File Server (a computer and storage device dedicated to storing files), Print Server (a computer that manages one or more printers), a Network Server (a computer that manages network traffic), and a Database Server (a computer system that processes database queries). Although servers are frequently dedicated to performing only server tasks, certain multiprocessing operating systems allow a server to manage other non-server related resources.

“Web server” as used herein, includes, but is not limited to, a server which serves content to a web browser by loading a file from a disk, or automatically generating a response by combing a search result from a database or other repository with calculations based on client request parameters and business rules and logic embedded in the software, and serving it across a network to a user's web browser, typically using a hyper text transfer protocol (HTTP).

Reference will now be made to the drawings.FIG. 1is a high level overview of the inventive system100. System100comprises a mobile application130(“ecard app”), which is housed on a portable computing device120. The portable computing device120and the ecard app130are in communication with a network110. Access to network110allows the portable computing device120to obtain and refresh content that is subsequently utilized by the ecard app130. A user150utilizes the ecard app130to create and send one or more electronic greeting cards (“ecard”)160.

The electronic greeting card(s) may be any commercially or non-commercially available electronic greeting card. One embodiment of a customizable electronic greeting card160is disclosed in U.S. patent application Ser. No. 13/460,045, entitled “SYSTEMS, METHODS AND APPARATUSES FOR CREATING, EDITING, DISTRIBUTING, AND VIEWING ELECTRONIC GREETING CARDS,” (“the '045 application”) which is hereby incorporated by reference in full.

The ecard160is customizable. For instance, user150may add/edit a personalized message, a signature, a photo, and a sound recording to the ecard160.

FIG. 2is a flow chart of exemplary system100of the present invention. The system flow represents the flow of the software and begins at step201. At202, the ecard app130will be implemented as a mobile application on the portable computing device120and presented to user150. The ecard app130may be programmed using object oriented technology such as Objective-C® and Java®.

If user150proceeds to build an ecard160, user150is directed to four personalization options203,204,205, and206, which allow user150to personalize the ecard160by adding a photo, adding a message, adding a signature, and adding a sound recording respectively. User150can then preview the customized card at step207, and choose to send the card at step208.

If the user150chooses to send the ecard160at step208, user150is directed to step209, where the system100checks to see if user150is signed in to the services offered as part of the system100. If user150is signed in (210), user150is directed to the send options page at step216. If user150is not singed in (211), user150is presented with two options, an existing user sign in page at step212, or a new user sign up page at step214. If user150is an existing user and indicates as such in the app130(step212), user150is directed to step213, where user150signs in to the system100with their user credentials (e.g. a username and a password). After the sign-in process is complete, user150is directed to the send options page at step216. If user150is a new user and indicates as such in the app130(step213), user150is directed to step215, where user150creates new user credentials (e.g. a username and a password). After creating new user credentials, user150is directed to the send options page at step216.

The send options step216further presents user150with four send options217,218,219, and220, which allow user150to send the ecard160via Email, Facebook®, Text Message (or Short Messaging Service Message or iMessage®), and Twitter® respectively. If user150chooses the Facebook send option at step218, user150is able to either send the ecard160to a “friend” on Facebook (at step222), or simply share the electronic greeting card160on their own Facebook “wall” (at step221). The four send options presented at steps217,218,219, and220are not mutually exclusive. User150may choose to send the ecard160using one or more of the four send options (217,218,219, and220) sequentially or in any order.

After sending the ecard160using one or more of the four options217,218,219, and220, user150is directed to a card send-confirmation page at step223, thereby completing the send cycle.

Referring now toFIGS. 3-18, an exemplary embodiment of the operations of the inventive system100for creating, editing, and distributing electronic greeting cards160on a client device120is shown.

FIG. 3shows an exemplary start screen301of the ecard app130.FIG. 4shows an exemplary home page401of the ecard app130. At401, user150begins the process of choosing an ecard160by first selecting a category selector402. Once user150chooses the category selector402, user150is directed to category screen501shown inFIG. 5. In the category screen501, user150is presented with one or more categories502. Categories502represent the groupings by which all ecards160available in the system100are made accessible to the app130. One user150chooses a category502, user150is directed to card selector screen601as shown inFIG. 6. Card selector screen601may further comprise additional categories or sub-categories602. Categories602represent sub-groupings (under each category502) by which all ecards160available in the system100are made accessible to the app130. User150is prompted to select one ecard160from the card selector screen601.

An advantage of the present invention is that the ecard160may include an animated electronic greeting card. An animated electronic greeting card renders animations (such as shaking cards, shaking or moving objects, talking objects, talking cards etc.) both while building and while viewing the electronic greeting card. Animations of the cards are made possible by utilizing technologies such as Objective-C®, Java®, JavaScript®, Scalable Vector Graphics, Extensible Markup Language®, Cascading Style Sheets and the like.

Upon selection of the ecard160, user150is directed to the card home page screen701as shown inFIG. 7. Here, user150is prompted to personalize and send the ecard160via selector702. Screen801ofFIG. 8shows the additional information that is made available to user150regarding ecard160. Screen901ofFIG. 9shows the selected ecard160to user150prior to the personalization steps. One embodiment of the ecard personalization options are shown in screen1001ofFIG. 10. Screen1001comprises three personalization options, for adding a photo (1002), for adding a message (1003), and for adding a signature (1004). Another embodiment of the ecard personalization options are shown in screen1101ofFIG. 11. Screen1101comprises the previously disclosed personalization options for adding a photo (1002), for adding a message (1003) and for adding a signature (1004). Additionally, screen1101further comprises an option for the user to record a message at1102.

If user150selects1002to add a photo, user150is directed to screen1201ofFIG. 12, where user150may choose to upload a photo either by choosing an existing photo from the portable computing device's120native photo album (at1202), or by choosing to take a new photo using the portable computing device's120native camera (at1203). Once user150uploads a photo, either by selecting an existing photo or by taking a new photo, user150is shown a preview of the uploaded photo in screen1204. Screen1204is identical to screen1101, with the exception that an uploaded photo is now shown in place of personalization option1002. User150may choose to remove, edit, or replace the photo shown in screen1204, by selecting the photo shown in screen1204. Once selected, user150is presented with the option to remove the photo (at1206), edit it (at1207), or replace it (at1208) as shown in screen1205. If user150chooses to remove the photo uploaded at screen1204by selecting1206, user150may be re-directed to screen1201to upload another photo. Alternately, user150may be re-directed to screen1101to further customize ecard160. Similarly, if user150chooses to replace the photo uploaded at screen1204by selecting1208, user150may be re-directed to screen1201to upload another photo. Alternately, user150may be re-directed to screen1101to further customize ecard160. If user150chooses to edit the photo uploaded at screen1204by selecting1207, user150may be re-directed to screen1204or to another screen (not shown) to edit the existing photo. Although not shown in the Figures, user150may also choose to upload photos from social network sites such as Google+®, Facebook®, Twitter®, Instagram® and the like.

Referring back toFIG. 11, if user150selects1003to add a message, user150is directed to screen1301ofFIG. 13, where user150may choose to enter a personalized message. Once a personalized message is entered, user150is directed to screen1302where a preview of the personalized message is shown. Screen1302is identical to screen1101, with the exception that the personalized message is now shown in place of personalization option1003.

Referring back toFIG. 11, if user150selects1004to add a signature, user150is directed to screen1401ofFIG. 14, where user150may choose to enter a personalized signature in a signature area1402. The size of the signature may be adjusted using the adjustment radio buttons1403. Adjustment buttons1403may any selector including buttons, a sliding bar, size selection menus, etc. The signature may also be deleted/cleared using the clear selector1404. Once a personalized signature is entered, user150is directed to screen1101(or to an intermediary screen, not shown), to show user150a preview of the personalized signature, in place of showing the personalization option selector1004.

Referring back toFIG. 11, if user150selects1102to record a message, user150is directed to screen1501ofFIG. 15, where user150may choose to record a personalized message by activating the recording selector1502. User150may choose to record any message using the selector1502. In an embodiment, user150may record his/her own voice. In another embodiment, user150may record an external sound, such as music playing on an external device or on device120. In another embodiment, user150may mix his/her own voice with an external sound. The progress of a user's message recording is shown in screen1503. After the message is recorded, user150is given the option to play back the most recently recorded message (at1505) or to re-record a message (at1506), as shown on screen1504. Screen1507shows the playback of the recorded message (at1508).

Referring back toFIG. 11, user150has the option to preview the ecard160by selecting the preview selector1103, or to send the ecard160to a recipient (as described below with reference toFIGS. 19-23) by selecting the send selector1104. The preview selector1103and the send selector1104may be activated by user150either before or after the personalization steps1002,1003,1004, and1102. Further, user150may activate preview selector1103and the send selector1104even after having completed less than the four personalization steps available.

The following description provides an exemplary workflow of the steps involved in sending the ecard160.

If user150chooses to send the card by activating the send selector1104, user150is directed to an authentication screen2401as shown inFIG. 24, where user150is given the choice to either sign in to the system100(at2402), or to create a new account in the system100(at2403).

If user150chooses to create a new account on screen2401, user150is directed to a new account creation screen2501as shown inFIG. 25. User150may enter one or more sign-up details2502(e.g. first name, last name, email address, password, date of birth) to create a new account with the system100. User150may then activate the create account link2503to create a new account.

If user150chooses to sign in on screen2401, user150is directed to a sign in screen2601as shown inFIG. 26. User150may enter their username2602, password2603and sign in using link2604. User150has an option to request a new password by activating the forgot password link2605.

Once user150either creates a new account or signs in, user150is directed to screen1601ofFIG. 16. On screen1601, user150is presented with four send options: send card160via email (1602), send card160via Facebook® (1603), send card160via a text message or a short message service message or an iMessage® (1604), and send card160via Twitter® (1605). Although not shownFIG. 16, user150and the recipient may have the option to share and “like” the card160on various social networking sites such as Google+®, Facebook®, or Twitter®.

If user150chooses to send the card160via email1602, user150is directed to an email page (not shown). The email page has an option for user150to enter one or more email addresses and send the card160by activating a send link.

If user150chooses to send the card160via Facebook®1603, user150is directed to a Facebook® page (not shown). If user150is not already signed in to the Facebook® service on the portable computing device120, user150is directed to a login screen where user150is able to enter their user credentials (e.g. a username and a password) and login to the Facebook® service. Next, user150is able to choose between posting the card160on their own wall or on a friend's wall. If user150chooses to post the card160on their own wall, user150is directed to their Facebook® wall page, where user150is able to post the card160along with a personalized message. If user150chooses to post the card160on a friend's wall, user150is directed to a friend selector page on Facebook®, where user150is able to choose from one or more friends by either selecting them from the Facebook® friend list or by searching for them within the Facebook® interface. Once user150chooses a friend on whose wall to post the card160, user150is directed to the selected friend's Facebook® wall page, where user150is able to post the card160along with a personalized message.

If user150chooses to send the card160using the text message link1604, user150is directed to a text message page (not shown). User150is able to fill out the recipient contact information (e.g. mobile number) and send the card160, with an optional introductory message. The contact information for the recipient may also be extracted from the portable computing device120. The text message may also be sent using the native text message options built into the portable computing device120(e.g. iMessage®).

If user150chooses to send the card160via Twitter®1605, user150is directed to a Twitter® page (not shown). If user150is not already signed in to the Twitter® service on the portable computing device120, user150is directed to a login screen where user150is able to enter their user credentials (e.g. a username and a password) and login to the Twitter® service. Next, user150is able to choose between posting the card160on their own wall or on a friend's wall. If user150chooses to post the card160on their own wall, user150is directed to their Twitter® wall page, where user150is able to post the card160along with a personalized message. If user150chooses to post the card160on a friend's wall, user150is directed to a friend selector page on Twitter®, where user150is able to choose from one or more friends by either selecting them from the Twitter® friend list or by searching for them within the Twitter® interface. Once user150chooses a friend on whose wall to post the card160, user150is directed to the selected friend's Twitter® wall page, where user150is able to post the card160along with a personalized message.

If user150chooses to send the card160via any of the four send options1602,1603,1604or1605, a transcoding process is initiated as shown inFIG. 27. At2701, the user's audio recording (e.g. personalized message), if any, is uploaded to network110. At110, the audio recording is processed via an application programming interface2702and saved on a server2703. Server2703may be a web or a network server that is in communication with network110. Exemplary web or network servers are Amazon S3 servers provided by Amazon®. Contemporaneous to the user's audio recording being uploaded to network110, the remaining portions of the card160, e.g. signature, are uploaded to the network110through a second application programming interface2704. In the network110, a request to transcode the card160along with a notification url is sent to a processor2705, which transcodes the audio portions of the card160. Another server2706stores the transcoded audio and saves it on the network110. The transcoding process may utilize transcoding technology such as Zencoder® provided by Brightcove®. Server2706may be a web or a network server that is in communication with network110. Exemplary web or network servers are Amazon S3 servers provided by Amazon®. In one embodiment, a cloud server2707saves the transcoded audio on the network110. Processor2705processes the transcoded audio files and notifies the application programming interface2704of one or more transcoded url links for the transcoded audio files. At2708, the card160is sent to the recipient chosen by user150. When the recipient picks up or chooses to play the card at2709, the previously stored transcoded audio is rendered via network110and/or cloud server2707onto the card160. Prior to playback on the card160, the transcoded audio is de-coded to fit the specific computing environment of the recipient. For example, the decoded audio file rendered to the recipient will be different in a desktop platform as compared with a mobile platform. Transcoding and decoding of messages allows the ecard160, and specifically the audio recordings, to be played across a wide variety of mobile platforms such as iOS® and Android®.

In an embodiment, if signed in to the system100via ecard app130, user150is presented with a reminder screen1701as shown inFIG. 17. Reminder screen1701may serve as a reminder hub for user150, where user150is able to review a list of events1702. The list of events1702may be events that have previously been entered by the user150, or events that were imported from user's device120, or events that were imported into the app130by way of the user150connecting and downloading a list of events stored on the user's social networking account(s) (e.g. Facebook®, Twitter®). User150may select an event1702, to prepare and send an ecard160to the selected contact associated with the event1702.

FIG. 18shows an exemplary options screen1801that presents user150with a list of available options in the ecard app130.

FIGS. 19-23show an exemplary embodiment of the pickup experience of ecard160as viewed by the recipient of ecard160. For the purposes of this description, it is assumed that the recipient also has the ecard app130installed on their device, and chooses to pick up the ecard160using the app130. Screen1901ofFIG. 19shows the recipient receiving the ecard160on a device1902. Device1902may be a device that houses the ecard app130(similar to device120), or may be a standalone device.

As shown inFIG. 20, Ecard160is a hamburger head that moves up and down, wiggles, animates, talks, and sings. Any of the parts that comprise the hamburger, such as the vegetables and cheese, may move as well. The animation may be a partial or full animation, with a partial animation configured to show the animation along with other customizable components of the ecard160, whereas a full animation is implemented to show the animation by itself without any other component interactions. Ecard160may be rendered as described in the '045 application referenced earlier. Further, the animations of the ecard160may be designed to imitate the mechanical movements of the mobile objects and moveable objects described in U.S. Pat. No. 8,695,242, entitled “MOTION GREETING CARDS,” which is hereby incorporated by reference in full.

When the recipient opens an exemplary rendering of a digital outer envelope, ecard160is shown, as can be seen on screen2001. An exemplary view of a fully loaded ecard160is shown in screen2101ofFIG. 21. The recipient may choose to open the ecard160to find the customized message and signature as shown in screen2201ofFIG. 22, and the personalized photo as shown in screen2301ofFIG. 23. The personalized recorded message as shown with reference toFIG. 15may be played in the background when the recipient opens the ecard160, and may continue to play during the entire card viewing experience. Alternately, the recipient may be presented with a message player (not shown), selecting which plays the personalized recorded message back to the recipient.

The recipient interactions in receiving and viewing the card160through the ecard app130may also be replicated on a web browser, especially in situations where the recipient is unable or unwilling to download the ecard app130. If the ecard160is being picked up on a web browser, the web browser may be optimized to render the content and graphics of the card160. As an example, the web browser may be optimized using HTML, JavaScript, and GreenSock (an animation library for website pickup, including using HTML5) in order to properly render the content and graphics of the card160. Utilizing HTML or HTML 5 in conjunction with JavaScript and GreenSock, ecard160is rendered to the user150as a 3-dimensional card. The web page that renders the ecard160may also be configured to check for the technical specifications of the web browser in which the card160is being rendered. If the web browser being used to render card160does not contain the technical features (e.g. a certain pre-determined version of the browser, JavaScript etc) required for a full rendering of card160, the web page may present the user150with a “pared-down” version of card160without some features, such as the 3-dimensional rendering.

Ecard160may also be picked up using a mobile optimized browser builder. Exemplary operations and flow of receiving and viewing an exemplary ecard via a mobile optimized web browser are fully described in International Patent Application No. PCT/US14/24074, entitled “VIRTUAL SHOP FOR ELECTRONIC GREETING CARDS” (“the '074 application”) which is incorporated herein by reference in full.

As described in further detail in the '074 application, the mobile optimized browser builder is rendered to user150on the portable computing device120via JavaScript, an interpreted computer programming language. The mobile optimized browser builder is essentially a single web page JavaScript application. All of the page interactions happen through JavaScript, in addition to Cascading Style Sheets and Canvas technology. The rendering of the card happens through Scalable Vector Graphics (SVG) and Extended Markup Language via Application Program Interfaces. Further, advanced image processing and rendering on the card160are accomplished using JavaScript and Canvas technologies.

One method of rendering an animation in an ecard that has been picked up by a recipient of the ecard builds on the description of using SVG files provided in U.S. patent application Ser. No. 13/460,045, which has been incorporated herein by reference in full, particularly at Paragraphs 51 through 61. For example, to create animation effects on page 1 of an ecard that is a hamburger shown inFIG. 21for example, information is added to the SVG XML library file by the creator of the ecard. This information is as follows:1. The names of the image assets to be animated on page 1 in coordination with decoded music in the audio file. Examples of assets to be animated in this example would include the “whites” of the hamburgers eyes, the pupils of the hamburgers eyes and any other portion of the hamburger to be animated or moving in coordination with the audio file.2. The X, Y and Z coordinates of each animation effect identified in 1. The X and Y coordinates are horizontal and vertical coordinates respectively. The Z coordinate is the order of objects as they appear looking into the ecard. Z-order is an ordering of overlapping two-dimensional objects in a 3D application. One of the features of a typical Graphical User Interface such as a computer monitor or portable computing device is that windows may overlap, so that one window hides part or all of another. When two windows depicting objects overlap, their Z-order determines which one appears on top of the other. The coordinates must be specified for the initial start or origin of each animation effect as well as the coordinates of the placement of the animation throughout the activation of the animation effect.3. The duration of the time for each animated asset to be animated that is described in 1.4. Setting the start and stop times for animation to begin and end. This is called, setting key frame times. Setting key frame times is done to coordinate certain animations to coincide with certain sound effects or beats in songs contained in the audio file.5. The type of animation movement for each animation effects such as straight line, repetitive or circular movement.

These parameters are defined or programmed in each SVG file for each ecard. This information is parsed from the SVG file into JSON format that is then used by the JavaScript of the page. JSON or JavaScript Object Notation, is an open standard format that uses human-readable text to transmit data objects consisting of attribute-value pairs. It is used primarily to transmit data between a server and web application, as an alternative to XML. The animated assets within the card are transcoded into JavaScript and used by the animation library (GreenSock) to coordinate the visual effects with the audio file when the card is picked up by the recipient in2709onFIG. 27, so that the animation appears synced or coordinated with sound effects or music in the card. The recipient then views or experiences the synced audio and visual effects of the animation. The animation effects can be placed on any page of the ecard and can be any type of visual effect or animation. The hamburger is just one example.

The above description of specific embodiments has been given by way of example. From the disclosure given, those skilled in the art will not only understand the general inventive concepts and attendant advantages, but will also find apparent various changes and modifications to the structures and methods disclosed. For example, although the embodiments disclosed herein have been primarily directed to a portable computing device, the general inventive concepts could be readily extended to a non-portable computer (PC) or other relatively fixed console computers, and may be pursued with reference to a website and/or other online or offline mechanisms. Further, other social networking sites other than those specifically described herein may be used as delivery media for electronic greeting cards. As another example, the general inventive concepts are not typically limited to any particular interface between a user and the user's mobile computing device. Thus, for example, use of alternative user input mechanisms, such as voice commands and keyboard entries, are within the spirit and scope of the general inventive concepts. As a further example, the general inventive concepts are not typically limited to just mobile applications. Other browsing environments which permit the rendering and usage of the mobile application's features may be employed. For example, social networking applications such as Facebook® and Twitter® may be utilized to render and use the mobile application's pages (e.g. within the Facebook® browser), or mobile optimized web browsers may be used. It is sought, therefore, to cover all such changes and modifications as fall within the spirit and scope of the general inventive concepts, as described and claimed herein, and equivalents thereof.