Instrument metrics for Android for the IA project

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

• Bounce rate from funnel: open search > visit room > open search (within time constraint) could be solved with userPath: - for group chat: RoomDirectory -> RoomPreview -> RoomDirectory - for DMs StartChat -> Room -> People/Home -> Start Chat

• Time and frequency to go from open search to tap result userPath: RoomDirectory/StartChat -> Room/RoomPreview

• Frequency of open search and go back without tapping result userPath: RoomDirectory/StartChat -> not Room/RoomPreview

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, People, Rooms, etc:

• From which tabs do users open global search separate events for searching people and rooms globally: StartChat and RoomDirectory

Room header menu

User paths from RoomDetails:

• When users tap on the room header, where do they go next? userPath: Room -> RoomDetails-> any of ‘Room*’ events
• Add Home(create shortcut) Interaction(name: MobileRoomAddHome)
• Leave Interaction(name: MobileRoomLeave)

Left panel

User paths from SideBar:

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

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. Taken out to https://github.com/vector-im/element-android/issues/5356
• 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) screen SpaceExploreRooms
• Funnel from left panel to explore space userPath SideBar -> SpaceExploreRooms

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. Taken out to https://github.com/vector-im/element-android/issues/5355
• Path to joining to room (were they invited, room directory, link, etc) event JoinedRoom. Taken out to https://github.com/vector-im/element-android/issues/5356
• Point of entry to create room dialog screen events StartChat and CreateRoom

[novocaine]

@niquewoodhouse added https://github.com/vector-im/element-meta/issues/208

[niquewoodhouse]

@nadonomy last week you suggested not having the subspace functionality on mobile. I totally understand the reasons but I just want to check please what you’re thinking of stopping:

• people making subspaces on mobile
• people viewing a space by subspace on mobile

I’d like to us to add something to this issue to include a way to check if people on android are using the relevant feature(s) depending on what we intend to do.