Designing Setu’s product

Proposed homepage

OVERVIEW

Setu’s mission was to empower content creators and expand their reach beyond web2 social media.

The early stage startup’s goal was to bridge the gap between Web2 and Web3 social media platforms, by empowering content creators to expand their reach across multiple platforms.

I joined Setu in 2022, when the SaaS platform was still in its conceptual stage. Over time, our cross-functional team developed both a website of the MVP product that was used by 20k+ users.

TEAM

Meghalee, Product Manager

MY ROLE

I played a key role in designing the product by conducting competitive analysis and developing user flows and prototypes.

Also worked closely with developers and marketing to successfully release the product to the public.

OUTCOME

As of April 2023, Setu has been used by more than 20k users, with over 4k subscribers and 800k+ content synced.

But since the API rules have changed for twitter, the product is currently on standby mode.

Current MVP design

Features and how does Setu work?

THE CHALLENGE

To create a seamless experience for creators to expand their footprint to web3 social media.

To create a seamless experience for creators to expand their footprint to web3 social media

To create a seamless experience for creators to expand their footprint to web3 social media

To introduce Setu to the world of DeSo protocol, I was given the task to design the MVP - a seamless sync of content from Twitter to DeSo protocol enabling creators to earn from their twitter content.

The objective was to set up a hassle-free method to connect both the social media accounts, and let creators be in control of what content to send over.

COMPETITIVE ANALYSIS

During the exploration of the DeSo Protocol ecosystem, I found a tool that closely resembled our MVP and was being currently utilised by several prominent entities on the platform. As this tool already had an established user base, we recognised that it would be challenging for us to get into the field to improve upon it.

During the exploration of the DeSo Protocol ecosystem, I found a tool that closely resembled our MVP and was being currently utilised by several prominent entities on the platform.

As this tool already had an established user base, we recognised that it would be challenging for us to get into the field to improve upon it.

DESIGN:

FIRST ITERATION

After receiving the technical instructions, I simplified the process by breaking it down into smaller tasks and providing a clear page indicator.

However, we noticed a high drop-off rate at the Twitter login page. To address this, we updated the messaging to reassure users that they have control over their content. This led to an improvement in user engagement.

Video - First iteration of design

DESIGN:

CHALLENGES WITH FIRST ITERATION

Lack of flexibility in design

As our focus was not on Twitter, the current design was unable to incorporate login options for other social media platforms.

Lack of flexibility in design

As our focus was not on Twitter, the current design was unable to incorporate login options for other social media platforms.

Ineffective use of webpage

Being an inexperienced intern at the time, I had limited technical knowledge and was unsure how to utilize the available space.

Ineffective use of webpage

Being an inexperienced intern at the time, I had limited technical knowledge and was unsure how to utilize the available space.

DESIGN:

SECOND ITERATION

With the expansion of the scope to include additional web2 social media platforms, I needed to modify the previous design.

To address this, I made adjustments to the existing design to enable users to view their various social media accounts they can link and sync content from.

Video - Second iteration of design

DESIGN:

CHALLENGES WITH SECOND ITERATION

Absence of visible subscription status

It can be challenging to keep track of subscription status since users can only confirm it by accessing the real-time sync page.

Absence of visible subscription status

It can be challenging to keep track of subscription status since users can only confirm it by accessing the real-time sync page.

Expansion to other web3 social media

The existing design was tailored to the Deso protocol, with Deso accounts serving as the sole login method to eliminate the need for email logins. However, as our scope broadened to accommodate other blockchains, we needed to consider alternative solutions.

Expansion to other web3 social media

The existing design was tailored to the Deso protocol, with Deso accounts serving as the sole login method to eliminate the need for email logins. However, as our scope broadened to accommodate other blockchains, we needed to consider alternative solutions.

Management of multiple accounts

Currently, the platform only allows users to log in with one social media account. However, what if a user wanted to sync content from multiple accounts?

Management of multiple accounts

Currently, the platform only allows users to log in with one social media account. However, what if a user wanted to sync content from multiple accounts?

DESIGN:

THIRD ITERATION

To accommodate the integration of different web3 social media protocols, we had to update the design to meet product requirements.

This involved introducing an email login feature to map a user's connected accounts and settings. As the design has not been released to the public yet, I can only share a user flow to illustrate the process.

User flow for future iteration

DESIGN SYSTEM

To meet the evolving needs of the product, it was crucial for the design and it’s components to be flexible and consistent to ensure that the design could adapt to changing requirements while maintaining a cohesive experience across different platforms.

Design components - not to scale

Design components - not to scale

KIND WORDS FROM COMMUNITY

KIND WORDS FROM COMMUNITY

KIND WORDS FROM COMMUNITY