Visual UI for updating parameters to the /events endpoint. Save/Apply button should:

• call API
• push all events from API into redux store
• go back to event lister

User Initialization Process

• Specify the requirements to onboard a user.
• Develop a frontend flow.
• Develop backend schema to accommodate.

Frontend:

• React Native
• Redux

Backend:

• Python
• Docker
• Postgres on GCP
• SQLAlchemy

Make it more beautiful :)

• Move filter button to menu bar
• Distance and start date in cells

Set up Redux and create store for events

Create API client and add a method for pulling events based on location.
Pull these events and place into Redux store when the app starts

Eventador presentation slides
Backend API Documentation

Must display:

• Title
• Map with pin at location
• Start time
• End time

Cell displaying event info and onPress going to event info page, passing along the event info/id so the info view can render correctly

Takes a list of events from a redux store and renders a scrollable list of ListItem components

@jordanschalm commented on Fri Oct 06 2017

Install and setup navigation library.

Views:

• Home screen
  • only shows u when not logged in
  • button to login with OAuth
• Event list screen
  • Scrollable list of events
• Event filter screen
  • Change filters for events
• Event info screen
  • View all info for an event
  • button to RSVP

Design a schema for storing application data. Models that must be represented are users and events.

EventBrite Client

• Write a small Eventbrite client for the backend.

Login/Auth Process

• Add a login process using Facebook or Google.
• Create a login screen for the app.

... and pop it into a redux store

Show all the info about an event in a screen. This is where we go when someone selects an item in the event lister

if you use it between 3 and 3:01 am local time it plays OG Kush Diet by 2 chainz

Back End Initialization

• Start up a Flask + SQLAlchemy app.

Implement page with a list of events, pulled from a redux store

Weekly progress report, which should include a description of:

• deliverables for the week,
• plans for the next week,
• major decisions and changes in the scope of the project,
• contributions of the individual team members.

Starting next this week, you may also attach extra material (i.e., your actual deliverables, such as use case and design diagrams) to the reports, as an appendix.

Document here

Submit here

Draft a formal specification for the web API, including supported endpoints, success and error conditions, and formats for payloads.

Weekly progress report, which should include a description of:

• deliverables for the week,
• plans for the next week,
• major decisions and changes in the scope of the project,
• contributions of the individual team members.

Starting next this week, you may also attach extra material (i.e., your actual deliverables, such as use case and design diagrams) to the reports, as an appendix.

Document here

Submit here

Weekly progress report, which should include a description of:

• deliverables for the week,
• plans for the next week,
• major decisions and changes in the scope of the project,
• contributions of the individual team members.

This week you have no deliverables, but can report on everything else.
Starting next week, you may also attach extra material (i.e., your actual deliverables, such as use case and design diagrams) to the reports, as an appendix.

Document here

Submit here

Front End Initialization

• Start up a React Native app.

Weekly progress report, which should include a description of:

• deliverables for the week,
• plans for the next week,
• major decisions and changes in the scope of the project,
• contributions of the individual team members.

Starting next this week, you may also attach extra material (i.e., your actual deliverables, such as use case and design diagrams) to the reports, as an appendix.

Document here

Submit here