diff --git a/README.md b/README.md index 79aa2a6..5705dd3 100644 --- a/README.md +++ b/README.md @@ -1,54 +1,8 @@ -### Unit 3: Final Project - -All apps: - * Will solve a relevant problem that serves an existing market - * Are technically complex and ambitious enough to highlight the skills you have gained - * Are fully functional and polished for presentation at Demo Day - -With that in mind, things to think about when ideating projects are the **technical complexity**, **design**, and **product**. - -###[Final Project Schedule](/final_project_schedule.md) - -###[Final Project Rubric](/final_project_rubric.md) - -###[Groups](/final_project_groups.md) - - -###App requirements: -* Overall product requirements - - Technically complex - - Compelling use case - - Polished implementation (UI/UX) - - Original product - - An engaging pitch that connects with the audience -* Basic technical requirements - - Does not crash - - Does not hang (little or no delay visible to the user) - - Does not fail when internet connection is slow/unavaialable - - Have a consistent look and feel visually across the app - - Consistent with [iOS Human Interface Guidelines](https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/#//apple_ref/doc/uid/TP40006556-CH66-SW1) - - Look great in both landscape and portrait - - Have well-organized, high-quality code - - -### Tips & Ideas -* Things that would impress: - - Super cool library that other devs could use - - Integration of complex APIs (e.g video, web services, etc...) - - Awesome UI - - Work with the OS in a more intimate way - - Advanced Separation of Concerns -* Things to Avoid: - - Unusable: Good technical implementation, but does not consider the end user's interaction - - Non-function: Good UI, but does not actually incorporate the tools needed to be feature complete. - - Obvious: Solution can easily be found in tutorials or examples, copies an existing system tool, or simply strings together APIs. - - Not Useful: This app doesn’t have a clear purpose or solve a problem. -* Some sample project ideas: - - Weather + Calendar - - Poll app / trivia app - - Really good photo journal app - - Really good note taking app - - - - +## Team: Poseidon Project +### Project: Zetron + +###Members: +* Natalia +* Dan +* Kaira +* Jamaal diff --git a/final_project_groups.md b/final_project_groups.md deleted file mode 100644 index afc53df..0000000 --- a/final_project_groups.md +++ /dev/null @@ -1,13 +0,0 @@ -###Final Project Groups - -|Members|Team Name|Link to Repo| -|---|---|---| -|Jackie
Brian
Umar
Elber|Geobased game|---| -|Christella
Felicia
Justine
Daniel|TBD|---| -|Derek
Xiulan
Christian
Chris|TBD|---| -|Diana
Mesfin
Jason
Varindra|Video compiler|---| -|Charles
Ayuan
Erica|Goal setting|---| -|Artur
Shena
Zoufishan
Henna|Travel App|---| -|Lauren
Jovanny
Bereket|Community Organizing|---| -|Kaira
Natalia
Jamaal|TBD|---| - \ No newline at end of file diff --git a/final_project_rubric.md b/final_project_rubric.md deleted file mode 100644 index 2a1da6f..0000000 --- a/final_project_rubric.md +++ /dev/null @@ -1,8 +0,0 @@ -###Project Rubric -|Criteria|0-Does not meet expectations|1-Partially meets expectations|2-Meets expectations|3-Exceeds expectations| -|---|---|---|---|---| -|**Performance**|App has major bugs. App hangs and/or crashes.|App has minor bugs and/or hangs briefly.|App has no bugs and doesn’t hang.|App runs as smoothly and cleanly as a default iOS app. | -|**UI Design**|Little to no effort has been put into aesthetics. Design/layout between and within pages varies widely.|Some, but not all pages have consistent design. Some elements are appealing, but others are not.|The app has a consistent look and feel. Intentionality has been put into the color scheme and visuals.|The app is simple to use and elegant. The aesthetic and design perfectly match the app’s function.| -|**UX Design**|The app is confusing and unintuitive. Buttons' functions are unclear and navigating between screens is challenging. Virtually no testing for UX.| Aspects of the app are sensible, but some remains confusing. There has been little testing with users.| App is layed out in a sensible format. Navigating between and within screens is clear.| UX design is fluid and intuitive. Users are naturally driven to navigate the app correctly with no prior knowledge or outside help.| -|**Presentation**|Group is unenthusiastic and does not increase interest in their app. Pacing is much too fast or slow. Script and deck are crude or non-existant. |Group has some stage presence. Pacing is slightly off. Script and deck are rudimentary, but communicate key information. |Group has solid stage presence. Pacing is reasonable. Script and deck engage audience and showcase their app. |Group expertly commands the stage. Pacing is perfectly geared to maximize impact. Deck is beautifully designed and supplements a well-crafted script for a fantastic presentation.| -|**Product**|Group does not explain who would use the app and what it does. Group does not present the problem their app will solve.|It is somewhat clear who would use the app and what it does. Group presents either the problem or the solution, but not both.|Group clearly indicates who would use the app and what it does. Group presents both problem and solution. |Group clearly indicates who would use the app and why their app is specifially targeted towards the demographic that they picked. Group expertly explains the exact niche their app fills.| diff --git a/final_project_schedule.md b/final_project_schedule.md deleted file mode 100644 index cc4deaf..0000000 --- a/final_project_schedule.md +++ /dev/null @@ -1,29 +0,0 @@ -###Final Project Schedule -|Week|Day|Activity|Deliverables| -|---|---|---|---| -|1|Tuesday 10/27|[Project Intro](https://docs.google.com/presentation/d/1eiKlYdSkdFxaOHpVqbyYTcl5AyKr9DO7zRITqwCcaB4/edit?usp=sharing)|Come to class with app ideas| -|1|Thursday 10/29|Hackathon Groups + Planning|---| -|1|Saturday 10/31|Hackathon|---| -|1|Sunday 11/1|Hackathon|---| -|2|Tuesday 11/3|Project Proposal Working Session|[Final project proposals](/project_proposals.md) due at 10:00 pm| -|2|Thursday 11/5|Project proposal reviews + Lessons Learned from 2.1 Final Projects|---| -|2|Saturday 11/7|All day UI/Design Workshop|---| -|2|Sunday 11/8|Wireframing|Wireframing due at 6:00 pm
[Weekly Retrospective](/weekly_retrospective.md)| -|3|Tuesday 11/10|How to Demo Workshop|---| -|3|Thursday 11/12|---|---| -|3|Saturday 11/14|---|---| -|3|Sunday 11/15|---|[Weekly Retrospective](/weekly_retrospective.md)| -|4|Tuesday 11/17|FIRST RELEASE + [DEMO](/presentation_guidelines.md)
Guest: Wesly Ross from Fueled|Push Beta Builds, Logos Due, Presentation Deck Due| -|4|Thursday 11/19|---|---| -|4|Saturday 11/21|---|---| -|4|Sunday 11/22|---|[Weekly Retrospective](/weekly_retrospective.md)| -|5|Tuesday 11/24|SECOND RELEASE + DEMO|Presentation Scripts due| -|5|Thursday 11/26|Thanksgiving Break-No Class|---| -|5|Saturday 11/28|Thanksgiving Break-No Class|---| -|5|Sunday 11/29|Thanksgiving Break-No Class|[Weekly Retrospective](/weekly_retrospective.md)| -|5|Monday 11/30| Individual team demo reviews|---| -|6|Tuesday 12/1|THIRD RELEASE + DEMO|Personal Pitches due| -|6|Thursday 12/3|Individual meetings to review personal pitches|---| -|6|Saturday 12/5|Individual meetings to review demos|---| -|6|Sunday 12/6|---|[Weekly Retrospective](/weekly_retrospective.md)| -|x|Tuesday 12/8|DEMO DAY|Submit final version to App Store| diff --git a/presentation_guidelines.md b/presentation_guidelines.md deleted file mode 100644 index 1e5dcdc..0000000 --- a/presentation_guidelines.md +++ /dev/null @@ -1,30 +0,0 @@ -###Presentation Guidelines: - -1) Presentations will take around 10 minutes. - -###Presentation Schedule -|Time|Event| -|---|---| -|0-3|Personal Pitches| -|3-4|Discuss the problem that exists and how your app solves it| -|4-5|Discuss use case| -|5-8|Demo app| -|8-10|Q & A| - -Time should be distributed evenly to each team member. - - - -2) Teams will be using a script - --Make sure that everything is well rehearsed and practiced
--There should be total clarity on which group member is speaking when
--The script should be memorized
- - - -3) Teams will be presenting from a deck. - --Include photos for the personal pitches
--Include engaging visuals and images
--Do not simply display the script
\ No newline at end of file diff --git a/project_proposals.md b/project_proposals.md index 34d5551..6a1acbd 100644 --- a/project_proposals.md +++ b/project_proposals.md @@ -1,45 +1,32 @@ -# Final Project Proposal Submission - -### The following is due Tuesday, 11/03 at 10:00pm: - - -Please create a repository for your final project, with the following contents: - * README with your group members - * project_proposal.md (template below. Feel free to use the markdown from this file and fill in your responses.) - * Your app - * Folder that contains [Weekly Retros](weekly_retrospective.md). (Empty for now) - - ---- - # Access Code 2.2 Final Project Proposal -#### For each group, please submit the final project proposal by 10:00 pm on Tuesday 11/03/2015. You will receive feedback on the proposal on Thursday 11/5. - ---- **Project Name:** +The Poseidon Project **Team Name:** +Poseidon Team **Team Members:** +* Kaira Villanueva +* Jamaal Sedayao +* Natalia Estrella +* Daniel Distant ## The Problem -Describe the problem that your app will address. This does not need to be a novel idea or product, but your app should not directly recreate an existing product. If you are basing the app on an existing product, there should be some edge to your design or feature that solves a problem with that existing product. - -In this section, please frame the issue with supporting statistics about the need (market size, competitors, use cases). You should fully think through your user - who is your user? Why do they need this app? How are they using it? +People are bored. ## The Solution -Please provide a detailed description of the app here. Map out how the app solves the problem described in section I. You should also include: - * Baseline features you plan to implement by Demo 1 (what + why). - * Bonus features you plan to implement if baseline features are completed in time (what + why). +We combat the crippling effects of boredom with our games. -## Execution -Please describe how you will build this app. Include: +## The Minimum Viable Product - Due Thursday, 11/17/15 + * Users can connect multiple devices connect via MultiPeer Connectivity + * Users can tell where other users are via MPC/Geolocation/Bluetooth + * Users can TAG other users by getting close to them with their device + * Users can tell they have been TAGGED because their device registers the TAG and responds + +## Execution [SOON] * A detailed timeline for building the product, broken out by weekly sprints. Think about the user stories you would frame your weeks around. *Your polished MVP (baseline features) should be ready to demo by Demo 1 on Thursday 11/17/2015.* * A breakdown of team member responsibilities. Team members should take ownership over a specific feature or aspect of the app. -[Example of a project proposal (from Mozi)](https://github.com/jaellysbales/access-robot/blob/master/ProjectProposal.md) - -[Example of a project plan (from Espy)](https://docs.google.com/spreadsheets/d/1n4XtthaWqkg7YvaTfJZwC9Fc10RKd4JLr4HaUtYAh1c/edit#gid=0) diff --git a/week1-summary.md b/week1-summary.md new file mode 100644 index 0000000..2357cf2 --- /dev/null +++ b/week1-summary.md @@ -0,0 +1,50 @@ +## Weekly Retro +### Due: November 17, 2015 + +**Goals for last week**: + * Create a unified theme. + * Thoroughly research and become familiarized with necessary technology. + * Connect users via Multipeer Connectivity. + * Detect proximity via Core Bluetooth while users are connected to Multipeer Connectivity. + + +**Goals for this week**: + * Fine tune bluetooth proximity response. + * Research wifi incorporation for proximity detection. + * Implement shake gesture. + * Add sound effects. + * Refine UI/UX. + + +**Guiding Questions** (consider before the meeting): + + * What went well? + * Tracking down the necessary technology was difficult, but with the whole team eager to implement it, the task was done quickly. + * What should we do differently next time? + * Restructure demo process. + * What did we learn? + * Refining the connection between users is essential. + * Users are receptive to the product. + * We must restucture the demo presentation. + * What still puzzles us? + * Exactly how to get the BEST proximity reading. + +**Team Member Analysis**: +If you did not meet your goals, how will this affect the progression of the product? What will you do differently to meet your goals this week? + +We met all of our goals. As a result, this gives our team time to refine the product and enhance functionality. + +**Additional Discussion Topics**: + + * Compare your work planned with what your work completed. + * We accomplished everything we sought out to complete by this demo. + * Is the divison of roles within your team working? + * The division of roles works, but we often overlap for the sake of speed and efficiency: One person might be more familiar with a certain task. + * How is communication and collaboration between team members? + * Communication and collaboration happens frequently. We try to work outside of class as often as possible, and keep each other abreast of any changes and potential ideas. + * Are you getting adequate support? How are you reviewing code? + * Michael Vilabrera, our mentor, regularly checks in with our team and gives us guidance on how to move forward with the project. + * How can you improve productivity and get the most work done within the next week? + * To improve productivity we could continue having a defined list of goals to accomplish, but having more defined deadlines. + +**Mentor Comments**: diff --git a/week2-summary.md b/week2-summary.md new file mode 100644 index 0000000..f536b8f --- /dev/null +++ b/week2-summary.md @@ -0,0 +1,51 @@ +## Weekly Retro +### Due: November 24, 2015 + + +**Goals for last week**: + * Create a unified theme. + * Thoroughly research and become familiarized with necessary technology. + * Connect users via Multipeer Connectivity. + * Detect proximity via Core Bluetooth while users are connected to Multipeer Connectivity. + + +**Goals for this week**: + * Fine tune bluetooth proximity response. + * Research wifi incorporation for proximity detection. + * Implement shake gesture. + * Add sound effects. + * Refine UI/UX. + + +**Guiding Questions** (consider before the meeting): + + * What went well? + * Tracking down the necessary technology was difficult, but with the whole team eager to implement it, the task was done quickly. + * What should we do differently next time? + * Restructure demo process. + * What did we learn? + * Refining the connection between users is essential. + * Users are receptive to the product. + * We must restucture the demo presentation. + * What still puzzles us? + * Exactly how to get the BEST proximity reading. + +**Team Member Analysis**: +If you did not meet your goals, how will this affect the progression of the product? What will you do differently to meet your goals this week? + +We met all of our goals. As a result, this gives our team time to refine the product and enhance functionality. + +**Additional Discussion Topics**: + + * Compare your work planned with what your work completed. + * We accomplished everything we sought out to complete by this demo. + * Is the divison of roles within your team working? + * The division of roles works, but we often overlap for the sake of speed and efficiency: One person might be more familiar with a certain task. + * How is communication and collaboration between team members? + * Communication and collaboration happens frequently. We try to work outside of class as often as possible, and keep each other abreast of any changes and potential ideas. + * Are you getting adequate support? How are you reviewing code? + * Michael Vilabrera, our mentor, regularly checks in with our team and gives us guidance on how to move forward with the project. + * How can you improve productivity and get the most work done within the next week? + * To improve productivity we could continue having a defined list of goals to accomplish, but having more defined deadlines. + +**Mentor Comments**: diff --git a/weekly_retrospective.md b/weekly_retrospective.md deleted file mode 100644 index 6bf2b75..0000000 --- a/weekly_retrospective.md +++ /dev/null @@ -1,42 +0,0 @@ -## Weekly Retro Template - -**Goals for last week**: - -**Goals for this week**: - -**Guiding Questions** (consider before the meeting): - - * What went well? - * What should we do differently next time? - * What did we learn? - * What still puzzles us? - -**Team Member Analysis**: -If you did not meet your goals, how will this affect the progression of the product? What will you do differently to meet your goals this week? - - * Team Member #1 - * Goals/Responsibilities Last Week: - * Did you meet your goals/responsibilities last week? Why or why not? - * Goals/Responsibilities This Week: - * Team Member #2 - * Goals/Responsibilities Last Week: - * Did you meet your goals/responsibilities last week? Why or why not? - * Goals/Responsibilities This Week: - * Team Member #3 - * Goals/Responsibilities Last Week: - * Did you meet your goals/responsibilities last week? Why or why not? - * Goals/Responsibilities This Week: - * (Team Member #4) - * Goals/Responsibilities Last Week: - * Did you meet your goals/responsibilities last week? Why or why not? - * Goals/Responsibilities This Week: - -**Additional Discussion Topics**: - - * Compare your work planned with what your work completed. - * Is the divison of roles within your team working? - * How is communication and collaboration between team members? - * Are you getting adequate support? How are you reviewing code? - * How can you improve productivity and get the most work done within the next week? - -**Mentor Comments**: