This page is the whole AP Create task in one place: what you are building, what College Board needs from you, what I can and cannot do from now on, and how you hand it in. Come back to it whenever you are not sure what to do next. The checklist at the bottom is yours to tick as you go, and your My Progress page keeps count.

What you are building

You are building an app for your clients: the three or four LDPS children you interviewed and showed a paper prototype to in Thread 1. You already know what they need, and you have a storyboard they have tried. Before you write Swift, you plan your list and your procedure on paper, in Planning Your List and Procedure. Then you build, in Swift, on your own.

Nobody tells you what to work on in a work period. You decide, from your own storyboard and plan, what is most important to build next. Your clients try a running version of it at the third visit, and they receive the finished app at the fourth.

What College Board needs from you

The Create task has three parts, and you make all three alone:

  1. Program code. A PDF of every file in your app, with comments.
  2. A video. Up to one minute, with no narration and nothing that identifies you, showing your app taking input, doing something, and producing output.
  3. A Personalized Project Reference. Four screenshots of your own code, with no comments in them: your procedure, the place it is called, your list being filled, and your list being used.

Your app must contain:

  • A list (an array) that holds data your app uses, and that makes the app easier to build or change than it would be without it.
  • A procedure (a function) that you wrote, with at least one parameter that changes what it does, and whose body uses sequencing, selection (an if), and iteration (a loop).
  • A call to that procedure, somewhere your app really uses it.

You plan these in Planning Your List and Procedure, and you saw each one in a finished app in Building Multiplication Maestro. When your procedure runs, Testing Your Procedure shows how to check it with inputs you choose on purpose.

On the AP exam in May, you answer written questions about this list and this procedure, with only your Personalized Project Reference in front of you, and no AI. Build something you can explain, line by line, in your own words.

What I do from now on

The official administration of the task has started. College Board’s rules change what I can do for you until you submit:

  • I can answer questions about what the task requires, fix a problem with Xcode, Git, or your Mac, and keep teaching the class.
  • I cannot write, fix, debug, test, or suggest changes to your code or your design, and I cannot give feedback on any part of your work until all three parts are submitted as final. If you ask “is this good enough?”, I will ask you to explain what you have built instead.
  • You have no partner. You may ask a classmate a question about your code, the way you might ask AI, and you acknowledge that help in a comment the same way. Nobody but you touches your video or your screenshots.
  • Your clients can try your app and tell you what they think. They do not help you build it.

Expect me to sit beside you and ask you to explain what a line does. That is not a test; it is practice for May.

Work periods

Most Thread 2 classes are work periods. Here is how to use one:

  1. Pull, so you are working on your latest code.
  2. Choose what matters most today. Look at your storyboard, your plan, and your last commit. Your clients try a running version at the third visit, and what they try is your choice.
  3. Build it, and commit each time something works.
  4. Push before you leave.

If you are stuck, work out exactly what you expected and what happened instead, then ask a classmate a question or ask AI. Acknowledge any help in a comment.

The freeze

On Thread 2, Day 9, after the third visit and a class to revise, you add your comments, freeze your app, make your PDFs, take your screenshots, and record your video, all in class and on your own. Then you upload it all to the AP Digital Portfolio, and submit it as final, in the same class. The steps are below, under Freeze your code, Prepare your submission, and Upload day.

College Board allows students to write the program code with a partner, but never the video or the Personalized Project Reference. In our class, you have no partner: the program, the video, and the Personalized Project Reference are all yours alone.

First, a few notes about attributions in your code.

Acceptable AI Use

From the College Board:

Students are permitted to utilize generative AI tools as supplementary resources for understanding coding principles, assisting in code development, and debugging. This responsible use aligns with current guidelines for peer collaboration on developing code.

Students should be aware that generative AI tools can produce incomplete code, code that creates or introduces biases, code with errors, inefficiencies in how the code executes, or code complexities that make it difficult to understand and therefore explain the code. It is the student’s responsibility to review and understand any code co-written with AI tools, ensuring its functionality. Additionally, students must be prepared to explain their code in detail, as required on the end-of-course exam.

In our class, the same rule applies. You may use AI in your code, including your list and your procedure, when you acknowledge it, as in Acknowledging AI in Your Code.

Plagiarism

From the College Board:

The use of program code, media (e.g., video, images, sound), data, information, or evidence created by someone else or with generative AI tools in the creation of a program and/or a program code segment(s), without appropriate acknowledgment (i.e., through citation, through attribution, and/or by reference), is considered plagiarism.

