TakeTones
A music platform connecting artist accounts, track discovery, licences and subscription access.
My part of TakeTones joined the artist and buyer journeys: a track needed a home in the catalog and a clear license after purchase.
- Field
- Media & entertainment
- Built with
- React / Next.js / Laravel
- Project year
- 2024–2025
The challenge
TakeTones had to support two distinct journeys in one music catalogue. Artists needed a route to publish tracks and manage their side of the platform. Buyers needed to discover music, obtain permission to use a track and find that licence again after purchase. Subscription access added a further layer: paying for a plan and receiving rights for a particular track are related, but not the same task.
The approach
During the 2024–2025 engagement, I planned and programmed parts of TakeTones with the project team. My contribution spans the React and Next.js frontend, separate account areas for artists and buyers, Laravel Orchid administration, the connection that generated a licence after a track purchase, and Paddle subscription integration.
Inside the music catalog
The screens, photography and cover art on this page come from TakeTones’ public site in 2026. They show the catalog today; my work took place in 2024–2025.
A video editor at work makes the creator audience for licensed music immediately recognisable.
A quiet forest scene gives the Ambient section a visual entry into the catalogue.
The Electronic category uses a listener portrait to give this part of the catalogue its own mood.
A film reel signals the Cinematic category before a buyer opens its track list.
The project, in detail
The images show the interface and its context. Captions distinguish project archives from current-site views.
One catalogue, two account journeys
An artist's next action is different from a buyer's. One side needs to supply music and follow its activity; the other needs search, purchasing and a record of permitted use. Separate account areas kept those jobs legible without splitting the catalogue into two disconnected products.
A purchase needs a usable licence
The documented work included connecting track purchases to a rights system that generated a licence. That turns an abstract payment into an identifiable permission for a particular piece of music. TakeTones' public help material also explains where a buyer can retrieve the licence in their account.
Subscription access and track licences
Paddle handled subscription purchase and management. The subscription route had to coexist with the licensing route so customers could understand both access to the catalogue and the rights attached to a track. The site presents Creator and Business plans with different permitted uses.
The outcome
Planning and programming across role-specific accounts, React and Next.js screens, Laravel Orchid, licensing and Paddle integration.
Artist submission and buyer discovery meet in one catalogue, with purchases tied to usage permissions.
Details of TakeTones
How did the two sides of TakeTones connect?
The documented work covered separate areas for artists and buyers within one music catalog. Licensing linked a purchased track to its use permission, while Paddle handled subscriptions.
What was my part in the project?
My documented role covered planning and programming on a team working with React, Next.js and Laravel Orchid. I do not claim sole authorship of the platform or its current design.
