Plan

[MickMelon]

Plan

[MickMelon]

Users create an account that is stored in a remote database.
Users can add a desired destination.

Desired destination will have following details:

• User who created it
• Pickup location
• Times and dates needed
• Recurring

Users can specify whether they have a car and available for car sharing
Users can add a current destination

Current destination is like desired destination, but it is created by somebody who already has a car and drives the route already. Will contain the following details:

• User who created it
• Route taken (start to end)
• Times and dates
• Recurring
• All users on the route
• Route including all user stops

GPS awareness to work out a suitable route to pick up all people on the course.

StartupActivity: Checks if the user is logged in (shared preferences maybe? Needs to be secured). If they aren’t get them to login or register.
LoginFragment
RegisterFragment

MainActivity: The main shit with the navigation drawer
HomeFragment
SearchRoutesFragment
CreateRouteFragment
CurrentRoutesFragment
Logout (prob doesn’t need to be fragment)

ViewModel and Room is good to use for the route view because you want the data to persist even if the internet connection is lost. This is very important for this app. Should utilise Google Maps GPS route creator thing. But I can’t use Room with the remote database, so might be a bit shit, but it must work with remote database because they said that’s a case hmm

Send reminders for routes.
Send notification if someone wants to join or leave route.
Ability to cancel route for that day.
Contact details for driver of route.
Send notification to route passengers when driver is near.
Ability for driver to say they can’t do the route today
Have backup drivers
Possibly have to store route locally temporarily in case internet connection is lost

Use dummy data for other users on route to present.

Need to figure out way to demonstrate the GPS awareness

Use cases:

• Search routes
• Add route
• Cancel route
• Login
• Register
• Remove route

[MickMelon]

v1 will just have enough to satisfy assessment requirements to get A+

• Full UI
  • List of available routes (no search yet)
• Login and register
• Add route with stopping locations to pick people up and the final destination
• Have Google maps calculate the best route from the driver's position
• Store current route data locally (make sure it can still be used when offline)
• Store it all in a remote database
• Reminder notifications
• Driver can add other users to the route
• Need some contact options for the route creator

v2 will improve:

• Messaging within app
• Request route
• Request to join a route
• Search routes

The problem is needing to send notification to other users. Can check periodically for changes. Would be annoying as fuck, I don't like that idea. Probably the only way...

[MickMelon]

How about a vehicle trading app instead of car share.

Wouldn't need to calculate the route, and lets face it, steal some code.

The GPS awareness could get where the user currently is and calculate time and distance to the selling location.

Remote database driven through the Rest API.

Local storage for ads that haven't been published yet?

Sounds easy enough to me.

Takes away the needless complication of calculating routes and designating drivers, sending notifications between users, etc.

[MickMelon]

• Login
• Register
• Browse Vehicles
• Search Vehicles
• Add Vehicle
• Remove Vehicle
• Update Vehicle Details
• Publish Ad
• Contact Seller
• Get Distance to Seller

[MickMelon]

All the screens needed:

• Screen to browse all the vehicles
• Search (could be incorporated with above screen)
• Login / Register for uploading ads
• View single vehicle
• Create ad
• Edit ad
• Edit seller details

Will have a navigation drawer available for all screens (I guess except Login/Register so we can demonstrate passing data to the main activity, perhaps telling it that login is successful)