A student who commits plagiarism will receive a score of 0 on the Create performance task, including their responses to the written response prompts on the end-of-course AP Exam.

Attribution

From the College Board:

Some examples of ways to provide attribution for program code that was not authored by you are as follows:

  • If the program code has been made available for your use by your teacher, add a comment that states: This code was provided as starter code by my teacher.
  • If the program code has been made available through an API or open- source code, add a comment that states: This code was made freely available by [source of code].
  • If the program code has been co-created with the assistance of a generative AI tool, add a comment that states: This code was generated using [Generative AI Tool Name].

Add comments to your program code to clarify the functionality of program code segments or to acknowledge and credit authors of media, data sources, or program code.

Add your comments

If AI or a classmate helped with any part of your code, make sure every such file says so in its comment header, and that your README.md says what the help was. If nobody helped, say that in your README.md instead, so a reader does not have to guess.

Here is one example of how to do this. As needed, modify the header that should already exist at the top of each source code file in your project:

//
//  ResultsView.swift
//  FractionPizza
//
//  Created by [your name] on 2026-11-04.
//  This code was generated using GitHub Copilot: the answer button style.
//  The scoring procedure is my own.
//

Freeze your code

When your comments are in:

  1. Build and run the app, and run your tests (Command-U), once more.

  2. Commit and push anything left, then tag that commit, in Terminal in your repository folder:

    git tag create-task-final
    git push origin create-task-final

Everything you submit comes from that tagged commit. You can keep improving the app for your clients afterwards; the tag does not move.

Prepare your submission

IMPORTANT

Complete this step for real only when your app is complete and tagged. A trial run on unfrozen code, to make sure the tools install, is fine and encouraged.

Make a folder on your Mac called Create Task Upload. Everything you prepare below goes in it, ready for upload day.

Program Code

From the College Board:

Submit one PDF file that contains all of your program code (including comments). Include comments or acknowledgments for any part of the submitted program code that has been written by someone other than you and/or your collaborative partner(s) [for example, AI tools].

To do this, first find the folder that your project is contained within, then open a Terminal window at that folder:

You should then be at a window that looks like this, except in your own project folder:

NOTE

The script below needs Homebrew. Type brew --version and press Return. If it says command not found, install Homebrew first, as in Part 2 of Installing GitHub Copilot, or ask me.

Type ls and verify that you can see the .xcodeproj file:

NOTE

When I tested this, I needed to run the next command twice, and you probably will too. The command is given immediately after this note.

The first time you run the command, you will see the system automatically install quite a few small software packages via Homebrew that are required to generate the PDF files of your program code. The command will show a small error message after all of the software packages are installed.

If you then press the ↑ arrow on your keyboard to recall the command and press Return on your keyboard to run it a second time, it should generate the PDF files successfully.

Finally, when you copy the command, remember to use the copy button at right:

You will know you copied the complete command successfully when you see the green arrow:

Now copy this command and paste it in that Terminal window, remembering to press the Return key to run the command:

curl -sL https://www.russellgordon.ca/lcs/generate-pdf.zip -o generate-pdf.zip && unzip -qj generate-pdf.zip && rm generate-pdf.zip && chmod +x generate-fullcode.sh && ls

TIP

What that command does, step by step:

PartPurpose
curl -sL … -o generate-pdf.zipDownload silently (-s), following redirects (-L), saving to a local zip
unzip -qj generate-pdf.zipExtract quietly into the current folder
rm generate-pdf.zipClean up the zip file
chmod +x generate-fullcode.shMake the shell script executable
lsList the contents of the current folder

When you run the command above, the output should look like this:

Now copy and paste this command, then run it in the same Terminal window:

./generate-fullcode.sh

The output will look like this:

Now type open . and press Return in the Terminal window to get a Finder window in the same folder:

The following file (look for the -fullcode.pdf suffix) is the file you will submit to the College Board for the Program Code requirement:

Double-click to open the file and review it. Make sure that all the program code from your project is present and that you see comments:

Copy this PDF into your Create Task Upload folder.

Video

From the College Board:

Submit one video file that demonstrates the running of your program as described below.

Collaboration is not allowed during the development of your video.

Your video must demonstrate your program running, including:

  • Input to your program
  • At least one aspect of the functionality of your program
  • Output produced by your program

Your video may NOT contain:

  • Any distinguishing information about yourself
  • Voice narration (though text captions are acceptable)

