Team

---

Joe Iaquinto [email protected] Brendan Courson [email protected]

Help from Chris Dower @Cdower

Drops-Phoenix

Customized with drop info and added new fields to view. Started work on modifying schema for use with Drop data.

Description

---

Drops is a flexible event planning web app that simplifies the process to the 5 W’s: Who, What, When, Where, Why, and How? A Drop created by a user can be as detailed or open-ended as they choose by allowing guests to suggest activities, locations, and times they are available. Drops provides a sleeker approach to gathering your friends and taking your group chat plans to the real world because Facebook events are too inflexible and cumbersome to set up. Facebook Events Yes/ Maybe/ No does not give reliable data on when you could reschedule to allow more people to join you. Drops will utilize a built in when-is-good system to help Drop creators democratically decide when is best. Other flexible meeting and event planning solutions like Fasterplan are geared towards the business world and lack integration with major social media platforms.

Goals

---

Create the main Drop screen

This will be the core of the user experience in Drops. Users create, edit, and interact with a Drop. It is critical that the Drop creation process be simple and quick to complete. Hopefully Drops can save people time and energy so they can come together with their friends and turn their online plans into real life experiences.

Getting Started

• Create barebones web-app
  • Using Phoenix-hipster-stack
• Create editable fields for the Drop ( 5 W’s)
  • 11/27: Modify schema to allow creation of Event names, locations, times, descriptions
  • Display schema information in updated cards
  • Create map of local Drop locations with pins displaying info
  • Sort events by closest upcoming times within x mile radius

Who?

• Enable Drop invitations
  • Hotlink individual drops in server with sharable links/ buttons
• Allow admins to set visibility on Drop
  • Private to link only

What?

• Allow Admins to set an activity for the drop
  • Name and description fields
• Populate field with searchable suggestions for Drop activities
• Enable straw poll suggestions from users
• Enable straw poll voting

When?

• Implement custom When-Is-Good system
• Allow Admins to adjust duration
• Allow admins to finalize time
• Notify users that responded to the when-is-good when time is finalized
  • Sign up for Drop updates via email

Where?

• Allow Admins to set a location or create a poll
• Add custom Where-Is-Good educated polling
• Google Places ratings
• Straw poll voting

Why?

• Text field for why the Drop was made

Home

Outside of the Drop screen, there needs to be a place to manage Drops and see what local public Drops are happening. There also could be a feed of Drops the user’s friends are going to.

• Allow users to view invites
• Allow users to view upcoming and past Drops
• Allow users to see local public Drops
  • Display on map with pins
• Allow users to see what Drops their friends are going to

Bonus Drop Features

• Advanced Drop permission control
• Allow admins of the Drop to be set other than the Creator
• Enable commenting on Drops
• Stickied comments for Admins

Moonshots

• Make web and mobile web friendly
• Venmo or Tilt integration for Drop funding
• Add Messenger and Slack Drops integration to create a drop right from a group chat
• Automatically make a messenger group/ slack channel for the Drop.

Forked from Phoenix hipster stack!

• [Phoenix] (http://www.phoenixframework.org/)
• [React] (https://facebook.github.io/react/)
• Relay
• GraphQL
• RethinkDB
• Webpack
  • Hot module reload
• Immutable.js
• Flow
• Eslint
• Jest
• Docker

Getting Started

Clone this repo then:

1. Install dependencies with mix deps.get && npm i
2. Start rethinkDB rethinkdb
3. Start Phoenix endpoint with mix phoenix.server
4. Create database by going to localhost:4000/reset
5. Visit localhost:4000/graphql to test the amazing graphiql interface
6. Query the database

query myQuery{
  store{
    authors {
      id
      name
    }
  }
}

7. Visit localhost:4000 for a basic relay app using the data.

Jest is not implemented. Feel free to contribute :)

DOCKER

1. docker-compose build
2. docker-compose up
3. visit localhost:4001/reset
4. visit localhost:4001

When changeing the graphql schemas run mix CreateSchema to make a new schema.json. This schema.json is used by Relay.

Running in production.

MyAwesomePrompt> MIX_ENV=prod mix compile
MyAwesomePrompt> MIX_ENV=prod mix phoenix.digest
MyAwesomePrompt> MIX_ENV=prod PORT=4000 mix phoenix.server

###Used resourses

• phoenix-hipster-stack
• updated-phoenix-webpack-react-setup
• GraphQL & RethinkDB
  • GraphQL-Elixir
  • plug_GraphQL
  • [graphql-phoenix-rethinkdb] (https://github.com/AdamBrodzinski/graphql-phoenix-rethinkdb)
  • phoenix-rethinkdb-example