The pitch
When Epic Games dropped the preview of its new launcher on October 14, it came with an unusual announcement. The company's blog post said it plainly: "Programming is hard. So, instead of doing that, we vibe coded a new Epic Games Launcher that's way faster and more responsive than the current one."
Fair enough. The preview really does launch faster than the old client. Epic's own benchmarks, reported by Tom's Hardware, showed it hitting the store in around 5.5 seconds versus Steam's 10 seconds, a 46% improvement. And it's a beta, explicitly labeled as such.
What users actually found
According to coverage from Tom's Hardware and Windows Report, among others, the preview shipped with a handful of bugs that users found within the first few days: store pages loading blank, the launcher window becoming impossible to drag, login errors, and the Fab and friends panel disappearing entirely on Linux. Valve quietly updated the Steam client shortly after launch and reportedly matched the speed advantage. A 0.100.0 patch on October 21 addressed some of those issues. The launcher is still in preview.
Why the backlash wasn't really about bugs
Betas ship with bugs; that is the point of them. What got people's backs up was the framing, not the bugs themselves. Epic's blog post credited AI tooling as the reason the launcher came together at all, and that message landed right after the company had made significant cuts to its workforce, including a round widely reported at around 1,000 positions in early 2026. The timing, more than the message itself, is what drove the reaction.
The real lesson for indies
For someone building an indie game, the lesson is not "Epic had bad PR." It is something smaller and more practical. Vibe coding and AI-assisted development are real tools. They help you move faster. But they do not change what happens when a player opens your thing for the first time and finds the login does not work, or has a panel that will not load. The bugs Epic's users found in the first days of the preview are the same kind that QA catches before a release: not obscure edge cases, but the stuff that shows up in the first five minutes of normal use.
Epic can push patches every week until the product is solid. An indie developer who ships a demo has one first impression. The gap between "it works on my machine" and "it works for a stranger who just picked it up" is exactly what testing is for.
IndieBug works with indie developers to find the problems that only show up when someone outside the team opens the build for the first time.