Memory Game is a Light & Sound Memory game to apply for CodePath's SITE Program.

Submitted by: Nikita Wilson

Time spent: 5 hours spent in total

Link to project: https://glitch.com/edit/#!/luxuriant-ripe-shallot?path=index.html%3A1%3A0

The following required functionality is complete:

• Game interface has a heading (h1 tag), a line of body text (p tag), and four buttons that match the demo app
• "Start" button toggles between "Start" and "Stop" when clicked.
• Game buttons each light up and play a sound when clicked.
• Computer plays back sequence of clues including sound and visual cue for each button
• Play progresses to the next turn (the user gets the next step in the pattern) after a correct guess.
• User wins the game after guessing a complete pattern
• User loses the game after an incorrect guess

The following optional features are implemented:

• Any HTML page elements (including game buttons) has been styled differently than in the tutorial
• Buttons use a pitch (frequency) other than the ones in the tutorial
• More than 4 functional game buttons
• Playback speeds up on each turn
• Computer picks a different pattern each time the game is played
• Player only loses after 3 mistakes (instead of on the first mistake)
• Game button appearance change goes beyond color (e.g. add an image)
• Game button sound is more complex than a single tone (e.g. an audio file, a chord, a sequence of multiple tones)
• User has a limited amount of time to enter their guess on each turn

The following additional features are implemented:

• List anything else that you can get done to improve the app!

If you recorded multiple GIFs for all the implemented features, you can add them here:

1. If you used any outside resources to help complete your submission (websites, books, people, etc) list them here. w3 schools

2. What was a challenge you encountered in creating this submission (be specific)? How did you overcome it? (recommended 200 - 400 words) A challenge I encountered I guess was creating a web project. I had been working with swift and x code for the past 3 months. Brushing up on my web development skills had me notice the specific differences between native mobile programming and web development languages. The only challenge I had was making sound work, as in when I was debugging I wasn’t sure if my browser was having issues or if it was the code. In the end, I restarted my machine and it was an IT issue and not software issue.

3. What questions about web development do you have after completing your submission? The only question I can think of, when is web development languages viable to use over native mobile development languages? Is it for budget reasons or does it matter up to a certain user scale. Is there a point in a legacy product when it is more viable to use docker & kubernetes vs building up a native mobile application.

4. If you had a few more hours to work on this project, what would you spend them doing (for example: refactoring certain functions, adding additional features, etc). Be specific.

For this project, if I had more hours available, I would add a registration page hooked up to a MongoDB database. The reasoning behind this is to save history between users and see how the user can get better at the game. I would also like to have added a timer and score tracker which would be calculated by speed and accuracy. After this is implemented, I would add better functionality by devices so they are optimized for a variety of screen sizes. A reward feature could also be added to the game based on how many levels are completed or by adding a payment system. With a video sharing API I would also like to add group matches with friends where they can have video chat support.

[My 5-minute Interview Recording]https://streamable.com/p6y2oq

Copyright Nikita Wilson

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.