ReconScribe
Text size
Hackathons Practical guide
Published Last updated 38 min read

Meta VR Start Developer Competition 2026: $1M for hands-first VR apps

The Meta VR Start Developer Competition 2026 offers up to USD 1,000,000 in cash for VR apps that work with your hands alone, and adults in most countries can enter. Meta is paying out 20 cash prizes, with USD 100,000 for each Gaming and Entertainment winner and USD 70,000 for each Productivity winner. Entries close on Wednesday 18 November 2026 at 12:00 PM Pacific Time (PST), which is 20:00 UTC; the dates table shows that moment in your local time. The main catch: whoever submits must be a Meta VR Start member by then.

It is a Meta Quest hackathon with serious money behind it, open to solo builders, teams and studios, and it runs entirely online. You do not need to own a headset to compete, a web build is allowed, and adults in most countries qualify on the same terms; the exclusions are Brazil, Quebec, areas under comprehensive international sanctions and any country or person designated by the US Treasury’s Office of Foreign Assets Control (OFAC).

This guide covers what to build, how to join the Start program, how to get a playable build in front of the judges, how scoring works and what happens with tax if you win, whether you live in the US or anywhere else. Every rule, date and amount below comes from the official contest pages and the Official Rules as of 17 October 2026.

Meta logo
Hackathon guide · Meta Platforms, Inc. (managed by Devpost)
Meta VR Start Developer Competition
Open
Time left to submitWed 18 Nov 2026, 20:00 UTC
Last moment to submit: Wed 18 Nov 2026, 20:00 UTC
Prize pool
Up to USD 1,000,000
20 cash prizes; track winners get USD 100,000 or USD 70,000
Deadline (UTC)
Wed 18 Nov 2026, 20:00 UTC
Official: 18 Nov 2026, 12:00 PM PT (PST, UTC-8)
Who can enter
Adults 18+ in most countries; submitter must be a Meta VR Start member
Brazil, Quebec, sanctioned areas such as Russia, Iran and North Korea, and OFAC-designated countries excluded
Format
Online, eight weeks
Solo, team or organisation; judged on Quest 3 and 3S
Seated developer using hand tracking on a VR headset while building an app for the Meta VR Start Developer Competition 2026
Hands-first means no controller is ever needed: the whole app must work with hand tracking and be playable on Meta Quest 3 and 3S.

Meta VR Start Developer Competition: the short answer

What it is: An eight-week online build contest from Meta, run on Devpost (a website that hosts hackathons), for hands-first VR and mixed reality apps in three tracks: Entertainment, Gaming and Productivity.
Prize pool: Up to USD 1,000,000 in cash across 20 prizes. Each Gaming and Entertainment winner gets USD 100,000 and each Productivity winner gets USD 70,000.
Deadline: Wednesday 18 November 2026 at 12:00 PM PT (PST, UTC-8), which is 20:00 UTC. The dates table shows it in your local time.
Who can enter: Anyone aged 18 or over who is an adult where they live and has a Meta account with Developer Access (developer permissions on the account; the rules require it but the contest pages do not explain how to switch it on). The person submitting must be a Meta VR Start member (Meta’s developer program, formerly Meta Horizon Start) by submission time.
Countries: Open worldwide except residents of, or organisations based in, Brazil, Quebec (Canada) and areas under comprehensive international sanctions such as Crimea, Russia, Cuba, Iran, North Korea and Syria, plus any country or person designated by OFAC (the US Treasury’s Office of Foreign Assets Control).
Hard rule: The whole experience must work with hands alone, without pairing a controller, and the build must be playable on Meta Quest 3 and 3S.
What you submit: An Invite URL (a link that lets judges install your build from a private release channel), or a public link for a web build, plus a public demo video under three minutes and a completed Devpost form.
Headset: Not required to compete. Judges test every entry on a Meta Quest 3 or Quest 3S.

What is Meta VR Start Developer Competition?

The Meta VR Start Developer Competition is an eight-week online build challenge from Meta Platforms, Inc., run on Devpost. Devpost is a website that hosts hackathons and handles sign-ups, submission forms and judging. The entry period opened on 24 September 2026, and the brief is easy to say and hard to do well: build a hands-first app for Meta VR devices. Hands-first means the headset’s cameras track your hands, so a person can finish the entire experience by pinching, grabbing and pointing, without ever pairing a controller. Controller support is allowed as an extra, but it can never be needed.

You can build a VR app (virtual reality, where you are inside a fully digital world) or an MR app (mixed reality, where digital objects sit inside your real room). MR relies on passthrough, which is the headset showing you a live camera view of your surroundings. Meta’s overview mentions both Meta VR Glasses and Meta Quest, but the FAQ says every build must be playable on Meta Quest 3 and 3S, and judges review apps on a Meta Quest 3 or Quest 3S.

