Few products define a franchise the way the original John Madden Football did for Electronic Arts. In the mid-1980s, software developer Robin Antonick built that first game for the Apple II under contract with EA, writing the source code that turned a coaching concept into a playable simulation of the sport. The franchise that grew out of that work, later branded Madden NFL, became one of the most successful in the history of video games. Years later, in Robin Antonick v. Electronic Arts Inc., Antonick brought suit in the U.S. District Court for the Northern District of California, and the technical heart of the dispute reached back to the code he had written decades earlier.
A source-code-comparison case at its core
Antonick alleged that later generations of the Madden franchise were unauthorized derivative works of his original copyrighted source code, and he pursued a parallel contract theory tied to royalties on those later versions. That framing put software copyright, rather than patents, at the center of the matter, and it made the question of derivation a technical one. To decide whether the later games derived from the original, the parties could not simply compare box art or gameplay: they had to look at the software itself.
That is what distinguished this case. Proving or rebutting a claim of derivative work in software copyright turns on substantial similarity between protected expression in one program and expression in another, examined across versions built years apart on different hardware and by different teams. The original game and its successors were separated by generations of console platforms, programming languages, and development tools, so the comparison had to account for how a design can carry forward even as the surrounding technology changes. Sorting the protected expression from the unprotectable ideas, methods, and functional constraints of simulating football is precisely the kind of analysis that calls for a rigorous, engineer-led source code review rather than a lay reading of the finished games.
Source-code experts for the plaintiff
Barr Group served on behalf of the plaintiff, providing source-code-comparison expertise for Antonick's side of the technical dispute. The engagement centered on analyzing Antonick's original source code against EA's later versions of the game to assess questions of derivation and substantial similarity, the issues on which the copyright claim depended. That work drew on the same discipline Barr Group brings to any software copyright matter: reading code carefully, understanding how a program is structured and how its logic is expressed, and distinguishing the parts of a program that reflect an author's protectable choices from the parts dictated by the problem being solved.
The specific findings from that analysis are confidential and are not recounted here. In general terms, the role was to give counsel a technical foundation grounded in the code itself, so that arguments about derivation rested on direct examination of the software rather than on impressions of the games as played. This is the plaintiff-side counterpart to the defensive code reviews Barr Group performs in patent and trade-secret matters, and it reflects the breadth of the firm's software and electronics experts across copyright as well as patent litigation.
Litigation outcomes
The case was tried to a jury in the Northern District of California in 2013, with the comparison of source code across generations of the game central to the technical presentation. The jury found in Antonick's favor, concluding that the earlier games infringed his copyrighted work, and awarded 11 million dollars.
The jury verdict was later set aside as a matter of law, a ruling affirmed on appeal in 2016, on the ground that the games themselves had not been placed before the jury for comparison, a question about the trial record rather than about the technical analysis.
The lesson holds regardless of the final disposition: when a software copyright claim depends on whether one program is a derivative work of another, the dispute turns on a disciplined, credible comparison of the actual source code, and that is work for experts who read code for a living.
Learn more about Barr Group's expert witness services.