Music has social aspects. How might we use social behaviour to drive retention?
A design language is an overarching scheme or style that guides the design of a complement of products. It is a set of patterns, conventions, and techniques that are used to give a line of designs a consistent customer experience. ... They may also include foundational elements such as a design philosophy and set of principles.
Basically, this means setting up the bigger picture that serves as a guiding light.
A representative image of diversity and similarity. All are dragons, but all have different skins, just like music genres. All genres are music, and yet all are different.
Definition of a Tribe: “Tribe, in anthropology, is a notional form of human social organization based on a set of smaller groups (known as bands), having temporary or permanent political integration, and defined by traditions of common descent, language, culture, and ideology.”
Especially relevant here because of the tribe-like nature of music, for example, ‘techno-heads’- people feel immense pride in calling themselves techno-heads, etc.
🧠 Reason: Identity encourages retention and growth
💡 Implementation ideas:
:
:
Bottom line: Top-level feature, gotta figure out ways as well as the scale of its implementation(s)
Keywords: Lively, social, universally recognized, colourful, magnificent, comes in varieties- tribe
🎯 Objective: Setting up the app’s personality, i.e. the look and feel like that of a butterfly.
💡 Implementation ideas:
<aside> 👉 Bottomline
In my role as the sole designer at an early-stage startup, I had big plans for the product's design. I envisioned a user experience that would be truly exceptional, drawing inspiration from my real-world observations and making connections across different social domains. However, being at an early stage meant that I had to focus on taking things one step at a time. There wasn't much room for idealism when I was constantly juggling experimental projects and fixing minor UX issues.
I had two approaches to consider: a top-down approach where I implement my vision directly, or a bottom-up approach where I deeply research every decision before building anything. Unfortunately, the CEO and others in the company leaned more toward the bottom-up approach. Since no one else seemed to grasp my core ideas, and I was also a bit shy, I kept them to myself. This meant that most of my time was spent on mundane tasks, and my ambitious project of creating a comprehensive design language took a backseat.
It was a challenging situation for me. I had a strong desire to bring my exciting ideas to life, but the practical realities of the startup environment limited my ability to do so.
</aside>