Every entry picks at least one track and one division. The three tracks are Entertainment (lean-back media such as spatial cinema, interactive video, music visualisation, immersive storytelling, spatial audio and media companion apps), Gaming (puzzle, strategy, casual, social and narrative games that thrive seated and without controllers) and Productivity (multi-panel workspaces, task management, creative tools and habits tied to a daily moment such as a morning routine, a commute or winding down). The two divisions are New Experience, for projects conceived and built inside the competition window that started on 24 September 2026 with no older code, and Adapted / Significantly Updated Experience, for any build, prototype or published app that existed earlier and gains a meaningful new feature, mode or platform integration during the window. Meta may move an entry to a different track or division.

Meta also sets three design tests. The airplane seat test asks whether every interaction works in a small seated space of about two feet (the overview says a two-foot radius, the FAQ says about 2ft in diameter). The one bus stop test asks whether a session is satisfying in 10 minutes or less. The take it away test asks whether there is still a project if you remove the third-party service, because thin wrappers around platforms such as YouTube or ChatGPT are highly discouraged. These are guidelines, not hard rules, but the scoring rewards seated, hands-first design. Devpost showed 3,329 registered participants on 17 October 2026, and the full legal terms sit in the Official Rules.

Key dates and deadlines in UTC and your local time

The Official Rules state times in Pacific Time (PT). US clocks go back on 1 November 2026, so the September and October dates use PDT (UTC-7) and the November and December dates use PST (UTC-8). The table gives each time as the organiser states it, the same moment in UTC (Coordinated Universal Time, the reference clock every time zone is measured from) and the matching time in your own time zone, shown automatically.

The webinars are open to registered Start members logged in to the Meta Developer Forum. Most run in two slots: an EMEA slot (Europe, Middle East and Africa) at 3:00 PM Central European time and a North America slot at 10:00 AM PT, and some run only in the North America slot. In UTC, the EMEA slot is 13:00 up to 22 October and 14:00 from 26 October, and the North America slot is always 17:00. The table lists each session on its own row, so you can see both slots in your local time.

Official times with UTC conversions and your local time. The deadline is 12:00 PM PST on Wednesday 18 November (20:00 UTC), which is exactly midnight at UTC+4 and already Thursday 19 November anywhere further east.
What As the rules state it UTC Your local time
Entry period opens (start of the competition window) September 24, 2026 at 10:00:00 AM PT (PDT) Thu 24 Sep 2026, 17:00 UTC Worked out by your browser
Webinar, EMEA slot: Monday Unblock: Playable Prototype Mon Oct 19, 2026, 3:00 PM CEST Mon 19 Oct 2026, 13:00 UTC Worked out by your browser
Webinar, North America slot: Monday Unblock: Playable Prototype Mon Oct 19, 2026, 10:00 AM PT Mon 19 Oct 2026, 17:00 UTC Worked out by your browser
Webinar, EMEA slot: First Build Review Tue Oct 20, 2026, 3:00 PM CEST Tue 20 Oct 2026, 13:00 UTC Worked out by your browser
Webinar, North America: Agentic Workflows for New & Existing Apps Tue Oct 20, 2026, 10:00 AM PT Tue 20 Oct 2026, 17:00 UTC Worked out by your browser
Webinar, North America: Show Your Workflow: How VR Developers Actually Build Wed Oct 21, 2026, 10:00 AM PT Wed 21 Oct 2026, 17:00 UTC Worked out by your browser
Webinar, EMEA slot: First Build Review Thu Oct 22, 2026, 3:00 PM CEST Thu 22 Oct 2026, 13:00 UTC Worked out by your browser
Webinar, North America slot: First Build Review Thu Oct 22, 2026, 10:00 AM PT Thu 22 Oct 2026, 17:00 UTC Worked out by your browser
Webinar, EMEA slot: Monday Unblock: Building and Testing Mon Oct 26, 2026, 3:00 PM Berlin time (Devpost labels it CEST) Mon 26 Oct 2026, 14:00 UTC Worked out by your browser
Webinar, North America slot: Monday Unblock: Building and Testing Mon Oct 26, 2026, 10:00 AM PT Mon 26 Oct 2026, 17:00 UTC Worked out by your browser
Webinar, EMEA slot: Playtest & React Tue Oct 27, 2026, 3:00 PM Berlin time (Devpost labels it CEST) Tue 27 Oct 2026, 14:00 UTC Worked out by your browser
Webinar, North America slot: Playtest & React Tue Oct 27, 2026, 10:00 AM PT Tue 27 Oct 2026, 17:00 UTC Worked out by your browser
Webinar, EMEA slot: Playtest & React Thu Oct 29, 2026, 3:00 PM Berlin time (Devpost labels it CEST) Thu 29 Oct 2026, 14:00 UTC Worked out by your browser
Webinar, North America slot: Playtest & React Thu Oct 29, 2026, 10:00 AM PT Thu 29 Oct 2026, 17:00 UTC Worked out by your browser
Submission deadline (last moment to edit the form, track, division or build) November 18, 2026 at 12:00:00 PM PT (PST) Wed 18 Nov 2026, 20:00 UTC Worked out by your browser
Scored judging begins (the no-changes freeze already started at the deadline) Devpost schedule: November 23 at 9:00am PST. Rules: judging runs from on or around November 18, 2026 Mon 23 Nov 2026, 17:00 UTC Worked out by your browser
Scored judging ends Devpost schedule: December 09 at 7:00pm PST. Rules: on or around December 9, 2026 Thu 10 Dec 2026, 03:00 UTC Worked out by your browser
Winners announced Devpost schedule: December 11 at 10:00am PST. Rules: on or around December 11, 2026 Fri 11 Dec 2026, 18:00 UTC Worked out by your browser
Last day to request the winners list by email No later than three months after the end of the contest, by email to MetaHorizonStart@meta.com No exact date stated No fixed date

The line that matters most is the deadline: 12:00 PM PT on Wednesday 18 November 2026, which is 20:00 UTC. Check the local time in the table and treat a few hours before it as your real deadline, because a slow upload or a broken Invite URL in the final hour leaves no time to fix anything. East of UTC+4, which covers much of Asia and all of Australia and New Zealand, the deadline falls on Thursday 19 November local time (at UTC+4 itself it is exactly midnight), so do not plan around a full Wednesday there. The official Devpost schedule lists every phase.

The freeze starts at the deadline, not when scored judging begins. The schedule shows judging from 23 November to 9 December, but the FAQ tells you not to make any updates from 12:00 PM PST on 18 November until winners are announced. Your app must also stay available and free of charge to judges until the winner announcement, which the schedule lists for 11 December at 10:00 AM PST (18:00 UTC) and the rules describe as on or around 11 December 2026.

One small trap on the Webinars & Office Hours page: the 26, 27 and 29 October EMEA sessions are labelled 3:00 PM CEST, but Central Europe moves to winter time (CET, UTC+1) on 25 October 2026. The linked Zoom registration pages use Berlin local time, so those three sessions start at 14:00 UTC, not 13:00 UTC, and the table above uses the corrected time.

Prizes

The rules put the total approximate retail value (ARV, the rules’ term for the stated value of each prize) at up to USD 1,000,000, and every prize is cash. There are 20 prizes: a winner and a runner-up for each of the three tracks in each of the two divisions, six special awards and two Judge’s Choice awards.

Each entry can win only one prize. If your project is in line for more than one, the FAQ says you receive the one with the highest value.

Best New Gaming Experience
USD 100,000
1 winner; New Experience division, Gaming track
Best New Entertainment Experience
USD 100,000
1 winner; New Experience division, Entertainment track
Best Adapted / Significantly Updated Gaming Experience
USD 100,000
1 winner; Adapted division, Gaming track
Best Adapted / Significantly Updated Entertainment Experience
USD 100,000
1 winner; Adapted division, Entertainment track
Best New Productivity Experience
USD 70,000
1 winner; New Experience division, Productivity track
Best Adapted / Significantly Updated Productivity Experience
USD 70,000
1 winner; Adapted division, Productivity track
Runner-up, Best New Gaming Experience
USD 50,000
1 winner
Runner-up, Best New Entertainment Experience
USD 50,000
1 winner
Runner-up, Best Adapted / Significantly Updated Gaming Experience
USD 50,000
1 winner
Runner-up, Best Adapted / Significantly Updated Entertainment Experience
USD 50,000
1 winner
Runner-up, Best New Productivity Experience
USD 35,000
1 winner
Runner-up, Best Adapted / Significantly Updated Productivity Experience
USD 35,000
1 winner
Special Award: Best Social & Multiplayer Experience
USD 25,000
1 winner; shared presence such as co-watching, cooperative play, social spaces or asymmetric multiplayer
Special Award: Best Agentic Interaction
USD 25,000
1 winner; AI as a core part of the experience, such as spatial agents, voice-first AI, procedural content or context-aware help
Special Award: Best Reason to Come Back
USD 25,000
1 winner; progression and reward design that brings users back, built for longevity
Special Award: Best First Five Minutes
USD 25,000
1 winner; an opening that teaches controller-free interaction without a wall of text
Special Award: Best Accessibility Forward Experience
USD 25,000
1 winner; for example voice alternatives to hand interactions, eyes-only navigation or high-contrast modes
Special Award: Boldest Original Concept
USD 25,000
1 winner; an idea that depends on presence, spatial depth, real-world scale, or eyes and hands
Judge’s Choice
USD 20,000 (2 winners)
Standout entries that do not fit a single track or category; the USD 1,000,000 total only adds up if each of the two winners receives USD 20,000

By track, Entertainment and Gaming each carry USD 300,000 and Productivity carries USD 210,000 across the two divisions. The six special awards add USD 150,000 and Judge’s Choice adds USD 40,000, which brings the total to exactly USD 1,000,000.

The special awards are open to both divisions and all three tracks, so a small Productivity app can still compete for Best First Five Minutes or Best Accessibility Forward Experience. Read the full descriptions on the official Special Awards page before you decide what to emphasise.

Prize money goes to one person per entry, and US tax may be withheld before it reaches you. The ownership, prize payment and tax section below explains the forms and what to check.

Who can enter, and from which countries

As of the start of the entry period, every entrant (each solo entrant, and every member of a team or organisation) must be at least 18 and have reached the age of majority where they live. Entrants cannot be residents of, or organisations based in, Brazil, Quebec (Canada) or any area under comprehensive international sanctions, such as Crimea, Russia, Cuba, Iran, North Korea and Syria, or any country or person designated by OFAC (the US Treasury’s Office of Foreign Assets Control), including countries with banking or wire transfer restrictions.

By the time you submit, you need an active Meta account with Developer Access enabled, and the Representative or person submitting must be a member of the Meta VR Start program. Meta VR Start is Meta’s developer program, formerly called Meta Horizon Start, which offers members community mentorship, software credits and go-to-market guidance. The FAQ confirms that joining Start or enabling Developer Access after 24 September 2026 is fine, as long as it happens before you submit. Meta’s separate Start Program Terms also ask members for a valid email, the age of majority and a registered developer Organization in good standing; the competition pages do not explain how a solo builder meets that last point, so read the terms carefully when you apply.

The contest is not limited to students or professionals. Companies, nonprofits, LLCs and partnerships can enter, but politically affiliated organisations cannot. Government and political officials are excluded, as are employees, officers and agents of Meta and of anyone involved in running the contest, their affiliates and agencies, their family and household members, and anyone with a conflict of interest. Apps that received or are receiving direct Meta funding, such as request for proposals (RFP) funding, are ineligible. Developers who have a Meta Launch or Partner Manager can enter only if the submitted app is not in development with financial support from Meta and significant updates were made to it during the competition. Being a tax resident of an excluded country does not by itself rule you out if you live and bank in an eligible country and use that address on all your documents, though proof of legal status may be requested.

Country check: Adults in most countries can enter, as individuals, teams or organisations. Section 2(b) of the Official Rules excludes residents of, or organisations domiciled in, Brazil, Quebec, or any area subject to comprehensive international sanctions such as Crimea, Russia, Cuba, Iran, North Korea and Syria, plus any other country or person designated by the US Treasury’s Office of Foreign Assets Control (OFAC), including countries with banking or wire transfer restrictions. Residents of every other country enter on the same terms: be 18 or older and an adult where you live, have a Meta account with Developer Access, and make sure the person submitting is a Meta VR Start member before submitting. The other exclusions in the eligibility section, such as Meta employees and apps with Meta funding, still apply. Winners outside the US receive IRS Form 1042-S and may have US tax withheld, so check with a tax adviser before you count on the full amount.

Teams and solo entries

You can enter alone, as a Team (two or more eligible people who have not formed a legal entity) or as an Organization (a legally existing company or other entity that is not politically affiliated). There is no maximum team size, but every single member must meet the eligibility rules on their own.

Each Team or Organization appoints one Representative. That person submits the entry, receives all communication from Meta and receives any prize, then splits the money with teammates without Meta’s involvement. Our advice: agree the split in writing before you start, because the rules leave it entirely to you.

Each person gets one Entry. You can submit either one solo Entry or one Entry as a Team Representative, never both. You can still be a non-Representative member of any number of other teams, because that does not count as submitting an Entry. Each Team submits only one project, and the form asks for the name, email and role of every member.

Looking for teammates? The 29 September kickoff session included live matchmaking, and the organiser’s weekly updates point Start members to ways of finding people to build with.

How to enter Meta VR Start Developer Competition, step by step

Here is the full path from no account to a submitted entry, in the order the official pages describe it. Do steps 1 and 2 first, because Start membership can take more than a day to show up and nothing else matters without it.