Your video must be:

  • Either .webm, .mp4, .wmv, .avi, or .mov format
  • No more than 1 minute in length
  • No more than 30MB in file size

Make your own video, on your own, in class on Thread 2, Day 9, after the freeze. If you run out of time, finish it at home before you submit. You might show your procedure at work; College Board requires only input, one feature working, and output.

If you can use the Simulator to run your app, that will be the easiest way to obtain a screen recording. Press Command-R to start recording while your app runs in the Simulator.

Alternatively, run your app on your phone, and make a screen recording there. Be careful not to accidentally include any information to identify yourself (such as notifications while you are recording your app running, or your phone’s home screen).

Check its length and file size, then put it in your Create Task Upload folder.

Personalized Project Reference

IMPORTANT

Screenshots for your Personalized Project Reference must not contain any comments whatsoever.

You will use the second PDF generated earlier to take screenshots:

Use the Command-Shift-4 keyboard shortcut to capture clear screenshots of the relevant portions of your program code from this file.

Your screenshots are of your list and your procedure, and you make them on your own (College Board’s rule), in class on Thread 2, Day 9, after the freeze, or at home before you submit if you run out of time. Put them in your Create Task Upload folder. Name them so you can tell them apart on upload day, such as 1 procedure.png, 2 procedure call.png, 3 list stored.png, 4 list used.png.

Procedure

The first two screenshots (program code segments) are related to the procedure (also known as a function) that you wrote within your app.

From the College Board, this is what you need to upload screenshots of:

The first program code segment must be a student-developed procedure that:

  • Defines the procedure’s name and return type (if necessary)
  • Contains and uses one or more parameters that have an effect on the functionality of the procedure
  • Implements an algorithm that includes sequencing, selection, and iteration

The second program code segment must show where your student-developed procedure is being called in your program.

List (Array)

From the College Board:

Capture and paste two program code segments you developed during the administration of this task that contain a list (or other collection type) being used to manage complexity in your program.

The first program code segment must show how data have been stored in the list (e.g.: where the list is populated).

The second program code segment must show the data in the same list being used, such as creating new data from the existing data or accessing multiple elements in the list, as part of fulfilling the program’s purpose.

Upload day

Near the end of Thread 2, Day 9, log in to the College Board Digital Portfolio site and upload:

  1. Program Code: the -fullcode.pdf file.
  2. Video: your video file.
  3. Personalized Project Reference: add your screenshots to the boxes on the page. If a procedure is too long for one clear screenshot, add it in pieces, in order. Save often.

Then open each component in the Digital Portfolio and check it on screen. I check only that the right file is in each place and that it opens; College Board does not allow me to comment on anything else. Then press Submit Final for each component, in this class. Once you submit as final, you cannot change anything. When you do, the Digital Portfolio asks you to confirm that the work is your own and that you have removed personally identifying information, and to say which programming language you used (Swift).

The College Board deadline is Friday, April 30, 2027, at 11:59 p.m. Eastern Time. We are finishing long before that on purpose. If something stops you from submitting today, tell me before you leave.

If something goes wrong on upload day

ProblemWhat to do
The video is too large (over 30 MB)Record again, shorter, or in the Simulator rather than on a phone. In QuickTime Player, File > Export As at a lower resolution also makes it smaller. Check the size in Finder (Command-I).
The video is over one minuteTrim it: open it in QuickTime Player, choose Edit > Trim, and drag the yellow handles.
The video format is refusedExport it from QuickTime Player as a .mov file, or record it again in the Simulator.
Your name, a notification, or your home screen appears in the video, or a person’s name appears in a screenshotRecord or capture it again. Nothing may identify you, and no real person’s name belongs in your submission.
A screenshot shows a commentYou used the wrong PDF. Take it again from the second PDF, the one without comments.
A screenshot is blurry or the text is tinyZoom in on the PDF before you take the screenshot; never enlarge a screenshot afterwards. Text should be at least 10-point. For a long procedure, take two or three screenshots of it in pieces.
The program code PDF is missing a file, or shows no commentsCheck that you ran the script in the folder that holds your .xcodeproj file, on the tagged commit, and run it again.
You cannot press Submit FinalA required part of the page is probably still empty. Check every field, save, and try again. If it still will not work, show me.

Success criteria

Tick each one when it is true. Your My Progress page keeps count.

Planning and building

Testing with my clients

Honesty

Freezing and submitting