Abstract:
Embodiments of the present disclosure include systems and methods of a desktop application for accessing a cloud collaboration platform. The disclosed application utilizes a native desktop environment to provide a better cloud collaboration experience by making the cloud-based platform accessible for file editing, file opening/closing/previewing, moving files between the local desktop environment and a web application (e.g., native to the cloud-based platform), syncing folders or marking any folders or parents/children of any folders to sync and/or utilizing any of the collaborative features (e.g., emailing links or inviting collaborators to collaborate on a file directly via the desktop environment using native contacts or contacts in the web app environment).

Description:
CROSS-REFERENCE TO RELATED APPLICATION(S) 
       [0001]    This application is entitled to the benefit of and/or the right of priority to U.S. Provisional Application No. 61/894,340, entitled “DESKTOP APPLICATION FOR ACCESSING A CLOUD COLLABORATION PLATFORM” (Attorney Docket No. 61599-8107.US00), filed Oct. 22, 2013, which is hereby incorporated by reference in its entirety. 
     
    
     BACKGROUND 
       [0002]    In the field of cloud-based storage and collaboration technology, synchronization applications provide a suitable solution for synchronizing personal files and the files of small teams that collaborate on projects. However, existing solutions are not suitable to serve as a shared-drive replacement, because users cannot synchronize all of the shared files at every user&#39;s computer device. This involves too much storage space, too much bandwidth utilization, and can increase the risk of data loss. Accordingly, various systems and methods associated with an integrated desktop application are disclosed herein for providing users with efficient access to all content stored in a cloud-based collaboration platform 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0003]    The present embodiments are illustrated by way of example and are not intended to be limited by the figures of the accompanying drawings. In the drawings: 
           [0004]      FIG. 1  illustrates an example diagram of a system having a host server of a cloud service (e.g., collaboration or file sharing platform) and/or cloud storage accounts with capabilities for enabling a desktop application such as described herein for accessing a cloud-based collaboration platform; 
           [0005]      FIG. 2  depicts a diagram of a cloud-based or online collaboration platform deployed in an enterprise or other organizational setting for organizing work items and workspaces, as one example of a collaboration or file sharing service which may be or include hosted cloud service and/or cloud storage with capabilities enabling a desktop application such as described herein for accessing a cloud-based collaboration platform; 
           [0006]      FIG. 3  depicts an example diagram of a workspace in an online or cloud-based collaboration platform accessible by multiple collaborators through various devices authorized to access the work space; 
           [0007]      FIGS. 4A-4I  respectively depict screenshot portions showing example user interfaces, each depicting one or more features enabling users to utilize a desktop application such as described herein for accessing a cloud-based collaboration platform; 
           [0008]      FIG. 5  shows a flowchart of an example process for providing an integrated interactive interface for accessing a cloud-based collaboration platform; 
           [0009]      FIG. 6  shows a flowchart example process for creating a work item via an integrated interactive interface for accessing a cloud-based collaboration platform; 
           [0010]      FIGS. 7A-7C  show flowcharts for example processes for accessing work items via an integrated interactive interface for accessing a cloud-based collaboration platform; and 
           [0011]      FIG. 8  shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed. 
       
    
    
     DETAILED DESCRIPTION 
       [0012]    The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure can be, but not necessarily are, references to the same embodiment; and, such references mean at least one of the embodiments. 
         [0013]    Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments. 
         [0014]    The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms may be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way. 
         [0015]    Consequently, alternative language and synonyms may be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification including examples of any terms discussed herein is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification. 
         [0016]    Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions will control. 
         [0017]    Embodiments of the present disclosure include systems and methods for enabling a desktop application such as described herein for accessing a cloud-based collaboration platform. 
       Cloud-Based Collaboration Platform 
       [0018]      FIG. 1  illustrates an example diagram of a system having a host server  100  of a cloud service (e.g., collaboration or file sharing platform) and/or cloud storage accounts with capabilities for enabling a desktop application such as described herein for accessing a cloud-based collaboration platform. 
         [0019]    The client devices  102  can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection, including wired, wireless, cellular connections with another device, a server and/or other systems such as host server  100  and/or notification server  150 . Client devices  102  will typically include a display and/or other output functionalities to present information and data exchanged between among the devices  102  and/or the host server  100  and/or notification server  150 . 
         [0020]    For example, the client devices  102  can include mobile, hand held or portable devices or non-portable devices and can be any of, but not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices including, a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a smart phone, a PDA, a Blackberry device, a Treo, a handheld tablet (e.g. an iPad, a Galaxy, Xoom Tablet, etc.), a tablet PC, a thin-client, a hand held console, a hand held gaming device or console, an iPhone, and/or any other portable, mobile, hand held devices, etc. running on any platform or any operating system (e.g., Mac-based OS (OS X, iOS, etc.), Windows-based OS (Windows Mobile, Windows 7, etc.), Android, Blackberry OS, Embedded Linux platforms, Palm OS, Symbian platform. In one embodiment, the client devices  102 , host server  100 , and app server  110  are coupled via a network  106  and/or a network  108 . In some embodiments, the devices  102  and host server  100  may be directly connected to one another. 
         [0021]    The input mechanism on client devices  102  can include touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination of the above. 
         [0022]    Signals received or detected indicating user activity at client devices  102  through one or more of the above input mechanism, or others, can be used in the disclosed technology by various users or collaborators (e.g., collaborators  108 ) for accessing, through network  106 , a cloud-based collaboration platform or online collaboration platform (e.g., hosted by the host server  100 ). 
         [0023]    The collaboration platform or environment hosts workspaces with work items that one or more users can access (e.g., view, edit, update, revise, comment, download, preview, tag, or otherwise manipulate, etc.). A work item can generally include any type of digital or electronic content that can be viewed or accessed via an electronic device (e.g., device  102 ). The digital content can include .pdf files, .doc, slides (e.g., Powerpoint slides), images, audio files, multimedia content, web pages, blogs, etc. A workspace can generally refer to any grouping of a set of digital content in the collaboration platform. The grouping can be created, identified, or specified by a user or through other means. This user may be a creator user or administrative user, for example. 
         [0024]    In general, a workspace can be associated with a set of users or collaborators (e.g., collaborators  108 ) which have access to the content included therein. The levels of access (e.g., based on permissions or rules) of each user or collaborator to access the content in a given workspace may be the same or may vary among the users. Each user may have their own set of access rights to every piece of content in the workspace, or each user may be different access rights to different pieces of content. Access rights may be specified by a user associated with a work space and/or a user who created/uploaded a particular piece of content to the workspace, or any other designated user or collaborator. 
         [0025]    In general, the collaboration platform allows multiple users or collaborators to access or collaborate efforts on work items such each user can see, remotely, edits, revisions, comments, or annotations being made to specific work items through their own user devices. For example, a user can upload a document to a work space for other users to access (e.g., for viewing, editing, commenting, signing-off, or otherwise manipulating). The user can login to the online platform and upload the document (or any other type of work item) to an existing work space or to a new work space. The document can be shared with existing users or collaborators in a work space. 
         [0026]    A diagrammatic illustration of the online collaboration platform and the relationships between workspaces and users/collaborators are illustrated with further reference to the example of  FIG. 2 . A diagrammatic illustration of a workspace having multiple work items with which collaborators can access through multiple devices is illustrated with further reference to the example of  FIG. 3 . 
         [0027]    In one embodiment, the host server  100  of cloud-based services and/or cloud storage such as an online or cloud-based collaboration platform is able to track or monitor the devices used by users to access content or activities. 
         [0028]    In one embodiment, client devices  102  communicate with the host server  100  and/or notification server  150  over network  106 . In general, network  106 , over which the client devices  102 , the host server  100 , and/or notification server  150  communicate, may be a cellular network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination thereof. For example, the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-232, SDH, SONET, etc. 
         [0029]    The network  106  can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices  102  and the host server  100  and may appear as one or more networks to the serviced systems and devices. In one embodiment, communications to and from the client devices  102  can be achieved by, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet. In one embodiment, communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS). 
         [0030]    In addition, communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMax, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WWAN), enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Digital Advanced Mobile Phone Service (D-Amps), Bluetooth, Wi-Fi, Fixed Wireless Data, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, 3G LTE, 3GPP LTE, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, 1xRTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS, extensible messaging and presence protocol (XMPP), real time messaging protocol (RTMP), instant messaging and presence protocol (IMPP), instant messaging, USSD, IRC, or any other wireless data networks or messaging protocols. 
         [0031]      FIG. 2  depicts a diagram of a cloud-based or online collaboration platform deployed in an enterprise or other organizational setting  250  for organizing work items  215 ,  235 ,  255  and workspaces  205 ,  225 ,  245 , as one example of a collaboration or file sharing service which may be or include hosted cloud service and/or cloud storage with capabilities for enabling a desktop application such as described herein for accessing a cloud-based collaboration platform. 
         [0032]    The cloud-based platform for collaborating on projects or jointly working on documents can be used by individual users and shared among collaborators. In addition, the collaboration platform can be deployed in an organized setting including but not limited to, a company (e.g., an enterprise setting), a department in a company, an academic institution, a department in an academic institution, a class or course setting, or any other types of organizations or organized setting. 
         [0033]    When deployed in an organizational setting, multiple workspaces (e.g., workspace A, B C) can be created to support different projects or a variety of work flows. Each workspace can have its own associate work items. For example, work space A  205  may be associated with work items  215 , work space B  225  can be associated with work items  235 , and work space N can be associated with work items  255 . The work items  215 ,  235 , and  255  may be unique to each work space but need not be. For example, a particular word document can be associated with only one work space (e.g., work space A  205 ) or it may be associated with multiple work spaces (e.g., Work space A  205  and work space B  225 , etc.). 
         [0034]    In general, each work space has a set of users or collaborators associated with it. For example, work space A  205  is associated with multiple users or collaborators  206 . In some instances, work spaces deployed in an enterprise may be department specific. For example, work space B may be associated with department  210  and some users shown as example user A  208  and workspace N  245  can be associated with departments  212  and  216  and users shown as example user B  214 . 
         [0035]    Each user associated with a work space can generally access the work items associated with the work space. The level of access will depend on permissions associated with the specific work space, and/or with a specific work item. Permissions can be set for the work space or set individually on a per work item basis. For example, the creator of a work space (e.g., one of user A  208  who creates work space B) can set one permission setting applicable to all work items  235  for other associated users and/or users associated with the affiliate department  210 , for example. Creator user A  208  may also set different permission settings for each work item, which may be the same for different users, or varying for different users. 
         [0036]    In each work space A, B . . . N, when an action is performed on a work item by a given user or any other activity is detected in the work space, other users in the same work space may be notified (e.g., in real time or in near real time, or not in real time). Activities which trigger real time notifications can include, by way of example but not limitation, adding, deleting, or modifying collaborators in the work space, uploading, downloading, adding, deleting a work item in the work space, creating a discussion topic in the work space. 
         [0037]    Specifically, items or content downloaded or edited in accordance with the techniques described in the present disclosure can be cause notifications to be generated. Such notifications can be sent to relevant users to notify them of actions surrounding a download, an edit, a change, a modification, a new file, a conflicting version, an upload of an edited or modified file. 
         [0038]    In one embodiment, in a user interface to the web-based collaboration platform where notifications are presented, users can, via the same interface, create action items (e.g., tasks) and delegate the action items to other users including collaborators pertaining to a work item  215 , for example. The collaborators  206  may be in the same workspace A  205  or the user may include a newly invited collaborator. Similarly, in the same user interface where discussion topics can be created in a work space (e.g., work space A, B or N, etc.), actionable events on work items can be created and/or delegated/assigned to other users such as collaborators of a given work space  206  or other users. Through the same user interface, task status and updates from multiple users or collaborators can be indicated and reflected. In some instances, the users can perform the tasks (e.g., review or approve or reject, etc.) via the same user interface. 
         [0039]      FIG. 3  depicts an example diagram of a workspace  302  in an online or web-based collaboration platform accessible by multiple collaborators  322  through various devices authorized to access the work space. 
         [0040]    Each of users  316 ,  318 , and  320  can individually use multiple different devices to access and/or manipulate work items  324  in the work space  302  with which they are associated with. For example users  316 ,  318 ,  320  can be collaborators on a project to which work items  324  are relevant. Since the work items  324  are hosted by the collaboration platform (e.g., a cloud-based platform), each user can access the work items  324  anytime, and from any physical location using any device (e.g., including devices they own or any shared/public/loaner device). 
         [0041]    Work items to be edited or viewed can be accessed from the workspace  302  in accordance with the platform and/or application independent mechanisms. Users can also be notified of access, edit, modification, and/or upload related-actions performed on work items  324  by other users or any other types of activities detected in the work space  302 . For example, if user  316  modifies a document, one or both of the other collaborators  318  and  320  can be notified of the modification in real time, or near real-time, or not in real time. The notifications can be sent through any of all of the devices associated with a given user, in various formats including, one or more of, email, SMS, or via a pop-up window in a user interface in which the user uses to access the collaboration platform. In the event of multiple notifications, each notification can be depicted preferentially (e.g., ordering in the user interface) based on user preferences and/or relevance to the user (e.g., implicit or explicit). 
         [0042]    For example, a notification of a download, access, read, write, edit, or uploaded related activities can be presented in a feed stream among other notifications through a user interface on the user device according to relevancy to the user determined based on current or recent activity of the user in the web-based collaboration platform. 
         [0043]    In one embodiment, a notification feed stream includes updates when an invited user accepts an invitation and/or successfully creates a new account through receipt of an invitation from an existing user. The invited user, upon creation of the new account, receives the account having enhanced features. The new user can automatically be connected to the existing user who sent the invitation. The system can also automatically prompt both users to query they wish to be collaborators in a common work space. 
       Example Integrated Interactive Interface 
       [0044]    A desktop application for providing access to a cloud-based collaboration platform can provide a seamless experience for desktop users. Some embodiments can provide access to all files stored at the cloud based collaboration platform, including files not associated with synchronized local copies at the client device. Additional example functions of the desktop application can include enabling shared drive replacement functionality, supporting virtual desktops (VDI) where synchronization is not viable, providing an incredibly fast, native experience (e.g., as opposed to access through a web-based application). 
         [0045]    Some embodiments can also take advantage of OS-specific features and integration points. In some embodiments, a single installer can be used for all Box desktop features. For some embodiments, the desktop application can be OS specific, such as “Box for Windows” and “Box for Mac.” 
         [0046]    According to some embodiments, the desktop application can be pre-installed upon signing into a cloud-based collaboration account via a client device, or can be installed, using a single file that is associated with other applications for accessing a cloud based collaboration platform (e.g. Box Edit). The installed software can provide immediate access to all work items hosted at the cloud-based collaboration platform. There is no need to select folders and wait for initial synchronization, or select folders to synchronize. 
         [0047]    According to some embodiments the desktop application can be written in, for example, Cross-platform Python code. The application includes straightforward UI work (e.g., as shown in  FIGS. 4A-4I ). In some embodiments, the desktop application Sync all file metadata locally (but only contents of synced files) 
         [0048]    Some embodiments can also include features such as work item previews, comments, annotations, update feeds, in-app messaging to desktop users, dynamic caching of un-synchronized files, and opening of files directly from email links. 
         [0049]      FIGS. 4A-4I  respectively depict screenshot portions showing example user interfaces, each depicting one or more features enabling users to utilize a desktop application at a client device such as described herein for accessing a cloud-based collaboration platform. 
         [0050]      FIG. 4A  shows an example integrated interactive interface  420   a  for a desktop application, according to some embodiments. As shown in  FIG. 4A , the example integrated interactive interface  420   a  may be integrated into the overall desktop interface  410   a  for the particular device. Accordingly, integrated interface  420   a  presents a seamless interface through which a user may access work items hosted at a cloud-based collaboration platform. According to some embodiments, integrated interface  420   a  includes features specific to an operating system of the client device. For example, according to some embodiments, display of work items via interactive interface  420   a  may follow that of other files stored on the local drive of the client device. 
         [0051]    In an embodiment according to  FIG. 4A  a user accesses interface  420   a  by selecting (via an input device) menu item  430   a . Integrated interactive interface  420   a  includes a listing of work items  460   a  hosted at the cloud-based collaboration platform (described above). As opposed to a synchronization client, all work items associated with a given account or workspace are displayed via interface  420   a  regardless of whether a synchronized local copy of a work item is available at the client device. Here, some of the plurality of displayed work items  460   a  are associated with synchronized local copies stored at the client device through and some are not. According to some embodiments, work items  460   a  with associated synchronized local copies may are identified with an icon overlay  462   a . Here an icon overlay  462   a  with a “check box” indicates that a work item  460   a  hosted at the cloud-based collaboration platform is synchronized with a local copy of the work item at the client device. Work items  460   a  can be displayed via interactive interface  420   a  in a number of ways. Here, as shown by notification  450   a  the interactive interfaces lists work items  460   a  in an order based on recent updates. Alternatively, work items may be listed according to favorites, alphabetical order by title, in order of file type, chronologically based on the date the work item was created, etc. Work items may also be displayed in the list in a tree structure according to associated folders. Further, each listed work item  460   a  includes information regarding the file/folder, the date on which is was modified and the collaborator who modified it. The interface  420   a  may also include a search tool  440   a  to search all the work items accessible to the associated account. 
         [0052]    A user can access contextual menus such as contextual menu  470   a  via interactive interface  420   a . A contextual menu may be accessed by a user through an input provided via an input device. For example, a right click on a mouse may bring up contextual menu  470   a . Again, functionalities, such a contextual menu functionality can implement the underlying functionality of an operating system of the client device. 
         [0053]      FIG. 5  shows an simplified example process  500  for providing an integrated interactive interface. At step  510  a native application (also referred to as a “desktop application” native to an operating system) generates an integrated interactive interface including a list of a plurality of work items stored at the cloud based platform. As previously stated, some of the listed plurality of work items will be associated with synchronized local copies stored at the client device and some will not. Further the integrated interactive interface is configured to enable a user to access one or more or more of the plurality of work items to enable a user to create a new work item to be stored in the cloud-based collaboration platform. The term “access” in this context may mean view, create, edit, move, save, etc. At step  520  the integrated interactive interface may be displayed via a display device of the client device. 
         [0054]      FIGS. 4B-4I  shows additional interfaces, which can be subpages under interface  420   a  of  FIG. 4A , that have additional functions. 
         [0055]      FIG. 4B  shows an example interface  420   b  that includes a listing of work items  460   b  similar to the listing of work items in interface  420   a  of  FIG. 4A . Interface  420   b  demonstrates a “drag and drop” functionality  426   b  for creating, uploading, or accessing work items hosted at a cloud-based collaboration platform. For example, a user may upload a file or folder stored at the client device by simply dragging and dropping an icon representing that file or folder into the interactive interface  420   b . Similarly, a user may synchronize an unsynchronized work item  460   b  by selecting an icon representing that work item from the listing in interactive interface  460   b  and dragging the selected work item onto the desktop or into a finder window at a client device and dropping that selected work item. While the drag and drop functionality is illustrated in  FIG. 4B  with respect to interface  420   b , it shall be understood that the same functionality may be applied via any of the interfaces shown in  FIGS. 4A-4I . 
         [0056]      FIG. 4C  shows an example interface  420   c  for creating a new work item to be hosted at the cloud-based collaboration platform. Here, interface  420   c  includes an editable field  450   c  for creating a text based-document without the need for a separate application. A user inputs text via an input device at the client device and can save the document to the cloud-based collaboration platform. Other types of documents may be created by a user using similar methods, for example, an illustration, a video, a picture, a CAD drawing, etc. Further, if certain document creation capabilities are required, a desktop application associated with interface  420   c  may identify a local application at the client device and may automatically open that local application through which a user may create the new document. For example, an option may be pre provided in interface  420   c  to create a new word document. If a user selects that option, a local instantiation of Microsoft® Word opens to create the document. Once the desktop application detects that the new document has been created, it may automatically upload the newly created document to the cloud-based collaboration platform. 
         [0057]      FIG. 6  shows an example process  600  for creating a new work item similar to as shown in  FIG. 4C . Steps  610  and  620  are similar to steps  510  and  520 , described with reference to  FIG. 5 . Returning to  FIG. 6 , at step  630  an input from a user may be received via an input device (e.g. touch screen display) to create a new work item to be stored at the cloud-based collaboration platform. At step  640  the desktop application may identify a local application at the client device configured to create the new work item. According to some embodiment, the desktop application providing the integrated interactive interface may include functionality to create a new work item (see e.g., interface  420   c  in  FIG. 4C ). According to some embodiments, the desktop application may identify a third-party application (e.g. Microsoft® Word) capable of creating a new work item. At step  650  the desktop application may detect that a new work item has been created and may at step  660  automatically upload the new work item to a host server of a cloud-based collaboration platform. According to some embodiments, the desktop application automatically deletes any local copy of the newly created work item after uploading to the cloud-based collaboration platform. 
         [0058]      FIG. 4D  shows an example interface  420   d  through which a user may copy link to one or more work items  460   d  hosted at a cloud based collaboration platform. According to some embodiments, by hovering a cursor over a work item  460   d  (e.g. using an input device) an option  430   d  may be presented to a user to copy a link. The copied link may then be sent to another collaborator via a messaging system (e.g. email). 
         [0059]      FIG. 4E  shows an example interface  420   e  through which a user can access a work item  460   e  that is hosted at a cloud-based collaboration platform but not synchronized o the local client device. According to some embodiments, when a user double clicks (e.g. via an input device) a work item  460   e  the desktop application may facilitate the user with access to the work item hosted at the cloud-based collaboration platform. This process is described in part with reference to  FIGS. 7A and 7C . 
         [0060]      FIG. 7A  shows an example process  700   a  for accessing a work item hosted at the cloud-based collaboration platform via an integrated interactive interface. Steps  710  and  720  are similar to steps  510  and  520 , described with reference to  FIG. 5 . At step  730 , the desktop application receives via an input device, a user input (e.g., a double click) to access a selected work item from the plurality of work items listed in the integrated interactive interface. At step  740  the desktop application detect if the selected work item is associated with a synchronized local copy at the client device. In  FIG. 4E , work items  460   e  are not associated with synchronized local copies at the client device. Returning to  FIG. 7A , at step  760 , if the selected work item is not associated with a synchronized local copy, the desktop application facilitates the user with access to the work item stored at a host server of the cloud-based collaboration platform via a local application at the device. According to some embodiments, the local application can include an application associated with the desktop application (e.g., Box Edit). According to some embodiments, the local application is associated with a file type of the selected work item. For example, if the user selects a Word document hosted at the cloud-based collaboration platform and that Word document is not associated with a synchronized local copy, the desktop application may identify a local instantiation of the Microsoft Word application through which access to the document stored at the cloud-based collaboration platform may be provided. 
         [0061]      FIG. 7C  shows an example process  700   c , which according to some embodiments, may include steps that comprise step  760  of  FIG. 7A . With reference to  FIG. 7C , at step  761 , a desktop application automatically identifies a local application (e.g. Microsoft Word) at the client device configured to facilitate networked access to the work item stored in the cloud-based collaboration platform. At step  762 , the desktop application may automatically download to the client device, via a network, a temporary copy of the selected work item. At step  763 , the desktop application may automatically open the temporary copy of the selected work item via the identified local application (e.g. open a temporary Word .doc file in local instantiation of Microsoft Word). At step  764 , the desktop application receives, via the input device, a user input configured to edit the temporary copy of the selected work item. At step  765 , the desktop application detects that the temporary copy of the selected work item has changed to a new version. In other words that the user has made a change to the temporary copy of the work item. At step  766 , the desktop application automatically uploads the new version of the temporary copy to the cloud-based collaboration platform. Finally, at step  767 , the desktop application automatically deletes the temporary copy of the selected work item at the client device. 
         [0062]    Process  700   c  represents one embodiment for facilitating the user with access to a selected work item at a cloud based collaboration platform. Alternatively, the local application may facilitate access via a process of application streaming. In other words, a local application may receive edit inputs from a user, via an input device, and stream commands associated with those inputs to another application at a server side that may edit the work item stored at the server side. Using this method, the desktop application can avoid having to download a temporary copy of the selected work item. 
         [0063]      FIG. 4F  shows shoes an example interface  420   f  through which a user may be provided an option to synchronize a selected work item with a synchronized local copy at the client device or open the selected work item via a web client. According to some embodiments, A user may select (e.g. via a double click) one or more work items  460   f  listed in interface  420   f . If the selected work item is not associated with a synchronized local copy at the client device, the desktop application can provide the user with an options  440   f  to either synchronized the selected work item (i.e. create a synchronized local copy), or open the selected work item via an alternative viewing client, such as a web client. 
         [0064]      FIG. 4G  shows an example interface  420   g  through which a user can access a work item  460   g  that is hosted at a cloud based collaboration platform. As previously mentioned, some work items  460   g  may be associated with synchronized local copies (e.g. as indicated by an icon overlay  462   g ) and some may not be associated with synchronized local copies. According to some embodiments, when a user selects (e.g. via a right click of a mouse) a work item  460   g  a contextual menu  440   g - 452   g  comes up providing the user with options to access the selected work item  460   g.    
         [0065]    If a selected work item  460   g  is not associated with a synchronized local copy, a contextual menu  450   g  (if a folder) or  452   g  (if a file) may be displayed. As shown in  FIG. 4G , menu  450   g  provides the user with options to open the non-synchronized folder in the operating system finder, open the folder via an alternative viewing client (such as a web client) or to synchronize the folder to the local device. Similarly, menu  452   g  provides the user with options to open the folder location in the finder, open the file via the web client, synchronize the file, or directly access or “edit” the remotely stored file hosted at the cloud-based collaboration platform. The process of directly accessing the file is previously discussed with reference to  FIGS. 4E ,  7 A, and  7 C. 
         [0066]    If a selected work item  460   g  is not associated with a synchronized local copy, a contextual menu  440   g  (if a folder) or  442   g  (if a file) may be displayed. As shown in  FIG. 4G , menu  440   g  provides the user with options to open the synchronized folder in the operating system finder or open the folder via a web client. Similarly, menu  442   g  provides the user with options to open the folder location in the finder, open the file via the an alternative viewing client (e.g., web client), or directly access or “edit” the selected file. 
         [0067]    Returning to  FIG. 7A , at step  750 , if the selected work item is associated with a synchronized local copy, the desktop application facilitates the user with access to the synchronized local copy stored at a client device via a local application at the client device. 
         [0068]      FIG. 7B  shows an example process  700   b , which according to some embodiments, may include steps that comprise step  750  of  FIG. 7A . At step  751 , the desktop application automatically opens the synchronized local copy of the selected work item via a local application at the client device. For example, if the selected work item is a Word .doc file, the desktop application will automatically open the synchronized local copy of the .doc file via a locally instantiated copy of the Microsoft Word application. At step  752 , the desktop application receives, via an input device, a user input configured to edit the synchronized local copy. This input may be initially received via the local application. For example the user may edit the synchronized local copy of a .doc file via a locally instantiated copy of Microsoft Word. Edits to the synchronized work item received by the Word application may be relayed to the desktop application. At step  753 , the desktop application may detect that the synchronized local copy has changed to a new version. Again, this information may be relayed form the local application through which the user is editing the file. At step  753 , the desktop application automatically uploads the new version of the synchronized local copy to the cloud-based collaboration platform. According to some embodiments, this step may be performed in response to a user input to save the work item provided via the local application. 
         [0069]    Additional example functions and interfaces are illustrated in  FIGS. 4H and 4I . As shown in  FIG. 4H , an interface  420   h  may include options  450   h  to edit preferences for the desktop application, log out of the collaboration platform account, or synchronize work items to the local device.  FIG. 4I  shows an example interface  420   i  for editing preferences for a desktop application, according to some embodiments. 
       Computer Devices/Systems 
       [0070]      FIG. 8  shows a diagrammatic representation of a machine  800  in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed. 
         [0071]    In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. 
         [0072]    The machine may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. 
         [0073]    While the machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation. 
         [0074]    In general, the routines executed to implement the embodiments of the disclosure, may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure. 
         [0075]    Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution. 
         [0076]    Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include, but are not limited to, recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links. 
         [0077]    The network interface device enables the machine  800  to mediate data in a network with an entity that is external to the host server, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface device can include one or more of a network adaptor card, a wireless network interface card, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater. 
         [0078]    The network interface device can include a firewall which can, in some embodiments, govern and/or manage permission to access/proxy data in a computer network, and track varying levels of trust between different machines and/or applications. The firewall can be any number of modules having any combination of hardware and/or software components able to enforce a predetermined set of access rights between a particular set of machines and applications, machines and machines, and/or applications and applications, for example, to regulate the flow of traffic and resource sharing between these varying entities. The firewall may additionally manage and/or have access to an access control list which details permissions including for example, the access and operation rights of an object by an individual, a machine, and/or an application, and the circumstances under which the permission rights stand. 
         [0079]    Other network security functions can be performed or included in the functions of the firewall, can be, for example, but are not limited to, intrusion-prevention, intrusion detection, next-generation firewall, personal firewall, etc. without deviating from the novel art of this disclosure. 
         [0080]    Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list. 
         [0081]    The above detailed description of embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments of, and examples for, the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further, any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges. 
         [0082]    The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments. 
         [0083]    Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the disclosure. 
         [0084]    These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosure with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosure under the claims. 
         [0085]    While some aspects of the disclosure may be presented herein in some claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is recited as a means-plus-function claim under 35 U.S.C. §112(f), other aspects can likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. §112(f) will begin with the words “means for”.) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure.