shemetz / googleworkshopproject Goto Github PK

This tutorial should fit: https://developers.google.com/maps/documentation/javascript/examples/directions-waypoints

Passenger can enter:

• Where I come from - suggests "Current location" and "Choose on map..."

And optional fields: (should have the word "optional" near/in them, or something similar)

• Am I bringing something extra? (e.g. a snack, music)
• Extra notes? (e.g. big suitcase)

Do a very simple project (in whatever language, e.g. python) to get some basic data from the Facebook API, like the name of a profile or some extra details. Would be great if we can already get event data.

Floating action buttons: ➕/➖, 🚫, 🕑
Clicking a pickup "selects" it and moves camera and displays title+snippet (default behavior of the "return false" thing)
➕/➖ adds/removes from path (things in path will be confirmed at end)
🚫 will decline
On the bottom of the screen, show total estimated time. For each passenger, edit its snippet to be the time when getting to them, replacing previous value.

So passengers can join existing rides.

it's already done, but this should have had a GitHub Issue to represent it.

Took about 3 hours, or 8 hours including all the bugfixing and refactoring.

Server functionality is two things: have all the database tables and send notifications.

Should probably be using Flask or Django. Maybe we should look at MongoDB.

Get by ID
Get list of events for this user,
Create a new ride object
Add user to ride (create pickup object)

currently they should just use some mock data, and in the future they should actually make calls to the servers.

decide on name of tabs:
app events - already opened groups
all facebook events - different color for events already existing in app (database) and not.
my rides - list of all rides ordered by date regardless of whether the user is driver or passenger

My events, My pending rides and/or my confirmed rides and/or my past rides.

maybe a "Recents" list?
maybe an "import event + link" button?

Update screens for milestone 1 : https://xd.adobe.com/view/d188914d-4e84-44dd-656b-da7f8b55797c-a7b9/

This activity should take a ride ID number in the intent extras, use it to get the ride (use mock data right now), and show details about the ride using this UI more or less: https://xd.adobe.com/view/d188914d-4e84-44dd-656b-da7f8b55797c-a7b9/

help link https://medium.com/@crossphd/android-image-loading-from-a-string-url-6c8290b82c5e

After you submits a new ride you see the new ride you've just created. When you press back, you should go back to the available rides and NOT back to the form (NewRiderActivity).

When entering an event's page, the first thing a user should see is "Are you a passenger or a driver?". Riders will go to the "Drivers" tab. Drivers will go to the "Add new ride" activity, and afterwards, to the "Riders" tab.

took about 20 hours work

Everyone who isn't a driver should appear in the "riders" list. If they have a confirmed ride they will be gray, or green, or have an outline, or be half translucent, etc.

Drivers can click (or long-click) the user to send the user a notification/alert such as "<driver_name> is offering to give you a ride!". This notification will be visible in the "Alerts" activity and the user can see it there to quickly go to the ride's page.

Drivers should get a lot of points, with possible bonus for long-distance rides or filling up all seats or points per rider. Example: 10 × number of passengers

Riders should get a few points. Example - 1 × ride, with a bonus if they bring a snack.

All people should be able to see their amount of points. Maybe users with a lot of points should be marked with a nicer picture or a crown or a colored outline or something.

Event name, location, date+time, link to facebook (maybe in menu)