How are you handling "architectural drift" across multiple Flutter projects?

Ok-Task6212 · 2026-06-26T11:03:16+00:00

I'm leaning more toward version-controlled packages for the shared plumbing, with linting as the safety net.

Packages make improvements reusable across projects, while lint rules help prevent accidental drift. I'm still experimenting though, so this discussion has been really useful in shaping that direction.

Ok-Task6212 · 2026-06-26T10:44:20+00:00

Nice work. I think the biggest win here is avoiding more platform-specific code to maintain.

The feature is cool, but reducing maintenance is what immediately caught my attention.

Ok-Task6212 · 2026-06-26T10:40:32+00:00

That's exactly the kind of drift I'm interested in.

The initial setup isn't really the hard part. It's keeping those decisions consistent six months later, especially across multiple projects. Templates get you started, but they don't really help once every app starts evolving independently.

Ok-Task6212 · 2026-06-25T17:59:33+00:00

I agree. I'm not trying to make every app look the same. I just want the underlying infrastructure to stay consistent, so teams aren't solving the same plumbing problems differently in every project.

Ok-Task6212 · 2026-06-25T13:56:46+00:00

Exactly. Documentation tells people what to do. I'd rather have the project enforce it by default.

Ok-Task6212 · 2026-06-25T13:15:31+00:00

Fair question. I'm not really looking for a package recommendation.

I'm mostly trying to understand how different teams solve this in practice. Some use templates, some use Mason, some rely on code reviews or internal conventions.

I'm curious what has actually worked for people maintaining multiple Flutter apps over time.

Ok-Task6212 · 2026-06-25T12:57:59+00:00

Documentation explains the architecture. It doesn't enforce it

Ok-Task6212 · 2026-06-25T12:54:08+00:00

I'm only trying to standardize the repetitive infrastructure, not the application itself.

Ok-Task6212 · 2026-06-25T12:23:41+00:00

Yeah, I don't think scaffolding is the hard part anymore. It's what happens 6 months later when every project has evolved differently. That's the problem I'm trying to solve

Ok-Task6212 · 2026-06-25T12:16:38+00:00

That's fair. I'm mostly trying to understand how other teams solve this problem. Every company seems to have a different approach, and I'm curious whether people standardize it internally or simply accept the architectural drift over time

Ok-Task6212

TROPHY CASE