Project 3 for GA
##Features
Splashscreen
- Splash screen (Gabe)
Game Fragment
- Animation (Gabe)
- Search Functionality (Leo)
- Notifications (Leo)
- Icons (Paul)
- Include: drink, movement, car, writing
Game Detail
- Animation (Paul)
- Breakdown (Paul)
- Review/Rating (Leo)
- Video Link (Paul)
Tools Detail
- Dice & Cards (Spencer)
- Link from games (Spencer)
Questions
- Clean, Dirty, Random (Gabe)
- Facebook share (Gabe)
Design
- Horizontal design (Paul & Gabe)
- Node backend (Leo)
###optionals
- search
- interactive: Deck, Dice, Rule Tracker
- drink tracker
##Use Cases
- party
- kickback
- small-ish group of people
- events
- family
##Themes
- Birthday
- Party
- Funeral
- Company
- Gatherings
##Games
- Vikings
- Laser Eye
- Untangle
- Hokey Pokey
###Drink-oriented Games
- CharDeeMacDenis
- Beer Pong
- King's Cup
- Don't Drink and Drive
##Motivation A common scenario: A number of people are called to a function room for a meeting, since arrival no one’s made eye contact, there’s awkwardness and the silence is deafening. The meeting leader needs an effective way to get the disparate group to work comfortably and cohesively.
##Requirements / Constraints
Your work must:
-
Include at least 2 prototypes
-
Include user stories based on your research and feature prioritization in a Trello board for the complete flow of your app
-
Have at least one Activity--more if it makes sense. The activity should include a list of interactive cards implemented with Android’s RecyclerView and CardView APIs.
-
Include at least three types of cards:
- One card should present data that is stored and updated on the user’s phone using a Content Provider or Shared Preferences (e.g. To-do card, Reminder card, Alarm card).
- Two cards should present data provided through a web API (e.g. Weather card, Twitter card, Maps card, Photo of the Day). Check out this directory of APIs if you need some API ideas.
-
Use the Retrofit library to handle HTTP requests and parse JSON data
-
Include at least one Notifications feature (e.g. reminder, alarm)
-
Look great in both landscape and portrait modes and reflect Material Design principles
-
Not crash or hang and should handle for when networking/internet is slow or unavailable
-
Have code that is semantically clean and well-organized
-
Integrate with the Twitter and/or Facebook's APIs
-
Allow the user to share breaking news developments with friends
Bonus:
- Integrate additional APIs
Week 7:
By the end of week 7:
- A completed research plan according to the template provided in class
- Competitive research in a Google Sheet
Week 8:
By the end of week 8:
- Written user personas--ideally from both new and longtime Yelp user perspectives
- A list of prioritized features
- A project plan presentation
- Completed user stories
- A link to your team's Trello Board set up according to Trello's suggestions
- A completed, basic version of the user interface for your app, with placeholder data and resources to fill out your screens
Week 9:
By the end of week 9:
- Working cloud synchronization using Sync Adapters and API integration
- A final, working version of your app
- A git repository hosted on GitHub, with frequent commits dating back to the very beginning of the project. Commit early, commit often
- A
readme.md
file describing what the app does, and any bugs that may exist - One screenshot in the
readme.md
- Automated tests for your code