Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instrument metrics for iOS for the IA project #5401

Closed
18 of 19 tasks
Tracked by #159
kittykat opened this issue Jan 18, 2022 · 5 comments · Fixed by #5836
Closed
18 of 19 tasks
Tracked by #159

Instrument metrics for iOS for the IA project #5401

kittykat opened this issue Jan 18, 2022 · 5 comments · Fixed by #5836
Assignees
Labels
A-Telemetry Telemetry / analytics to understand usage T-Task Refactoring, enabling or disabling functionality, other engineering tasks Z-IA Issues relating to information architecture Z-Labs

Comments

@kittykat
Copy link
Contributor

kittykat commented Jan 18, 2022

We want to know if the IA changes are successful. For this we need to learn more about how users currently use element and whether the IA changes are improving or not making worse their workflows.

Details of what needs to be instrumented are in this internal spreadsheet.

Search

Global search

User Paths: MobileSearchRooms

  • Bounce rate from funnel: open search > visit room > open search (within time constraint)
    could be solved with userPath MobileSearch* -> Room -> MobileSearch*
  • Time and frequency to go from open search to tap result
    userPath: MobileSearch* -> Room = success, MobileSearch* -> Home = failure
  • Frequency of open search and go back without tapping result
    userPath: MobileSearch* -> Home = failure

Needs steps in Funnel (screen->event->screen)

  • Funnel for no progress from search results - guesstimate based on users that fell off search and how long did they stick around

User paths from Home, MobilePeople, MobileRooms, etc:

  • From which tabs do users open global search
    userPath: MobileSearch*

Room header menu

User paths from RoomDetails (Home means "Leave", "Room" means go back without further action):

  • When users tap on the room header, where do they go next?
    userPath: Room -> RoomDetail

Left panel

User paths from MobileSidebar:

  • Which menu items are users using in the left panel and how often?
    userPath: MobileSideBar -> MobileSpaceMenu, Settings,and other related screens
  • Do users switch spaces?
    Interaction event SpacePanelSwitchSpace
  • How often do users tap on the selected space?
    Interaction event SpacePanelSelectedSpace

TBD: find the right way:

  • How many users have Home set to "show all rooms"
    Not able to provide reliable properties as cohorts are user and not device related.

Settings

  • How often are people accessing their settings and what are they doing? (track screens for the moment)
    As discussed: userPath from Settings

Spaces

  • Add a user property for how many spaces the user is in - to split users into cohorts
    user property numSpace still to be discussed which event we will use
  • Path to joining to space (were they invited, room directory, link, etc)
    event JoinedRoom
  • Number of times explore space is accessed and how (there is a screen for this - note that navigation from space to subscace is a second event)
    event ViewRoom with isSpace = true
  • Funnel from left panel to explore space
    userPath MobileSideBar -> MobileSpaceExploreRoom
  • Do users use the home space or which metaspace tabs (this is tabs on iOS: from Home -> MobilePeople) ?
    userPath Home, MobileFavourites, MobilePeople, MobileRooms

Rooms

  • Source of room open (did they click a link, did they search for the room, did they open it from one of the tabs? note that spaces look like rooms?)
    event ViewRoom
  • Path to joining to room (were they invited, room directory, link, etc)
    event JoinedRoom
  • Point of entry to create room dialog
    screen events StartChat and CreateRoom
@kittykat kittykat added T-Task Refactoring, enabling or disabling functionality, other engineering tasks A-Telemetry Telemetry / analytics to understand usage Z-IA Issues relating to information architecture labels Jan 18, 2022
@gileluard
Copy link
Contributor

@kittykat

About app settings, things are slightly different. We don't Have the following screens:

  • Preferences
  • Help & About
  • advanced
  • Legals

But we have the following sections in the main settings screen:
Simulator Screen Shot - iPhone SE (2nd generation) - 2022-03-07 at 15 00 29
Simulator Screen Shot - iPhone SE (2nd generation) - 2022-03-07 at 14 56 52

Some of the items lead to other screens as:

  • Language
  • Theme
  • Copyright
  • Terms & Conditions
  • Privacy Policy
  • Third-Party polices

Do you want to track the screens above?

@gileluard
Copy link
Contributor

gileluard commented Mar 7, 2022

@kittykat

We have room preview bottom sheet but also space preview bottom sheet (which are mostly the same). We have the following possibilities:

  • track only room preview bottom sheets
  • tack room and space preview bottom sheets as room previews
  • tack room bottom sheets as room previews and space preview bottom sheets as space previews

@gileluard
Copy link
Contributor

gileluard commented Mar 9, 2022

@kittykat

About trigger for joinedRoom event. one of the trigger is RoomPreview and this trigger is triggered by the other ones usually. Some use cases:

  • User taps a notification (trigger Notification) -> the app displays the RoomPreview -> user joins room
  • User taps a room in ExploreRooms (trigger SpaceHierarchy) -> the app displays the RoomPreview -> user joins room

What about suggested rooms in home and rooms screens? We can use the SpaceHierarchy trigger but you may want to have a specific trigger.

@kittykat
Copy link
Contributor Author

Do you want to track the screens above?

No, lets not track them.

If we can treat room and space previews separately, that would be best.

Yes, lets have separate trigger for Home and Room screens - ideally one each as we want to know how often those screens are used to inform the designs Nique is doing right now.

gileluard added a commit that referenced this issue Mar 16, 2022
gileluard added a commit that referenced this issue Mar 17, 2022
gileluard added a commit that referenced this issue Mar 17, 2022
…or_the_IA_project

Instrument metrics for iOS for the IA project #5401
@gileluard
Copy link
Contributor

Waiting for #5834 to be reviewed before closing this ticket.

@gileluard gileluard reopened this Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Telemetry Telemetry / analytics to understand usage T-Task Refactoring, enabling or disabling functionality, other engineering tasks Z-IA Issues relating to information architecture Z-Labs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants