Create Task

Timelines

• You will have a minimum of three full class periods to work on your Create Task over the coming week.
  • You are encouraged to use your culminating task from last year as a starting point.
  • You will have the choice of using additional in-class time, but may need to then complete AP CSP exam prep or other tasks outside of class time.
• Your Create Task must be fully submitted to the College Board through your Digital Portfolio no later than the end of this module – ideally before that point in time.

Requirements

1. Review the formal 2025 AP Create Task requirements.
2. Understand the 2023 AP Create Task rubric.
   • These are the guidelines that the College Board evaluator will likely use to score the responses that you author in May on the exam.
   • To better understand requirements, please watch this video that compares the exemplar to the rubric.

Exemplar

Multiplication Maestro is another MVP (minimum viable product) for the AP Create Task.

1. Watch the 53 second video demo of Multiplication Maestro.
2. Familiarize yourself with the source code by reviewing commits step by step.
   • Here is the list of commits for Multiplication Maestro.
   • Green segments reflect code that was added in a given commit.
   • Red segments reflect code that was removed.
3. Clone the exemplar project and try it out.
   • Note the following:
     1. Code is written to be as simple to understand as possible.
        • You can likely think of better ways to organize the code…
     2. Results are filtered using an approach that is:
        • designed to meet AP Create Task requirements
        • not the way you would filter a list “in real life” when writing an app using Swift and SwiftUI
4. Watch this video that explains Create Task requirements and how the exemplar meets them.
   • For the exemplar, here is: 
     • The complete program code as a PDF file
     • The 1-minute video
     • The written responses, which this year, you will write on the exam itself on Thursday, May 15, 2025 at 12 noon.

Things to do

1. If writing your program from scratch, consider making a plan for your project.

   • While not formally required, paper prototypes may help organize your thoughts.

2. Author your program code – source control must be used.

   • Commit and push your code regularly, using descriptive commit messages.

3. Test your code thoroughly.

4. Leave enough time to:

   1. Print your code to PDF – here is how to do it in less than 5 minutes.

      1. Download, install, and open BBEdit.

      2. Complete these steps – follow the links to see a video demo:

         • 00:00 - Open Xcode and BBEdit side-by-side
         • 00:06 - Copy and paste each file into BBEdit, removing your name
         • 01:23 - Save the file in BBEdit with .swift as the file extension
         • 01:48 - Print the document with line numbers and syntax highlighting
         • 02:31 - Optionally print the document in landscape mode to show longer lines better

           TIP

           The full program code PDF with comments is what you will upload to the Digital Portfolio website.

      3. Finally, make a version of your PDF that does not have comments by using this regular expression ([ ]){0,}//.* to find and replace all comments with blanks:

         • Getting Full Program Code Without Comments

           TIP

           This second full program code PDF without comments is what you will use to take screenshots for your Personalized Project Reference.

   2. Record your 1-minute video.

      • The easiest way to record a video is to press Command-R when your app is running in the Simulator (if writing an iOS app) or to press Command-Shift-5 to record your screen (if writing a macOS app)
      • Here is how to “make small text large” if you wish to use this effect in your video.

      NOTE

      It is not required to show text captions within your video, although it is encouraged if you have the time as it makes the College Board evaluator’s job easier. If you choose to do this, use Quicktime Player to record your video.

   3. Take your screenshots for the Personalized Project Reference and save these in a folder on your computer. You will later upload these to your AP CSP Digital Portfolio.

      IMPORTANT

      Take screenshots for your written responses from the second PDF you created using BBEdit – the one without comments.

      Do not take screenshots from Xcode directly, or line numbers will not match up with your full program code PDF, which would be confusing for the College Board evaluator who reviews your submission.

      Be sure that code screenshots are legible – code cannot be so tiny that it becomes nearly impossible to read without a magnifying glass.

   4. Author your written responses to the probable exam questions.

      • Although you are not submitting your written responses now, you can keep these to refer to prior to the exam in May.
      • You will also need these written responses to prepare for the end-of-module evaluation here at LCS.

5. When you are all finished, submit your work to the College Board through your Digital Portfolio.

   TIP

   When you upload your work to the Digital Portfolio, you will be asked what programming language you completed the AP CSP curriculum in – of course, here you would select Swift.

   You will also be asked what programming environment you used – here, please select Other and then type Xcode.