The Prototype Pivot: Recognizing the Line Between Fan Tribute and IP Infringement
Realizing our initial prototype looked too official, hitting a 5-month shelf pause, and establishing our unbreakable Fair Use development rules.
The screen was glowing with an undeniable, brilliant gold.
It was late at night, and after nearly five months of pouring hours into an IDE alongside artificial intelligence assistants, the first minimum viable product of our daily sci-fi trivia web app was finally sitting on the display. It was a 3x3 grid, sleek and dense with lore. On top sat glowing, official-looking movie title logos pulled straight from high-resolution SVG assets. The headers shimmered in sharp yellow typography, set against a starfield backdrop.
If you looked at the screen for even a fraction of a second, your brain made an instant association. It looked like an official product. It looked like something released directly by a multi-billion-dollar entertainment conglomerate.
I leaned back in my chair, looked at the board, and felt a cold knot form in my stomach.
It was not a feeling of triumph. It was a sudden, heavy realization that Scott and I had built ourselves straight into a legal corner.
The Illusion of the "Cool" Prototype
When indie developers and vibe coders set out to build a fan project, the initial impulse is almost always aesthetic mimicry. We want our creation to feel authentic. We want to evoke the exact nostalgic high of sitting in a theater or opening a comic book.
In our original prototype, every single visual choice was dialed in to clone that official atmosphere:
Brand-Identical Fonts: We utilized custom font files matched to the exact typography of a legendary space-opera franchise.
Proprietary Media Assets: The grid headers did not just spell out movie titles in standard text; they loaded raw SVG graphic logos directly from popular media archives.
Trade Dress Color Palettes: We leaned heavily into bright yellow and gold borders, replicating iconic film opening crawl aesthetics.
The prototype looked incredible. It also violated the most fundamental rule of brand protection under intellectual property law: trademark confusion.
If a casual player stumbled across our site and reasonably believed that a major studio built, endorsed, or licensed the game, our fair use arguments would collapse before a judge ever read a line of our backend code. We were not just indexing trivia facts; we were accidentally impersonating the brand.
Coming to Grips with the Hard Stop
The temptation to rationalize is real. You tell yourself that it is just a non-commercial hobby project, that you are not selling physical merchandise, or that millions of fan sites exist online.
For weeks, I tried to debate the AI models I was using for development guidance. I fed prompts into AI assistants, asking for edge cases, historical precedent, and legal commentary. I wanted the models to give me permission to keep the cool graphics. I wanted a guarantee that our tribute would slip under the radar.
Instead, the deeper I dug into legal precedents surrounding transformative use (17 U.S.C. § 107) and nominative fair use, the clearer the truth became.
Fair use protects the raw expression of facts, research, commentary, and transformative game mechanics. It does not protect taking a company's registered trademarks, graphic logos, and distinct visual trade dress to decorate your custom web app.
I realized Scott and I could not launch the game like this. The risk was absolute. If we released an app that looked like an official studio release, we would receive a cease-and-desist letter within days, destroying months of quiet hobby work.
I closed the IDE, pushed the code to a private branch, and walked away.
The Five-Month Shelf and the Parody Breakthrough
For five long months, the project sat untouched on my hard drive. No code was committed. No new components were generated.
That pause felt like a massive setback at first, but it turned out to be the most critical incubation period of the entire build. I thought about the game constantly, wrestling with a core question: Could a fandom trivia game remain fun, atmospheric, and deeply satisfying if you stripped away every single official image, font, and trademarked visual asset?
The breakthrough came from an unexpected place. My wife surprised me with a mystery date night, keeping the destination a complete secret until we arrived. We pulled up to a theater hosting a well-known, unauthorized theatrical parody burlesque show based on our favorite space opera.
Sitting in that audience, watching how a creative team built an entire live performance that was unmistakably parody, deeply transformative, and legally protected, a lightbulb went off. Seeing how they navigated the boundaries of fair use in live entertainment gave me complete clarity for our digital architecture. It proved that true fan appreciation does not rely on corporate logos; it relies on homage, clever transformation, and respecting the legal line.
I went back to our codebase alongside Scott with a renewed sense of purpose and established two unbreakable development rules:
Rule #1: Do not do anything to compromise our fair use defense.
Rule #2: Make it the greatest user experience we possibly can, as long as it does not compromise Rule #1.
I repeated this mantra constantly to the AI assistants throughout the remainder of the project build.
The "Cyan & Text" Architecture
When we opened the project folder again, we completely purged the original gold-and-black palette and replaced it with an original, high-tech cyan visual aesthetic (#5bc0de). Almost the entire user interface was rebuilt around variations of pure cyan glowing borders and high-contrast white text set against dark space backgrounds.
The biggest technical evolution happened in how we rendered game title headers. Originally, we used static SVG graphic logos. But we realized that using static graphics brought two major flaws: legal trademark risk and zero accessibility. We wanted fans all over the world to be able to play our game, which meant the titles needed to be dynamically translatable into multiple languages.
We replaced the graphic images with an innovative hybrid solution: rendering real HTML text elements inside responsive SVG viewport wrappers.
By switching to plain-text rendering inside SVG containers, we achieved two massive wins at once:
Legal Safety: We eliminated all proprietary graphic logos, keeping our application firmly within nominative fair use.
Global Accessibility: The board headers were now pure DOM text, allowing browser translation engines and localization tools to translate movie titles instantly for international players.
Lessons for Aspiring Developers & Vibe Coders
If you are an indie developer using AI to build tools or games around existing pop-culture worlds, recognizing the line between fan tributes and commercial risk is your most important skill.
Facts Are Free; Trademarks Are Not: You can build relational databases around fictional characters, planets, and events. Fictional facts are not copyrightable. However, using an official studio logo to present those facts immediately triggers trademark liability.
Anchor Your Project in Strict Rules: Establish your legal boundaries on Day 1 and never compromise them for visual shortcuts. Instruct your AI coding tools to respect those constraints in every prompt.
Design for Functionality: Pivoting from static images to plain text did not just make our app legal; it made it better by unlocking multi-language support for a global audience.
Pivoting away from our original visual design felt painful at the time. In hindsight, it was the single decision that made our application viable, scalable, and safe for public release.