Anyone Can Build a VR World Now - Starting from Zero

I'm dyslexic and low-vision, and I build immersive worlds in Unity. The secret isn't that I learned to code — it's that I stopped needing to. Here's the step-by-step, no experience required.

Anyone can build! No Previous Knowledge

by Michelle Deborah Weishat-Dane

The thing that kept most people out of building XR was never the headset. It was the wall of prerequisites: learn Unity, learn C#, learn 3D. For me there was an extra wall — I'm dyslexic and low-vision, so even the tutorials were locked. For five years, worlds were what I asked other people to build.

Please upload the image you'd like me to work with, and tell me what you want done with it (for example: describe it, generate a caption, create alt text, suggest edits, create a social post, or analyze content). Include any style, tone, length, or audience requirements.

Here is what I learned, and it's the whole point of this piece: you can start with **no previous knowledge at all.** Not "a little." None. You bring the dream; the AI teaches you the tool as you go — including how to download and set the software up in the first place. Let me show you exactly how, in steps.

**1. Get the tool that teaches.** Download the **Claude Cowork app** onto your computer. Running there — not just in a browser tab — it can see your screen and walk you through other software click by click. That's the piece that changes everything: you never sit stuck in front of a menu you don't understand, because you can ask about the exact thing on your screen and get an answer about *that*, right then.

**2. Bring your dream, not your skills.** Don't start by learning Unity. Start by describing what you want to exist — the space, the feeling, what a visitor does inside it. Then ask the simplest possible question: *"How do I build this?"* You are allowed to know nothing. The vision is your job; the how is the AI's. This is the reversal that opens the door — you lead with what you can already do (imagine it) instead of what you can't (code it).

**3. Let it set up Unity *with* you — even if you've never opened it.** If you don't already have Unity, it walks you through the whole setup: installing Unity Hub, choosing a version (I'm on Unity 6 LTS), picking the right template (a 3D / URP project handles most headset work), and creating the project. One rule it will hand you that saves real heartbreak: **never put a Unity project inside a synced cloud folder like OneDrive.** Cloud sync grabs Unity's `Library` folder mid-build and corrupts it — I lost a whole project to a zero-byte error that way. You don't have to understand *why*. You just have to be told, and it tells you.

**4. Build in small, testable pieces — and let it write the code.** Describe one behavior; let the AI write the C# for it; try that one thing before adding the next. Example: to wrap art onto a sphere for a world — drop the image in, make a sphere, let Unity auto-create the material, assign the texture, make it a reusable **prefab**, export it as a **`.unitypackage`**. One gotcha worth knowing up front, because it's invisible until you're in the headset: **scripts in a folder named `Editor` get stripped out of the finished build.** Runtime code goes in a normal folder like `Scripts/`. Just ask the AI, for each script: does this run in the world, or is it an editor tool? Then file it where it says.

**5. Edit safely — disable before you delete.** When you want to remove something, have the AI trace what it's connected to first. I once went to delete a moon from a night sky; it turned out other things depended on the setup, and deleting blind would have broken the whole scene. Disabling an object is reversible; deleting it often isn't. Let the AI check the wiring before you cut.

**6. Test in your own world first.** Before anything goes to anyone else, walk through it in-headset in a space you control. The AI can reason about your scene, but it isn't wearing the headset — presence, scale, and comfort are things only a human in the room can feel. The loop is: AI builds → you test in-world → you say what felt wrong → it fixes. Repeat until it's right.

**7. Publish deliberately.** Set your build target to your actual platform (headsets differ — I publish for both PC and Quest), publish, and check the *live* build, not the editor preview. Then hand it off in a form the recipient can open.

Here is the part I most want you to hear. I came to this with a genuine handicap — I could not type the code or reliably read the screen — and it *still* worked, because the AI became my hands and my eyes. Which means the bar for everyone else is now on the floor. You don't need my fifty years around computers. You don't need one line of C#. You need something you wish existed and the nerve to ask how to make it. That is the whole barrier now.

So bring your dream. Ask the first question. It will teach you the rest.