Bridgerton author Julia Quinn addresses fan dismay over gender-swap character in season 3 finale

Julia Quinn addresses fan concerns over the gender-flipping of Francesca love interest in the Netflix series.


Pop Culture & Art June 26, 2024
Photo: Netflix

Julia Quinn, the author behind the beloved "Bridgerton" novels, recently addressed the fan outcry following a significant change in the Netflix adaptation's Season 3 finale.

The series introduced Michaela Stirling, a female cousin of John Stirling, as a potential love interest for Francesca Bridgerton, deviating from the books where the character is male.

"Anyone who has seen an interview with me from the past four years knows that I am deeply committed to the ‘Bridgerton’ world becoming more diverse and inclusive as the stories move from book to screen," Quinn wrote in a statement.

Quinn acknowledged the fans' "disappointment" and explained that she had extensive discussions with showrunner Jess Brownell to ensure the change remained true to the spirit of the books. She emphasized the importance of portraying Francesca's love for John while also embracing the opportunity for a new and emotionally resonant storyline with Michaela.

Quinn expressed confidence in Shondaland's vision for "Bridgerton" and assured fans that Francesca's season would be the "most emotional and heart-wrenching story of the show," even with the gender-flipped character.

Brownell, in a separate interview, acknowledged the sensitivity surrounding the change and assured viewers that the show aims to portray queer joy and happiness, ultimately leading to a happily ever after for Francesca.

While some fans remain skeptical, others are intrigued by the potential for a fresh and inclusive storyline. The change has sparked conversations about representation and adaptation in popular culture, highlighting the ongoing dialogue between creators and fans.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