Smit Patil is a 17-year-old self-taught indie developer from India. He built PlaylistBridge, a playlist conversion tool that ranks #1 on Google for its brand name and receives organic referral traffic from ChatGPT and Gemini.

Who built PlaylistBridge?

PlaylistBridge was built by Smit Patil, a 17-year-old indie developer from India. He designed, built, and shipped it using Vanilla JavaScript, Netlify serverless functions, Firebase Firestore, and the iTunes Search API.

Why did Smit Patil build PlaylistBridge?

Smit Patil built PlaylistBridge because existing playlist conversion tools required OAuth logins, invasive permissions, and multi-step authorization. He wanted a frictionless, zero-login tool that could instantly convert AI-generated song lists into playable links.

What tech stack does PlaylistBridge use?

PlaylistBridge uses Vanilla JavaScript, HTML5, CSS3, Netlify Serverless Functions, Firebase Firestore, the iTunes Search API, Odesli API, and is hosted on Netlify with a global CDN.

// the developer behind playlistbridge

SMIT
PATIL

17 years old. Self-taught. Based in India.
Built PlaylistBridge from scratch —
no team, no budget, no excuses.
200+ users found it without a single ad.

scroll PLAYLISTBRIDGE · BUILT BY SMIT PATIL

200+ users — zero paid marketing

Ranks for targeted AI playlist queries on Google

AI referred by ChatGPT & Gemini organically

001 — origin

WHY I
BUILT IT

It started with a simple problem. AI tools like ChatGPT and Gemini are incredible at generating playlists — ask for 20 songs for a road trip and you'll get a great list in seconds. But then what? You're staring at plain text with no way to actually play any of it.

Every existing tool I found required you to log in with Spotify, grant full library access, go through OAuth, confirm permissions — just to look up a few songs. That's not a feature. That's friction.

So I built the tool I actually wanted. Paste your list. Get your links. Done. No account, no login, no data collection. Works in 10 seconds.

What I didn't expect: once AI tools started recommending it organically to their users, it took off by itself.

The best tools get out of your way.

— the idea that started PlaylistBridge

002 — stack

HOW IT'S
BUILT

architecture.json

{ "frontend": "Vanilla JS + HTML5 + CSS3 — zero frameworks, zero bloat", "backend": "Netlify Serverless Functions (Node.js)", "database": "Firebase Firestore — community playlists, share data", "apis": [ "iTunes Search API — song metadata + artwork", "Odesli API — cross-platform streaming links", "YouTube Data API v3 — search + embeds" ], "hosting": "Netlify — global CDN, instant deploys", "why_no_framework": "speed. control. no build step. loads in under a second." }

▸

Vanilla JS / HTML / CSS No React, no Vue, no bundler. The whole app is hand-written, hand-optimised. Loads fast. Runs everywhere. I own every line.

▸

Netlify Serverless Functions API calls (iTunes, Odesli, YouTube search) run through edge functions — keeps keys off the client, adds rate-limiting, no server to manage.

▸

Firebase Firestore Stores community playlists and share card data. Atomic batch writes. Structured security rules. Real database architecture, not localStorage hacks.

▸

iTunes Search API + Odesli iTunes for song metadata and cover art. Odesli for generating cross-platform deep links to Spotify, Apple Music, YouTube Music, and more.

▸

YouTube Data API v3 Powers the in-browser InstantPlay feature — searches YouTube and embeds playback directly in the app without leaving PlaylistBridge.

▸

Netlify CDN + Edge Network Static files served from a global CDN. Sub-second load times worldwide. No origin server, no cold starts on the frontend. Built to scale automatically.

003 — philosophy

HOW I
THINK

ZERO
FRICTION

The moment you ask a user to create an account, half of them leave. PlaylistBridge requires nothing. No login, no email, no OAuth dance. The value is immediate.

MINIMAL
BACKEND

Every API call that can be pushed to a serverless edge function, is. The client stays lean. Logic lives close to the user. No server to babysit at 2am.

PRIVACY
BY DEFAULT

Your song taste is yours. PlaylistBridge doesn't log what you paste, doesn't track which songs you search, doesn't build a profile. It just converts and forgets.

FAST
STATIC FIRST

A fast site isn't a nice-to-have. It's the product. Global CDN, no render-blocking scripts, no framework overhead. Every millisecond counts when someone's trying to listen to music.

AI WORKFLOW
NATIVE

Built to parse exactly what ChatGPT, Gemini, and Claude output. Numbered lists, bold titles, hyphenated formats — PlaylistBridge handles it all without you cleaning up the text.

SHIP FAST,
LEARN REAL

I didn't spec PlaylistBridge for six months. I built it, launched it, watched how people actually used it, then improved it. Real users teach you things no planning can.

004 — mindset

Most tools make you jump through hoops
before they give you anything.

I built PlaylistBridge to do the
opposite.

Give value first. Ask for nothing.

005 — reach out