Test - MD Project Submission

How can I help a participant submit an eligible project?

Comment

eplace every [bracketed placeholder] and delete

these instruction lines before you submit.

Inspiration [REQUIRED]

What problem, experience, or idea led you to build this? Why does it matter to you or your users?

[Your answer]

What it does

Describe the core experience: what users see, do, and get out of it.

[Your answer]

How we built it [REQUIRED]

Tools, engines, SDKs, languages, hardware, and APIs you used, plus how the main pieces fit together.

  • Engine / framework: [e.g., Unity 6, Unreal Engine 5]
  • SDKs / APIs: [e.g., Meta XR SDK, Interaction SDK]
  • Languages: [e.g., C#, C++]
  • Target device(s): [e.g., Meta Quest 3, Quest 3S] [Short explanation of your build process and architecture]

Challenges we ran into

[Your answer]

Accomplishments that we're proud of

[Your answer]

What we learned

[Your answer]

Future plans for improvement [REQUIRED]

What will you add, fix, or expand after the hackathon? Be specific. A short roadmap works well.

  • [Planned improvement 1]
  • [Planned improvement 2]
  • [Planned improvement 3] ## Store status and target launch date [REQUIRED IF APPLICABLE]

Check one box. If your app is not on the Meta VR Store yet, you must give a target launch date.

  • [ ] Already published on the Meta VR Store. Store link: [URL]
  • [ ] Not yet published. Target launch date: [Month DD, YYYY]
    • Launch plan / milestones: [e.g., closed beta in MM/YYYY, store submission in MM/YYYY] ## New features and capabilities [REQUIRED IF APPLICABLE]

Only for Adapted / Significantly Updated Experiences. If your project is an existing app you adapted or significantly updated during the submission period, summarize what's new. If your project is brand new, write "N/A – new project."

  • Original app: [Name and link, if published]
  • Summary of what changed: [2–3 sentences]
  • New features / capabilities added:
    • [New feature 1: what it does and why it matters]
    • [New feature 2]
    • [New feature 3] ### Changelog [RECOMMENDED]
Version / Date Change
[v1.0 – MM/DD/YYYY] [Original release baseline]
[v2.0 – MM/DD/YYYY] [New feature or update]

Media [RECOMMENDED]

Screenshots and demo videos help judges understand your project quickly. Upload images to the project gallery, and put your demo video link in the video field on the submission form.

  • Demo video: [YouTube / Vimeo link]
  • Screenshots: [Add to gallery, or embed here: ![Screenshot description](image-url)]

- Before / after comparison (updated experiences): [Optional]

Submission checklist

Tick every box before you hit Submit.

  • [ ] Inspiration is explained
  • [ ] How we built it is explained
  • [ ] Future plans for improvement are listed
  • [ ] Store status is confirmed, and a target launch date is given if the app isn't published
  • [ ] New features are summarized (Adapted / Significantly Updated Experiences only)
  • [ ] Screenshots, changelog, and/or demo video are included (recommended)
  • [ ] All [bracketed placeholders] and instruction text are removed

Built With

Share this project:

Updates