Designing a Geo Based Music Platform, Songcry App

Songcry is a mobile music platform where artists can upload and stream their own music. In the closed Beta phase, the product focused mainly on the artist experience. Artists needed to join using an invitation code, complete their profile, submit verification, upload songs, and understand the visibility status of their music.

The design challenge was not only about making the interface look clean, but also about helping artists understand what they need to do next. Since Beta users may not fully understand the rules of the platform, the experience needed to clearly explain approval status, profile publishing, song visibility, and upload requirements without overwhelming them.

Artists often need guidance when joining a new music platform. In Songcry, there were several important states that could create confusion if not explained properly.

An approved song does not automatically become visible if the artist profile has not been published. Artists also need to understand why verification may be rejected, why a song may be denied, and what action they should take next. Since the product is still in Beta, the platform also needed to communicate limits clearly, such as invitation based access and the absence of analytics during Beta.

Without clear UI copy and structured flows, artists could assume their song is already live, misunderstand the approval process, or feel stuck after receiving a rejected status.

I designed a clearer artist focused experience by improving the onboarding, verification, song upload, and status communication flows.

The interface was structured to guide artists step by step. Each important state was supported with simple copy, clear labels, and direct actions. For example, artists can understand whether their profile is unpublished, their song is pending approval, their verification was rejected, or their uploaded song is not visible yet.

The solution also included better UX writing for empty states, approval messages, rejection messages, and Beta limitations. Instead of using technical language, the copy was written in a more human and helpful tone so artists can quickly understand what is happening and what they need to do next.

The improved experience gives artists a clearer path from joining Songcry to preparing their music for discovery.

Artists can better understand the difference between uploading a song, getting a song approved, and publishing their profile. The flow reduces confusion around visibility status and gives users clearer next steps when something requires action.

Since Songcry was still in closed Beta and analytics were not available yet, success was evaluated through product clarity, stakeholder feedback, and reduction of unclear product states during design review.