Requirements

1)Home Page

• Main page to start search; large easy to find search bar. This search bar starts off simple and easy to use, as per client's requests. The contextual search functionality will be implemented in the back-end, and will show most "relevant" data first (with relevance stemming from like, retweet, heart, and other reactionary indicators of popularity or importance).

2)Navigation bar

• Simple top-navigation with labels instead of symbols.
• About, FAQ, Contact Us, Syntax, Login, Home / Search

3)Facebook API integration

• Need to be able to pull public information from Facebook, parse into excel type data (.csv, since it's tabular) to be exported, keep fields as organized and standard as possible.

4)Twitter API integration

• Need to be able to pull public information from Twitter, parse into excel type data (.csv, since it's tabular) to be exported, keep fields as organized and standard as possible.

5)Reddit API integration

• Need to be able to pull public information from Reddit, parse into excel type data (.csv, since it's tabular) to be exported, keep fields as organized and standard as possible.

6)Instagram API integration

• Need to be able to pull public information from Instagram, parse into excel type data (.csv, since it's tabular) to be exported, keep fields as organized and standard as possible.

7)Standardize search language

• Google standard implementation Criteria can be filtered using Google's search functions (https://support.google.com/websearch/answer/2466433?hl=en).
• Separate "Help" page also details this syntax and gives examples!

8)Advanced search selectables

• Date/time filtering
• Geo-location - > translate to zip (coordinates if at all possible) + filtering IP localization will also suffice if there is no GPS source or device tracking, since this will cause permission issues on chrome
• Source filtering

9)Sentiment analysis

• Free software package may lack credibility
• API implementation
• Very important to client, willing to pay; on a TBD basis at this point, but definitely an essential.

10)Line graph and Word cloud implementation

• Visualizations of data over time
• Word Cloud (reliant on sentiment analysis that will have to be implemented first)

11)Results Page

• Able to export to CSV or data table type for manipulation
• Able to display data in a results method (this includes graphs, but also actual query data by relevance as listed above)

12)Intuitive Navigation with Graphics

• Design accommodations for user-base (average age being 50)
• Simple and clear navigation; every part of the app does a separate task and links are not ambiguous.

Design Page

NOTES:

• This web app will not be widely available and thus will not need to be submitted to or found via search engines.
• A login page is being considered to limit user traffic per client request. (dependent on server logistics and above, but still a concern)