Crowd Intelligence Grocery Shopping Mobile App Gnosis Solutions Crowd Intelligence Grocery Shopping Mobile App Speak on our app.

Our Team and Mentor Christopher Simcox - Database/Connections Lead Kristoffer Schindele - Front End Developer Thomas Back - Front End Lead Kalen Wood-Wardlow - Team Leader Our Client and Mentor: Dr. Michael Leverington Kalen Introduce Team, Client/Mentor and Project name Animate the order of introducing the graphic, one by ione

Problem Statement What options are available to grocery shoppers to shop smarter and more efficiently? I want to present you the question of what resources exist for grocery shoppers to shop smarter and more efficiently? They could sign up for individual stores rewards programs in which they receive deals and price off items, but they can do little to research the prices within local stores through their site, or what products are contained locally. In the way of applications there are curbside pickup programs, but the price is only known when you’ve purchased the items, besides this list making applications catered towards groceries exist, such as out of milk, which allow s virtual list to be built tht is more customizable and saveable than a written list.

Problem Statement Shoppers frequent these stores weekly and are quite familiar with layout and expected products. Crowdsourcing For the lack of insight on being able to conduct research about specific grocers and what theirs tore contains, most people develop a favorite tore they frequent mainly because they are familiar with the layout and what is offered at this store.

Solution Statement Create a useful shopping list application to serve as an organization tool for users, while collecting the information of products on their list to build a grocery product database. In short, the we want to create a consolidated source of information on local grocers and provide services where current applications are lacking which is for example the ability to compare prices of local grocers, and the ability to cut down on time spent searching through the store by knowing where each item is located on your list. In order to make this information more readily available to the public, we will build a collective database of each store’s products, placement of the products, and prices, through user contributed information on these products. Our solution to this goal is an application which will serve as the vehicle through which we will collect and analyze the data to improve the user’s experiences shopping. Animate the order of introducing the graphic, one by ione

Solution Workflow: Step 1- User Accounts Create user accounts for each individual Database saves user’s list data under their account The app will go hand in hand with the user’s shopping experience in two parts, the preparation phase before heading to the store where list creation happens, and the actual shopping. To accommodate the first phase, we will have designed a list making interface so that the user can have an electronically stored list that is easy to edit, save, and share. Crowdsourcing applications involve an incentive to motivate users to contribute and part of our incentive will be this easy to manage list UI. Once the user arrives at the store, they will need to check off and remove items from the list that they have collected. It is at this step that we will ask the user to enter details they found out about their item on site. For UI mention This includes the price of the item and the location of the item within the store This information will be stored in a database, along with the store it was found at, and once sufficient data is built about each store, we can improve future shopping experiences by analyzing their list and providing services powered by our new found data of the stores. As of now these services will be price comparisons of your list items between stores, and ordering their list based on a pathfinding feature that will display the best order to tackle their list within the store Animate this slide, in order of steps, Show where user’s end is,

Solution Workflow: Step 2 - List Creation User will create a new list Desired items will be entered and the list will be saved The app will go hand in hand with the user’s shopping experience in two parts, the preparation phase before heading to the store where list creation happens, and the actual shopping. To accommodate the first phase, we will have designed a list making interface so that the user can have an electronically stored list that is easy to edit, save, and share. Crowdsourcing applications involve an incentive to motivate users to contribute and part of our incentive will be this easy to manage list UI. Once the user arrives at the store, they will need to check off and remove items from the list that they have collected. It is at this step that we will ask the user to enter details they found out about their item on site. This includes the price of the item and the location of the item within the store This information will be stored in a database, along with the store it was found at, and once sufficient data is built about each store, we can improve future shopping experiences by analyzing their list and providing services powered by our new found data of the stores. As of now these services will be price comparisons of your list items between stores, and ordering their list based on a pathfinding feature that will display the best order to tackle their list within the store Animate this slide, in order of steps, Show where user’s end is,

Solution Workflow: Step 3 - Shopping Mode User will set shopping mode on and head to store of their choice Once at store Geolocation tools will recognize store and route product data to that store’s table Figure 1. List Creation Phase The app will go hand in hand with the user’s shopping experience in two parts, the preparation phase before heading to the store where list creation happens, and the actual shopping. To accommodate the first phase, we will have designed a list making interface so that the user can have an electronically stored list that is easy to edit, save, and share. Crowdsourcing applications involve an incentive to motivate users to contribute and part of our incentive will be this easy to manage list UI. Once the user arrives at the store, they will need to check off and remove items from the list that they have collected. It is at this step that we will ask the user to enter details they found out about their item on site. This includes the price of the item and the location of the item within the store This information will be stored in a database, along with the store it was found at, and once sufficient data is built about each store, we can improve future shopping experiences by analyzing their list and providing services powered by our new found data of the stores. As of now these services will be price comparisons of your list items between stores, and ordering their list based on a pathfinding feature that will display the best order to tackle their list within the store Animate this slide, in order of steps, Show where user’s end is,

Solution Workflow: Step 4 -Save Product Info When a user marks an item off their list, they will be prompted to enter location and price of item, or update price and location if change occured. Entry for product with price and location will be stored on cloud database (or entry will be updated if different) Figure 2. List Creation Phase The app will go hand in hand with the user’s shopping experience in two parts, the preparation phase before heading to the store where list creation happens, and the actual shopping. To accommodate the first phase, we will have designed a list making interface so that the user can have an electronically stored list that is easy to edit, save, and share. Crowdsourcing applications involve an incentive to motivate users to contribute and part of our incentive will be this easy to manage list UI. Once the user arrives at the store, they will need to check off and remove items from the list that they have collected. It is at this step that we will ask the user to enter details they found out about their item on site. This includes the price of the item and the location of the item within the store This information will be stored in a database, along with the store it was found at, and once sufficient data is built about each store, we can improve future shopping experiences by analyzing their list and providing services powered by our new found data of the stores. As of now these services will be price comparisons of your list items between stores, and ordering their list based on a pathfinding feature that will display the best order to tackle their list within the store Animate this slide, in order of steps, Show where user’s end is,

Solution Workflow: Step 5 -Provide Services With sufficient data, the preparation phase offers services Services include price comparisons for lists based on nearby stores; Shortest path for items in list Figure 3. Services Offered The app will go hand in hand with the user’s shopping experience in two parts, the preparation phase before heading to the store where list creation happens, and the actual shopping. To accommodate the first phase, we will have designed a list making interface so that the user can have an electronically stored list that is easy to edit, save, and share. Crowdsourcing applications involve an incentive to motivate users to contribute and part of our incentive will be this easy to manage list UI. Once the user arrives at the store, they will need to check off and remove items from the list that they have collected. It is at this step that we will ask the user to enter details they found out about their item on site. This includes the price of the item and the location of the item within the store This information will be stored in a database, along with the store it was found at, and once sufficient data is built about each store, we can improve future shopping experiences by analyzing their list and providing services powered by our new found data of the stores. As of now these services will be price comparisons of your list items between stores, and ordering their list based on a pathfinding feature that will display the best order to tackle their list within the store Animate this slide, in order of steps, Show where user’s end is,

Requirements Overview Key Requirements: A mobile app that is fun and easy to use, Shopping list capability, Crowd sourcing of user data, Minimal device impact Chris Talk about aqcuisition graphics! Mention managing of data remotely Animate,

Architecture Overview Figure 5. Chris Talk about aqcuisition graphics! Mention managing of data remotely Animate,

Implementation Overview React native deploys on both android and ios platforms which allows users to interact with the firebase data solution to pass data back and forth. Figure 6.

Prototype Review Usability: React native deploys on both android and ios platforms which allows users to interact with the firebase data solution to pass data back and forth.

Prototype Review Continued Functionality: React native deploys on both android and ios platforms which allows users to interact with the firebase data solution to pass data back and forth.

Challenges and Resolutions React-Native Custom Geolocation Malicious User Input Kris

Timeline Kris

Testing “It should be so easy to use, they won’t want to put it down.” Intuitive Responsive Attractive Kris

Conclusion Give customers an consolidated source of knowledge on local grocers via a shared database on stores and their products Thomas Strong conclusion Graphics, pop things up and summarize our technologies as well, Emphasize ease of use with UI, Emphasize the data management Show what user’s will do with the list In conclusion given our powerful tools, our app smart shopping looks to create a simple easy to use application that will have a simple to use UI that will improve the effiencieny of users shopping expierience.