Contact us
We read everything that comes in. Corrections and accessibility reports get answered first.
We aim to reply within three business days. For a correction, please include the lesson URL and, if you can, the Flutter version you are on — it makes the fix much faster.
What to write about
Corrections and outdated code
The most useful message you can send. Tell us the lesson URL and what is wrong — a deprecated API, a sample that no longer compiles, an explanation that is misleading. We prioritise these above everything else.
Lesson requests
If there is a Flutter topic you cannot find a decent written explanation of anywhere, we want to hear about it. Requests that come up repeatedly get written first.
Accessibility problems
If any part of this site is difficult to use with a screen reader, keyboard, or at a large text size, please tell us which page and which assistive technology. These are treated as bugs, not suggestions.
Privacy and advertising
Questions about the data this site collects, or about the ads shown on it, including requests relating to your data under GDPR or CCPA.
What we cannot help with
We are a small team and cannot debug private codebases, do paid consulting, or provide one-to-one tutoring. For general Flutter help, the Flutter GitHub discussions and the community Discord are far better places to ask — more people, faster answers.
We also do not accept guest posts, sponsored articles, or paid links. Every lesson on this site is written in-house.