Project: Soundboard
04
Embedded Files
This performance task requires you to develop a Soundboard App similar to the I Have a Dream App from this unit. You may work individually or make a similar app as a partner (you must each do your own app). For this project you may seek guidance from TClark or other students.
Project Directions
Project Directions
You are to create a soundboard app similar to the I Have a Dream app from earlier in this unit.
You may pick the theme, but all images and sounds must be related to that theme.
If you absolutely must have your perfect sounds it will be homework for you to acquire those sounds. If you spend more than 1 period getting media you will have points deducted.
If you think you have the best sound files and want to share with others TClark can put them in a folder and link below.
The app must only play one sound at a time.
Play & Pause Features
4+ different pictures & sounds (or text-to-speech)
4+ events with event handlers
button click, shaking, or voice input, etc.
One creative enhancement of your own choice!
App Requirements
App Requirements
App Title (change the screen1 title property)
All components and media must be named clearly
The app must not be larger than 5MB, so any media you get needs to be resized to be smaller images, etc.
DO NOT USE .JFIF files
Sound files acceptable: wav, mp3, ogg
Resources
Resources
Many sounds and images online are copyrighted and it is a violation of copyright to include such images in your app. So, you should be careful about the images and sounds you put into your apps. If you want to use a copyrighted image or sound in your app, you will have to get permission from the holder of the copyright. It might be easier just to search for free media.
There are sites that offer free audio and image files, including the following:
Wikimedia commons is a great source of free and open source media. Any files found on its sites can be used in apps without violating copyright.
When finding images with Google image search, click on tools and select "Usage rights" to be:
Labeled for noncommercial reuse with modification
IF YOU CANNOT FIND YOUR "PERFECT" SOUND SOON
IF YOU CANNOT FIND YOUR "PERFECT" SOUND SOON
JUST USE SOUNDS THAT ARE AVAILABLE
JUST USE SOUNDS THAT ARE AVAILABLE
DO NOT SPEND MORE THAN 20 MINUTES GETTING SOUND FILES
DO NOT SPEND MORE THAN 20 MINUTES GETTING SOUND FILES
Note: when you acquire your files, you should rename them so that they work with App Inventor: no spaces, no special characters, and short file names i.e. yourname1.jpg, yourname2.jpg, etc.
Convert music files:
Compress media files:
What is Due
What is Due
Video: One video that demonstrates the running of your app and highlights the features of your app. Your video must be 20 - 60 seconds long and must not exceed 1 minute in length and must not exceed 30 MB in size. Make a Video
Written Response: One PDF that responds to the prompts listed below. Template
Program Code: One PDF that has screenshots of all your blocks. Template 3
AIA File
Upload all files into a new Google Drive folder for this project, then select from My Drive in the Google Form.
Upload all files into a new Google Drive folder for this project, then select from My Drive in the Google Form.
Written Response Directions - Template
Written Response Directions - Template
A - Provide a written response or audio narration in your video that:
Identifies you created your app with "MIT App Inventor"
Identifies the purpose of your program and your enhancement(s)
Explains what the video illustrates
(Approximately 150 words)
B1 - Describe the incremental and iterative development process of your program code. What is the overall core functionality of your program. What features/enhancements did you add in what order. How did you go about troubleshooting problems that arose?
B2 - Describe one distinct point in the development process, either one difficulty or opportunity you encountered and how you resolved it with code. In your description clearly indicate that your code development is for code you developed independently.
(Approximately 200 words)
[Basically write about how you went about coding, testing and fixing errors in your code. Make sure you are writing mostly about the code and not the files or images.]
Report abuse