Creating a Safe Social Media App

TUVU is a social media platform built on Christian values, providing a safe, family-friendly environment for individuals, ministries, and businesses to engage their communities. Today, the app supports over 5,000 users, sees hundreds of daily active users in the US, and is rapidly onboarding dozens of organizations to host private communities.

The challenge — app screens

The Challenge

I joined TUVU over three years ago when the app was just a live concept. While the core idea was good, the user experience was rough, creating a lot of friction that made users reluctant to use or pay for the platform.

As the first designer of the company, my challenge was to transform this raw concept into a polished, scalable product.

My immediate priorities were:

  • Understanding the core needs of our target audience.
  • Auditing our existing technology and features.
  • Aligning with stakeholders on timelines and expectations.
  • Defining the scope of the redesign and identifying key MVP features.

Designing
for customization

After validating initial wireframes with users and stakeholders, I hit my biggest challenge, building a flexible, scalable design system. Because TUVU allows users to create 90% of the content they will see on the screen, I needed to figure out how to maintain a consistent look and feel while giving users total freedom.

I built a system relying heavily on component properties, nested instances, and design tokens. This allowed me to create single master components capable of handling countless variations, like a post with a photo, a video, a link, reactions, or even without anything. The color tokens would support color modes for automatic translation to dark mode across all screens.

To build a scalable system that a solo designer could realistically maintain, I designed every component around four core principles:

Optimization

Components must be optimized to include the maximum amount of customization with the minimum amount of variants possible, to reduce the number of components for development and maintenance.

Auto Layout & Modularity

Components must adapt dynamically to their content while supporting multiple screen sizes, allowing us to reuse the same components for the future web app.

Edge Case Control

Component sizes must contain minimum and maximum values. To ensure the UI won't break during extreme edge cases, like unusually long user names or content.

Tokenization

Components must use tokens for everything, starting with colors and font scaling, to eventually expand to all numeric variables (border radius, padding, margins), providing flexible variables to easily modify our ever evolving platform.

Documentation

Documenting
design and rules

Given the nature of the app, a screen in Figma could look drastically different in production depending on user content.

The key for documentation was to create a set of rules of how the app should handle every possible scenario for that feature and its components; the designs would be used as a reference for how these scenarios would be handled visually. The best advice I got from our CTO was to over communicate everything, and this has been a rule until this day: explain every single detail of the screen, what it should do, and how it should behave under different conditions.

The impact
today

The app was re-released to an overwhelmingly positive reception. Three years later, TUVU has scaled massively, our design system now holds together an app with over 800 mobile screens and 800 web screens, all of them powered by fewer than 50 highly optimized components following the exact rules established on day one.

We have tackled a lot of challenges these years, like letting organizations create their own private communities, allowing the creation of paid groups, dealing with internal moderation, and more that I could fit in this place. If you want to learn more about these, let's chat.

Back to portfolio