Users are able to access a plurality of applications on their computing devices. In addition, a user may be able to create multiple user accounts with many of these applications. In this regard, the user may have different purposes for each user account and for each application. Switching user accounts may require the user to log out of a particular account, and then log in to another account by typing in the necessary credentials, such as a username and password. This can be time consuming and cumbersome, especially when using handheld communication devices such as mobile phones.
A system and method for quickly and effortlessly switching between user accounts in an application are provided. A user may have multiple user accounts associated with his or her computing device. An application running on the device may display an indicator for each user account that the user has with that particular application. In this regard, when a first user account is displayed with a first indicator, the user may swipe the display of their computing device to switch to, for example, a second user account. As another example, the user may tap the second user account indicator to switch to that account. When the second user account is selected, the details and settings associated with that user account may be displayed and replace the details and settings associated with the first user account.
Aspects of the technology generally pertain to quickly and efficiently switching between user accounts while using a computing device. A user may have more than one user account for a particular application, such as, for example, e-mail. In this regard, to quickly switch between the different user accounts, a user may swipe, using an input mechanism, across the screen. The swipe may be done, for instance, using a cursor of a mouse, a stylus, or the user's finger. The swipe may be done in a predetermined direction, e.g., from left to right, right to left, etc. Upon completion or concurrently with the swipe, the computing device may switch user accounts. For example, prior to the swipe, a user's work e-mail account along with all the details and settings associated therewith may be displayed. After the swipe the user's personal e-mail account along with all of the details and settings associated therewith may be loaded and displayed. In this regard, as a result of the swipe the user can quickly and efficiently switch between user accounts.
While using a computing device, such as a mobile phone, tablet PC or netbook, a user may utilize multiple applications. These applications may include, as some examples, e-mail, text documents, games, mapping applications that provide directions, and cloud storage applications that provide access to stored music, documents, spreadsheets, etc.
As noted above, the user may have more than one account associated with any particular application. For instance, when the user accesses an e-mail application, the user may have more than one e-mail account. The user may have a work e-mail account set up specifically for their occupational communications, and a personal e-mail account set up for their personal communications.
The e-mail application may display each e-mail account associated with the user. For instance, the e-mail application may display indications of each user account. As an example, the indications may be images and/or text that were pre-selected by the user. In addition, each user account may have a theme associated therewith, such as a background, color scheme, sound, etc., that the user may have chosen. The background may be, for example, the sky and clouds for the personal e-mail account, and sky rise buildings or mountains for the work e-mail account.
According to one aspect of the technology, the user is able to switch between the two e-mail accounts within the e-mail application. For instance, the user can swipe across the display of the computing device using an input mechanism. For example, the user may use a mouse to hold a click and then swipe a cursor across the screen. As another example, the user may press their figure on, or hover over, the touch-screen display and swipe in a particular direction.
Performing the swipe function causes the application to switch e-mail accounts. For example, if the user was viewing their work e-mail account prior to the swipe, then after the swipe the personal e-mail account may be displayed instead. Thus, after the swipe the user would be able to check his or her personal e-mail account's inbox, drafts, sent e-mails, etc. In addition, the user may switch back to their work e-mail account using the same swiping function described above.
Memory 174 may also include data 178 that may be retrieved, manipulated or stored by the processor. The memory may be of any type capable of storing information accessible by the processor, such as a hard-drive, memory card, ROM, RAM, DVD, CD-ROM, write-capable, and read-only memories.
The instructions 176 may be any set of instructions to be executed directly, such as machine code, or indirectly, such as scripts, by the processor. In that regard, the terms “instructions,” “application,” “steps” and “programs” may be used interchangeably herein. The instructions may be stored in object code format for direct processing by the processor, or in any other computing device language including scripts or collections of independent source code modules that are interpreted on demand or compiled in advance. Functions, methods and routines of the instructions are explained in more detail below.
Data 178 may be retrieved, stored or modified by processor 172 in accordance with the instructions 176. For instance, although the subject matter described herein is not limited by any particular data structure, the data may be stored in computer registers, in a relational database as a table having many different fields and records, or XML documents. The data may also be formatted in any computing device-readable format such as, but not limited to, binary values, ASCII or Unicode. Moreover, the data may comprise any information sufficient to identify the relevant information, such as numbers, descriptive text, proprietary codes, pointers, references to data stored in other memories such as at other network locations, or information that is used by a function to calculate the relevant data.
The processor 172 may be any conventional processor, such as a commercially available CPU. Alternatively, the processor may be a dedicated component such as an ASIC or other hardware-based processor. Although not necessary, computing device 130 may include specialized hardware components to perform specific computing processes, such as encoding, decoding or modifying audio.
The computing device 170 may be at one node of a network 105 and capable of directly and indirectly communicating with other nodes of network 105. Although only a few computing devices are depicted in
As an example, computing device 170 may include a web server that is capable of communicating with storage system 160 as well as computing devices 110, 130, 140, and 150 via the network 105. For example, server computing device 170 may use network 105 to transmit and present information to a user, such as user 210, 230, 240, or 250 on a display of computing devices 110, 130, 140, or 150. In this regard, computing devices 110, 130, 140, and 150 may be considered client computing devices and may perform all or some of the features described herein.
The client computing device 110 may include a processor 112, memory 114, instructions 116, and data 118, all components of which may function similarly the processor 172, memory 174, instructions 176, and data 178 as described above with respect to server computing device 170. In addition, each of the client computing devices may be configured similarly to the client computing device 110, with a processor, memory and instructions, and data as described above. Each client computing device 110, 130, 140, and 150, may be a personal computing device intended for use by user 210, 230, 240, and 250, respectively and as shown in
The client computing devices 110, 130, 140, and 150, may each comprise a mobile computing device capable of wirelessly exchanging data with a server over a network such as the Internet. By way of example only, each client computing device may be a mobile phone or a device such as a wireless-enabled PDA, a tablet PC, a wearable computing device or a netbook that is capable of obtaining information via the Internet. As an example, the user may input information using a keyboard, a keypad, a microphone, a touch screen or via visual signals captured by a camera. In another example, one or more of the client computing devices, such as device 150, may be full-sized personal computer.
Client computing devices 110, 130, 140, and 150, may also include a geographic position component (not shown) in communication with the client computing device's processor for determining the geographic location of the device. For example, the position component may include a GPS receiver to determine the device's latitude, longitude and/or altitude position. The client computing device's location may also be determined using one or more localizing techniques, such as cellular tower triangulation, IP address lookup, Wi-Fi SSID lookup (e.g., querying a database that maps Wi-Fi SSIDs to geographic positions), a Wi-Fi positioning system or other techniques, all with various ranges of accuracy.
The client computing devices may also include other devices such as an accelerometer, gyroscope, compass or another orientation detection device 124 to determine the orientation of the client computing device. By way of example only, an acceleration device may determine the client computing device's pitch, yaw or roll (or changes thereto) relative to the direction of gravity or a plane perpendicular thereto. The client computing devices' provision of location and orientation data as set forth herein may be provided automatically to the user, as well as to other computing devices such client device 140 via network 110.
As with memory 174, storage system 160 can be of any type of computerized storage capable of storing information accessible by one or more of server computing devices 110, such as a hard-drive, memory card, ROM, RAM, DVD, CD-ROM, write-capable, and read-only memories. In addition, storage system 160 may include a distributed storage system where data is stored on a plurality of different storage devices which may be physically located at the same or different geographic locations. Storage system 160 may be connected to the computing devices via the network 105 as shown in
Storage system 160 may store information related to any number of applications accessible by computing devices 110, 130, 140, and 150. For instance, storage system 160 may store e-mails associated with a particular user account, such as e-mails from an inbox, deleted e-mails, draft e-mails, or sent e-mails. Alternatively, storage system 160 may be store text documents, spreadsheets, music, etc., which are associated with a particular user account. Previous searches conducted by a user may be stored as well, such as web-based searches in a web browser, or searches in a map application such location searches or direction searches.
Although
Various aspects of the system are particularly advantageous when used in connection with e-mail applications. While most of the descriptions of the system and method herein focus on user accounts associated with an e-mail application, the system and method may be used in a wide variety of applications that permit multiple user accounts that are associated with settings for a particular user.
In one scenario, a plurality of applications is available to a user while using his or her computing device. For example, while using mobile computing device 110, a user 210 may access e-mail or other productivity applications, games, maps, and cloud storage applications to access documents, spreadsheets or music or other content. As shown in example 300 of
The e-mail application may have two distinct portions that display different information to the user. For instance, a top portion 310 may contain indicators, such as icons, of the various user accounts associated with the e-mail application. And bottom portion 340 may contain certain features of the e-mail application. For example, the bottom portion 340 of
As mentioned above, the user may have more than one user account associated with the e-mail application. For instance, as shown in example 300 of
Each indicator may be of an image or text, which may be selected by the user or assigned by the application. For instance, as shown in example 300 of
As illustrated in example 300 of
The user may decide to switch between the different user accounts. In this regard, the user may perform a swiping action on the top portion 310 of the e-mail application of computing device 110. The swipe may be performed using an input mechanism, such as, for example, a cursor of a mouse, a stylus, or a finger across a touch screen display. By way of example only, the user may swipe their finger across the screen in a given direction. The user swipe may be in a predetermined direction, e.g., horizontally, vertically, or diagonally.
As shown in example 400 of
Example 500 of
Concurrently, or after the user performs the swiping motion, a transitional stage of switching between user accounts takes place. For instance, as already discussed above with respect to
In addition to the transition of the background, the e-mail address (or other account) transitions as well. For instance, as shown in
Examples 700 and 800 of
When the transitional stage is complete, the details and information associated with another user account are presented in the e-mail application. In this regard, the user account associated with indicator 316 is displayed because indicator 316 has taken the main position. As already discussed above, the main position signifies to the user which user account details and information are currently being displayed. For instance, the e-mail address JSmith@workmail.com that has loaded is associated with indicator 316.
In addition, the information contained in the bottom portion 340 is associated with the user account that is associated with indicator 316, and not indicator 312. Thus, the upcoming and inbox links in bottom portion 340 may present the user with information associated with indicator 316 only. E-mail folders such as trash, spam, and sent (not shown) may only display e-mails and other information associated with the user account of indicator 316. Furthermore, background 824 is the fully loaded background associated with indicator 316. In this example, background 824 is a sky and cloud design, but it may be any background that is given to the user, chosen by the user, or created by the user. It should be understood that any position on the screen may be considered the main position that indicates which details of the respective indicators are displayed.
As an alternative to switching user accounts by swiping, a user may tap a particular indicator to switch accounts. For instance, referring to example 900 of
Similar to the transitional stage from the swiping motion described above, indicators 312 and 314 may transitionally switch positions. In this regard,
Furthermore, transition background 1122 in example 1100 of
When the transition is completed, the user account details and settings associated with indicator 314 may be displayed. The location of indicator 314 is the main position that, as described above, indicates which user account details are currently being displayed in the e-mail application. Thus, the background of top portion 310 and the e-mails contained in the various links and folders of bottom portion 340 are associated with the user account of indicator 314. For example, when the user selects the inbox in bottom portion 340, the e-mails in the inbox will only be the e-mails associated with the indicator 314. In addition, it should be understood that any position on the screen may be considered the main position that indicates which details of the respective indicators are displayed.
Once the user account switches, the user may use the functions of the e-mail application as shown in bottom portion 340. For example, the user may click on the inbox to display their received e-mails. As one example, when the user clicks on the inbox, the received e-mails in the inbox may be displayed on a separate screen. In this regard, the separate screen may be considered an inbox screen, and the screen with the multiple indicators that the user can switch from may be considered the home screen. On the inbox screen the e-mail application may show the headings of the received e-mails to the user. In this regard, the screen may not be partitioned between a top and bottom portion.
To revert back to the home screen from the inbox screen, the user may select an options menu. For example, the user may select the options menu by selecting a button displayed on the inbox screen. As another example, the user may open the options screen by swiping their finger from one end of the display to the opposite end of the display. For instance, the user may swipe their finger from the left end of the display to the right end. When this occurs, the home screen may appear either concurrently or after the finger swipes from the end of the screen. As illustrated in example 1400 of
Once the home screen is in front of the inbox screen, the user is able to switch back to the inbox screen by clicking on any portion of the inbox screen. For example, the user may click, either through the touch screen display or by using a cursor and mouse, any portion of inbox screen 1450. Once the user selects any portion of inbox screen 1450, the inbox screen 1450 will re-appear and the home screen 1452 will disappear. The user is able to open the home screen again by performing the functions described above.
Most of the foregoing alternative examples are not mutually exclusive, but may be implemented in various combinations to achieve unique advantages. As these and other variations and combinations of the features discussed above can be utilized without departing from the subject matter defined by the claims, the foregoing description of the embodiments should be taken by way of illustration rather than by way of limitation of the subject matter defined by the claims. As an example, the preceding operations do not have to be performed in the precise order described above. Rather, various steps can be handled in a different order or simultaneously. Steps can also be omitted unless otherwise stated. In addition, the provision of the examples described herein, as well as clauses phrased as “such as,” “including” and the like, should not be interpreted as limiting the subject matter of the claims to the specific examples; rather, the examples are intended to illustrate only one of many possible embodiments. Further, the same reference numbers in different drawings can identify the same or similar elements.
The present application is a continuation of U.S. patent application Ser. No. 16/740,730 filed Jan. 13, 2020, which is a continuation of U.S. patent application Ser. No. 15/837,253 filed Dec. 11, 2017, now issued as U.S. Pat. No. 10,572,120 on Feb. 25, 2020, which is a continuation of U.S. patent application Ser. No. 14/598,981, filed Jan. 16, 2015, now issued as U.S. Pat. No. 9,880,717 on Jan. 30, 2018, which claims the benefit of the filing date of U.S. Provisional Patent Application No. 62/015,664, filed Jun. 23, 2014, the entire disclosures of which are hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
D550227 | Sato | Sep 2007 | S |
7594193 | Thomas | Sep 2009 | B2 |
D641372 | Gardner et al. | Jul 2011 | S |
D652841 | Arnold | Jan 2012 | S |
D665395 | Lee et al. | Aug 2012 | S |
8271894 | Mayers | Sep 2012 | B1 |
D677180 | Plitkins et al. | Mar 2013 | S |
D687058 | Corcoran et al. | Jul 2013 | S |
D687059 | Bruck et al. | Jul 2013 | S |
D699257 | Yang et al. | Feb 2014 | S |
D706827 | Harre | Jun 2014 | S |
D734770 | Kim et al. | Jul 2015 | S |
D735751 | Hwang et al. | Aug 2015 | S |
D736239 | Maner | Aug 2015 | S |
D737833 | Anzures et al. | Sep 2015 | S |
D739424 | Ku et al. | Sep 2015 | S |
D741896 | Park et al. | Oct 2015 | S |
D742901 | Choi et al. | Nov 2015 | S |
D744528 | Agrawal | Dec 2015 | S |
D745550 | Sanderson | Dec 2015 | S |
9268477 | Lai et al. | Feb 2016 | B2 |
D754717 | Li et al. | Apr 2016 | S |
9304668 | Rezende et al. | Apr 2016 | B2 |
D757058 | Kai | May 2016 | S |
D757085 | Zukerman et al. | May 2016 | S |
D758403 | Lee et al. | Jun 2016 | S |
D758422 | Zhao | Jun 2016 | S |
D759682 | Myung et al. | Jun 2016 | S |
D760732 | Sakai et al. | Jul 2016 | S |
D760769 | Ishii | Jul 2016 | S |
D760770 | Zhu | Jul 2016 | S |
D760773 | Cho | Jul 2016 | S |
D761303 | Nelson et al. | Jul 2016 | S |
D762655 | Kai | Aug 2016 | S |
D763279 | Jou | Aug 2016 | S |
D763306 | Lee et al. | Aug 2016 | S |
D764520 | Lee et al. | Aug 2016 | S |
D765099 | Kim et al. | Aug 2016 | S |
D765100 | Kim et al. | Aug 2016 | S |
D765102 | Lee et al. | Aug 2016 | S |
D765720 | Joo et al. | Sep 2016 | S |
D767629 | Gupta et al. | Sep 2016 | S |
D769929 | Kim et al. | Oct 2016 | S |
D769930 | Agrawal | Oct 2016 | S |
D773502 | Park et al. | Dec 2016 | S |
D776674 | Raykovich et al. | Jan 2017 | S |
D777768 | Persson et al. | Jan 2017 | S |
D778295 | Wang et al. | Feb 2017 | S |
D778311 | Denis et al. | Feb 2017 | S |
D778312 | Goodwin et al. | Feb 2017 | S |
D782521 | Pilch | Mar 2017 | S |
D788138 | Lee et al. | May 2017 | S |
D789960 | Alonso Ruiz et al. | Jun 2017 | S |
D792438 | Kim et al. | Jul 2017 | S |
D792444 | Cho et al. | Jul 2017 | S |
D794670 | Lee et al. | Aug 2017 | S |
D795892 | Kim et al. | Aug 2017 | S |
D801362 | Wang et al. | Oct 2017 | S |
D801382 | Seo et al. | Oct 2017 | S |
D801384 | Jeon et al. | Oct 2017 | S |
D802607 | Apodaca et al. | Nov 2017 | S |
D803850 | Chang et al. | Nov 2017 | S |
D806742 | Choi et al. | Jan 2018 | S |
D806743 | Choi et al. | Jan 2018 | S |
D807899 | Hilhorst et al. | Jan 2018 | S |
D807912 | Kim et al. | Jan 2018 | S |
D808998 | Wu et al. | Jan 2018 | S |
10154316 | Zhao | Dec 2018 | B2 |
10783576 | Van Os | Sep 2020 | B1 |
10990951 | Bishnoi et al. | Apr 2021 | B2 |
11409412 | Ho | Aug 2022 | B1 |
20040054646 | Daniell et al. | Mar 2004 | A1 |
20070035513 | Sherrard et al. | Feb 2007 | A1 |
20070189737 | Chaudhri et al. | Aug 2007 | A1 |
20080165136 | Christie et al. | Jul 2008 | A1 |
20090228562 | Uchiyama et al. | Sep 2009 | A1 |
20100088634 | Tsuruta et al. | Apr 2010 | A1 |
20100095240 | Shiplacoff et al. | Apr 2010 | A1 |
20100185989 | Shiplacoff et al. | Jul 2010 | A1 |
20110022982 | Takaoka et al. | Jan 2011 | A1 |
20110035691 | Kim | Feb 2011 | A1 |
20110225545 | Horodezky et al. | Sep 2011 | A1 |
20110271192 | Jones et al. | Nov 2011 | A1 |
20110271207 | Jones et al. | Nov 2011 | A1 |
20120096396 | Ording et al. | Apr 2012 | A1 |
20120124475 | Foote et al. | May 2012 | A1 |
20120157165 | Kim | Jun 2012 | A1 |
20120226978 | Harberts et al. | Sep 2012 | A1 |
20130027613 | Kim | Jan 2013 | A1 |
20130145144 | Newell et al. | Jun 2013 | A1 |
20130198680 | Schwend et al. | Aug 2013 | A1 |
20140109024 | Miyazaki | Apr 2014 | A1 |
20140125856 | Kim et al. | May 2014 | A1 |
20140152591 | Odakura | Jun 2014 | A1 |
20140237378 | Gonen et al. | Aug 2014 | A1 |
20140282208 | Chaudhri | Sep 2014 | A1 |
20140298253 | Jin et al. | Oct 2014 | A1 |
20140365912 | Shaw | Dec 2014 | A1 |
20140365971 | Laadan et al. | Dec 2014 | A1 |
20150067596 | Brown et al. | Mar 2015 | A1 |
20150186017 | Lee | Jul 2015 | A1 |
20150186156 | Brown et al. | Jul 2015 | A1 |
20150188720 | Winter | Jul 2015 | A1 |
20150215739 | Lee | Jul 2015 | A1 |
20150223308 | Yen | Aug 2015 | A1 |
20150309689 | Jin et al. | Oct 2015 | A1 |
20150341752 | Flynn | Nov 2015 | A1 |
20170123638 | Yamada et al. | May 2017 | A1 |
20170251268 | Zhao | Aug 2017 | A1 |
20170295278 | Lyren et al. | Oct 2017 | A1 |
20170300122 | Kramer et al. | Oct 2017 | A1 |
20170359506 | Manzari et al. | Dec 2017 | A1 |
20200186648 | Schwarz et al. | Jun 2020 | A1 |
20210042025 | Haggerty et al. | Feb 2021 | A1 |
Entry |
---|
Chalvet et al., GIF-Account, posted at dribbble, posting date Jan. 16, 2014. [online] [site visited Jan. 2, 2018]. Available from Internet <URL: https://dribbble.oom/shots/1380713-GIF-Account>. |
Gadget Hacks, Enable Multiple User Accounts on Any Android Phone, posted at You Tube, posting date Aug. 22, 2014. online] [site visited Jan. 2, 2018]. Available from Internet <URL: https://www.youtube.com/watch?v=TpapOCHbLko>. |
Google, The Gmail app for Android, posted at YouTube, posting date Nov. 4, 2014, © 2016 YouTube, LLC. (online], [site visited Jan. 8, 2016]. Available from Internet, <URL: https:/twww.youtube.com/watch?v=egjApkX8slk>. |
Hoffman, Share Your Android Tablet, posted at How to Geek, posting date Aug. 13, 2013. [online] [site visited Jan. 2, 2018] Available from Internet <URL: https://howtogeek.com/170191/share-your-android-tablet-and-keep-your-privacy-With-a-guest-account/>. |
How to use the fast user switching featuring in Windows XP, Last Review: Mar. 27, 2007, <http://support.microsoft.com/kb/279765>, 2 pages. |
Kilic, Sidebar Menu, posted at dribbble, posting date Jul. 30, 2013. [online] [site visited Jan. 2, 2018]. Available from Internet <URL:https://dribbble.com/shotes/1175816>. |
Mac OS X 10.6: quickly switching between accounts, <http://support.apple.com/kb/PH6983>, Last Modified: Nov. B. 2013, 2 pages. |
Kondrat, Tomek , Gmail 5.0: Material Design & Multiple Account Support, posted at xda-developers, posted date˜0 20, 2014, © xda-developers. [online], [site visited Jan. 8, 2016]. Available from Internet, <URL:http://www.xdadevelopers.com/gmail50materialdesignmultipleaccounts/>. |
Number | Date | Country | |
---|---|---|---|
62015664 | Jun 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16740730 | Jan 2020 | US |
Child | 17476638 | US | |
Parent | 15837253 | Dec 2017 | US |
Child | 16740730 | US | |
Parent | 14598981 | Jan 2015 | US |
Child | 15837253 | US |