In this phase, we are focused on creating any API needed to support your app as well as demonstrating a mastery of any external API that will be used by the app. In some cases this may not be applicable, but most apps use an API to distribute and collect data for a mobile app, whether it is an external API maintained by someone else or one that the app team creates themselves. In this sprint, you will assess the need for an API and then create, test and document the API.

If API access/creation is not necessary for your app or you are using Firebase, you will be asked to assess the information needs of your app and demonstrate that they will be properly met. The exact nature of this will be worked out by the team and the instructional staff.

In this phase, each team will also create prototype using either Keynote or one of the other prototyping tools available on the market. The prototype will look realistic, will click through to appropriate screens, but will not actually work or save any data. The team must build this prototype and test it on at least 4 users and report on the experience and lessons learned.

Using what was learned from the prototyping experience, each team must submit a schedule for implementing features on their feature list. The key here is that as we prepare to move to the next sprint -- in which you develop a first functional version of the app -- that you will have thought through and know which features will be included in that first release. We will use this list to assess your first version deliverable in the next phase.

Deliverables

This sprint's deliverables include either or both an API that the team created and a walkthough demonstrating use of an external API. For an internal API, the team must provide the link to the API and its documentation. For an external API, the team must provide a Swift playground (similar to what was done in class) showing that they can access the API and parse the JSON provided.

If the team is using Firebase, they must document the JSON structure of the documents they are going to create and then access in Firebase.

All teams must provide a marked-up version of their high-fidelity wireframes that provide a clear mapping of the data needed on each screen and where that data is coming from. To that end, teams must also provide a set of structs that when populated, will provide the data needed by the app.

All teams must have a working prototype using Keynote or other tools as mentioned above. In addition, a brief report (2-3 pages max) detailing the user tests run on the prototype and the lessons learned (table or bullet points highly recommended for the latter).

All teams must provide a detailed list of features to be implemented in version 1 of the app as well as the additional features to be implemented in version 2 at the end. This list will be used to assess progress in the next sprint.

The submission of these deliverables is due electronically to Prof. H, your supervising TA, and alumni mentor by 4pm on Thursday, October 26, 2023. It will constitute 3 percent of your final course grade.

During this sprint you will have two required 15-minute check-ins with your supervising TA (on 10/09 and 10/23) and you have one required check-in with your alumni mentor (to be scheduled with him/her for some date between 10/12 and 10/22; note this range is wider because of the break). As a reminder, failure to complete these check-ins in a timely manner will result in a grade penalty.

In addition, you are required to turn in a one-page report on your mentor meeting(s). You will be provided a template for these reports and must use the template; failure to do so will result in a 25% penalty on this phase.