Forum rules · Pinned
Community desk · September 18, 2026
A useful place to think out loud.
These forums are for people exploring product problems, early concepts, prototypes, testing, and development questions. Clear context and constructive discussion make the resource more valuable for current participants and future readers.
Before creating a topic, search the discussion resource and take a moment to frame the problem you are trying to solve. Share only details you are comfortable making public.
How to participate
- Lead with the problem. Explain the user, situation, and need before presenting a proposed solution. This gives others enough context to respond thoughtfully.
- Keep discussion constructive. Address the work, evidence, assumptions, and practical tradeoffs. Disagreement is welcome when it remains specific and respectful.
- Protect private work. Forums are public discussion spaces. Avoid posting confidential material, unpublished technical details, or anything you do not want others to see.
- Use clear, relevant titles. A focused title and a concise first post make a topic easier to find, understand, and revisit later.
- Do not make commercial promises. Posts should not claim guaranteed results, endorsement, licensing, funding, or development outcomes.
- Respect the shared workspace. Keep promotional material, repeated posts, and unrelated links out of the discussion. Add useful context rather than noise.
- Ask for the feedback you need. State whether you are looking for research leads, prototype observations, user questions, or another practical next step.
Community discussion can help clarify a concept, but it is not a substitute for professional legal, technical, safety, or business advice. Consider your own confidentiality and intellectual-property needs before posting.
What makes a strong forum post?
A strong contribution is grounded in an observable need. It explains what has already been tried, identifies the uncertainty that remains, and invites feedback on a specific question. Photos, sketches, or prototype notes can be helpful when they support that purpose.
Thank contributors for their time, return to your topic with what you learned, and keep the conversation centered on evidence and next steps. That simple practice builds a more useful resource for the whole community.