HitRecord - Project Activity

The HitRecord community is a project based creative collaboration platform. Projects can be created by anyone and range from Songs, Music Videos, Short Films, among many others, and are the fuel that inspires the community to contribute and flex their creative muscles for positive mental health.
Organization
HitRecord
Role
UI
UX
Team
Branden Ushijima
Matt Pell

Problem

Projects on the mobile app were not getting enough contributions, and lacking views. We needed to increase project engagement, so we kicked off a design sprint to find a solution.

We broke into teams of two to figure out what we could do on the project level to increase engagement. After a series of crazy eights and some user stories, we agreed on a hypothesis that there was a story missing at the project level, it was only acting as a skeleton that would house prompts within. So we set out to give project views a story and bring them to life by adding, what started off as a timeline concept but spiraled into an activity feed.

Information Architecture

We broke down every possible activity item that could take place on a project level. There are items that can alter a project and items that will not alter a projects trajectory. After that, we broke down each component that made up each activity item.

Our ultimate goal within the activity feed was to increase contributions. We highlighted activity items that would take users through the contribution flow funnel to get them to participate.

Key activity areas

Updates
Comment
Tertiary Activity

How do we show multiple contributions without taking up the whole feed.

We needed to show conversations happening but couldn't pull in real time, how do we show this visually?

All other activity that doesn't affect the outcome of any given projects.

Contributions

Contributions were a huge part of this feed, our research suggested that users who contribute once had a higher chance of contributing 3 times. We needed a way to consolidate contributions as they came in. We worked with our back end engineers to figure out a logic, while staying pragmatic of our API capabilities.

Individual and Multiple Contributions

Additional activity items ranging from comment fields, step additions and team member additions.

User Interface

Components started to come together and work in a cohesive manner, a batching system taht would house comments and contributions every 24 hours proved to be the most challenging, it had to be flexible, informative yet it couldn't overpower the rest of the activity items.

Batched Comments

Comments batching system. The most recent comment would appear, any additional comments done within the given time frame would be accessible through a button call out.

Batched Contributions

Our contributions batch housed 3 main contributions while showing community members that there were additional contributions, the step it belongs to and the ability to get involved from the feed.

Team Members

Projects can have multiple team members, this gave community members the ability to add team leads from the feed itself.

Step Added

Project steps can get added throughout the life of the project, this gave users the ability to contribute while seeing who added the step, the type of step and the title of the step.

Final Activity Feed

Data from the first iteration is currently being gathered, there definitely have been some surprised learnings that have come out of this so far. Users are browsing contributions and contribution count is up, but they are not coming from the contribution flows within the activity feed itself. Version 2 is set to release soon.