https://github.com/rocity/event-buddy
🎉 Event Buddy App from https://designchallenge.xyz/event-buddy-app
https://github.com/rocity/event-buddy
ngx
Last synced: 15 days ago
JSON representation
🎉 Event Buddy App from https://designchallenge.xyz/event-buddy-app
- Host: GitHub
- URL: https://github.com/rocity/event-buddy
- Owner: rocity
- License: mit
- Created: 2018-06-21T21:08:05.000Z (almost 8 years ago)
- Default Branch: master
- Last Pushed: 2018-06-22T10:00:56.000Z (almost 8 years ago)
- Last Synced: 2025-03-22T03:12:19.927Z (about 1 year ago)
- Topics: ngx
- Language: TypeScript
- Homepage:
- Size: 5.6 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Event Buddy App
https://designchallenge.xyz/event-buddy-app
## Overview
Sometimes people want to go to an event (concert, museum exhibit, etc.) that none of their friends are interested in. These people might not want to experience the event alone, so they forego the opportunity. Create an app to allow people like this to find one or more person to go to the show with them.
This mobile application is about making friends and spending time with people, so consider what people might want to learn before messaging others to go to the event together. It should feel like a safe environment, so think carefully about the application design and available features.
Please propose a design for the event search, user profile, and event meetup confirmation while keeping in mind the overall functionality and structure.
## Features
The application could include:
Profile pictures.
Previous events.
List of tastes and hobbies.
Ticket-splitting.
Keep in mind that these are not the only features that might be required, and you should use your initiative to ensure a usable and interesting experience.
## Please Prioritize
Good usability.
Appropriate aesthetics for the demographic, tone, mobile/touch paradigms, etc.
Insight into your process, including any sketches, brainstorms, notes, wireframes, and assumptions on the product.
# Mockups
[MOCKUPS](./MOCKUPS.md)
# Installation
## Django
Run `pip install -r requirements.txt`
## Angular
Run `yarn install`
# Django Development
| Tech | Version |
| ---- | ------- |
| Python | `>= 3.5.2` |
| Django | `2.0.5` |
# Angular Development
| Tech | Version |
| ---- | ------- |
| Node Version | `v9.10.0` |
| Typescript | `2.7.2` |
| NPM Version | `5.6.0` |
| Angular CLI | `6.0.3` |
| Angular | `6.0.2` |
| Package Manager | `yarn v0.27.5` |
## Development server
Run `ng serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.
## Code scaffolding
Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.
## Build
Run `ng build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `--prod` flag for a production build.
## Running unit tests
Run `ng test` to execute the unit tests via [Karma](https://karma-runner.github.io).
## Running end-to-end tests
Run `ng e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).
## Further help
To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
# Production
## Building
Run `npm postbuild` to build the angular app in the server.
# License
[MIT](./LICENSE)