Your App Deserves an Audience¶
Beyond the Workshop¶
Right now, your app works. It shows real data from live sources. You've connected it to live data sources, added features your team is proud of, and your AI coding assistant knows the project inside and out thanks to the context file you set up in Lesson 3.
As you've been building, you've likely been checking the Web App preview to see how your app looks and behaves, using that to decide what to work on next. That preview is your workshop: a place to build, experiment, and iterate. Think of it like working on a painting in your studio. You can see it taking shape, but it might have rough edges, half-finished sections, or things you'd want to fix before showing it to anyone outside your team.
Workspace vs. Production¶
Back in Lesson 2, we mentioned that every time you run Save & Sync, if your application passes quality checks, it gets shipped to production. Let's dig into what that means.
When you're looking at the Web App preview in your workspace, you might still have issues: features that are half-finished, things that don't look right yet. That's fine. That's the workshop. But when you run Save & Sync, you're making a deliberate choice: "This is ready to be seen." If the quality checks pass, your application moves from the workshop to the gallery: a live URL, a web address anyone can visit from any device, anywhere. If a friend needed it tomorrow, they'd have a functioning, quality-checked app to use.
Think of it like...
An artist's studio and a gallery. The studio is where you experiment, iterate, and live with rough edges. The gallery is where the finished piece goes on display. You, the artist, decide when it's ready to be seen by others. That's what Save & Sync does: it's your decision to move the work from the studio to the gallery.
What's Been Happening Behind the Scenes¶
Every time you ran Save & Sync, your AI assistant pushed your changes to GitLab. Each push triggers a pipeline: an automated process that runs a series of quality gates against your application. Think of it like a quality check at a factory. Your code goes in one side, gets inspected, and if everything looks good, comes out the other side as your live application.
These quality gates include security scans, code formatting checks, and tests. If something doesn't pass, the pipeline stops and your application stays as it was. Your AI assistant has visibility into these quality gates and can help you investigate what failed and fix it.
You don't need to understand the mechanics. The point is: you've been doing the right thing all along. Every Save & Sync is a deliberate choice to ship, and the quality gates make sure only working code reaches your users.
Who Would Use This?
Team Discussion | ~4 minutes total
Think about your app as if it were live right now, accessible to anyone with a link.
Discuss:
- Who would benefit from using your app?
- What behavior change are you hoping for? If someone used your app for its intended purpose, what would they do differently, and what impact might that have?
- What assumptions did your team make while building this? What unknowns would you want to test by putting it in front of real users?
Hold onto those answers. They'll shape your final sprint in Challenge 4.
Key Insight
Your workspace is a workshop. Production is the gallery. Deployment is the act of moving your work from one to the other, and your Save & Sync habit has already been preparing you for it. Every time you run Save & Sync, your changes go through an automated pipeline that checks your code before it goes live. You've been using this system all along without needing to think about it.