THE MISTAKE THAT COST ME A YEAR

last year i was randomly visiting a website and couldnt download a video in hd quality. then as a dev, when something doesnt work, you think "let's build it." so i got the same thought. i started researching idea validation and found like 0.2% of websites actually worked fine, but they were full of shitty ads. i thought this is the perfect market , we should go all in. and when i checked their traffic i got shocked , cause they werent getting one or two million, they were getting tens of millions.

after some weeks of confusing "thinking" with actual progress, and a lot of procrastinating, i finally started. chose a regular tech stack, MEAN stack, to build it. at that time i wasnt even an experienced dev, just a kid at 17 with some exposure to stuff, knew how to code, but those traffic numbers pushed me to build as fast as possible.

i came to know we needed a scraper, and one of the best is yt-dlp. there were other options too, like youtube-dl, gallery-dl, unofficial tiktok apis. by all means i was overengineering, trying to build a robust system with multiple fallbacks that could download video and audio in every format avaliable. built that in two months, even using ai to figure stuff out. and by the end i had added so much complexity into one codebase that changing a single line meant updating 15 or 20 files, controllers, services, everything. that's when i realized this is what people call bad code.

so i rewrote it. this time removed external dependencies and just used yt-dlp efficiently in node js. after building that i felt it was pretty slow, taking about 10 to 15 sec just to fetch info, then another 10 to 15 sec to start the download. felt way too slow. tried optimizing with yt-dlp arguments and prewarmed pools, still around 9 to 10 sec. i was obsessed with speed at this point. almost 3 months gone.

shifted to bun to experiment, thinking it'd be faster than node, but turns out the cmd process time was basically the smae regardless. decided i needed a framework that could actually run cmd commands faster , so between rust and golang i picked golang and spent the first 15 days just learning its architecture. rebuilt the thing again, tested it, and it worked, starting in 4 to 5 sec. got such a dopamine hit from that i procrastinated a full week just enjoying the small win.

start of month 5, i began optimizing more. tried different things, like why show basic metadata using yt-dlp --dump-json when it takes 5 sec. tried oembed and iframely instead and they responded in like 250 milliseconds. realized we just need basic metadata upfront, the user gets that instantly while yt-dlp starts the actual download in the bakcground. COOL.

after that i optimized the frontend, did some technical seo, and launched after 6 months. the good part, i picked a name, "videosaver." the bad part, it was too common, google wouldnt even show it if you searched "videosaver" or "videosaver . online " even only searching site:videosaver . online showed it . that's when i learned the name was wrong and ranking a brand new domain in this compitation takes way longer than i thought, google just doesnt prioritize it.

then a real depression hit, and i spent another month just overthinking. month 8, i convinced myself i'd solved the hard problems, better ui and ux, better architecture, a decent fallback system, and that ego crept in. the only thing left was traffic. so i rebuilt the whole frontend again under a new name and a new concept, kind of like an ai chatbot that takes a url and just downloads it. felt like ai was doing the work in the backend when really it was still yt-dlp. new name this time, "buckty,good name, did the technical seo properly, scored 100/100 on every metric.

site went live start of month 9, worked fine, fast downloads, all the stuff, but the core issue never left, still no traffic. tried adding a blog, wrote a few posts, google never indexed them. wrote on medium and other platforms comparing video downloaders, still nothing. friends were using the site, needed constant updates, and two real issues kept showing up, cookies problems and ip throttling. also tried aria2 to boost download speed which turned out to be a bad call on the server side. tried backlinks wherever i could, still zero audience.

after two more months struggling for an audience, i started a theme page on instagram posting movie clips, and within a month had 50k followers and 70 million plus reach. thought i'd convert that into traffic for buckty, started posting memes to drive people over, and within 3 days meta announced they were blocking accounts flagged for bot behavior or copyright content poster . got blocked, never recovered.

that's when it clicked, fast downloads and decent ui isnt a usp, it needs to actually mean something . so i built a mobile app in kotlin with a feature like "seal" has, direct download with share, except i'd download server side then stream it to the user. added another big feature for the usp, google drive integration, so users connect their drive and downloads auto upload there. built that across web and mobile with a nest js middleware sitting between frontend and the golang backend engine, handling download history, auto drive upload, and more. decent platform now, but still no audience. decided no more features, just focus on traffic and ranking.

last month i went through every strategy to rank on google, still nothing. figured i needed real leverage, so i looked into how other platforms did seo and found a lot of it was straight up blackhat, bulk backlinking and similar tactics. found one site spending 10k a month on backlinks and pulling 200k a month through cpm ads, that was the actual playbook. the other option is paying a tech creator to make a video about your product since it already has real value, people use it, and slowly google starts ranking you for stuff like "yt video downloader hd 2026."

after analyzing all of this, my final thought on the project is... nothing. i learned a ton of tech, learned how to optimize, learned what good design looks like, learned how to make things scale, and the biggest lesson, product is nothing, marketing is everything. when i ask people what they're building they say "ai this" or "ai that," basically ai wrappers, and part of me felt better than that, like i wasnt chasing hype, i was building an actual system. but that feeling doesnt pay the bills.

so here's the point of all this. i'm going to open source the whole ecosystem, mobile app, web app, all of it. i'll make sure you can run it locally too, just using wails to turn the web app into a system application, self host it, connect your accounts, back everything up. i have already designed it in a way that it doesnt need constant maintainence, it should run fine for a straight 6 months without me touching it. within a week of open sourcing it, i'm going to leave it and move on to the next project. it's genuinely hard to walk away from something like this, but someone once said the best time to leave anything that hurts you was the moment you regretted it, and the second best time is now.