falldownthesystem / recycle4me Goto Github PK

Authentication is based on Firebase, using https://github.com/angular/angularfire2 library (same as database).

• Registration only with Google or Facebook account

• Registration and logging in happens on the front page view

• Logout button in the header, along with "Logged in as _________".

• Only logged in users are authorized to access the pick-up request, redirect to home page

We will use Firebase for the backend, using the https://github.com/angular/angularfire2 library.

• Has a dependency on RxJS observables: https://github.com/ReactiveX/rxjs

• We will need databases for:

  • Users
  • Pick up requests
  • Scheduled pick-ups
    • Routes (list of userpoints)
    • Times
    • Something else?

Two elements side by side:

• A map where you can select your pick-up address by clicking on map(+ ability to type in an address)
• Request form:
  • Address
  • Description of items that need pickup
  • Estimated weight / volume
  • Available time of day for pick-up

Create routing for all the views.

Test that all the generated components work.

Create the template / framework / scaffolding where the rest of the views (content) is placed in.
This includes any possible header, footer, navigation, etc.

• Header:

  • (Logo, Title) < left aligned; Logged in as ___ [Logout] > right aligned.

• Footer:

  • Name of app, copyright, creators / credit, dependencies used, some links, etc, very small font.

The project will use Bootstrap for the layout only

• https://getbootstrap.com/docs/4.0/getting-started/introduction/

Angular material components:
https://material.angular.io/components/categories

Generally following the material theme guidelines:
https://material.io/guidelines/

More information about material theme and useful resources:
https://material.io
https://material.io/icons/
https://material.io/color/#!/?view.left=0&view.right=0

Since we have so little time, we will not prototype anything first, instead the the design of specific views if left mostly to the developer.

The actual css is preprocessed with sass, more specifically scss
http://sass-lang.com/guide

Recycle4Me is a recycling service, which lets users request a recycling pick up to their home. The service looks for certain number of requests within an area, and then schedules a pick-up time and plans a route. The users are notified of an incoming pick-up, and asked if they are available for the pick up, or can leave their recyclables outside.

Application overview:
The angular application is composed of components with html templates, and typescipt controller, as well as services which can be injected for specific components.

Our application has three components besides the main app component

• Front page
• Information
• Request pick-up

Two services:

• Google maps
• Authentication

And a realtime database at the backend.

Plan and create specs for all the main tasks for the project implementation

• Static information about how to recycle
• Categories of recyclables (paper, waste, cardboard, clothes, glass, whatever)
• A Google maps view based on users location (geoloc) that shows all nearby recycling centers

This issue will be implemented only if Firebase + Auth + Google Maps don't get counted for 3 API's.

• Fetch weather information from an API, for a specified pick up location (whichd date/time?)
• Notify user if it will be raining, when requesting pick up (or when scheduling delivery)?

What gets done with all the requests stored in the database.

• Admin view where all of the requests get stored in a database.
• Automated pick-up plan after x amount of requests within certain distance of each other?
  • Notification to users?
  • Archiving old requests, deleting?
• Actual path planning or just going from nearest to nearest?
• How is the area where pick-ups are considered decided?

Using https://angular-maps.com

• We will have two Google maps views, one for choosing your location for a pick-up, and second for showing all recycling centers near you (on the information view).

Users need to get a notification when their items are ready to be pick-up.

The first view shown to both logged in users and guests.

• Generic information about the service
• Login / Register forms for non logged users
• Maybe user information for logged in users?