Join the Meta VR Start programApply on the Meta VR Start program page; the overview estimates the application takes about five minutes. Meta VR Start is the new name for Meta Horizon Start, so it is the same program. Remember that the person who submits the entry must be a member by submission time.
Confirm your membership and turn on Developer AccessLog in to the Meta Developer Forum and look for the Start Member or Start Partner flair (a small badge) next to your name. If you applied more than 24 hours ago, qualify and still see no flair, file a ticket with Meta developer support. Also make sure your Meta account has Developer Access enabled, since the rules require it by the time you submit.
Register on DevpostOpen the competition page, click Join Hackathon, and log in or sign up for a free Devpost account. This puts you on the participant list and gets you the organiser’s updates.
Choose your track and divisionPick Entertainment, Gaming or Productivity, then pick New Experience or Adapted / Significantly Updated Experience. If any code, prototype or published version existed before 24 September 2026, you belong in Adapted. If you are adapting, keep a changelog from day one, as the organiser advises, because the form asks what you added during the window. You can change both choices until the deadline.
Learn the toolsWork through the Getting Started list on the competition overview. The overview estimates about 30 minutes to explore last year’s winning submissions and sample use cases, and about 30 minutes for a quickstart tutorial for your engine (Unity VR 101 and 102, Unreal UE5, Android or the Immersive Web SDK). It also points to Getting Started with Hands & Eyes. An engine is the software you build the app in, such as Unity or Unreal, and an SDK (software development kit) is a package of ready-made code and tools for one platform. The Resources page holds the deeper technical documentation. Join the weekly webinars and office hours as well. To attend, you must be a Start member logged in to the Meta Developer Forum.
Build a hands-first VR appBuild an app for Meta VR devices that someone can complete end to end without pairing a controller, that is playable on Meta Quest 3 and 3S, that uses only publicly released or Start-released Meta tools, and that is in English or has English subtitles. Aim for at least 60 frames per second (fps, how many times the picture redraws each second) on Quest 3 and 3S, because judges score performance under Technical Implementation.
Put a testable build in front of the judgesFor Unity, Unreal, Godot, Native/Android or another engine, upload your APK (the Android app file a Quest installs) to the Meta VR Developer Dashboard under a new release channel named exactly Competition. A release channel is a private distribution track for your app. Then create an Invite URL, a link that lets judges install and test that build. A raw APK file on its own is not accepted. For an Immersive Web SDK project (WebXR, the standard that runs VR inside a web browser), deploy it to GitHub Pages, Vercel, Digital Ocean, AWS, Azure or a similar host and get a public link judges can open.
Record the demo videoRecord a video under three minutes showing your project running on a Meta Quest device, the XR Simulator or an equivalent emulator. XR (extended reality) is the umbrella term for VR and MR, and the XR Simulator is a tool that runs VR apps on a computer without a headset. Upload the video to YouTube or Vimeo and make it publicly visible. Show real gameplay and lead with your best material, because judges do not have to watch past three minutes.
Fill in the Devpost form and submitOn the Enter a Submission page, complete every required field: name, a 140-character tagline, track, division, a description of your inspiration, how you built it and your future plans (500 words or less is suggested), a target launch date if the app is not published, a feature summary if you are in Adapted, each team member’s name, email and role, the Invite URL or web link, and the video link. Submit before 12:00 PM PT on Wednesday 18 November 2026, which is 20:00 UTC; the dates table shows that moment in your local time.
Freeze everything and stay availableAfter the deadline, do not change the submission or the app; projects modified after the deadline may be disqualified. Keep the project available and free of charge until the winner announcement, which the Devpost schedule lists for 11 December 2026 at 10:00 AM PST (18:00 UTC) and the rules describe as on or around 11 December 2026. Keep your own copies of everything you submitted, because the rules say screenshots are not proof of entry.

What you must submit

Your entry has two parts: a playable project the judges can install or open, and a set of materials on the Devpost form. Here is everything the rules and the overview ask for.

A playable build: for Unity, Unreal, Godot, Native/Android or another engine, an APK uploaded to the Meta VR Developer Dashboard under a new release channel named “Competition”, plus the Invite URL so judges can test it
For Immersive Web SDK (WebXR) projects: a working public link judges can open, hosted on GitHub Pages or any host such as Vercel, Digital Ocean, AWS or Azure
A public demo video under three minutes on YouTube or Vimeo, showing the project on a Meta Quest device, the XR Simulator or an equivalent emulator
Submission name and a 140-character tagline
Track (Entertainment, Gaming or Productivity) and division (New Experience, or Adapted / Significantly Updated Experience)
A text description of your inspiration, how you built it and your future plans (500 words or less suggested)
Your target launch date, if the app is not already published on the Meta VR Store
For Adapted entries: a summary of one or two paragraphs on the new features added during the competition window, ideally backed by screenshots, changelogs and demo videos
Optional: how your hand interactions are implemented and what excites you about the future of VR
The name, email and role of every team member, if you are a team
Everything in English, or with English subtitles or translations, including the video, description and testing instructions

A code repository is not required, and the rules do not ask you to open source anything. Publishing to the Meta store is not required either; what matters is a working release channel Invite URL, or a URL for a web build.

Testing access must be good enough for Meta and the judges to view, use and test the project on Meta Quest 3 or 3S. Content must follow the Meta VR Developer Content Guidelines for a 10+, 13+ or 18+ rating and all Meta developer policies, and the project must stay available and free of charge until the winner announcement.

One FAQ answer is worth knowing in advance. If you cannot generate an Invite URL, or your accessible build is past what the official FAQ calls a 90-day limit, Meta suggests creating a new project with a different name and a private Alpha channel, or as a fallback submitting your public Meta Quest Store link, with no updates during judging. The official pages do not explain the 90-day limit further, so if you are reusing an older project in the Adapted division, generate and test your Invite URL early.

How entries are judged

Judging runs in two stages. Stage One is a pass or fail viability check. Entries that pass move to Stage Two, where Meta and third-party judges score them on four criteria worth 25% each, testing on Meta Quest 3 or Quest 3S.

Ties are broken by a judges’ vote. The rules say AI tools may help with judging, but human judges make the final decisions, possibly over one or more rounds. The full wording is on the official Judging page.

Stage One: viabilityPass or fail
The entry must reasonably fit the theme and reasonably apply the required tools and features. The FAQ adds that it must match the track and division you selected. Fail this check and the scored criteria never come into play.
Innovation & Creativity25%
Originality, creative ambition and relevance to your chosen track. High scores go to apps that use what Meta devices do uniquely, such as spatial depth, hands-first design, gaze, passthrough, scene understanding and persistent anchors (virtual objects that stay pinned to a spot in your room), to drive repeat use.
Experience Design25%
Design, mechanics and the user journey for your intended audience, with emphasis on seated, hands-first or context-specific use. Judges look for intuitive navigation, clear onboarding and a habit-forming purpose. Passthrough must be purposeful, meaning the real room should change the experience, and the design should account for field of view (FoV, how much a user can see at once) across Meta VR devices.
Technical Implementation25%
Technical skill, reliability and use of the platform tools behind hands-first experiences: gaze interactions (Unity or Unreal Interaction SDK v207 or later), hand tracking, passthrough, spatial anchoring and FoV-aware design. High-scoring entries are performant on Meta Quest hardware at a minimum of 60 fps and bug-free. Passthrough entries are judged on correct scene understanding with MRUK (Meta’s Mixed Reality Utility Kit) and anchoring to room geometry that holds up in rooms you never tested.
Polish & Presentation25%
User interface (UI) and user experience (UX), art direction, sound design, visual cohesion and the quality of your text, images and video. The video should show real gameplay that honestly represents the experience and should not lean on AI-generated video.

Tools, APIs and what they cost

Besides a free Devpost account to register and submit, the required accounts are an active Meta account with Developer Access and, for the person submitting, Meta VR Start membership. Neither the Start program page nor the Start Program Terms mention a membership fee, though neither says outright that membership is free. The Start terms say participants bear their own hardware, software, internet, transport and lodging costs beyond the benefits Meta specifies. The Start program page lists software credits among member resources, but no credits specific to this contest are stated, and the rules do not state any engine or hosting costs.

You choose the build path, and the choice does not affect prize eligibility: Unity, Unreal, Godot, Native/Android, the Immersive Web SDK or another engine. An SDK (software development kit) is a package of ready-made code and tools for one platform. The overview suggests four starting points: Unity with Meta’s XR SDKs (the All-in-One package), Unreal Engine 5.8 with the Oculus Integration SDK v207 or later, Android apps built with React Native/Expo or Jetpack Compose using the Meta VR Plugin for Android Studio, and the Immersive Web SDK, which needs Node.js v20.19.0 or higher and starts with the command npm create @iwsdk@latest. Node.js is a free program that runs JavaScript on your computer, and npm is the package tool that comes with it. Non-Meta options such as Unity XR Interaction Toolkit with XR Hands or other OpenXR solutions are allowed, but Meta recommends its own Interaction SDK and judges score technical use of hands-first platform features. OpenXR is the open industry standard for VR and AR (augmented reality) apps. Any 3D tool such as Blender or Maya is fine if properly licensed. Only publicly released or Start-released Meta tools are allowed; unreleased Meta SDKs or features are not.

On hardware, you do not need to own a Meta Quest, and your video can come from the XR Simulator or an emulator, but the build must be playable on Quest 3 and 3S, and the Start program does not provide devkits or hardware. Backward compatibility with Quest 2 or Quest Pro is allowed but not judged, and your app must not require third-party, non-Meta devices such as Bluetooth accessories. For AI-assisted building, the official resources list the Meta VR CLI, Meta XR Operator, Unity CLI and the meta-quest agentic-tools repository on GitHub; a CLI (command-line interface) is a tool you run by typing commands.

Rules that trip people up

These are the rules most likely to catch you out. Each one comes straight from the Official Rules or the FAQ, and each can sink an otherwise strong entry.

Start membership comes firstThe Representative or person submitting must be a Meta VR Start member by the time of submission, and the Start Program Terms also ask for a registered developer Organization in good standing. Membership flair can take more than 24 hours to appear, so apply now rather than in the final week.
Hands only, from start to finishHand interaction is a hard requirement, not a bonus. If any part of the experience needs a controller to finish, including menus, settings or the tutorial, the entry fails the core test the overview sets: can someone complete the whole thing without ever pairing a controller.
Choosing the wrong divisionNew Experience means nothing existed before 24 September 2026. Prototypes, projects from earlier Start Accelerators such as the Social VR or Hands-First VR Accelerator, games ported from other platforms and published apps all go in Adapted. Adapted entries need a genuinely significant new feature, mode or platform integration; bug fixes, minor UI tweaks, cosmetic changes and performance work without new user-facing features do not count. Past winners can win again in Adapted with a qualifying update.
A raw APK is not an entryUpload to a new release channel named exactly Competition and submit the Invite URL. The FAQ says APKs alone will not be considered and recommends against reusing last year’s competition channel.
Any change after the deadlineFrom 12:00 PM PT on 18 November (20:00 UTC) you must not update the app or the submission, and projects modified after the deadline may be disqualified. The app must also stay available and free of charge until the winner announcement.
Brands, people and borrowed assetsThe project cannot show identifiable people other than the entrants, or commercial advertising, logos, brand names, recognisable branded products or commercial artwork. Every third-party tool, code library and asset must be properly licensed, and thin wrappers around services like YouTube or ChatGPT are highly discouraged.
Meta funding, mentorship and one entry per personApps with direct Meta funding (such as RFP funding) and technology built with Meta financial or preferential support are excluded. Projects that had one-to-one Start mentorship before 24 September stay eligible only if that mentorship is not used during the window. You get one Entry, solo or as a Team Representative but never both, and entries made by automated means or by someone else on your behalf (other than a Team Representative) are void.

Ownership, prize payment and tax

You keep ownership: the rules say all entries and projects remain the intellectual property of the individuals or organisations that built them. By entering, though, you grant Meta and the other released parties an irrevocable, transferable, sublicensable right to use, edit, modify, copy, reproduce and distribute your entry, in whole or in part, worldwide and in perpetuity, in any medium and language, for judging, running the contest and any marketing or promotion, without further payment. You also license your and your app’s names, trademarks and logos and your Meta usernames and profiles, give a publicity release over your name, voice, face and likeness, and waive moral rights claims and injunctive relief against Meta’s use. The FAQ calls this a limited license, but the Official Rules wording is broader, and the rules say Meta resolves any inconsistency. No open source licence or public repository is required, but your project must be original, public domain or Meta-provided, every third-party asset must be properly licensed, and Meta may ask for written proof.

Prizes go to the solo entrant, or to the Representative of a winning team or organisation, who is responsible for splitting the money. Payment happens only after the winner returns the Winner Documents, which are forms confirming you followed the rules and may include a government-issued ID or ID number, plus any other required forms. A valid bank account may be required for prizes of USD 1,000 or more, and winners may need to provide a mailing address, bank details or an account with an electronic payment provider chosen by Meta. Winners who do not respond or cannot be reached may be disqualified and an alternate chosen, and Meta need not pursue more than two alternate winners. The rules do not say how long after the announcement prizes are paid.

All taxes are the winner’s responsibility, and Meta may withhold amounts required under US federal, state, local or foreign tax law. US residents who win USD 2,000 or more receive IRS Form 1099-MISC. Winners outside the US receive IRS Form 1042-S (the US tax form that reports payments made to non-US persons) for the total ARV, and prizes paid outside the US may be subject to US federal income tax withholding, so the amount that reaches you may be less than the stated prize. The rules do not mention tax treaty rates or Form W-8BEN by name and say nothing about how your home country taxes the prize, so check with a tax adviser where you live before you plan around the full amount.

Project ideas that fit the brief

These four ideas are ours, not Meta’s. Each one is built around the hands-first rule and the seated, short-session guidelines, and each points at a track, with some also aiming at a special award. Treat them as starting points and make the concept your own, because originality carries a quarter of the score.

Gaming: a daily puzzle box at arm’s lengthOur idea: a small mechanical puzzle box floats in front of you, and you open it by twisting dials, sliding panels and pinching hidden catches with your bare hands. Each box takes a few minutes, which fits the one bus stop test, and everything sits within reach of a seat. A fresh box every day gives players a reason to come back, and a first box that teaches each gesture with a ghost hand instead of text speaks directly to the Best First Five Minutes award.
Productivity: a spatial reconciliation deskOur idea, drawn from the finance work we know: a seated, multi-panel workspace that shows a bank statement on one panel and a cash book on another. You pinch a line on each side to match them, matched pairs snap away, and anything left over drifts into a review tray you sort with a flick. Use invented sample data only, keep a session short enough for a commute, and make the hand gestures the point rather than floating a flat spreadsheet in space.
Entertainment: conduct your own light showOur idea: a lean-back music visualiser where the height, spread and speed of your hands shape the light and spatial audio around you, like conducting an orchestra from your chair. In passthrough mode, the visuals could bounce off your real walls and furniture using scene understanding, which is the kind of purposeful passthrough the Experience Design criterion asks for. Use original or properly licensed music, since the rules require every asset to be licensed.
Entertainment or Gaming: a story that listens and looksOur idea: an interactive story where an AI narrator reacts to where you look (gaze, as the judging criteria call it) and what you say, and bends the plot around you. Every hand interaction also gets a voice or gaze alternative, which aims at Best Accessibility Forward Experience as well as Best Agentic Interaction. Check that every gaze feature works on Quest 3 and 3S, the devices the judges use. Keep the AI at the core of the design rather than wrapping a chatbot in a 3D room, because thin wrappers are highly discouraged, and remember each entry can win only one prize.

