I will begin with completing a fair chunk of the JS work. To see how well the JS works I will use the DOM to show
"Ask The Cosmos"
In this project I will create a site that will 'answer' a question with either a 'Yes' or 'No' accompanied with an embedded GIF. A user's will be confirmed as a question by checking for the presence of a '?'.
I will be using the "YesOrNo" API: http://yesno.wtf/api/
Sample JSON:
"answer": "yes",
"forced": false,
"image": "https://yesno.wtf/assets/yes/5-64c2804cc48057b94fd0b3eaf323d92c.gif"
}
Mobile: (https://i.imgur.com/3hlAEOa.png)
Desktop: (https://i.imgur.com/eef1uNB.png)
The functionality will then be divided into two separate lists: MPV and PostMVP. Carefully decided what is placed into your MVP as the client will expect this functionality to be implemented upon project completion.
These are examples only. Replace with your own MVP features.
- Find and use external api
- Render data on page
- Save user input history on page
These are examples only. Replace with your own Post-MVP features.
- Add second API
- Use local storage to save user favorites
This schedule will be used to keep track of your progress throughout the week and align with our expectations.
You are responsible for scheduling time with your squad to seek approval for each deliverable by the end of the corresponding day, excluding Saturday
and Sunday
.
Day | Deliverable | Status |
---|---|---|
July 10-12 | Prompt / Wireframes / Priority Matrix / Timeframes | Incomplete |
July 13 | Project Approval | Incomplete |
July 13 | Core Application Structure (HTML, CSS, etc.) | Incomplete |
July 14 | Pseudocode / actual code | Incomplete |
July 15 | Initial Clickable Model | Incomplete |
July 16 | MVP | Incomplete |
July 17 | Presentations | Incomplete |
Include a full list of features that have been prioritized based on the Time and Importance
Matrix. Link this image in a similar manner to your wireframes
Tell us how long you anticipate spending on each area of development. Be sure to consider how many hours a day you plan to be coding and how many days you have available until presentation day.
Time frames are also key in the development cycle. You have limited time to code all phases of the game. Your estimates can then be used to evalute game possibilities based on time needed and the actual time you have before game must be submitted. It's always best to pad the time by a few hours so that you account for the unknown so add and additional hour or two to each component to play it safe. Throughout your project, keep track of your Time Invested and Actual Time and update your README regularly.
Component | Priority | Estimated Time | Time Invested | Actual Time |
---|---|---|---|---|
Adding Form | H | 3hrs | 3.5hrs | 3.5hrs |
Working with API | H | 3hrs | 2.5hrs | 2.5hrs |
Total | H | 6hrs | 5hrs | 5hrs |
Use this section to include a brief code snippet of functionality that you are proud of and a brief description.
function reverse(string) {
// here is the code to reverse a string of text
}
Use this section to document what changes were made and the reasoning behind those changes.