SYSTEM AND METHOD FOR CONTINUING PLAYBACK IN WIDGET AFTER APP IS BACKGROUNDED
This disclosure generally relates to systems and methods that facilitate transitioning a current playback of a video in a video application to a video widget when the video application is moved to a background of a multitasking operating system in which the video application is executing. The transition occurs seamlessly at a point of the current playback in the video application when the video application is moved to the background. Furthermore, upon the video application being moved to the foreground of the multitasking operating system, current playback of the video in the video widget is seamlessly transitioned to the video application.
This application is a continuation of U.S. patent application Ser. No. 15/619,038, filed Jun. 9, 2017, which is a continuation of U.S. patent application Ser. No. 14/206,838, filed Mar. 12, 2014, each of which is hereby incorporated by reference herein in its entirety.
TECHNICAL FIELDThis disclosure generally relates to systems and methods that facilitate seamlessly transitioning a current playback of a video in a video application to a video widget when the video application is moved to a background of a multitasking operating system in which the video application is executing. The transition occurs seamlessly at a point of the current playback in the video application when the video application is moved to the background. Furthermore, upon the video application being moved to the foreground of the multitasking operating system, current playback of the video in the video widget is seamlessly transitioned to the video application.
BACKGROUNDMobile devices allow users to switch across varieties of applications installed on the device. However, when an application, such as a video application, that is currently in the foreground of the operating system of the mobile device (e.g., an application that the user has selected for current operation and/or interaction) is moved to the background of the operating system (e.g., an application that the user has navigated away from), the video application is stopped, paused, or closed. This is not an ideal user experience, for example, when the user may want to employ another application or check notifications, but let the backgrounded video application continue to play the video.
SUMMARYA simplified summary is provided herein to help enable a basic or general understanding of various aspects of exemplary, non-limiting embodiments that follow in the more detailed description and the accompanying drawings. This summary is not intended, however, as an extensive or exhaustive overview. Instead, the purpose of this summary is to present some concepts related to some exemplary non-limiting embodiments in simplified form as a prelude to more detailed description of the various embodiments that follow in the disclosure.
In accordance with a non-limiting implementation, a first input is detected that moves a video application from a foreground to a background of a multitasking operating system; and in response to the first input: a first current playback point of the video in the video application is determined, playback of the video at the first current playback point is initiated in a widget application, and the video application is moved to the background of the multitasking operating system.
In accordance with a non-limiting implementation, an application transfer component is configured to determine that a video application has been moved from a foreground to a background of an operating system of the device, determine a first current playback point of the video in the video application, and start playback of the video at the first current playback point in a video widget.
In accordance with a non-limiting implementation, it is detected that a video application has been moved from a foreground to a background of an operating system of the device, a first current playback point of the video in the video application is identified, and playback of the video at the first current playback point in a video widget is commenced.
These and other implementations and embodiments are described in more detail below.
Various aspects or features of this disclosure are described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In this specification, numerous specific details are set forth in order to provide a thorough understanding of this disclosure. It should be understood, however, that certain aspects of this disclosure may be practiced without these specific details, or with other methods, components, materials, etc. In other instances, well-known structures and devices are shown in block diagram form to facilitate describing this disclosure.
In accordance with various disclosed aspects, a mechanism is provided for a client device (e.g., user device) to seamlessly transition (e.g., transfer, handoff, shift, switch, or move) a current playback of a video in a video application to a video widget (e.g., live widget, real-time widget, live tile, widget application, or live icon) when the video application is moved to a background of a multitasking operating system in which the video application is executing. Upon the video application being moved to the foreground of the multitasking operating system, a mechanism is provided to seamlessly transition current playback of the video in the video widget to the video application. It is to be appreciated that in a non-limiting example, a widget can be an application that comprises a subset of functionality of a corresponding full application. For example, the video widget can comprise a subset of the functionality of the video application. In another example, the video widget can be a completely different type of application from the video application (e.g., different form, different publisher, different codecs supported, different functionality, or any other suitable differentiating characteristic)
While embodiments presented herein use videos being transitioned between a video application and video widget for ease of explanation, it is to be appreciated that concepts herein are applicable to any suitable content for which continued play can be transitioned back and forth between an application and a corresponding widget, non-limiting examples of which can include, music, speeches, cartoons, short films, movies, televisions shows, games, applications, or any other suitable creative work.
Referring now to the drawings,
Client device 110 and server 150 include at least one memory that stores computer executable components and at least one processor that executes the computer executable components stored in the memory, a non-limiting example of which can be found with reference to
Client device 110 and server 150 can be any suitable type of device for recording, interacting with, receiving, accessing, or supplying data locally, or remotely over a wired or wireless communication link, non-limiting examples of which include a wearable device or a non-wearable device. Wearable device can include, for example, heads-up display glasses, a monocle, eyeglasses, contact lens, sunglasses, a headset, a visor, a cap, a helmet, a mask, a headband, clothing, camera, video camera, or any other suitable device capable of recording, interacting with, receiving, accessing, or supplying data that can be worn by a human or non-human user. Non-wearable device can include, for example, a mobile device, a mobile phone, a camera, a camcorder, a video camera, personal data assistant, laptop computer, tablet computer, desktop computer, server system, cable set top box, satellite set top box, cable modem, television set, monitor, media extender device, Blu-ray device, DVD (digital versatile disc or digital video disc) device, compact disc device, video game system, portable video game console, audio/video receiver, radio device, portable music player, navigation system, car stereo, sensor, or any other suitable device capable of recording, interacting with, receiving, accessing, or supplying data. Moreover, Client device 110 and server 150 can include a user interface (e.g., a web browser or application), that can receive and present displays and data generated locally or remotely.
Referring to
Referring to
Video application 312 can be moved to the background of the multitasking operating system on client device 110 by user action or operating system action. For example, a user can select home button 307 to move video application 312 to the background and display the home screen 311. In another example, a notification can pop-up informing the user of an email that has arrived, and the user can select the notification to move video application 312 to the background and display an email application (not shown). In a further example, the multitasking operating system on client device 110 can automatically move video application 312 to the background and display another screen or application, such as based upon system defined or user defined settings and/or preferences. It is to be appreciated that any suitable mechanism can be employed to move video application 312 to the background or foreground of the multitasking operating system on client device 110.
Referring back to
Referring to
Referring back to
Referring back to
Referring to
It is to be appreciated that while the example herein discloses a video widget 360 playing a video that was transitioned from a video application 312 and then transitioned back to the video application 312, a user can initiate playback of a video in video widget 360 and upon a video application 312 being initiated or moved to the foreground, a current playback of the video in video widget 360 can be transitioned from video widget 360 to video application 312.
One of ordinary skill in the art can appreciate that the various embodiments described herein can be implemented in connection with any computer or other client or server device, which can be deployed as part of a computer network or in a distributed computing environment, and can be connected to any kind of data store where media may be found. In this regard, the various embodiments described herein can be implemented in any computer system or environment having any number of memory or storage units, and any number of applications and processes occurring across any number of storage units. This includes, but is not limited to, an environment with server computers and client computers deployed in a network environment or a distributed computing environment, having remote or local storage.
Distributed computing provides sharing of computer resources and services by communicative exchange among computing devices and systems. These resources and services include the exchange of information, cache storage and disk storage for objects, such as files. These resources and services can also include the sharing of processing power across multiple processing units for load balancing, expansion of resources, specialization of processing, and the like. Distributed computing takes advantage of network connectivity, allowing clients to leverage their collective power to benefit the entire enterprise. In this regard, a variety of devices may have applications, objects or resources that may participate in the various embodiments of this disclosure.
Each computing object 610, 612, etc. and computing objects or devices 618, 620, 622, 624, 626, 628, etc. can communicate with one or more other computing objects 610, 612, etc. and computing objects or devices 618, 620, 622, 624, 626, 628, etc. by way of the communications network 640, either directly or indirectly. Even though illustrated as a single element in
There are a variety of systems, components, and network configurations that support distributed computing environments. For example, computing systems can be connected together by wired or wireless systems, by local networks or widely distributed networks. Currently, many networks are coupled to the Internet, which provides an infrastructure for widely distributed computing and encompasses many different networks, though any suitable network infrastructure can be used for exemplary communications made incident to the systems as described in various embodiments herein.
Thus, a host of network topologies and network infrastructures, such as client/server, peer-to-peer, or hybrid architectures, can be utilized. The “client” is a member of a class or group that uses the services of another class or group. A client can be a computer process, e.g., roughly a set of instructions or tasks, that requests a service provided by another program or process. A client process may utilize the requested service without having to “know” all working details about the other program or the service itself.
In a client/server architecture, particularly a networked system, a client can be a computer that accesses shared network resources provided by another computer, e.g., a server. In the illustration of
A server is typically a remote computer system accessible over a remote or local network, such as the Internet or wireless network infrastructures. The client process may be active in a first computer system, and the server process may be active in a second computer system, communicating with one another over a communications medium, thus providing distributed functionality and allowing multiple clients to take advantage of the information-gathering capabilities of the server. Any software objects utilized pursuant to the techniques described herein can be provided standalone, or distributed across multiple computing devices or objects.
In a network environment in which the communications network/bus 640 is the Internet, for example, the computing objects 610, 612, etc. can be Web servers, file servers, media servers, etc. with which the client computing objects or devices 618, 620, 622, 624, 626, 628, etc. communicate via any of a number of known protocols, such as the hypertext transfer protocol (HTTP). Objects 610, 612, etc. may also serve as client computing objects or devices 618, 620, 622, 624, 626, 628, etc., as may be characteristic of a distributed computing environment.
Exemplary Computing DeviceAs mentioned, advantageously, the techniques described herein can be applied to any suitable device. It is to be understood, therefore, that handheld, portable and other computing devices and computing objects of all kinds are contemplated for use in connection with the various embodiments. Accordingly, the computer described below in
Although not required, embodiments can partly be implemented via an operating system, for use by a developer of services for a device or object, and/or included within application software that operates to perform one or more functional aspects of the various embodiments described herein. Software may be described in the general context of computer executable instructions, such as program modules, being executed by one or more computers, such as client workstations, servers or other devices. Those skilled in the art will appreciate that computer systems have a variety of configurations and protocols that can be used to communicate data, and thus, no particular configuration or protocol is to be considered limiting.
With reference to
Computer 710 typically includes a variety of computer readable media and can be any available media that can be accessed by computer 710. The system memory 730 may include computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) and/or random access memory (RAM). By way of example, and not limitation, system memory 730 may also include an operating system, application programs, other program modules, and program data.
A user can enter commands and information into the computer 710 through input devices 740, non-limiting examples of which can include a keyboard, keypad, a pointing device, a mouse, stylus, touchpad, touchscreen, trackball, motion detector, camera, microphone, joystick, game pad, scanner, or any other device that allows the user to interact with computer 710. A monitor or other type of display device is also connected to the system bus 722 via an interface, such as output interface 750. In addition to a monitor, computers can also include other peripheral output devices such as speakers and a printer, which may be connected through output interface 750.
The computer 710 may operate in a networked or distributed environment using logical connections to one or more other remote computers, such as remote computer 770 via network interface 760. The remote computer 770 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, or any other remote media consumption or transmission device, and may include any or all of the elements described above relative to the computer 710. The logical connections depicted in
As mentioned above, while exemplary embodiments have been described in connection with various computing devices and network architectures, the underlying concepts may be applied to any network system and any computing device or system in which it is desirable to publish or consume media in a flexible way.
Also, there are multiple ways to implement the same or similar functionality, e.g., an appropriate API, tool kit, driver code, operating system, control, standalone or downloadable software object, etc. which enables applications and services to take advantage of the techniques described herein. Thus, embodiments herein are contemplated from the standpoint of an API (or other software object), as well as from a software or hardware object that implements one or more aspects described herein. Thus, various embodiments described herein can have aspects that are wholly in hardware, partly in hardware and partly in software, as well as in software.
The word “exemplary” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the aspects disclosed herein are not limited by such examples. In addition, any aspect or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, for the avoidance of doubt, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.
Computing devices typically include a variety of media, which can include computer-readable storage media and/or communications media, in which these two terms are used herein differently from one another as follows. Computer-readable storage media can be any available storage media that can be accessed by the computer, is typically of a non-transitory nature, and can include both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable instructions, program modules, structured data, or unstructured data. Computer-readable storage media can include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other tangible and/or non-transitory media which can be used to store desired information. Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.
On the other hand, communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media. The term “modulated data signal” or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
As mentioned, the various techniques described herein may be implemented in connection with hardware or software or, where appropriate, with a combination of both. As used herein, the terms “component,” “system” and the like are likewise intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on computer and the computer can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. Further, a “device” can come in the form of specially designed hardware; generalized hardware made specialized by the execution of software thereon that enables the hardware to perform specific function (e.g., coding and/or decoding); software stored on a computer readable medium; or a combination thereof.
The aforementioned systems have been described with respect to interaction between several components. It can be appreciated that such systems and components can include those components or specified sub-components, some of the specified components or sub-components, and/or additional components, and according to various permutations and combinations of the foregoing. Sub-components can also be implemented as components communicatively coupled to other components rather than included within parent components (hierarchical). Additionally, it is to be noted that one or more components may be combined into a single component providing aggregate functionality or divided into several separate sub-components, and that any one or more middle layers, such as a management layer, may be provided to communicatively couple to such sub-components in order to provide integrated functionality. Any components described herein may also interact with one or more other components not specifically described herein but generally known by those of skill in the art.
In order to provide for or aid in the numerous inferences described herein (e.g. inferring relationships between metadata or inferring topics of interest to users), components described herein can examine the entirety or a subset of the data to which it is granted access and can provide for reasoning about or infer states of the system, environment, etc. from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The inference can be probabilistic—that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data.
Such inference can result in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources. Various classification (explicitly and/or implicitly trained) schemes and/or systems (e.g., support vector machines, neural networks, expert systems, Bayesian belief networks, fuzzy logic, data fusion engines, etc.) can be employed in connection with performing automatic and/or inferred action in connection with the claimed subject matter.
A classifier can map an input attribute vector, z=(z1, z2, z3, z4, zn), to a] confidence that the input belongs to a class, as by f(z)=confidence(class). Such classification can employ a probabilistic and/or statistical-based analysis (e.g., factoring into the analysis utilities and costs) to prognose or infer an action that a user desires to be automatically performed. A support vector machine (SVM) is an example of a classifier that can be employed. The SVM operates by finding a hyper-surface in the space of possible inputs, where the hyper-surface attempts to split the triggering criteria from the non-triggering events. Intuitively, this makes the classification correct for testing data that is near, but not identical to training data. Other directed and undirected model classification approaches include, e.g., naïve Bayes, Bayesian networks, decision trees, neural networks, fuzzy logic models, and probabilistic classification models providing different patterns of independence can be employed. Classification as used herein also is inclusive of statistical regression that is utilized to develop models of priority.
In view of the exemplary systems described above, methodologies that may be implemented in accordance with the described subject matter will be better appreciated with reference to the flowcharts of the various figures. While for purposes of simplicity of explanation, the methodologies are shown and described as a series of blocks, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Where non-sequential, or branched, flow is illustrated via flowchart, it can be appreciated that various other branches, flow paths, and orders of the blocks, may be implemented which achieve the same or a similar result. Moreover, not all illustrated blocks may be required to implement the methodologies described hereinafter.
In addition to the various embodiments described herein, it is to be understood that other similar embodiments can be used or modifications and additions can be made to the described embodiment(s) for performing the same or equivalent function of the corresponding embodiment(s) without deviating there from. Still further, multiple processing chips or multiple devices can share the performance of one or more functions described herein, and similarly, storage can be effected across a plurality of devices. Accordingly, the invention is not to be limited to any single embodiment, but rather can be construed in breadth, spirit and scope in accordance with the appended claims.
Claims
1. A method for transitioning content, the method comprising:
- causing, by a device including a hardware processor, a media content item to be played back in an application that is in a foreground state on the device;
- detecting that the application presenting the media content item has moved from the foreground state to a background state on the device; and
- in response to the detection, causing a widget application to be presented on an interface of the device, wherein the media content item continues to be played back within the widget application.
2. The method of claim 1, wherein the widget application is persistent on a display of the device.
3. The method of claim 1, wherein the widget application is a floating widget and wherein the continued playback of the media content item within the widget application comprises activating the floating widget.
4. The method of claim 1, wherein the application is moved to the background state by stopping playback of the media content item at a playback position in the application.
5. The method of claim 1, further comprising determining a playback position of the media content item in the application in response to detecting that the application presenting the media content item has moved from the foreground state to the background state on the device.
6. The method of claim 5, wherein the media content item continues to be played back within the widget application at the determined playback position of the media content item.
7. The method of claim 5, wherein the playback position of the media content item in the application is determined by receiving data from the application indicating the playback position.
8. The method of claim 5, wherein the playback position of the media content item in the application is determined by tracking current playback of the media content item in the application.
9. The method of claim 5, further comprising:
- receiving a second input that moves the application into a foreground of a multitasking operating system; and
- in response to the second input: determining a second playback position of the media content item in the widget application based on playback data received from the widget application; moving the application to the foreground of the multitasking operating system; causing the media content item to continue being played back at the second playback position in the application; and causing the playback of the media content item in the widget application to cease.
10. The method of claim 9, wherein initiating playback of the media content item at the second playback position comprises:
- presenting an element inquiring whether to continue playback of the media content item in the application;
- in response to receiving third input indicating to continue playback of the media content item, continuing playback of the media content item at the second playback position in the application; and
- in response to receiving third input indicating not to continue playback of the media content item, continuing playing back the media content item in the widget application.
11. A system for transitioning content, the system comprising:
- a memory; and
- a hardware processor that, when executing computer executable instructions stored in the memory, is configured to: cause a media content item to be played back in an application that is in a foreground state on a device; detect that the application presenting the media content item has moved from the foreground state to a background state on the device; and in response to the detection, cause a widget application to be presented on an interface of the device, wherein the media content item continues to be played back within the widget application.
12. The system of claim 11, wherein the widget application is persistent on a display of the device.
13. The system of claim 11, wherein the widget application is a floating widget and wherein the continued playback of the media content item within the widget application comprises activating the floating widget.
14. The system of claim 11, wherein the application is moved to the background state by stopping playback of the media content item at a playback position in the application.
15. The system of claim 11, wherein the hardware processor is further configured to determine a playback position of the media content item in the application in response to detecting that the application presenting the media content item has moved from the foreground state to the background state on the device.
16. The system of claim 15, wherein the media content item continues to be played back within the widget application at the determined playback position of the media content item.
17. The system of claim 15, wherein the playback position of the media content item in the application is determined by receiving data from the application indicating the playback position.
18. The system of claim 15, wherein the playback position of the media content item in the application is determined by tracking current playback of the media content item in the application.
19. The system of claim 15, wherein the hardware processor is further configured to:
- receive a second input that moves the application into a foreground of a multitasking operating system; and
- in response to the second input: determine a second playback position of the media content item in the widget application based on playback data received from the widget application; move the application to the foreground of the multitasking operating system; cause the media content item to continue being played back at the second playback position in the application; and cause the playback of the media content item in the widget application to cease.
20. The system of claim 19, wherein initiating playback of the media content item at the second playback position comprises:
- presenting an element inquiring whether to continue playback of the media content item in the application;
- in response to receiving third input indicating to continue playback of the media content item, continuing playback of the media content item at the second playback position in the application; and
21. A non-transitory computer-readable medium containing computer executable instructions that, when executed by a processor, cause the processor to perform a method for transitioning content, the method comprising:
- causing a media content item to be played back in an application that is in a foreground state on a device;
- detecting that the application presenting the media content item has moved from the foreground state to a background state on the device; and
- in response to the detection, causing a widget application to be presented on an interface of the device, wherein the media content item continues to be played back within the widget application.
Type: Application
Filed: Nov 4, 2019
Publication Date: Feb 27, 2020
Inventors: Kevin Greene (San Francisco, CA), Tim Johnson (Mountain View, CA)
Application Number: 16/673,192