Tips to give your entry the best chance

  • Apply to Meta VR Start and turn on Developer Access before you write any code. Flair can take more than 24 hours to show, and you cannot fix a membership problem in the final hours before the deadline.
  • Run a controller-free test every week: put the controllers in another room and ask someone who has never seen your app to finish it with hands alone while you stay silent.
  • Build seated by default. Play your whole app sitting in a chair within about two feet of reach, because judges weigh seated, hands-first design under Experience Design.
  • Watch performance from the first week, not the last. Aim for at least 60 fps on Quest 3 and 3S hardware, since judges score performance and bugs under Technical Implementation.
  • Set up the Competition release channel and Invite URL early, then test the link from a different Meta account so you know a judge can actually install the build.
  • Plan the video before you finish the app: under three minutes, real footage from a headset or the XR Simulator, your best moment first, and no AI-generated video standing in for gameplay.
  • If you are in the Adapted division, keep a dated changelog with screenshots of each new feature, since the form asks for a summary of what you added during the window.
  • Submit a complete first version days before the deadline. You can keep editing the form, track, division and build until 12:00 PM PT on 18 November (20:00 UTC), so an early submission costs you nothing.

Please note: we update this page from time to time, but hackathon dates, prizes and rules can change quickly, and there can be a gap between a change and our update. Check the official rules before you enter or submit. This guide helps you plan; it is not legal or tax advice, and ReconScribe is not responsible for decisions made on it.

Professional help
Building an AI tool or automation? Let us help you scope it
ReconScribe helps finance teams and builders scope and build AI tools and automations. We cannot promise any contest result, but we can help you plan and ship something that works.
Turn a rough idea into a clear scope, feature list and build plan you can finish on time
Build AI assistants and automations around real finance workflows such as reconciliations and reporting
Review your prototype for gaps and weak spots before a deadline
No spam. We use your details only to reply to this request.

Meta VR Start Developer Competition frequently asked questions

Which countries can enter the Meta VR Start Developer Competition?

Most countries can. The Official Rules exclude residents of, or organisations based in, Brazil, Quebec (Canada) and areas under comprehensive international sanctions such as Crimea, Russia, Cuba, Iran, North Korea and Syria, plus any country or person designated by OFAC. Everyone else must be 18 or older, have a Meta account with Developer Access, and the person submitting must be a Meta VR Start member before submitting.

What time is the Meta VR Start Developer Competition deadline?

The deadline is Wednesday 18 November 2026 at 12:00 PM Pacific Time (PST, UTC-8), which is 20:00 UTC. Anywhere east of UTC+4, that is already Thursday 19 November in local time; at UTC+4 it is exactly midnight. The dates table on this page shows the exact moment in your time zone; aim to submit a few hours early to leave a safety margin.

Do I need a Meta Quest headset to take part?

No. The FAQ says you do not need to own a Meta Quest headset, and your demo video can be recorded in the XR Simulator or an emulator. The build must still be playable on Quest 3 and 3S, judges review apps on a Meta Quest 3 or Quest 3S, and the Start program does not supply hardware.

Is Meta VR Start the same as Meta Horizon Start?

Yes. The FAQ says Meta VR Start is the updated name of the program formerly known as Meta Horizon Start. If you joined under the old name, check for the Start Member or Start Partner flair on the Meta Developer Forum to confirm your membership.

Does it cost anything to join Meta VR Start?

Neither the Start program page nor the Start Program Terms mention a fee, though neither says outright that membership is free. The terms say participants pay their own hardware, software, internet and travel costs beyond the benefits Meta specifies. Registering for the contest itself uses a free Devpost account.

How much prize money is there?

The total pool is up to USD 1,000,000 in cash across 20 prizes. Track winners get USD 100,000 in Gaming and Entertainment or USD 70,000 in Productivity, runners-up get USD 50,000 or USD 35,000, six special awards pay USD 25,000 each and two Judge’s Choice awards are listed at USD 20,000. Each entry can win only one prize.

Can I submit a game or app I already built?

Yes, in the Adapted / Significantly Updated Experience division, as long as you ship a meaningful new feature, mode or platform integration during the competition window that began on 24 September 2026. Bug fixes, minor UI tweaks, cosmetic changes and performance work without new user-facing features do not count. Games ported from other platforms also go in this division.

Can players use controllers in my app?

Controller support is optional, but the entire experience must be fully usable with hands from start to finish. The test Meta sets is whether someone can complete everything without ever pairing a controller.

Can I just upload my APK file?

No. Upload the APK to the Meta VR Developer Dashboard under a new release channel named Competition and submit the Invite URL; the FAQ says APKs alone will not be considered. Web builds made with the Immersive Web SDK submit a public link instead.

How long can the demo video be?

Under three minutes. It must show the project running on a Meta Quest device, the XR Simulator or an equivalent emulator, and it must be publicly visible on YouTube or Vimeo. Judges do not have to watch past three minutes, so put your best material first.

Is there a maximum team size?

No, there is no maximum team size. Every member must meet the eligibility rules, one Representative submits the entry and receives any prize, and each person can submit only one Entry, either solo or as a Team Representative.

Do I keep the rights to my project?

Yes, entries remain the intellectual property of the people or organisations who built them. By entering, though, you give Meta a broad, irrevocable, worldwide licence to use and modify your entry for judging, running the contest and marketing. No open source licence or public code repository is required.

More open hackathons

See every open hackathon, with filters and deadlines in your local time

Related reading

Sources