Proposal
- Servers are not getting their fair share of the tips they earn from customers.
- Allows 100% of tips to go directly to the server of choice instead of being split up amongst other employees/staff.
- TipEase: Serving the Servers
- OR
- TipEase: We Serve Servers Features
- Functioning Log in page
- Navigation on all pages
- Home Page
- List of possible Servers
- Marketing Page (About Us)
- Service Worker Page
- Profile for individual service worker
Optional but highly recommended Please refer to this document: Build Weeks: Planning & Design Worksheet (How to build a beautiful application) What design system will you use?
- Redux
- React
- Styled Component
No
No
You can gather information about the data set you’ll be working with from the project description. Be sure to collaborate with your PM, and your Backend Architect to chat about the resources you have.
Write a description for what the DS problem is (what uncertainty/prediction are we trying to do here? Sentiment analysis? Why is this a useful solution to a problem?)
A target (e.g. JSON format or such) for output that DS students can deliver to web/other students for them to ingest and use in the app
- Servers and their customers
- “Its amazing and convenient” -Kayla
- TBD
Research thoroughly before writing a single line of code. Solidify the features of your app conceptually before implementation. Spend the weekend researching so you can hit the ground running on Monday. Prototype Key Feature(s)
This is the “bread and butter” of the app, this is what makes your app yours. Calculate how long it takes to implement these features and triple the time estimated. That way you’ll have plenty of time to finish. It is preferred to drop features and spend more time working on your MVP features if needed. See Trello: https://trello.com/b/6kGo0ePS/tipease-buildweek