Idea or request
Suggest a new tool, a clearer explanation, a classroom use case, or an improvement to an existing workflow.
Best for: ideas others can discuss in public.
Start a public idea issueHelp shape the next useful improvement
Try a tool. Tell us what happened.
You do not need to write a formal review. A short account of what you tried, what worked, and where you got stuck can make an open tool more useful and more accessible.
Three routes
Choose the channel that fits
AlloFlow does not collect your feedback on this page. A link opens either a public GitHub issue or a draft in your email app, so you can review everything before sending it.
Bug or accessibility barrier
Report an unexpected result, a broken interaction, confusing instructions, or a barrier you encountered with assistive technology.
Best for: reproducible problems without private or security-sensitive data.
Start a public problem reportPrivate classroom story
Share contextual feedback that is not appropriate for a public issue. De-identify the story before sending it, even by email.
Best for: practitioner context, not student records or urgent support.
Draft a private emailProtect people and systems
Do not include sensitive material
Whether you use GitHub or email, do not send:
- student names, records, work samples with identifiers, or other education records;
- health, disability, assessment, or clinical information about an identifiable person;
- API keys, passwords, access tokens, credentials, or private security details;
- confidential school or organization information; or
- copyrighted source text, paid content, or files you do not have permission to share.
For a potential security vulnerability, use private email and provide only the minimum safe detail needed to begin a conversation. Never paste a working credential.
Useful, not lengthy
What helps us understand
A few concrete details are more useful than a polished review.
- Name the tool or workflow.Say what you opened and, if relevant, whether you used Gemini Canvas, the browser app, Desktop, a Skill, or the MCP connector.
- Describe the goal.Explain what you were trying to accomplish without sharing the original private source or identifying a learner.
- Explain what happened.Include the steps you took, the result you expected, and the result you saw. A de-identified screenshot can help when it is safe to share.
- Add access context when relevant.Name the browser, device, assistive technology, input method, or file type involved.
What happens next
Feedback is reviewed, but a response is not guaranteed
AlloFlow is an open-source project, not a staffed support desk. Public issues make ideas and progress visible to the community, but there is no guaranteed response time, fix date, or commitment to implement a request. Private messages may receive a reply when follow-up would be useful.
This channel is not appropriate for emergencies, legally required reporting, or urgent student support. Follow your school or organization’s established process for those needs.