KaiAnnFletcher/ShopHopping

ShopHopping

Background

ShopHopping is a grocery store planner and item locator that helps customers retrieve items in the store.

Real World Problem:

Supermarket giants like Costco and Walmart regularly move items around in the store in an attempt to make customers walk around the store longer. This is to manipulate shoppers into buying and trying new products.

Solution:

Our app offers customers the ability to ignore the sneaky ways supermarkets tricks people into spending more money and spend as little time as possible in the store, and get only what you need.

UX/UI Breakdown:

First of All. All users can sign up here: After finishing sign up, users can sign in here: Then, users will be directed to the dashboard page. Users may type the grocery items they want to brought

Overall UX:

Technology, Tools and Architecture

API - Walmart and Costco, Grocery APIs (note-to-team: must not expose sensitive API key information on the server)

https://developer.walmartlabs.com/docs
https://www.programmableweb.com/category/grocery/api 
http://www.supermarketapi.com/

Folder structure meets MVC Paradigm
Web Server - Node and Express
MySQL Database and ORM
Have both GET and POST routes for retrieving and adding new data
One New Library, Package or Technology - Passport.js and ESLint
Authentication - Member sign-in
Polished Front End / UI
Design & Sketch - Balsamiq
Testing - Travis CI
Deployment using Heroku (with Data)
Meeting good coding standard (indentation, scoping, naming)

Directory Structure

All the recommended files and directories from the steps above should look like the following structure:

.
├── config
│   ├── passport
│   │   └── passport.js
│   └── config.json
│
├── db
│   └── sequelize_passport.sql
│
├── models
│   ├── example.js
│   ├── index.js
│   └── user.js
│
│
├── public
│   ├── assets
│   │   └──images
│   ├── js
│   │   └── index.js
│   └── styles
│       └── styles.js
│
├── routes
│   ├── apiRoutes.js
│   ├── auth.js
│   └── htmlRoutes.js
│
├── test
│   ├── unit.js
│   └── ci.js
│
├── package.json
│
├── server.js
│
└── views
    ├── layouts
    │   └── main.handlebars
    ├── 404.handlebars
    ├── index.handlebars
    ├── signin.handlebars
    └── signup.handlebars

Some Improvements

Database for users' search history
PathFinder + browserify: Possible Approach
1. create the grid;
2. overlap the grid with the floor plan
3. create database for the floor plan
4. mark different section of the listed categories in the floor plan
5. deploy pathfinder
Database for the map
Handlebars for Server-Side Templating
Incorporate Authentication (JSON Web Tokens, Sessions, Etc)
Use an existing public dataset to power the database Create a migration strategy _{© May 2019: Kathy, Kai-Ann, Brij and Paul}

KaiAnnFletcher / ShopHopping