Message Cell System
Sprout Social • 2024
Project Hero Image

Problem

Sprout's native mobile apps message cards needed a complete redesign due to several issues:

  • Outdated UI with critical accessibility problems
  • Inconsistent card design
  • Limited scalability for future development
  • Engineering complexity and maintenance challenges

The Goal

Create a seamless experience that is both easy to maintain and simple for our users

Discovery

User Research

  • Average session 1-2 minutes
  • 40% of sessions start via tap notification
  • Scalability is key
  • User tap for more context only 26% of the time  
  • Majority of actions taken via stream page and are the faster actions like complete and like.

Audits

Engineering Audit

Looking into how the message cells are built, and all of the different ways we currently pull information. Focusing in on pain points our engineers face.

Mobile Audit

Along with looking into all the ways the cells are built. I talk took an audit and sorted out mobile Social cards and their different subject matters. Finding that while each one has their own unique message type. They all look the same making it difficult for scanning.

Web Audit

Looking at web there were many parity issues between the platforms. I started to log most of the difference calling out if they are treated differently or missing completely.

Social Media Audit  &  Inspiration Search

I also did an audit of all of the social networks Sprout connected to, and ones it didn't connect to. To see how that could help with the inspiration for the message cards. The idea was never to duplicate what each network looked like. That would create more inconsistencies. But to see what content we need to design for now and will need to design for in the future for better scalability.

Design Approach

Impact & Prioritization
  • Identify high-impact areas for immediate improvement
  • Create phased implementation plan
UI Enhancement Strategy
  • Establish clear visual hierarchy between message cards, details, and notifications
  • Implement consistent design patterns
  • Build flexible components for future scalability work with product managers to know future vision
Development Considerations
  • Optimize maintainability
  • Balance unique features with consistent architecture
  • Create modular, reusable message cards

Sub-System

Instead of focusing on each message type based on network and by feature like product intended to focus on, we have a more unified subsystem approach to message cells.Similar to how they were built, but with greater flexibility so the pieces could be used more holistically in any message cell, as well as notifications and detail pages.

Working with Web

After some time working on this project. The web design system team also started to work on redesigning there message cards. So I worked closely with them collaborating on new ideas.

One thing I helped out web with was they were introducing a new side panel layout. With that layout they needed to start thinking about how to design at a smaller size and utilize indicators. That is where I showed them the indicator bar component.

Results

  • The web platform implemented the interaction bar before mobile devices.
    • This resulted in a 20-30% increase in usage for those actions.
    • The update reduced action execution time.
  • Overflow menu improvements helped lessen user confusion what certain actions meant
  • Customer support tickets related to UI issues decreased by 15%
  • Mobile app store ratings improved
  • Improved image consistency helping engineers be able to add network faster