Participation Guidelines
Envision WWDC is a third party online activity built around the full WWDC week. These participation guidelines explain the basic expectations for joining, posting, collaborating, and sharing work inside the event.
The goal is to keep the community useful, respectful, readable, and worth returning to throughout the week. Participation should help people understand what is changing, build new work, find collaborators, and discuss ideas in good faith.
Envision WWDC is intended to feel open without becoming chaotic. The point of the event is not simply to increase volume during WWDC week. The point is to create a place where thoughtful launch thinking, meaningful technical discussion, early demos, and practical collaboration can remain visible while the week is still in motion.
Who Can Participate
Developers, designers, product thinkers, indie builders, students, and small teams are welcome. You do not need to represent a company or already have a published product. You do need to participate honestly and constructively.
People joining the event should have a clear reason to be there. That reason may be to discuss WWDC announcements, test ideas, find collaborators, take part in If You Ran The Launch, share early work, or follow new Apple platform changes as they are released. Passive presence is fine. Disruptive presence is not.
Expected Conduct
Participants should communicate respectfully. Direct disagreement is fine. Harassment, intimidation, hate speech, impersonation, spam, repeated disruption, or abusive behavior are not acceptable.
If you are giving feedback, keep it specific and useful. If you are asking for help, explain clearly what you are building, what you need, and what stage you are at.
Envision WWDC should remain readable for people across time zones and different levels of experience. That means discussion should stay focused, claims should be made carefully, and other participants should not be pressured, mocked, or drowned out for the sake of attention.
Posts And Submissions
If You Ran The Launch entries, Inside Apple Park posts, What Should Exist entries, Everyone Touched It edits, What Got Made posts, Until It Ends messages, and discussion threads should be clearly labeled. Do not present unfinished concepts as shipped work, and do not present someone else’s work as your own.
If a submission uses pre-existing assets, outside libraries, earlier code, or work from collaborators, say so. Clarity is more useful than trying to make a post appear larger or newer than it really is.
Submission quality is not measured only by polish. Early work is welcome if it is labeled honestly. A rough but real demo is more valuable than a misleading claim. A thoughtful prediction is more useful than a vague attempt to sound impressive after the fact.
Accuracy And Representation
Participants should take reasonable care when describing Apple announcements, platform capabilities, implementation status, and technical conclusions. Fast discussion is part of WWDC week, but speed is not a reason to publish claims that are knowingly misleading, recklessly incomplete, or designed to create confusion.
If a post reflects interpretation rather than confirmed platform behavior, it should be presented as interpretation. If a demo is a concept rather than a working implementation, it should be labeled accordingly. Clear labeling is a basic participation requirement, not an optional courtesy.
Collaboration
Collaboration posts should include a short project description, what roles are needed, what skills are already present, and how people can respond. Vague requests with no real direction may be ignored or removed.
If you join another person’s project, communicate expectations clearly. Respect the ownership of code, design work, writing, prototypes, and shared ideas.
Collaboration should not depend on hidden expectations. If a project is unpaid, say so. If a post is exploratory rather than production-ready, say so. If a role requires a specific time commitment during WWDC week, say so. The more exact the request is, the more useful the collaboration environment becomes.
Privacy And Data
Participants should not post personal information about themselves or others unless that information is intentionally being shared for event participation and is reasonably necessary in context.
Privacy handling for the site and related event services follows the published Privacy Policy. Where privacy expectations, storage practices, or contact handling are relevant, they should be understood in accordance with that policy.
Participants should also exercise judgment when sharing contact details, private messages, screenshots, testing links, or collaboration records. Information that was shared privately for one purpose should not be republished publicly without a clear basis for doing so.
Intellectual Property And Confidentiality
Do not post content you do not have the right to share. Do not upload stolen assets, private source code, confidential information, or material that violates another person’s rights. Respect NDA boundaries, collaborator ownership, and the rules of the platforms you build on.
This includes screenshots, documents, code, and recordings. If you are not sure whether you have the right to share something publicly, do not post it. WWDC enthusiasm is not a reason to ignore rights, ownership, or confidentiality.
Availability And Event Scope
Envision WWDC is an independent activity and may change as the event evolves. Activities, access pathways, community infrastructure, submission windows, or moderation mechanisms may be adjusted, paused, or removed if that is necessary to keep the event workable during WWDC week.
Participation in one part of the event does not guarantee access to every other part of the event. Certain areas may remain limited, delayed, or unpublished while the site and community structure are still being finalized.
Moderation
Content may be edited, hidden, or removed if it is abusive, misleading, spammy, plagiarized, or clearly outside the purpose of the event. Repeated or severe violations may result in limited participation or removal from the community space.
Moderation decisions are made to preserve clarity, safety, and usefulness. Not every low-quality post is malicious, but repeated low-quality or misleading participation can still damage the event and may therefore be limited.
Moderation may include warning, content removal, access limitation, comment restriction, or full removal from the relevant community space. The form of action taken will depend on the severity, pattern, and context of the conduct involved.
Changes To These Guidelines
These guidelines may be updated as the event structure becomes more specific. Changes may reflect moderation needs, new submission formats, or practical adjustments required during WWDC week.
If changes are made, the current version on this page should be treated as the active reference. Continued participation after updates means participants are expected to follow the revised guidelines.
Practical Standard
Before posting, ask a simple question: does this make the week clearer, more useful, or more collaborative for someone else? If the answer is yes, it likely belongs here.
If you have questions about participation expectations, privacy, or how the event is being run, review the Privacy Policy or contact the site owner through the links already provided on the site.
Envision WWDC should leave behind more than reaction. It should leave behind useful threads, better questions, new collaborators, and work that can still be understood after the busiest moments of WWDC have passed.
2026 Jiaxu Li