CMU 15-114: Effective Coding with AI
SPEC.md + REVIEW.md + README + prompt log on GitHub, short video, Google form submission, portfolio entryGoal: Build a mobile app capable of running on an actual phone or simulator. You'll use React Native with Expo, a framework that lets you build real iOS and Android apps using JavaScript. To do this assignment successfully in a reasonable amount of time, you must leverage AI thoughtfully. By the end of this assignment, you'll be able to show off a real app that you created.
Why This Matters: Mobile development has traditionally had a very steep learning curve, including specialized languages and complex build tools that differ between Android and iOS. After setting up your environment, using AI tools and React Native with Expo will allow you to build a working app on your phone in as little as an hour. This is still a challenging project, however, and you will be unlikely to succeed unless you practice attention to detail and use the strategies you have learned in class so far.
Examples of what you might build:
You're welcome to come up with your own idea! The key is that it should be something you'd actually want on your phone as more than just a webpage or webapp, and something you'd be excited to show other people. Start simple for this assignment! If you have a bigger idea, save it for your capstone project (since the capstone cannot be an extension of this assignment).
SPEC.md for HW7, so that part should feel familiar. What's new is the full cycle: you'll hand the spec to an agent, let it build the whole app, then open a second agent to review the result against your own spec and write up what it found. Since you're doing this on a framework you've never seen, your agentic review process matters a lot here, since you can't easily tell good code from bad.
SPEC.md you wrote before any code existed, and the REVIEW.md a second agent produced against it. Steps 3 through 5 walk through this.npm install, and then npx expo start. (More info on these commands below.)SPEC.md and REVIEW.md: At the repository root. The spec is yours, written before any code. The review is the second agent's output, kept as it was given to you.prompt_log.txt or prompt_log.md): Which AI tools you used, and the key prompts that shaped your work. Remember, share your actual prompts, verbatim, and not just summaries (AI generated or otherwise).For this assignment, we especially want to see prompts where you asked AI to explain React Native concepts—not just "build me a screen," but "what does useState do?" or "why do I need SafeAreaView?"| Grade | (Roughly) What We're Looking For |
|---|---|
| A (90-100) | App can be demoed and has at least 2 screens with navigation, meaningful user input, and data persistence. Looks intentional and polished. A specific SPEC.md committed before any code, and a REVIEW.md you clearly read and acted on. Clean README and prompt log that meet the assignment specifications and show learning (asking AI to explain, not just generate). Evidence of 3-4 hours of effort and some creativity in the concept. Video clearly demonstrates the app. |
| B (80-89) | App runs and has most core features working (screens, input, persistence). Functional but may look rough around the edges. Spec and review are present but thin, or the review's findings were left unaddressed without explanation. README and prompt log present but less detailed. Video might be a little unclear. |
| C (70-79) | App runs but may be missing one core feature (e.g., no persistence, or only one screen). Basic README, prompt log, and video. Spec or review missing. Limited evidence of the learning process. |
| Below C | App does not run, or submission is incomplete. |
Follow these steps in order, and read carefully. Each one builds on the last, and this sequence is designed to minimize the time you spend stuck. If any step takes significantly longer than the time listed, please ask on Ed or come to office hours!
Read this entire step before you start typing. Everything you need is written out below, and all of it was verified in November 2026. Expo released a new version in October, so several of the commands you'll find in older tutorials and blog posts no longer do what they say. Expo's own documentation is linked throughout if you want more detail, but parts of it are out of date and parts of it are aimed at production apps rather than a one-week assignment. Where this page and Expo's docs disagree, follow this page.
For iPhone:Install Expo Go from the App Store like any other app. You don't need a Mac and you don't need XCode. (XCode is only required if you'd rather use the iOS Simulator than a real phone. If that's your plan, start the App Store download right now, since it takes about an hour.)
For Android:Search for "Expo Go" in the Google Play Store and install it. Alternatively you can download a beta version of the Expo Go app if you wish to use the very latest version, but we don't recommend this since you'll probably have to unlock dev options on your phone.
For Everyone:You need Node.js on your computer, an AI-enabled code editor (you probably already have VS Code or Cursor), and a free Expo account.
You will be running commands in your computer's terminal. For Windows this is the Command Prompt, and for macs this will be the Terminal. We don't recommend trying to run these in VS Code. These are not Python commands!
node --version in your terminal. Expo now requires Node 22.13 or newer, and the current LTS is Node 26. If you already have Node 18 or 20 installed from an earlier assignment, you will need to upgrade for this one.npx create-expo-app@latest--template flag, even though Expo's "Create a Project" tutorial shows one and your AI will probably suggest one. Without the flag, the tool asks Expo which version the current Expo Go supports and builds your project to match. It then prints the template it used, naming the SDK, like default@sdk-58. Write down that number, because your README has to report it.cd your-project-name) and run npx expo login, using the same account you just signed into Expo Go with. If the two don't match, the QR code will scan and then nothing will happen.npx expo start. It will take a moment to load, and then it will show a QR code in your terminal. On a phone: make sure you're on the same wifi network as your computer, then scan the code. iPhone users scan it with the built-in Camera app, and Android users scan it from inside the Expo Go app. You should see a default welcome screen appear on your phone. On a simulator: press a for an Android emulator or i for the iOS simulator, and Expo will install Expo Go into it for you.eas go, and TestFlight. Ignore all of that, for the reasons in the red box at the top of this page.
npx expo start --tunnel. Tunnel mode routes through Expo's servers, so it reloads noticeably more slowly, but it gets through network setups that block the direct connection. Ask on Ed if you're stuck—this is a common setup hiccup.
claude plugin install expo@claude-plugins-official for Claude Code, codex plugin add expo@openai-curated for Codex, or npx skills add expo/skills for anything else.Before you start building, spend a few minutes getting oriented. The default project uses Expo Router, which means your screens live in a src/app/ folder and each file in it becomes a screen. Open src/app/index.tsx, which draws the first screen you saw, and ask AI some questions:
View different from a div?"useState hook."src/app/ become a screen, and what is _layout.tsx for?"Try making a small change to the app, like changing the text or a color, and watch it update on your phone in real time. (If it does not update immediately, you can go to your terminal and press 'r' to reload the app.)
AGENTS.md or .claude/settings.json that explain how AI tools should work with the project. Review any such files before Step 4, since your agent may follow them.
Before you write any code, write a detailed specification for your app in a file called SPEC.md. This should feel familiar from HW7, where your spec had to be clear enough for a classmate to build from. This is the most important step. As before, write this spec yourself and be thorough. This will help ensure that the app matches your vision and works well.
Keep your app idea simple: two screens, one or two key interactions, and one type of data to persist is plenty.
The part that matters most for Steps 4 and 5 is your numbered acceptance criteria. Write each one so that someone could check it off by using the app, without needing to ask you what you meant. "The app should feel responsive" can't be checked. "Tapping Save returns to the home screen and the new entry appears at the top of the list" can.
Now you hand your spec to an agent and let it build the whole app. This may be different from how you've mostly worked so far: instead of asking for one piece at a time and steering as you go, you write everything down first and then get out of the way.
SPEC.md into the project folder, add the folder to Github (in Github Desktop, click the current repository, click add, and click "add existing repository", and select your project folder) and make your first commit and push. Verify that you can see the app on github.com before proceeding.You might want to set your Agent to its most powerful setting for this step (bearing your usage limits in mind). Give your agent a prompt like this (adapt it to your actual spec):
Read SPEC.md in this project. Implement the full mobile app exactly as specified. This is an Expo project using Expo Router, so screens belong in src/app/. Check package.json for the exact Expo SDK version and write code for that version. Create all necessary files, components, and navigation. Make sure that appropriate data is persistent. Avoid security risks for sensitive data. Include proper error handling. Make sure the app starts without errors and displays the home screen correctly.
npx expo start (or press 'r' to refresh the app if it is already running) and test the app on your phone."Raw agentic build output". Don't fix anything before that commit. We want to see what the agent produced.Now you check the build against your spec, using a second agent that hasn't seen the conversation that produced the code. (Recall that the agent that wrote the code will be a bad judge of it: it will tend to agree that it did what it was asked. A fresh agent reading only your spec and the code has no such investment.)
Give this new agent a prompt like:
Review the React Native/Expo code in this project against the spec in SPEC.md. For each acceptance criterion in the spec, verify whether the code actually implements it correctly. Also check for: - Bugs or logic errors - Missing error handling - Code quality issues (unclear naming, repeated code, etc.) - Best practices for React Native or other technologies Format your review as a numbered list of findings, each marked as [PASS], [FAIL], or [WARN]. Be specific. Reference file names and line numbers. Do not fix anything in this session. Report only. Export the review as REVIEW.md at the root of the project.
"Fixes after AI review".With the core features working, now polish your app:
"Polish and final adjustments".Write your README and prompt log, record your video, add the project to your portfolio, push to GitHub, and fill out the Google form.
For the video, the easiest approach is to screen-record your phone or simulator, or to simply record your phone screen with another device. Walk through each screen, show the user interactions, and demonstrate data persistence.
Important: Your prompt log should include actual prompts, verbatim. Some recommended examples include:
Here's a reference for the new concepts in this assignment. AI will help you with all of these, but it's useful to know what you're working with.
<div> and <p>, you use <View> and <Text>.src/app/, and the file name determines the route, so src/app/settings.tsx becomes a settings screen. _layout.tsx files wrap the screens around them and are where shared navigation structure lives.View (a container, like a <div>), Text (displays text), TextInput (text field), Button (a button), FlatList (a scrollable list), Image (displays images), etc.useState): The way React Native tracks data that can change. When state updates, the screen automatically re-renders to reflect the new data. Example: const [count, setCount] = useState(0); creates a count variable and a setCount function to update it.<Text style={{color: 'red'}}>Hello</Text>, style is a prop being passed to the Text component.localStorage in web browsers. Data survives app restarts. It is not in the starter project, so add it with npx expo install @react-native-async-storage/async-storage.npx expo start. Also try shaking your phone in Expo Go to access the developer menu, where you can reload the app.npx expo login on your computer and make sure Expo Go on your device is signed into the same Expo account.expo version in package.json matches what Expo Go reports. If they still disagree, the fastest fix is to create a fresh project with a bare npx create-expo-app@latest (no --template flag) and move your code into it.npx expo start --tunnel. On campus, use CMU-SECURE.node --version, since Node 18 and 20 are no longer supported. Otherwise, try deleting the node_modules folder and package-lock.json file, then running npm install again. If that doesn't work, ask on Ed with the exact error message.