Imagine yourself searching for information for any question or problem you are thinking about. Figuring out how Jira works, looking for a job, and studying by watching tutorials. You may need help with the tabs you opened quickly to access multiple resources and lose focus on your work.

Our team explored a problem in people’s productivity in managing multiple tabs. How can we help users browse information, positively impacting their time management?

Problem Background

In a digital world of remote working and studying, it’s normal to open multiple tabs from articles and presentations shared by colleagues, friends, and family. By the end of the day, a person feels tired from looking at the computer screen for 5-8 hours daily.

At the same time, the Psychology Behind Opening So Many Tabs article refers to a Consultant Clinical Psychologist at The Summit Clinic who says that our computers/phones have now become an extension of our brain. The research team at Carnegie Mellon University completed a study on tab overload, which showed that people feel invested in the tabs they have open. They feel ashamed and overwhelmed by how many tabs they have open. In addition, while multitasking and paying attention to multiple tabs, the human brain allocates less power to each tab or task.

Our research included various jobs where users use tabs. We noticed a tendency in two scenarios: users who don’t mind trying a new tool and users who want to use a tab management tool. This clarified a perspective of productivity and frustration in time management.

Research Insights

To dive deeper into the problem Maria ran 3 user interviews to identify user pain points. One of the users, who works in the tech industry and spends on average 6-8 hours on a screen, shared that she gets lost in tabs and sometimes doesn’t know where she stopped reading,

‍“While working on a new project or completing the previous task, I need multiple tabs that relate to each other, such as a pipeline in CRM and a few workflows, for example. When switching between tabs, I found myself having three of the same tabs open at once. This was an indication for me that I overworked.”

However, the problem space can be vast depending on personal preferences. Lisa created a survey to provide the team with concrete data points. The results showed that the users were split into two groups: students and full-time employed individuals. Out of 48 responses, 39.1% of users spend on average 9-12 hours on a screen while almost the same percentage (32.6%) spend 5-8 hours. More than half of users feel somewhat productive. The feedback we received helped Maria to identify two user personas: a user who needs a tool and a user who doesn’t mind trying a new one.

Solution Explanation

What led us to a solution was that the surveyed audience uses Google Chrome as a primary browser. From here Manas and Mudassir suggested building an extension for users with a Google account and those who need to create an account in the extension itself.

From the beginning, we knew we needed to focus on core features such as:

Login functionality using a Google account
Tab visibility on a main screen
Organizing tabs into folders
Use Analytics to set time limits on tabs

Lo-fi & Hi-fi Mockups

Iterative Design Learnings

We ran a usability test with 3 users and found that there was confusion on grouping the tabs into folders. This informed us that we need to update the Instructions page or do an onboarding tutorial to make it more clear to the user on how to put tabs into the different folders. However, they completed the other tasks like navigating to a tab and deleting a tab easily.

We would like to test with more users to get even more recurring feedback that can help shape our product.

Implementation Details

Technical implementation:

Where is it hosted?

Chrome Web Store (Under Verification), Vercel, Render

What is your tech stack?

MongoDb, Express, React, NodeJs, NextJs

High level journey of a request:

Conceptualization and Ideation: Identify user needs and brainstorm ideas for the extension.
Design and Prototyping: Create wireframes and prototypes to visualize the user interface. Development kick-off.
Plan the project: Backend and Frontend Development. Develop server-side components using Node.js and Express.js. Create the user interface with React, Next.js, and TypeScript.
Testing and QA: Conduct testing to ensure stability and performance. Deployment and Launch. Prepare for deployment to the Chrome Web Store and execute a launch plan.
User Feedback: Monitor user adoption and gather feedback for future improvements. Post-Launch Maintenance

Technical challenges

Setting Time Limits for Specific Domains:

> Tracking user activity on specific domains accurately

Handling interruptions and ensuring a smooth user experience.
Implementing this securely and efficiently, dealing with browser APIs
Collecting and Displaying Time Usage with Pie Charts:

> Accurate time tracking for each saved tab.

Designing an intuitive and visually appealing pie chart interface.
Handling various technical complexities and edge cases.

While we have made significant efforts to address potential edge cases and scalability issues, it's important to acknowledge that like any software, there might still be a few small bugs that could emerge. We are committed to continuous improvement and quick resolution of any issues that may arise.

Key takeaways

Team Collaboration: Effective teamwork between developers, product manager, and designer.

Tech Skills: Gained expertise in React, Next.js, TypeScript, Node.js, Express, and MongoDB.

User Focus: Prioritised user feedback and research.

Iterative Development: Frequent testing and improvement.

Maintenance Commitment: Continued maintenance and prompt bug resolution.

Learnings

Product Manager Learnings:

Maria Dmitrieva

