AITA for not giving my father the source code of the app I made for him?

Picture a cozy family visit, filled with warm coffee and casual tech talk, suddenly derailed by an unexpected demand. A young developer, enjoying a well-earned vacation, crafts a sleek Android app for their father’s phone battery needs, only to find him eyeing a quick buck on the Play Store. What started as a kind gesture spirals into a clash over code, boundaries, and family ties, leaving the creator torn between loyalty and ownership. Readers can’t help but wonder: who’s really in the wrong here?

This tale of tech and tension unfolds with a son’s passion for coding colliding head-on with a father’s entrepreneurial dreams. The Reddit community buzzes with opinions, and the drama feels like a sitcom gone rogue. As the story unravels, it raises questions about intellectual property and family expectations, pulling readers into a relatable yet thorny dilemma.

‘AITA for not giving my father the source code of the app I made for him?’

This family feud over source code screams of mismatched expectations. Dr. John Gottman, a renowned relationship expert, notes, “Conflict arises when partners—or family—fail to align on mutual goals”. Here, the OP’s desire to help clashes with the father’s profit-driven vision, creating a classic boundary violation.

The OP’s reluctance to share the code stems from its personal value—hours of unpaid labor fueled by passion. Intellectual property, as explained by the World Intellectual Property Organization, protects creators’ rights, and the OP’s stance aligns with this principle. The father’s push ignores the effort required to maintain and market an app, revealing a gap in understanding.

This situation mirrors broader issues of family entitlement. A 2021 study from the Institute for Family Studies found that 68% of family conflicts involve unmet expectations around shared resources. The father’s demand for the code without contributing work reflects this dynamic, risking trust.

For the OP, setting boundaries is key. Experts suggest clear communication—like offering a licensing deal or explaining the app’s unsuitability for sale—can preserve relationships while protecting rights. The OP’s choice to share flawed code, though petty, signals a need for mutual respect. Moving forward, a calm discussion about intentions could rebuild trust.

Here’s what Redditors had to say:

The Reddit crew didn’t hold back, serving up a spicy mix of support and snark for the OP’s plight. Here’s the unfiltered scoop from the crowd, buzzing with cheers and sly jabs.

These Redditors rallied behind the OP, praising their stand on intellectual property while chuckling at the father’s tech-clueless ambition. Some suggested contracts to secure the OP’s rights; others urged a cheeky open-source release to thwart the plan. But do these fiery takes capture the full picture, or are they just adding fuel to the family fire?

This saga of code and kin leaves us pondering where loyalty ends and personal rights begin. The OP’s journey from a kind favor to a fractured bond highlights the delicate balance of family and creative control. It’s a reminder that even small projects can spark big disputes when expectations misalign. What would you do if a family member tried to profit off your passion project? Share your thoughts and experiences below—let’s keep the conversation coding along!