6 Months of Building: How Feedtracks Became Your Audio Workspace

Version 1 was simple: upload a file, share a link, leave timestamped comments. It worked for sharing individual tracks. But real work doesn't happen in isolated files—it happens in projects with dozens of files, multiple versions, nested folders, organized sessions.

You told us: "I need to organize this like my hard drive. Albums in folders. Sessions in subfolders. Stems, bounces, references—all in one place."

So we built a real drive. Unlimited folder hierarchy. Drag-and-drop files between folders. Real-time storage tracking at every level. Breadcrumb navigation so you always know where you are. Essentially, Google Drive's organizational power.

"But here's the revolution: the audio player follows you everywhere."

Click into a folder—music keeps playing. Open another track—smooth transition. Browse your entire library while listening. Google Drive makes you download files to listen. Dropbox is the same. Not us. The player is persistent, always there, always working.

This was the real shift from "file sharing tool" to "audio workspace." You can finally organize your work AND listen to it without friction.

Musicians don't work in one context. You've got your main project, a side band, freelance mixing work, a collaboration with someone in another city. All different people, different files, different conversations.

Google Drive forces you into one giant folder hierarchy. Dropbox is the same. But WhatsApp? You create a group, invite people, everyone sees the same stuff. Simple.

Shared drives work exactly like that. Create a workspace, invite your band or your client or your podcast team. Give people roles—admin (full control), editor (upload and organize), or viewer (listen and comment). Everyone has their own storage quota, but the workspace owner assumes the hosting cost for the group.

Move files between drives with one click. Your personal work, your band's project, your client's album—all separate, all organized, all accessible.

"I have five different projects going. Five separate drives. No confusion, no mess. It just works like my brain actually works."

Timestamped comments were a good start. But real collaboration needs more structure. You need to:

• Tag specific people: @mentions with autocomplete, just like Slack or Instagram
• Mark feedback as done: Resolve threads so you can focus on what's left
• See what needs your attention: Activity page with all unresolved comments across your drives

These feel like small features. But they're the difference between "I think someone commented?" and actually managing feedback workflows.

"The resolved toggle changed everything. I used to lose track of which notes I'd fixed. Now I just mark them done and hide them. Clean."

Here's a scenario we saw constantly: An engineer leaves a comment like "The vocal feels too dry in the second verse, maybe add some reverb around 60ms with a slight high-pass to avoid muddiness."

That takes 2 minutes to type. The recipient reads it three times trying to parse the intent. Then replies with questions. Back and forth, back and forth.

"What if you could just... talk? Hit record, play the track, explain the issue while you're hearing it. 30 seconds, done."

That's audio comments. Record up to 2 minutes of voice feedback, directly on the waveform. The context is right there—you're listening, you're reacting, you're explaining in real-time. No typing. No ambiguity.

The response: Within two weeks of launch, audio comments were used more than text comments on collaborative tracks. People got it immediately.

Once we had timestamped comments working for audio, people started uploading video files. Music videos, behind-the-scenes footage, video podcasts, even screen recordings of DAW sessions.

The question came up: "Can I leave timestamped comments on videos too?"

Now you can. Upload video files—MP4, MOV, whatever. Scrub through the timeline. Leave text or audio comments at specific timestamps. Everything that works for audio tracks works for video.

Turns out, video producers have the same feedback problems as audio engineers. "The cut at 1:35 feels abrupt." "Color grade looks off in this section." Now they can give that feedback in context, right on the timeline.

"We use it for music video reviews now. Director uploads the rough cut, band leaves comments, editor knows exactly what to fix. Way better than trying to describe timestamps over email."

We've all been there. You're working on a mix. You export "Song_v1.wav". Two days later, after revisions: "Song_v2.wav". A week later: "Song_v2_FINAL.wav". Then the client asks for one more change: "Song_v2_FINAL_actually_final.wav".

Your folder becomes a graveyard of abandoned versions. Which one was the good one? What changed between v2 and v3? You end up listening to five different files to figure it out.

Track versioning solves this. Stack all versions of the same track in one place—v1, v2, v3, v4. See them chronologically. Compare them side-by-side with A/B playback. Instantly switch between versions while listening.

"This is unique to Feedtracks. No competitor—not Google Drive, not Dropbox, not SoundCloud—has A/B comparison for audio mixes."

It's the difference between chaos and clarity. Your folder structure stays clean. Your version history is obvious. You can actually remember what you were thinking when you made v3.

Here's a common scenario: You're working on an album. Ten tracks. You want to send it to the label for consideration. What do you do?

Upload to SoundCloud? Too public, and the presentation is generic. Send a WeTransfer with ten files? They have to download everything, figure out the track order, play them one by one in iTunes or whatever.

Shareable playlists give you something in between. Create a sequential playlist, add a custom cover image, arrange the track order. Share one link. The recipient gets a mini-site—your album, your branding, proper playback order, waveform for each track.

It's not public like Spotify. It's not messy like Dropbox. It's professional presentation for work-in-progress. Perfect for label pitches, client reviews, or sending an EP to a music blog.

Bonus: Listening statistics. See who listened, when they listened, how many times they came back. This works for playlists, but also for any shared file in your drive. Know if your client actually reviewed the mix. See if the label played your demo all the way through.

"I send my album demos this way now. The label can listen sequentially, see the cover art, and it just feels more... intentional. Like I'm presenting something, not just dumping files. Plus I can see they actually listened to all 10 tracks."

Real scenario: You're on the subway. Client texts: "Can you approve the final mix?" You pull out your phone, open Feedtracks on mobile, and... it's janky. Tiny buttons. Weird scrolling. Half the features hidden.

We refused to build a native app—two codebases, constant sync issues, double the maintenance. But we also refused to accept that "mobile web" means "second-class experience."

We rebuilt the entire mobile experience from scratch. Touch-optimized gestures. Bottom sheets that slide up from the bottom (WhatsApp style). Swipe actions. Large tap targets. Persistent player that works while you browse. Everything you can do on desktop, you can do on your phone.

The goal: make it feel like an app you downloaded from the App Store, even though it's just a website. Hundreds of hours of tuning. Worth it.

This one's different. We were exploring blockchain authentication for another project and realized: IP theft is a real problem for anyone creating audio.

Someone steals your unreleased track, uploads it, claims it's theirs. How do you prove you made it first? Emails? Screenshots? Good luck in court.

Blockchain certification gives you permanent, tamper-proof proof of creation date. We write a hash of your file to the Tezos blockchain. It's like a digital notary stamp that can't be faked or changed.

Still in beta. We auto-suggest tracks that might be worth certifying—tracks in shared drives, frequently commented, or recently uploaded. But you decide what's worth protecting.

Use cases: Songs you're shopping to labels. Collaborations with people you don't know well. High-value unreleased work. Production work for hire (proof of delivery).