I learned how to apply key product management principles and agile methodology.
I learned how technical feasibility can impact ideas and final results.
I learned how to run user research and usability testing.

Designer Learnings:

Lisa Weng

I learned the importance of sharing designs with developers earlier to get their feedback on the feasibility of a feature.
I learned how to brush up on my usability testing skills.
I learned to create a mini design system to keep the product consistent.

Designer Learnings:

Jo Sturdivant

Adapting to an Established Team: Joining the team in week 6 of 8 was challenging, as I had to quickly adapt to existing workflows, dynamics, and goals. This mirrors real-world situations where you often integrate into teams mid-project, and flexibility is essential.
Work-Blocking for Efficiency: With only two weeks to complete the project, I learned the importance of a structured work-blocking system. This approach allowed me to manage my time effectively and meet deadlines under pressure.
Making Data-Driven Design Decisions: Unlike my past projects, I had to rely on research conducted by others. This was a valuable experience in using pre-existing data to guide design decisions, helping me focus on the core insights without starting from scratch.

Developer Learnings:

Manas Verma

Frontend Experience

I gained hands-on experience with React, Next.js, and TypeScript for frontend development.
Introduced TypeScript for improved code quality and bug prevention.

Backend Development:

Developed the backend server using Node.js, Express, and MongoDB.
Implemented authentication and authorization for data security.

Collaboration and Problem-Solving:

Collaborated closely with the product manager and designer on feature discussions.
Worked closely with the frontend developer to ensure seamless integration.

Version Control and Teamwork:

Proficiently used Git and GitHub for version control.
Coordinated efforts to meet project goals and deadlines.

Adaptability and Continuous Learning:

Embraced a growth mindset, adapting to both frontend and backend tasks.
Committed to ongoing learning and skill improvement.

Developer Learnings:

Vanady Beard

&

As the back-end developer, I learned how important it is to create efficient and reliable systems that support the entire application. This experience also taught me the importance of optimising the database and ensuring the backend is scalable and easy to maintain.

Developer Learnings:

Stephen Asiedu

&

As a back-end developer, I've come to understand the importance of being familiar with various database systems and modules. This knowledge enables me to build diverse applications and maintain versatility in my work. I've also learned that the responsibility for making the right choices rests on my shoulders, guided by my best judgement.

Developer Learnings:

Mudassir Khan

&

Cross-functional Collaboration: Working alongside a product manager and product designer provided valuable exposure to a collaborative team environment. Learning to effectively communicate and align design, development, and product goals was crucial.
Full Stack Exposure: While primarily a Frontend Developer, the project's nature allowed for the exploration of backend technologies like MongoDB and Express. This broadened your skill set and provided a more holistic view of web development.
Chrome Extension Development: Building Tabstacker as a Chrome Extension involved understanding the intricacies of browser-based applications. This experience now adds a unique skill set to your profile.
ReactJS Mastery: Developing the front end with ReactJS solidified your expertise in this widely-used library, enabling you to create responsive, dynamic, and efficient user interfaces.
Tailwind CSS Proficiency: Utilising Tailwind CSS for styling not only expedited the design process but also improved your knowledge of utility-first CSS frameworks.
Real-world Project Experience: Tabstacker provided hands-on experience in developing a real-world software product from ideation to deployment, enhancing your problem-solving and project management skills.
User Experience Focus: Collaborating closely with a product designer honed your ability to prioritize user experience (UX) in development, ensuring the final product meets user needs effectively.
Adaptability: Switching between frontend and backend tasks showcased your adaptability and willingness to learn new technologies and concepts.

Developer Learnings:

Maurquise Williams

&

Process of Creating an MVP: Developing a Minimum Viable Product (MVP) taught me how to focus on delivering core functionalities balancing between essential features and avoiding scope creep.
Collaboration in a Real-World Tech Setting: This experience taught me how to collaborate efficiently in a fast-paced tech environment, keeping the team aligned and productive, even while working remotely across time zones.
Sharpening Critical Thinking and Problem-Solving Skills: This experience honed my ability to think critically and solve problems efficiently. By tackling challenges and finding quick solutions, I sharpened my decision-making and troubleshooting skills in a dynamic, real-world setting.

Developer Learnings:

Jeremiah Williams

&

All in all this experience was very awesome I learned that in coding with others being transparent is key

Developers Learnings:

Justin Farley

&

I learned how important communication is when working with a team. Communication provides understanding, advice, ideas, and much more. While working with the product team, I’ve found that communication keeps everything flowing smoothly. Working with a team also showed me that every member brings something different to the table and we all have to work together in order to align and meet our end goal.

Full Team Learning

We learned how to cross-collaborate with each other, considering different time zones and the variety of work and study experiences each of us has.