Your constructive feedback is valued – thank-you in advance for your time with this.
By 12:30 PM (half past noon), be sure that you have finished filling in your Culminating Task portfolio entry – use this exemplar as a guide.
Important
Most of you will be dismissed at 11:30 AM. Please wait until I come out to dismiss you. Until then, to minimize traffic and noise in the academic block, please stay in Hadden Hall, with the exception of essential trips to the washroom.
Completing this entry in your portfolio is how your work will be handed in. This must be completed, in full, no later than 11 AM on the date of your end-of-year interview.
Have a look the chapters in each video – it's probably unlikely that you would want to watch every minute of every video, but it's likely that everyone will find at least one chapter of one of these videos useful.
Things to do before our next class
Share your progress in one or more updates on Notion.
Completing this entry in your portfolio is how your work will be handed in. This must be completed, in full, no later than 11 AM on the date of your end-of-year interview.
Have a look the chapters in each video – it's probably unlikely that you would want to watch every minute of every video, but it's likely that everyone will find at least one chapter of one of these videos useful.
Things to do before our next class
Share your progress in one or more updates on Notion.
Have a look the chapters in each video – it's probably unlikely that you would want to watch every minute of every video, but it's likely that everyone will find at least one chapter of one of these videos useful.
Things to do before our next class
Share your progress in one or more updates on Notion.
Have a look the chapters in each video – it's probably unlikely that you would want to watch every minute of every video, but it's likely that everyone will find at least one chapter of one of these videos useful.
Things to do before our next class
Share your progress in one or more updates on Notion.
You are not required to watch this video end-to-end (or at all) but are more likely to, instead, choose to consult only certain chapters.
For example, if your app includes an opening screen with a "Get Started" link you may wish to watch this chapter of the video.
If you are ready to start querying a database table joined to another database table – with either a one-to-many or a many-to-many relationship – review this example provided by the Supabase documentation team. Supabase automatically detects joined tables and makes writing queries against them much easier than they otherwise would be.
Tip
A more complete example of how to query joined tables is coming by tomorrow from Mr. Gordon.
Things to do before our next class
Share your progress in one or more updates on Notion.
You have one more day to work on your static interfaces this week.
Use your Keynote prototypes as a reference.
Be sure to use SwiftUI Views Mastery as a reference while building out static interfaces.
Tip
If you prefer, rather than making a truly static interface (where data is embedded in views as string literals) you can can instead store data in arrays and apply abstraction (which makes building an app out easier).
Remember to use source control – commit and push your work frequently.
Reminder
Next week, with guidance from Mr. Gordon, you will design, create, and populate your app's database.
Note that this step is necessary for completion of culminating tasks but database design and creation is not being evaluated.
If you are ready now, see Mr. Gordon today in class, and he will give you the condensed version of the database design and creation lesson on the spot.
Things to do before our next class
Share your progress in one or more updates on Notion.
Make a big push to score significant progress on your static interface today.
Use your Keynote prototypes as a reference.
Be sure to use SwiftUI Views Mastery as a reference while building out static interfaces.
Remember to use source control – commit and push your work frequently.
Tip
After your static interface is complete, the next step is to create and populate your database. A how-to guide on this topic is forthcoming.
Note that this step is necessary for completion of culminating tasks but database design and creation is not being evaluated.
If you are ready now, see Mr. Gordon today in class, and he will give you the condensed version of the database design and creation lesson on the spot.
Things to do before our next class
Share your progress in one or more updates on Notion.
If you are finished those tutorials, making reference to your Keynote prototypes built in our prior mod, begin making static, non-interactive interfaces for your culminating task app.
Be sure to use SwiftUI Views Mastery as a reference while building out static interfaces.
Things to do before our next class
Share your progress in one or more updates on Notion.
Add evidence for whatever might be missing from your portfolio for assigned tasks in this module.
Thinking back to your mid-module portfolio review, make a post for today's class identifying where you feel your current grade should land, based on the new evidence you have added since the mid-module reviews.
Using these iOS Design elements, adapt the completed prototype file to instead be a prototype for your app.
Note
The tutorial on how to build a version of the to-do list app that uses a cloud-hosted database has been deferred to a future class, so that you can have the weekend to begin working on your app prototype in Keynote.
Things to do before our next class
Then share your progress in one or more updates on Notion.
Then draw conclusions when prompted to understand how classes are handled differently from structures in the Swift programming language.
You are welcome to work through the playground and discuss ideas with a partner, but you please make your own notes – the process of thinking about what you are seeing, and then considering how to explain that in writing, is a big part of building your long-term memories.
Important
Share your notes in a portfolio post on Notion; Mr. Gordon will provide feedback.
How can information be organized within an app, beyond a simple list?
Almost every application you use has a database behind it.
Read on to learn what a database is and how to query it (obtain information) from it.
Note
If you have finished the App Design Journal, start on, or continue with, this activity.
When you are finished (or have gotten as far as you can) share your progress on Notion. Once you have done so, Mr. Gordon will send you a link to the solutions, and you can check your work.
Things to do before the end of class
Vacation
Have a restful, fun, and safe March Break! 😎 See you in April! 🌷
What problems are being solved by developers in this video?
Activity: App Design Journal
Continue working through the Brainstorm (green) section of this document.
Aim to complete the green section before you leave for March Break.
Tip
Edits during March Break are totally fine, but not required! Sometimes in a new setting (at home with family, out with friends) we get new ideas for a useful app...
Your learning path through the course is about to go like this: ⑃
That is, when we come back from March Break, it's definitely the case that each of you will be learning different things to bring the app you want to make to life.
What do you want to make? Let's discuss...
The goal is to really think about ideas, opportunities, problems, or challenges... please engage with and complete slides two through five.
Tip
There will be lots of conversation in this class! Feel free to bounce ideas off of peers, Mr. Gordon... you took this course to learn how to build something, right? Let's dive in to your ideas...
Chapters 1, 2, and 3 cover concepts that are largely review but still good practice.
Chapters 4 and 5 get into topics that we will learn about in this module, and can be completed as a preview of topics that Mr. Gordon will author separate lessons for later in this module.
Important
There is far too much content listed today to complete in a single class.
Continue with the items listed in order, where you left off from yesterday's class.
For Evening Study
Mr. Gordon is still not well enough to be at school but will make an effort to send some replies and feedback through Notion.
Chapters 1, 2, and 3 cover concepts that are largely review but still good practice.
Chapters 4 and 5 get into topics that we will learn about in this module, and can be completed as a preview of topics that Mr. Gordon will author separate lessons for later in this module.
Important
There is far too much content listed today to complete in a single class.
While Mr. Gordon is away with illness, use each class to make progress based on where you are, personally, with your learning. Some students have already completed items 1 and 2 above, so they should work on item 3. Some students have not completed any of these items, so they should begin with item 1.
For Evening Study
Mr. Gordon is not well enough to be at school but will make an effort to send some replies and feedback through Notion.
Work alone or with a partner to analyze this interface and then apply what you learned from reproducing the Stopwatch app to reproduce this interface.
Focus on the main portion of the interface at first – that is, the list.
Then, use SwiftUI Views Mastery, and look up the NavigationStack structure (pages 313 to 321) for examples of how to add:
a navigation title
toolbar items (also see pages 681 to 684)
Tip
Do not worry about items like the battery icon, WiFi status, or cellular network – these are provided in a real app by the operating system and you do not have to worry about adding these to an interface as an app developer.
Learn how to reproduce the interface of a real iOS app.
Portfolios: Mid-module Portfolio Reviews
Major skills learned to date:
authoring structures to model data
creating user interfaces
Meet privately with Mr. Gordon to review your portfolio and propose a current level of achievement for the skills list above, based on the evidence currently in your portfolio.
Not all software developers have graphic design skills.
Platform owners like Apple want their users to have a consistent experience when using apps written by different people.
One of the ways Apple helps their developers provide that consistent look and feel is by offering a wide variety of built-in images that can be used in apps.
Please follow these steps to create a new project for the Bento-Box exercise below.
Tutorial: Saving Revisions of Your Work
Xcode automatically saves your code as you type.
However, it is additionally useful to have "save points" while you author code.
Mr. Gordon will explain how to stage and commit your work to save revisions locally.
Important
As you go forward in this course, always commit your work frequently with descriptive messages.
This serves as a form of note-taking, makes it easier to debug problems, and if necessary, makes it possible for you to return to a prior version of your code.
Exercise: Create a "Bento-Box" Design
Marketing teams must be able to convey new features in a concise manner to an audience.
In recent years, Apple has used "Bento-Box" graphics to do so.
Try to reproduce this image using SwiftUI, or use it as inspiration to design a bento-box themed view related to something you care about.
Mr. Gordon will demonstrate how to add images into your project.
Do not install Xcode via the App Store, as using this method means that it will automatically get upgraded when a new version is released (which is not always ideal).
