What File Access Unlocks¶
From Fiction to Reality¶
Remember your Challenge 1 prototype? It looked real, but you likely hit some friction points. The data may have been hardcoded text you typed into the prompt. Your team couldn't collaborate together on it. It was a great prototype, but it wasn't connected to the real world.
Now that you're working in a real development environment, here's what becomes possible that wasn't before.
Live Data¶
There are free services on the internet that provide real, up-to-the-minute information: active park alerts from the National Park Service, weather forecasts from the National Weather Service, and river streamflow readings from USGS stream gauges. Your project can connect to these services and pull in real data automatically.
That means your Safety Brief can show actual NPS alerts for Yellowstone, a live weather forecast, and real-time streamflow at key river crossings, not data you made up in a prompt. You'll connect to these data sources in Challenge 2.
Multiple Pages¶
In chat, you built one thing at a time. In a real project, you can have a home page, a forecast page, a gear checklist page, all with navigation between them. A real app with real pages, not a single output.
User Accounts and Stored Data¶
Want people to be able to save their favorite routes? Track which gear they've checked off? Log in and see personalized content? When you're working with real files, you can build features that remember things about the people using your app.
Work That Persists¶
Come back tomorrow and pick up where you left off. Your AI coding assistant can read what's already there and continue building. No need to re-explain what you've already done.
Team Collaboration¶
Your whole team can contribute at the same time, like editing a shared Google Doc or an Office 365 document with your colleagues. Split the work: each person takes a different section and builds it in parallel. Version history keeps track of who changed what and brings it all together.
Imagine the Upgrade
Mob Session | ~3 minutes total | Gather around one screen. One person opens a scratch notepad (not the AI coding assistant).
Think back to your Expedition Safety Brief from Challenge 1. As a team, come up with two things you wish your safety brief could do that weren't possible in chat. Write them as user stories using the format you learned in Lesson 1.
For example:
As a backcountry hiker planning a route in Yellowstone,
I want the safety brief to show **active NPS alerts** for the park,
So that I'm making decisions based on real conditions, not hardcoded mock data.
Write your two stories in the notepad. Hold onto them. You'll use these as your first real tasks in Challenge 2.
Discuss: Which of the two would have the biggest impact on someone actually heading into the backcountry?
Key Insight
Moving from chat to a real development environment is what turns a clever prototype into real software. Live data instead of made-up text. Multiple pages instead of one output. Persistent work you can build on over time. Team collaboration instead of one person prompting. The prompting skills you learned in Lesson 1 are the same; what changes is what becomes possible.