Monday, April 27, 2020

Assignment 1: Checklist

Make a checklist of everything you'll need to do to finish your final app project. This should be some kind of bullet list or numbered list. If you do this correctly, your list should be about TWO PAGES long. If you don't do it correctly, you'll probably forget something that will make it impossible to finish your app. This checklist will remind you of everything you need to do so you won't forget something.

There will be several parts to your checklist.

1. You need a list of every screen in your app. You're going to plan out all the screens in a separate assignment. How are you going to connect between the screens? Tab navigation? Navigation controller? Other? You'll draw the screens in a separate assignment. For now, just list them.

Will there be an "about" screen where you display your email address and a way for people to pay you?

2. You need a list of every "asset" you'll need in your app. This includes all images, sounds, video, and other media. For each asset, list how you are going to create the asset.
  • Images: remember, you have to make them all yourself using Illustrator or other program. You are not allowed to use images you find on Google. You might ask, "What if I get permission?" I will tell you frankly that it will take longer to get permission than to just draw them yourself. You might ask, "What if they are royalty free?" I will tell you that even royalty free images require permission.
  • Sounds. You can create these yourself using Adobe Audition. You may not use sounds you find on Google. You might find some "free" sounds. Apple will probably reject your app from the app store if you can't provide written certification from the creators of the sounds. So it's quicker just to make them yourself.
  • Videos. The best way to record a video for your app is to use your phone. Phones have higher resolution than most cameras and video cameras.
 Don't forget that images also includes your app icons.

3. You need a list of every code you have to write. This includes every Swift file, every function, every piece of code you'll need. You can pretty much plan that every button needs to have an action associated with it. Every piece of data needs its place in the code, some struct or class in some file.

4. You'll need a list of all the data you'll need. This is part of the code, but you should list it separately. This could be a list of every color your users will learn, every food they will eat, every exercise they will do, every word they will learn in sign language, etc.

It's best to write this up in Google Docs.

Update

5. Make a list of all your tasks, including storyboard, actions, outlets, collecting data, making images, etc.

Here are some sample checklists you might refer to:

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.