Improvising Twitter Space Search Flow
Overview:
It all started when I saw a growth school advertisement for a two-week UX design workshop led by Mr.Anudeep Ayyagari. where he taught us the fundamentals of user experience design, as well as the whys and hows. I learned a lot and gained a clear understanding of product design.
For the final three days of the program, a UX design challenge was presented to us, asking us to select an app and develop a micro-flow for any stage. We were expected to identify flow issues, come up with potential solutions, carry out user testing, and then reiterate the final solution based on user insights using the lessons from the workbooks, including fundamental UX concepts and heuristics.
🤔 Why Twitter Space:
Spaces is a way to have live audio conversations on Twitter. This can happen in a Community too. Community Spaces allow creators to create Spaces to keep their members engaged and help new people discover and join their Community. And I am an FM person who enjoys audiobooks and audio space, so I installed the clubhouse application and joined various clubs, but there was a flaw in that we could only log in to the clubhouse if we were referred by someone. Later, I got to know about the new audio group feature on Twitter, which is spaces. Which was similar to the clubhouse in that it was simple to use and join a space.
🔍The Research:
As a space user, I found it aggravating at times to find out about the newest space or to participate in a live space. Additionally, I had the chance to discuss on Twitter space with members of a Discord community and gather some user feedback on it. The majority of the people I interacted with were in their adolescent years, and some are active on Twitter. I got some of their pain points about spaces from their insights.
In addition, parallelly I conducted secondary research on space and derived some statistics about global space usage as well as some common pain points of users searching for and joining space, eventually ending in a problem statement.
🔁Flow selected:
As part of the challenge I picked up the search flow on Twitter for spaces feature
- Initial flow
go to search on Twitter → If you search for an account or a phrase → your search results would be accounts, tweets, photos & videos related to the phrases shown.
2. Customized flow
go to search in Twitter → search for an account or a phrase → your search results would be accounts, tweets, spaces, photos & videos related to the phrases shown.
❓Problem Statement:
When searching for a space in the search tab, an account or hostname is required to join a space you cannot use a random phrase to search for a space.
Principle helped
- Flexibility and efficiency of use
If the user needs to search for space here they need to enter the account/hostname or the space name in order to join a live or register in an upcoming space.
💡Ideations:
In this phase, I came up with a lot of ideas, however, when it comes to implementation, as designers, we are also responsible for the business. So I narrowed it down to two ideas. To speed up the process of this flow. I arrived at this decision (Adding a space section on the search feed) as that would increase the possibilities of viewing the section of the space and joining or registering in a happening space.
- Adding a space section on the search feed (Selected one ⭐🌟)
- Adding spaces in the trending tags or video feed.
📍Prototypes:
Low-Fidelity Prototype:
Low-Fidelity Prototype link: https://marvelapp.com/2i081j8g
High-Fidelity Prototype:
High-Fidelity Prototype link: https://www.figma.com/proto/Mcl8sT127fltwktzqwpvvJ/Untitled?page-id=0%3A1&node-id=10%3A76&viewport=-1902%2C-357%2C0.69&scaling=scale-down&starting-point-node-id=10%3A76
🧑💻Usability Testing:
I Found 2 people for testing the prototype and I briefed them about the task and checked the initial flow and customized flow and I observed how the user reacted to the initial and custom flow.
Things I wanted to note:
1. Can the user understand the problem?
2. Does the user know where to find a space?
3. Is that an issue for the user?
4. Does the user know where to look for help if they get stuck?
Observations I had on the users:
