Oracle Documents Sync App Road Map. Maria Fernandez Trevino

Transcription

1 Oracle Documents Sync App Road Map Maria Fernandez Trevino

2 Agenda Background Competitive Analysis UX Direction UX Goals UX Walkthrough Final Implementation

3 Background The desktop app had the opportunity to become the client of choice for day to day tasks. Initial focus was on getting sync to work, new focus has shifted to providing a great user experience, catching up on feature set, and stabilization/optimization. Challenges included the overall usability of the app, a limited feature set, an outdated look and feel that was disconnected from the other 2 clients, poor problem solving and notification channels, and painful update experience. We needed to be mindful that user s first experience would be on web so they should be able to transfer those skills/model/experience onto the desktop. No formal competitive studies had been done on this client up until this point. 3

4 Competitive Analysis

5 Google

6 Google

7 Google

8 Google

9 One Drive

10 One Drive

11 Dropbbox

12 Jumpshare

13 Box

14 Syncplicity

15 Syncplicity

16 Syncplicity

17 Norton

18 UX Direction From a UX perspective, these were the things we wished to address: 1. Redesigning the desktop experience so that integration with the OS shell and web client UIs (host web dialogs in desktop) is seamless. This should address consistency issues across clients and command discoverability, usability, and scalability in the desktop platform (i.e. get link issues, reserve file, etc). 2. Changing the sync client UI so that it stops competing with the OS shell and it is perceived as utility that reports status and notifications and not a sync client/ file explorer. This should provide a more adequate home for problem reporting and notifications and the frustration of not being able to interact with files/folders through the sync client UI. Users will now know where to go to interact with their files (the OS).

19 UX Direction 3. Catching up on feature set and expanding feature set specific to the client Member management (P1), file reservation (P1), favorites (P4), support multiple accounts (P2), web edit (P2), sync top level files (P1) 4. Investing in User Assistance techniques Not to cover up usability fails, but to provide a better experience on par with the rest of the clients and industry standards. (Boilerplate text, getting started tour, tooltips.) 5. Revamp look and feel so that it is consistent with the other clients and industry trends. Flat look and feel 6. Streamline the update experience 7. Competitive study

20 1. Redesigning the desktop experience so that integration with the OS and web client UIs is seamless. This should address consistency issues across clients and command discoverability, usability, and scalability issues currently found in the desktop platform (i.e. get link issues, reserve file, etc). Hosting web dialogs in desktop is a closely related but separate effort. Commands accessible through the OS shell Hosting web UI dialogs in desktop app 20

21 2. Changing the sync client UI so that it stops competing with the OS shell and it is perceived as utility that reports status and notifications and not a sync client/ file explorer. This should provide a more adequate home for problem reporting and notifications and the frustration of not being able to interact with files/folders through the sync client UI. Users will now know where to go to interact with their files (the OS). This UI is not going to host any files/folders, it will be exclusively used to report and solve problems, and communicate notifications and status. Yes No *Open issue, how to select which folders to sync: -thru web client -through folder picker in sync manager settings -sync the whole folder structure 21

22 3. Catching up on feature set and expanding feature set specific to the client Member management P1 File reservation P1 Favorites P4 Support multiple accounts P3 Web edit P2 Sync top level files P1 22

23 4. Investing in User Assistance (help) techniques. Not to cover up usability fails, but to provide a better experience on par with the rest of the clients and industry standards. (Boilerplate text, getting started tour, tooltips, in app quick help.) New welcome tour These two should have the same visual treatment Example of boilerplate text in the app *Need to leverage tooltips to reflect status. *Add boilerplate to sync manager *Add in app hosted client specific quick help 23

24 5. Revamp look and feel so that it is consistent with the other clients and industry trends. Flat look and feel *Dialogs (coming from web), welcome tour and sync manager should have the same visual treatment. 24

25 6. Streamline the update experience David s This: No 25

26 UX Goals Modify the sync client UI so that it stops competing with the OS shell and it is perceived as useful set up, error and status reporting utility and not a file explorer. Provide a better experience on par with the rest of the clients and industry standards. (Incorporate UA elements where needed, match voice and tone and look and feel.

27 UX Walkthrough

28 Installation just ended Or user launches Documents for the first time after installing.

29 Sync manager now anchored to task bar. Gone when focus is lost. To bring back left-click Documents task bar icon, or right-click task bar icon to get to old main menu and select Open Sync Manager.

30 After splash screen comes login, not tour. There is inline error validation in this screen. Quick help is displayed in stand alone dialog (no change).

31 Establishing connection

32 On successful first login, launch old tour/setup.

33 Walkthrough tour/setup

34 Click next to select the content to sync. Options 1 and 2 would result in this screen being the last one in the tour and thus the button would read Finish instead of Next and one less nav dot would appear.

35 Filtering and sort order has been added. Cilck finish if user skips tour (and thus this step in the setup, they can always select which folders to sync later)

36 Main UI, if user skips tour. Notice boilerplate encouraging user to set up sync folders instead of sync status. Main UI is anchored to task bar. User clicks on choose to select which folders to sync (also available through preferences). Dropdown with options: Pause/Resume sync, Resync, Notifications, Preferences Displays quick help in dialog. Opens Oracle Docs folder in explorer/finder Opens Oracle Docs in the cloud

37 Main UI is dismissed, dialog is launched. Sync settings are a tab inside Preferences but since it was launched from a direct entry point, the dialog opens to the Sync tab. Click Done to dismiss the dialog. Left click on Documents icon on task bar to bring back main UI. Option 3 would turn the Done button into Next. Clicking next refreshes the dialog window to show the file picker where they can select which folders to sync. That dialog has a Done Cancel button.

38 Main UI is now set up. Click on Gear ->Preferences Problems status badge changed to # of notifications badge. Problems are now notifications, launches the problems dialog. Activity stream showing recent files that have been changed on the server (file names are linked to local copy) as well as editing conflicts that need the user s attention. Conflict entries would be linked to the local file as well as the Problems dialog so the user can get more detail on the editing conflict. Integrating the problems dialog, activity feed and notifications into one concept is something to address during r4. Cleaning up, and expanding, the events that we are reporting too.

39 Preferences dialog is a native dialog skinned to look like web dialogs. It contains 4 tabs and hosts most settings, advanced features, and remaining info currently found in the sync client. Secondary buttons launch the current (same) experiences but skinned accordingly when possible. Click on Sync tab. Need to figure out how multiple account supports fits into this area/dialog.

40 Sync tab is the home for selecting or modifying which folders to sync the user also gets the Opportunity to set this up during the welcome tour and if they don t then this tab can also be opened directly from the boilerplate text shown in the empty main UI.

41 Advanced features go here. Bruce to work on wording to introduce them. Click on Updates tab.

42 About & check for updates (can we just automatically check and display status? i.e. up to date, or if an update is available display download button here? Close dialog, open main UI (click on task bar).

43 Click on either attention in the conflict entry in the activity feed, or on the notifications icon in the status area.

44 Keep current dialog basically as is, just rename columns and skin accordingly for r3. Work on improving this during r4.

45 Dialogs are launched when commands are invoked from the shell too: sharing, properties, sync problems, sync status. Sharing shown here.

46 Sync status native dialog (launched from item s context menu). Skin accordingly, remove gear icon. Cut actions Delete and Stop sync from Product. Cut these 2 folder specific commands from the product: -Delete (they can do this using the OS s delete. Though deleting shared root folders shouldn t do anything at all (shouldn t unsyc the root folder nor do Delete it from the cloud.) -Stop Syncing (they can do this from their sync preferences)

47 Final Implementation

48

49

50

51

52

53

54

55

56