Stop Arguing in PRs. Let Your Code Handle It Instead

Stop Arguing in PRs. Let Your Code Handle It Instead.

Intro

We build mobile apps all the time at our company. Every time we start a new Flutter project, the same comments show up in pull requests sooner or later.

• “Please don’t use this directly”
• “We have an abstraction for this”
• “This breaks the design system”

A few comments like these are easy to handle, but when there are a lot, they slow down development and cause friction in the team.

The problem isn’t a lack of rules. We already have clear agreements on architecture, design system guidelines, and abstractions. These are written in our internal wikis, covered during onboarding, and brought up in reviews. Still, enforcing them is manual and relies on memory, discipline, and repeated reminders from developers. Sooner or later, this approach fails.

Make your code handle it

Flutter provides strong tooling for formatting and linting, but when it comes to enforcing team-specific architectural rules, there is a huge gap.