Skip to content
Page 3 of 7

Going Live

Deployment Is One Prompt Away

Deploying your application is not a big, technical ordeal. Your workspace comes with deployment tools already set up. The pipeline that checks your code and makes it live is pre-configured and ready to go.

You don't need to set up servers. You don't need to configure hosting. You don't need to understand networking or infrastructure. You just need to tell your AI coding assistant what you want.

Think of it like...

The difference between printing a document at home versus hitting "Print" at a hotel business center. At home, you'd need to set up the printer, install drivers, connect to Wi-Fi, load paper. At a hotel business center, you just hit print. Someone already did the setup for you. Your deployment pipeline is the hotel business center.

What Happens When You Deploy

When you tell your AI coding assistant to deploy, here's what happens behind the scenes (you don't need to do any of this; your tools handle it):

  1. Your AI assistant makes sure all your work is saved and synced
  2. It sends your work through the deployment pipeline
  3. The pipeline checks your code for problems and packages your application
  4. Your application gets placed on a server, a computer that's always on and always connected to the internet
  5. A live URL is generated: a web address that anyone can visit
  6. Anyone with that URL can now open your app from any browser, on any device

The whole process takes just a few minutes. And you trigger it with a prompt.

If something goes wrong during deployment, don't worry. Tell your AI assistant: "The deployment didn't work. Can you investigate why and fix it?" Your AI assistant can see what the pipeline flagged, make the necessary changes, and try again.

Pre-Flight Check

Mob Session | ~5 minutes total | Gather around the same computer. One person drives, everyone navigates.

Rotate the driver. Pick someone who hasn't been at the keyboard recently.

Before you deploy in Challenge 4, let's make sure everything is ready. Think of this as the pre-flight checklist before takeoff.

Step 1: Is your app working?

Open your app in a browser (the way you've been viewing it during your challenges). Click around. Check that your app's key features are working as expected. Does everything look right?

If something is broken, note it. You'll have time to fix it in Challenge 4.

Step 2: Is everything saved?

Tell your AI coding assistant:

Is all my work saved and synced? Check if there are any unsaved changes.

If there are unsaved changes, run Save & Sync before you go any further.

Step 3: Is your context file up to date?

Ask:

Read my project context file and tell me if it accurately describes what the project does right now.

If it's outdated (missing features you added in Challenge 3, for example), ask your AI assistant to update it. This ensures anyone (or any AI) picking up your project later will understand what you've built.

After the check: Give your team a thumbs up or note what needs fixing. You're ready for Challenge 4.

Challenge 4 Game Plan

Team Discussion | ~5 minutes total

Your final sprint is coming up. Here's how most teams use that time:

  1. Deploy first (~10 minutes): get your app live at a URL
  2. Polish and fix (~25 minutes): fix any issues from the pre-flight check, improve the experience
  3. Final features (remaining time): add one more thing that makes your Field Guide special
  4. Final Save & Sync (~5 minutes): make sure your deployed version reflects your latest work

Discuss:

  • What's the first thing you'll do in Challenge 4? Deploy? Fix something? Add a feature?
  • If you could add one more feature before the demo, what would it be?
  • Who's driving first?

Key Insight

Deployment is not a technical challenge. It's a single prompt. Your workspace has everything set up, including the pipeline that checks your code before it goes live. Your Save & Sync habit means your work is already backed up and ready to go. In Challenge 4, you'll tell your AI coding assistant to deploy, it will send your changes through the pipeline, and within minutes your app will be live at a real URL that anyone can visit. If something doesn't pass the pipeline's checks, your AI assistant can investigate and fix it. That's the moment your workshop project becomes a real product.