
🚀 Announcing DCM Dashboards general availability An ultimate solution to monitor code quality for your #Flutter projects. ✅Never let important issues slip ✅Visualize technical debt ✅Track trends within your org ✅Share reports with stakeholders

Advanced linter for Flutter and Dart developers. Join our discord discord.gg/Vzjprgk4sb. "its not AI, but it’s better!"

🚀 Announcing DCM Dashboards general availability An ultimate solution to monitor code quality for your #Flutter projects. ✅Never let important issues slip ✅Visualize technical debt ✅Track trends within your org ✅Share reports with stakeholders

I'm working on a 4 years legacy codebase with 500k LOC. It's time to integrate @DCMAnalyzer. I prepared a AI workflow, that will spawn a lot a subagents. Take the bet, will I one shot this ?

#Flutter devs: how many of these have you run into? We’ve rounded up 15 common Flutter & Dart mistakes you’ll definitely recognise: ⚠️ Memory leaks ⚠️ `setState` misuse ⚠️ Async pitfalls ⚠️ Testing gaps & more Find out how to spot and fix them: dcm.dev/blog/2025/03/24/fift…

🔥 DCM 1.36.0 includes 11 new rules for Flutter, Common, Equatable, & Mocktail categories. To learn how these rules can prevent potential issues and bugs, read: dcm.dev/blog/2026/03/19/what…

🤔 Most teams can tell when a Flutter method feels too complex. The problem is that “too complex” is subjective. Read "Cyclomatic Complexity, #Flutter Guide" & learn how to shield your code and to refactor it down and protect your team now & later! dcm.dev/blog/2026/04/01/cycl…

✨ Still doing manual null checks in your collection literals? DCM’s prefer-null-aware-spread rule warns when you could use ...? in your #Flutter code instead. 🎥 Watch to learn how to fix it: youtu.be/92X6GXwW-N8

What could be better than attending F&F with your friend? 💙 Doing it for FREE 😉 We’re raffling TWO tickets 🎟️🎟️ To participate: 1. Like & share this post 2. Follow @FlutterNFriends 3. Tag your friend in the comments 1 comment = 1 entry More tags = more chances to win 😉

When it comes to #Flutter widget code, there are different expectation compared to plain domain logic. That’s why our guide separates widget metrics from non-widget metrics, so UI, services, and domain logic are measured differently: dcm.dev/docs/guides/advanced…

Don’t disable a metric if the default threshold does not really work, instead: ✅ Use entries for stricter new code ✅ Give legacy folders a temporary threshold That way, new code improves without blocking every release because of old code.

Advanced metrics configuration in DCM is where metrics become practical. You’re not limited to one global threshold. You can tune metrics for legacy code, new features, widget-heavy UI, critical paths, and even dashboards-only tracking. In this guide, learn how you can do it 👇

🚀 Quality code tip: Use the variable you already created. It's easy to miss, but the "use-existing-variable" rule catches repeated expressions when a variable already exists. 🪧 Less code 🔁 Less duplication ✅ Fewer inconsistencies dcm.dev/docs/rules/common/us…

DCM has delivered measurable improvements for Appinio: ⚡ faster, smoother PR reviews 🐛 fewer runtime issues ✅ increased code consistency 👋 easier onboarding 🔄 continuous improvement without blocking development Read more: dcm.dev/customers/appinio/

The DCM baseline keeps the team on top of legacy issues, separate from new code. Real-time IDE feedback enforces consistent structure and patterns, and GitHub Actions automation ensures that no PR is merged without passing DCM checks.

Appinio adopted DCM in both local development and CI/CD. They use: 📐 recommended ruleset 📁 dcm check-unused-files 👩💻 dcm check-unused-code ✨ dcm check-parameters ✅ dcm analyze on every PR to ensure quality and consistency.

The issues well-said by Mohammed Alfatla, Senior Flutter Developer at Appinio: “We needed strong linting, something rigid. Manual checks for banned names, unused files, disposing controllers, streams… it’s too much to review every PR manually.”

As Appinio’s mobile team expanded, they faced: ⚠️ inconsistent coding patterns across contributors 💪 manual PR reviews for simple issues 📏 built-in/community lints are not strict or deep enough ⤴️ legacy code with architectural inconsistency