Djaminn (said “jamming”) is a music startup building a community where musicians record, collaborate and get discovered. The app was growing, but people left after a few sessions. I’m working with the founder on a gamification strategy, new features and the foundations underneath them.
Role
UX design consultant
Duration
3 months, ongoing
Team
A junior UI designer, working directly with the founder
Scope
Gamification strategy, journeys, design system, contests, open jams, recording
The new home: contests and challenges up front, shown with placeholder content.
8Core drives mappedOctalysis, rated by impact on Djaminn’s users.
2New features for the short termContests and open jams.
ReadyRecording, duet and publish flowsHanded to the developers.
01 · Context
A social network made only of music.
On Djaminn, a musician records a part on their phone, shares it, and others add their vocals or instruments on top, wherever they are in the world.
The founder’s aim: get people enthusiastic about making music together, so amateurs are inspired by pros and playing together beats sitting at home alone.
Platform
iOS, Android and web
Price
Free
For
Singers, players, producers, songwriters
Core loop
Record, add a layer, share
02 · Problem
Growing, but not sticking.
People leave after a few uses.
Downloads were growing, but there was little to do beyond record and share.
No reason to return.
There was no gamification, and no strategy for it.
Shaky foundations.
Both the logic and the UI were inconsistent from screen to screen.
The founder wanted new features and gamification to lift retention. The catch: they had to land on foundations that needed fixing at the same time.
03 · My role
Consultant to the founder, designer on the floor.
Consulted
Directly with the founder on the gamification strategy, what to build first and what to park.
Designed
Journeys, wireframes and UI with a junior UI designer, on a new design system.
Handed off
Tested flows to the developers, ready to build.
04 · Approach
Research, journey, screens.
Insights came from desk research, competitive analysis of karaoke and music-social apps such as WeSing, Smule and StarMaker, and personas from the research team.
Research
Desk, competitors and the research team.
Journey
Map the current journey, then improve or create one.
Wireframes
Flows before pixels.
UI
On the new design system.
Test
Check the flow works for both audiences.
Handoff
Ready for the developers.
Mapping the journey before redesigning it.
I mapped onboarding step by step, from download to first recording, with customer actions above the screens and pain points pinned to them: no way to skip, no idea whether a choice matters, no way back. The future journey cuts the steps that stall people, adds skip and back, and moves the notification ask to later.
Current onboarding: every step and its pain points.
Future onboarding: fewer steps, a way to skip, and the notification ask moved later.
Two audiences, one app.
Content creators
From shy amateurs polishing songs in their bedroom, to ambitious artists chasing a break, to loop makers building a brand. They want tools that sound good, a safe place for feedback, and exposure.
Listeners
Music lovers who browse, vote and share, and producers or A&R scouting new talent. They want to find what’s hot quickly and reach the artist behind it.
05 · Gamification strategy
Strategy first, features second.
We worked on two levels in parallel: a strategy for the whole app, and the mechanics for each feature. Ideas were discussed against Octalysis’s eight core drives and Bartle’s player types, so every reward had a reason to exist.
DriveOctalysisAt DjaminnImpact
CD2Development and accomplishmentProgression, mastery, a musical identity and portfolio.
CD3Empowerment of creativityCore music creation.
CD5Social influence and relatednessCollaboration, recognition and community.
CD1Epic meaning and callingCreating music with people around the world.
CD6Scarcity and impatienceChallenges and special opportunities.
CD7Unpredictability and curiosityDiscovery and new collaborators.
CD8Loss and avoidanceUnfinished tracks and streaks to keep.
Bartle’s player types.
PlayersWorldActing on
Killers
Head-to-head votes and leaderboards, kept friendly.
Achievers
Contest rankings, musician levels and role mastery.
Interacting with
Socialisers
Duets, open jams, groups and comments.
Explorers
Discovery, daily challenges and new collaborators.
06 · Key insights
What shaped the design.
1. Fix the foundation first.
New features on inconsistent logic would only add confusion. We mapped the core journey, rebuilt recording, solo and duet, editing and publishing on a new design system, and added a first-time tutorial that walks people through their first recording.
The new design system in Figma.
The camera screen as handed to the developers: recording states, mic choice and how each orientation displays.
The first-time tutorial, from first record to publish.
2. Record and share isn’t enough.
With only basic features, there was little to come back for. Contests and open jams give people a reason to show up this week: contests add a goal, a deadline and a vote; open jams put strangers or friends in a lobby, each on an instrument, building one track together.
Before any UI, we worked out the contest logic: open, voting, winner and closed phases, how many votes each person gets, what happens to drafts, and edge cases such as a participant quitting or breaking the rules. A contest also needs two sides: creators who enter and listeners who vote. So it has two paths. Creators submit, track their entries and see their ranking; listeners browse, vote, follow and, for producers scouting talent, reach the artist directly.
Contest logic and edge cases, before any screen.
Contest wireframes, from list to submission and votes.
A contest from open to winner announced.
An open jam: pick a part, meet the band, record, publish.
3. Rewards need a strategy behind them.
The app had no gamification strategy, so any reward risked feeling bolted on. With the drives agreed, small daily loops came first: a fresh set of challenges every day that nudge people to discover, explore and record, and keep a streak going.
Daily challenges: small goals, a visible streak.
Behind the challenges sits the game logic. Every activity is graded by difficulty and time, from a login streak under a minute to a contest over several days. Rewards feed one loop: coins and levels unlock status, access and tools, and anything unlocked has to come from using the app.
Activities by difficulty, and what each reward unlocks.
Then we prioritised every idea on an impact and effort matrix with the founder. Daily challenges, a first-jam journey, track completion and open jams were low effort and high impact, so they went first. XP levels, coins, contests and a creator marketplace came next. A season pass, subscriptions and a complex economy had to be validated first, and achievements and share cards waited until there was time.
Every idea placed by impact and effort: do it now, do it next, validate first, or when there’s time.
07 · Trade-offs
Fewer ideas, better balanced.
Ideas vs feasibility
We killed or parked some gamification ideas: they weren’t technically feasible yet, and the developers already had a lot of foundational fixes on their plate.
Generous vs balanced
The coin economy is calculated carefully so it doesn’t inflate. Users need ways to spend coins, not just pile them up with nothing to buy.
Fast vs considered
The strategy took many rounds of discussion with the founder. Slower, but each mechanic now has a clear job.
08 · Outcome
A strategy agreed, the foundation in build.
A gamification strategy for the whole app, agreed with the founder.
A new design system, and recording, duet, editing and publishing flows handed to the developers.
Contests, open jams, daily challenges, the coin shop and a first-time tutorial designed and in progress.
The project is ongoing; retention results will follow once the new features ship.
09 · Reflection
What I learned.
Strategy before features.
I now set the gamification strategy before designing a feature, so rewards are built in, not slapped onto something that already exists.
Audio comes first.
In a music app the details are technical: effects, recording delay, and external mics and instruments all shape the design.