Patent Grant
9377932
The disclosed embodiments relate generally to electronic devices, and more particularly, to electronic devices that enable users to rapidly peruse content in an intuitive manner.
Digital media content is plentiful and pervasive in today's online society. This content can be obtained from several data sources and presented for display on a user's electronic device. Different applications running on the electronic device can present the content in any number of different ways. For example, a web browser can present content based on the HTML coding of the webpage. As another example, various content aggregating applications such as Facebook™ and Twitter™ can present content according to predefined templates. Since the quantity of content that can be presented is virtually limitless, what is needed is an efficient approach for presenting content and providing users with intuitive navigational access to the content.
Systems and methods for enabling users to rapidly flip through displayed pages of content in an intuitive manner are provided. Graphical animations for transitioning from one page to another can be executed so that portions of three or more pages can be simultaneously viewed. This enables a user to make snap judgments as to whether she wishes to explore any one of those pages in more detail as she rapidly flips through the pages. Various embodiments and details of how a user can rapidly flip through and view multiple pages at once are discussed in more detail in the detailed discussion below.
The above and other aspects and advantages of the invention will become more apparent upon consideration of the following detailed description, taken in conjunction with accompanying drawings, in which like reference characters refer to like parts throughout, and in which:
Systems and methods for enabling a user to rapidly flip through displayed content are provided.
Embodiments of this invention can be implemented by an application running on an electronic device. The application may be a content aggregator type of application that is capable of sourcing media content from any suitable number of data sources. For example, the application can present a user with several selectable high-level categories (e.g., news, tech, sports, lifestyle), each of which may be associated with one more data sources. When the user selects one of the high-level categories, content sourced from one or more of the data sources associated with the selected category can be made available for viewing in accordance with embodiments of the invention.
The sourced content can be any suitable media such as, for example, printed media, video media, or audio media. Each data source can provide one or more articles or other content assets that can be viewed on the electronic device. Each article or content asset can be succinctly represented by a single page. When viewed, this page provides its reader with enough information to enable her to make a snap judgment as to whether she wants to read the article in more detail. For example, the single page can include artwork and a title representative of the article. In another embodiment, multiple articles can be shown at once. For example, two or three articles may be displayed, each having its own title, artwork, and text.
When a user selects one of the high level categories, the application may enter into a “flip” mode of navigation in accordance with an embodiment of the invention. In the flip navigation mode, the user can flip through a sequence of single pages representative of each article or content asset associated with the selected category by inputting touch gestures on the device. The user can flip through the sequence by going forward or backward. Though it will be understood that if the sequence is at the beginning, the user cannot flip backwards to the previous page, and if the sequence is at the end, the user cannot flip forward to the next page.
The flip is a transition animation in which either a top half or a bottom half of a currently visible page folds onto its other half, and as the currently visible pages fold on to itself, a different page unfolds in place of the current page. For example, assume a current page has a first half and second half, and that a different page has a third half and a fourth half. Further assume that the second and third halves are attached to each other. When the second half flips up towards the first half, the third half also flips up. As the second and third halves begin to flip up, a portion of the fourth half becomes visible. As the angle between the fourth half and the mated second and third halves increases, more and more of the fourth half can be seen, and less of the first half can be seen. When the angle reaches 180 degrees, none of the current page can be seen because the different page has fully flipped into view.
The user can control the speed in which she flips through the pages. The speed in which each transition animation is performed is based on the input gesture, which can be swipe gesture. The swipe gesture can include touchdown location (e.g., of a finger) on the device, drag time duration and speed across the screen, and liftoff location (e.g., of the finger) from the device. Each of these factors can determine whether the user intends to rapidly or slowly flip through the pages.
The user can rapidly flip through the pages by quickly inputting touch gestures (e.g., such as a series of rapid swiping motions) on the device. This rapid flip can provide the user with the impression she is thumbing through a rolodex. In some embodiments, if a sufficient number of input gestures are received within a predetermined period of time, the user may be presented with multiple pages at once. That is, two or more pages can be simultaneously inflight, thereby showing the user portions of at least three different pages simultaneously. Each flip transition animation is keyed off an input gesture, thereby prevent any scrolling between pages.
The user can slowly flip through the pages by inputting a relatively slow touch gesture on the device. In a “slow” flip, the transition animation flips the page at pace slower than the fast flip transition. Depending on the swipe gesture factors, the user can slowly pick up half of the page and flip it over. Alternatively, the user can pick up the page, but not move her finger far enough over, thereby resulting in having that page fall back down to its starting position.
After the user has finished flipping through the pages, she can select the current page to access more content associated with that page. For example, after tapping on the current page, the application will open up the article so the user can begin reading. The article can include several pages of content, and if the user desires, she may rapidly flip through those pages in accordance with embodiments of the invention.
User configuration option 120 may enable a user to customize the content obtained by the application. For example, the user can define which categories 110 appear on screen 100 and the user can create one or more custom categories 110. Settings option 130 can enable a user to set settings for how the application operates. For example, the user can set how often the application polls the data sources for new content. Refresh option 140 can enable a user to manually refresh the sourced content associated with one or more categories 110.
When a user selects one of categories 110, the application can transition from screen 100 to screen 200 of
A different page can exist for each article or content asset associated with the category selected in screen 100. These pages can be rendered and/or stored locally on or remote from the device running the application. In some embodiments, a predetermined number of pages can be stored in cache memory so that they can quickly accessed and rendered for display or for use in flip transition animations according to embodiments of the invention.
During a flip transition animation, page 201 can fold over itself about flip axis 210. Flip axis 210 can be a center axis that bisects the portrait orientation of screen 200 at its midpoint. Since page 201 is oriented in a portrait mode (i.e., the aspect ratio is such that the top-to-bottom dimensions are greater than the left-to-right dimensions), page 201 can fold onto itself in a vertical direction. For example, top half 220 can fold down over bottom half 230, or in the alternative, bottom half 230 can fold up over top half 220. If desired, however, page 201 can flip over itself in a horizontal direction, a diagonal direction, or any other suitable direction.
During a flip transition animation, page 251 can flip onto itself about flip axis 260. Flip axis 260 bisects page 251 along a vertical axis, thereby splitting page 251 in left and right halves 270 and 280. Thus during a flip transition, page 251 folds onto itself in a horizontal direction. For example, in a left-to-right transition, left half 270 can fold over right half 280, and in a right-to-left transition, right half 280 can fold over left half 270.
Beginning on the left side of
Although not shown in
For purposes of the description accompanying
In response to a trigger event, which is some event that may require a flip transition, the inflight module prepares several pages by splitting each page into top and bottom halves. In addition, the inflight module “mates” the bottom half of a given page (e.g., page N) to the top half of an adjacent page (e.g., page N+1) using a fold layer (e.g., fold layer 510). Fold layer 512 “mates” the top half of page N to the bottom of page N−1. The fold layer can be used by the inflight module as a marker for determining which halves of which pages need to be animated as part of the transition animation. For example, when the user provides an input to flip to the next page, the inflight module determines which fold layer is associated with the bottom half of page N, and after determining the fold layer, it knows that page N+1 is the next page to bring into view as page N begins its flight path out of view, as indicated by the dotted line. Page N+1 is “tethered” to page N and effectively follows the same flight path of page N. Continuing the example, the user can initiate another flip transition to cause page N+2 (not shown) to be displayed. The inflight module determines which fold layer is associated with the bottom half of page N+1 and initiates the transition animation of pages N+1 and N+2.
As another example, when the user provides an input to flip to a previous page (e.g., from page N to page N−1), the inflight engine determines which fold layer is associated with the top layer of page N. After determining the fold layer, it knows to initiate a transition operation of pages N and N−1.
Lighting layers 520 can be layered on top of each half as shown. A lighting module (shown in
The inflight module not only converts the pages into animation elements, it also handles the inflight characteristics of each flip transition animation. Inflight characteristics can include the speed of the transition, the physics of the transition, and the animation style. Some of the characteristics such as speed and physics of the transition depend on input gestures provided by the user. Other characteristics such as animation style are typically independent of user input gestures, but the speed in which the animation is executed can be user input gesture dependent.
Referring now to
The swipe gestures can be recognized by a touch hardware module that processes raw data received from a touch panel existing on the electronic device. The touch module can recognize other gestures such as taps (both single and multiple simultaneous taps) and multi-touch gestures (two-finger pinch or two-finger scroll). The touch module can work in concert with the inflight module and a physics module to determine inflight characteristics for a transition animation.
The physics module can calculate movement parameters of each transition animation based on the user input gesture. The physics module can determine how fast the inflight module should execute a transition animation. The physics module can determine whether the user input gesture was sufficient to enable the page to fully flip. For example, a user may “pick up” a page to flip it, but does not have enough velocity in her swipe gesture motion, and as a result, the page may lift off, but fall back down to the original position because there was not enough momentum to carry it over the flip axis.
The location of touchdowns and liftoffs can be determined using a polar coordinate system or a Cartesian coordinate system. In the polar coordinate system, the location is calculated with respect to the flip axis. The touchdown and liftoff location with respect to the flip axis provides more data points for the physics module to determine how to instruct the inflight module how to execute a transition animation. The following description of each gesture in
Gesture 1 shows a swipe gesture crossing the flip axis at velocity X. Since X is a relatively fast velocity and the gesture crosses the flip axis, the transition animation from page 1 to page 2 can be executed at a relatively fast pace.
Gesture 2 shows a swipe gesture crossing the flip axis at velocity Y. Since Y is a relatively medium velocity and the gesture crosses flip axis, the transition animation from page 1 to page can be executed at a pace proportional to Y.
Gesture 3 shows a swipe gesture that does not cross the flip axis, but is executed at velocity X. The physics module can deduce that the user intends a fast flip because the gesture is short and fast even though the gesture does not cross the flip axis. As a result, the flip transition animation is executed at a relatively fast pace.
Gesture 4 shows a swipe gesture that does not cross the flip axis, and is executed at velocity Z, a relatively slow velocity. In response to this gesture, the physics module can deduce that there is not enough speed to carry the page over the flip axis. Thus, even though the page may lift off, it does not have enough momentum to complete a full transition. As a result, the page will fall back down and the transition remains incomplete.
Gesture 5 shows a swipe gesture that crosses the flip axis at velocity Z, a relatively slow speed. In response to this gesture, the physics module can instruct the inflight module to execute the transition slowly but enables it to fully complete. Even though the user gesture is relatively slow, she lifted off just beyond the flip axis, thereby allowing “gravity” to do the work of completing the transition.
The gestures illustrated in
Another gesture/transition combination that can be exercised in accordance with embodiments of the invention is a series of relatively high speed swipe gestures that cause a series of relatively high speed flip transitions to be executed. The resulting flip transition animations may be referred to herein as fast flips. The inflight module can execute the fast flips so that multiple pages are inflight simultaneously. For example, when a first page goes inflight and a second input gesture is received during flight of the first page, the second page goes inflight while the first page is still inflight. If a third input gesture is substantially immediately received, a third page goes inflight simultaneously with at least the second page. The first page may still be inflight in which case all three pages are simultaneously inflight. This sequence of fast flips can continue indefinitely in either direction until there are no more pages to display or the user ceases proving gesture inputs.
Although the fast flips can occur in a relatively rapid succession, and multiple pages can simultaneously be inflight, the user is provided with a succinct snapshot of at least a portion of each page before the next fast flip commences. This gives the user the ability to quickly “thumb” through the pages in a rolodex fashion and make snap judgments as to whether to further explore any of the pages she just viewed.
Referring now to
Before any transitions commence, the user can view only page 1, as illustrated by timeslice t0 of layers 720 and 730. Commensurate with timeslice t0, a fast flip gesture is received, which prompts the inflight module to commence inflight operation of page 1. When page 1 goes inflight, it begins to flip about the flip axis, pulling page 2 along with it, as shown in timeslices t1 and t2. Then around timeslice t3, another fast flip gesture input is received, which prompts the inflight module to commence inflight operation of page 2. Similar to page 1, when page 2 goes inflight, it begins to flip about the flip axis, pulling page 3 along with it, as shown in timeslices t3-5. In timeslices t3-4, however, both pages 1 and 2 are simultaneously inflight. In timeslice t5, only page 2 is in flight because page 1 had finished its inflight execution. At timeslice t6, only page 3 is visible and page 2 has finished its inflight execution.
At step 920, the first gesture input is processed and inflight characteristics for a first transition animation is determined. The first gesture input may be processed, for example, by the physics module, the touch module, or a combination of both modules to determine the inflight characteristics of the first transition animation. The inflight characteristics dictate how the inflight engine executes the transition animation. As discussed above in connection with
At step 930, the first transition animation is executed in accordance with the determined inflight characteristics. In this step, the inflight module controls the animation of a page and ultimately, how the animation is presented to a user by transmitting animation instructions to, for example, a 3D animation engine and/or graphics hardware. Moreover, the inflight module may prepare other pages for animation and use fold layers and lighting layers as appropriate.
At step 940, a second gesture input is received while the first transition animation is in flight. For example, as a first page is flipping over, the second gesture input is received. At step 950, the second gesture input is processed and inflight characteristics for a second transition animation are determined. For purposes of this discussion, assume the second gesture input is a fast flip gesture and the inflight characteristics are determined as such.
At step 960, the second transition animation is executed in accordance with the determined inflight characteristics, and as a result both the first and second transition animations are simultaneously in flight. Thus, for at least a minimum period of time, both animations are presented to the user at the same time. It is understood that additional steps may be added and that various steps may be performed in any order or simultaneously.
At step 1020, a flip transition animation is executed in response to each received gesture input, wherein execution of each transition animation sends a page inflight along a flight path, wherein viewable portions of the inflight page and a different page change as the inflight page progresses along its flight path, and wherein the predetermined period of time is such that at least two pages are simultaneously inflight. Each transition animation displays at least a portion of a different page. That is, each time a new transition animation takes flight, a portion of a page “beneath” the inflight page(s) is presented to a user. In addition, because multiple gesture inputs are received relatively rapidly in sequence, at least two transition animations are simultaneously inflight. In some embodiments, three, four, five, six, or more transition animations may simultaneously be inflight.
Lighting parameters of each page can be dynamically adjusted depending on where a given page is within a given transition animation. This way, the user is presented with visual lighting effects for each visible page as she quickly flips through the pages.
Referring now to
Beginning with
At step 1230, a multiflip transition animation is executed in response to the received user selection to transition from the first page to a content (or landing) page. The multiflip transition includes simultaneous inflight execution of several blank and is performed automatically after the user selects one of the categories. The content page can be the first page associated with the selected category.
As an alternative to the blank page multiflip embodiment discussed above in connection with
It should be understood that processes of
Touch device 1310 may include a touch sensitive panel which is wholly or partially transparent, semitransparent, non-transparent, opaque or any combination thereof. Touch device 1310 may be embodied as a touch screen, touch pad, a touch screen functioning as a touch pad (e.g., a touch screen replacing the touchpad of a laptop), a touch screen or touchpad combined or incorporated with any other input device (e.g., a touch screen or touchpad disposed on a keyboard) or any multi-dimensional object having a touch sensitive surface for receiving touch input.
In one example, touch device 1310 embodied as a touch screen may include a transparent and/or semitransparent touch sensitive panel partially or wholly positioned over at least a portion of a display. According to this embodiment, touch device 1310 functions to display graphical data transmitted from processing system 1320 (and/or another source) and also functions to receive user input. In other embodiments, touch device 1310 may be embodied as an integrated touch screen where touch sensitive components/devices are integral with display components/devices. In still other embodiments, a touch screen may be used as a supplemental or additional display screen for displaying supplemental or the same graphical data as a primary display and to receive touch input.
Touch device 1310 may be configured to detect the location of one or more touches or near touches on device 1310 based on capacitive, resistive, optical, acoustic, inductive, mechanical, chemical measurements, or any phenomena that can be measured with respect to the occurrences of the one or more touches or near touches in proximity to device 1310. Software, hardware, firmware or any combination thereof may be used to process the measurements of the detected touches to identify and track one or more gestures. A gesture may correspond to stationary or non-stationary, single or multiple, touches or near touches on touch device 1310. A gesture may be performed by moving one or more fingers or other objects in a particular manner on touch device 1310 such as tapping, pressing, rocking, scrubbing, twisting, changing orientation, pressing with varying pressure and the like at essentially the same time, contiguously, or consecutively. A gesture may be characterized by, but is not limited to a pinching, sliding, swiping, rotating, flexing, dragging, or tapping motion between or with any other finger or fingers. A single gesture may be performed with one or more hands, by one or more users, or any combination thereof.
Processing system 1320 may drive a display with graphical data to display a graphical user interface (GUI). The GUI may be configured to receive touch input via touch device 1320. Embodied as a touch screen, touch device 1310 may display the GUI. Alternatively, the GUI may be displayed on a display separate from touch device 1310. The GUI may include graphical elements displayed at particular locations within the interface. Graphical elements may include but are not limited to a variety of displayed virtual input devices including virtual scroll wheels, a virtual keyboard, virtual knobs, virtual buttons, any virtual UI, and the like. A user may perform gestures at one or more particular locations on touch device 1310 that may be associated with the graphical elements of the GUI. In other embodiments, the user may perform gestures at one or more locations that are independent of the locations of graphical elements of the GUI. Gestures performed on touch device 1310 may directly or indirectly manipulate, control, modify, move, actuate, initiate or generally affect graphical elements such as cursors, icons, media files, lists, text, all or portions of images (e.g., such as pages discussed above in connection with
Feedback may be provided to the user via communication channel 1330 in response to or based on the touch or near touches on touch device 1310. Feedback may be transmitted optically, mechanically, electrically, olfactory, acoustically, or the like or any combination thereof and in a variable or non-variable manner.
Attention is now directed towards embodiments of a system architecture that may be embodied within any portable or non-portable device including but not limited to a communication device (e.g. mobile phone, smart phone), a multi-media device (e.g., MP3 player, TV, radio), a portable or handheld computer (e.g., tablet, netbook, laptop), a desktop computer, an All-In-One desktop, a peripheral device, or any other system or device adaptable to the inclusion of system architecture 1300, including combinations of two or more of these types of devices.
Data sources 1404 represent the various sources from which content can be obtained and ultimately displayed on electronic device 1402. The content can be any suitable media such as, for example, printed media, video media, or audio media. Each data source can provide one or more articles or other content assets that can be viewed on the electronic device. Electronic device 1402 can obtain content from data sources 1404 on demand or at regular intervals. The content at data source 1404 can update continuously.
It should be apparent that the architecture shown in
Communications circuitry 1450 can include RF circuitry 1452 and/or port 1454 for sending and receiving information. RF circuitry 1452 permits transmission of information over a wireless link or network to one or more other devices and includes well-known circuitry for performing this function. Port 1454 permits transmission of information over a wired link. Communications circuitry 1450 can communicate, for example, with data sources 1404. Communications circuitry 1450 can be coupled to processing system 1420 via peripherals interface 1424. Interface 1424 can include various known components for establishing and maintaining communication between peripherals and processing system 1420.
Audio circuitry 1470 can be coupled to an audio speaker (not shown) and a microphone (not shown) and includes known circuitry for processing voice signals received from interface 1424 to enable a user to communicate in real-time with other users. In some embodiments, audio circuitry 1470 includes a headphone jack (not shown).
Peripherals interface 1424 can couple various peripherals of the system to processor 1426 and computer-readable medium 1410. One or more processors 1426 can communicate with one or more computer-readable mediums 1410 via controller 1422. Computer-readable medium 1410 can be any device or medium that can store code and/or data for use by one or more processors 1426. Medium 1410 can include a memory hierarchy, including but not limited to cache, main memory and secondary memory. The memory hierarchy can be implemented using any combination of RAM (e.g., SRAM, DRAM, DDRAM), ROM, FLASH, magnetic and/or optical storage devices, such as disk drives, magnetic tape, CDs (compact disks) and DVDs (digital video discs). Medium 1410 may also include a transmission medium for carrying information-bearing signals indicative of computer instructions or data (with or without a carrier wave upon which the signals are modulated). For example, the transmission medium may include a communications network, including but not limited to the Internet (also referred to as the World Wide Web), intranet(s), Local Area Networks (LANs), Wide Local Area Networks (WLANs), Storage Area Networks (SANs), Metropolitan Area Networks (MAN) and the like.
One or more processors 1426 can run various software components stored in medium 1410 to perform various functions for device 1402. In some embodiments, the software components include operating system 1411, communication module (or set of instructions) 1412, touch processing module (or set of instructions) 1412, physics module (or set of instructions) 1414, inflight module (or set of instructions) 1415, multiflip module (or set of instructions) 1416, lighting module (or set of instructions) 1417, and one or more applications (or set of instructions) 1418. Each of these modules and above noted applications correspond to a set of instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. In some embodiments, medium 1410 may store a subset of the modules and data structures identified above. Furthermore, medium 1410 may store additional modules and data structures not described above.
Operating system 1411 can include various procedures, sets of instructions, software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 1412 facilitates communication with other devices using communications circuitry 1450 and includes various software components for handling data received from RF circuitry 1452 and/or port 1454.
Touch processing module 1413 includes various software components for performing various tasks associated with touch hardware 14334 including but not limited to receiving and processing touch input received from I/O device 1430 via touch I/O device controller 1432. For example, touch processing module 1413 can also include software components for performing tasks associated with other I/O devices (not shown).
Physics, inflight, multiflip, and lighting modules 1414-1417 include instructions for performing different flip transition animations in accordance with various embodiments of the invention. Modules 1414-1417 may use data provided by other modules within medium 1410 or operate in concert with the modules to execute transition animations.
Physics module 1414 can determine inflight characteristics of transition animations based on gesture inputs processed by touch processing module 1413. For example, physics module 1414 can determine the speed at which the transition animation is performed. As another example, module 1414 can determine whether sufficient momentum is present (based on the input gesture) to enable the transition animation to cross the flip axis and complete its inflight path.
Inflight module 1415 controls the transition animation based on data provided by physics module 1414, touch processing module 1413, lighting module 1417, and/or multiflip module 1416. Inflight module 1415 can include various known software components for rendering, animating and displaying graphical objects on a display surface. In embodiments in which touch hardware 1434 is a touch sensitive display (e.g., touch screen), inflight module 1415 includes components for rendering, displaying, and animating objects on the touch sensitive display. More particularly, module 1415 can provide animation instructions to 3D animation engine 1442, which can render the graphics and provide the rendering to graphics I/O controller 1444 so it can display the graphics on display 1446.
Inflight module 1415 can include instructions for converting pages into animation elements suitable for transition animations. For example, module 1415 can obtain pages from storage 1460 and prepare those pages for transition animations. For example, the pages can be prepared by being “split” into first and second halves. Module 1415 can use fold layers to keep track of which pages to include in a sequence of flip transition animations. Module 1415 can also incorporate lighting layers for each page.
Lighting module 1417 includes instructions for dynamically adjusting the lighting of each page as it moves along its flight path. Multiflip module 1416 includes instructions for simultaneously displaying multiple blank pages as part of a transition from one page to another.
One or more applications 1419 can include any applications installed on system 1402, including without limitation, a browser, address book, contact list, email, instant messaging, word processing, keyboard emulation, widgets, JAVA-enabled applications, encryption, digital rights management, voice recognition, voice replication, location determination capability (such as that provided by the global positioning system (GPS)), a music player, etc.
Touch I/O controller 1432 is coupled to touch hardware 1434 for controlling or performing various functions. Touch hardware 1432 communicates with processing system 1420 via touch I/O device controller 1432, which includes various components for processing user touch input (e.g., scanning hardware). One or more other input controllers (not shown) receives/sends electrical signals from/to other I/O devices (not shown). Other I/O devices may include physical buttons, dials, slider switches, sticks, keyboards, touch pads, additional display screens, or any combination thereof.
If embodied as a touch screen, touch hardware 1434 displays visual output to the user in a GUI. The visual output may include text, graphics, video, and any combination thereof. Some or all of the visual output may correspond to user-interface objects. Touch hardware 1434 forms a touch-sensitive surface that accepts touch input from the user. Touch hardware 1434 and touch controller 1432 (along with any associated modules and/or sets of instructions in medium 1410) detects and tracks touches or near touches (and any movement or release of the touch) on touch hardware 1434 and converts the detected touch input into interaction with graphical objects, such as one or more user-interface objects. In the case in which hardware 1434 is embodied as a touch screen, the user can directly interact with graphical objects that are displayed on the touch screen. Alternatively, in the case in which hardware 1434 is embodied as a touch device other than a touch screen (e.g., a touch pad), the user may indirectly interact with graphical objects that are displayed on a separate display screen.
Embodiments in which touch hardware 1434 is a touch screen, the touch screen may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, OLED (organic LED), or OEL (organic electro luminescence), although other display technologies may be used in other embodiments.
Feedback may be provided by touch hardware 1434 based on the user's touch input as well as a state or states of what is being displayed and/or of the computing system. Feedback may be transmitted optically (e.g., light signal or displayed image), mechanically (e.g., haptic feedback, touch feedback, force feedback, or the like), electrically (e.g., electrical stimulation), olfactory, acoustically (e.g., beep or the like), or the like or any combination thereof and in a variable or non-variable manner.
In some embodiments, peripherals interface 1424, one or more processors 1426, and memory controller 1422 may be implemented on a single chip. In some other embodiments, they may be implemented on separate chips. Storage 1460 can any suitable medium for storing data, including, for example, volatile memory (e.g., cache, RAM), non-volatile memory (e.g., Flash, hard-disk drive), or a both for storing data, including pages used for transition animations.
Notification module 238 can interface with one or more Application Programming Interfaces (“APIs”) to provide a notification center that can generate various types of notifications when system 200 is in either a locked state or an unlocked state. Furthermore, notification module 238 can provide multiple settings for customizing the notification center.
The described embodiments of the invention are presented for the purpose of illustration and not of limitation.
This application is a continuation of co-pending U.S. application Ser. No. 14/590,816, filed Jan. 6, 2015, which is a continuation of U.S. application Ser. No. 13/284,678 (now U.S. Pat. No. 8,935,629), filed Oct. 28, 2011, each of which is incorporated by reference their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 8473860 | Fong et al. | Jun 2013 | B2 |
| 8713011 | Asai et al. | Apr 2014 | B2 |
| 8756523 | Chiba et al. | Jun 2014 | B2 |
| 8788964 | Shin et al. | Jul 2014 | B2 |
| 8799778 | Flynn et al. | Aug 2014 | B2 |
| 8819569 | SanGiovanni et al. | Aug 2014 | B2 |
| 20050022139 | Gettman et al. | Jan 2005 | A1 |
| 20070016671 | Lee et al. | Jan 2007 | A1 |
| 20090007017 | Anzures | Jan 2009 | A1 |
| 20090172532 | Chaudhri | Jul 2009 | A1 |
| 20110078560 | Weeldreyer et al. | Mar 2011 | A1 |
| 20120096392 | Ording et al. | Apr 2012 | A1 |
| 20130080968 | Hanson et al. | Mar 2013 | A1 |
| 20130205202 | Xiao et al. | Aug 2013 | A1 |
| Entry |
|---|
| PCT International Search Report and Written Opinion, PCT/US2012/062046, Jan. 9, 2013, 9 pages. |
| US Office Action, U.S. Appl. No. 13/284,678, Mar. 26, 2014, 18 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20150370432 A1 | Dec 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14590816 | Jan 2015 | US |
| Child | 14835705 | US | |
| Parent | 13284678 | Oct 2011 | US |
| Child | 14590816 | US |
