Pretty big task, not entirely necessary either, however it would help improve the readability of the map. The goal is essentially to have a real-time update of the buses and shuttles on the map like the cdta website or rpi shuttle tracker.

Unfortunately, the actual google map widget in flutter just uses the default map view for the operating system, so it's not actually written in dart/flutter which means we'll have to code up some platform specific stuff if we want to animate the markers, and use a platform channel in flutter to display that (most likely requires redoing all of the map ui we've written so far).

Other option, we can fork the plugin repository and try to create this system from the ground up and submit a pull request. Seems way harder, but will help the flutter community in the future. This way we'll also be able to just integrate our changes with what we've already coded in smartrider.

Either way, here is an example someone made that contains platform specific code for animating markers in flutter. Potentially super helpful.

https://github.com/Dammyololade/flutter_marker_animation

Last option, we use the projection api to build the marker widgets on a layer over the map. Takes a lot of computing power since we have to listen for any changes in the positions on the map and update where the markers are drawn. Animations would most likely be pretty slow, but if we can't make the other two options work then it might be our only choice.

When scrolling down on the schedule page, the entire schedule panel moves. The schedule panel should be static when scrolling through the schedule options, but move when the user scrolls the upper tab of the schedule panel.

When I tested the app on the iOS simulator, the sliding panel wouldn't actually slide, it just sort of stayed in whatever position you left it and I was unable to interact with the shuttle schedules.

Not sure if this is an issue with just the simulator, hopefully someone with a Mac can check the issue out. I wasn't able to run the app on a physical device because of the version bug, so hopefully it only happens on the simulator. I haven't seen this issue reported on the sliding panel repo.

Description Bus indicator icons are not showing up on the map.

To Reproduce Steps to reproduce the behavior:

1. flutter run in the dev environment
2. toggle bus routes

Expected behavior Should be able to see bus indicators on map...

Device (please complete the following information):

• Device: Nexus 3

1. Add map icons to the legend (i.e. bus markers for the bus page, shuttle markers for the shuttle page, etc.)
2. Adjust the size using sizer, and make legend resize depending on contents.
3. Fix animation; when the legend is opened or closed, the position of the button moves briefly (see below)

Not sure if this is an iOS only bug or on both iOS and Android New users get added to the Authentication tab, but not to the Firestore tab User data only gets stored to onboard app cache Pretty sure it has to do with Issue #36, where registering crashes the app

Is your feature request related to a problem? Please describe. Right now, the schedule page is pretty confusing if you just want quick information on the next couple of buses or shuttles. We need a system that can allow you to quickly check the next couple of times for a given stop.

Describe the solution you'd like I'm thinking that we replace the current schedule sliding panel with something similar to the cdta bus website. Something like this:

You can click to expand a stop, and each stop will list the next 5 pickup times with an estimated arrival time. We can then move the current schedule page to floating button if someone wants to see the full schedule.

Additional context Gonna involve a lot of work manipulating the bus GTFS and shuttle data. We can start by designing the UI first, and then once the GTFS is modeled (see #24) we can start filling out the page.

See https://api.flutter.dev/flutter/widgets/AnimatedContainer-class.html and https://api.flutter.dev/flutter/material/ExpansionPanelList-class.html for ideas on how to implement the animated expansion list.

Need to complete integration of the bus GTFS data into the bloc refactor (see here or here for info about bloc pattern). Involves creating a repository and provider class to fetch the data, and model classes to decode and turn the data into usable objects. Look at shuttle bloc and shuttle data for examples.

Static and Realtime (RT) data are modeled differently, see https://gtfs.org/reference/static/ and https://gtfs.org/reference/realtime/v2/

Bus data links:

• GTFS Static Data : https://www.cdta.org/schedules/google_transit.zip
• GTFS RT Data – Trip Updates : http://64.128.172.149:8080/gtfsrealtime/TripUpdates
• GTFS RT Data – Vehicle Positions: http://64.128.172.149:8080/gtfsrealtime/VehiclePositions
• Service Advisories: https://www.cdta.org/service-advisories/json

Ideally, static data would only be downloaded and unzipped once during the app's first sign-in, and then whenever we push an update to the app. Real-time data should be fetched every couple of seconds, and used to update vehicle positions and route alerts. Probably have to branch off to a separate issue for this, once modeling is finished.

Right now they go over themselves which makes the dotted lines look solid sometimes, and they don't perfectly follow the roads.

Probably involves redoing the polyline coordinates for the bus routes, being extra careful to follow the roads and not double cross.

Describe the bug Prior to the shuttle tracker overhaul there seem to be multiple shuttle routes active simultaneously. Right now it seems there's only one route active and no "route name" field in the shuttle tracker API response. Therefore we can probably hard code the route name (e.g. Main Route).

To Reproduce Steps to reproduce the behavior:

1. Go to shuttles
2. Scroll down to see the route name ( right now it's using the ID field in shuttle tracker API response).

Expected behavior Route name should be Main Route or something along the line.

Device (please complete the following information):

• All

Notifications work, but still lack the following features:

• Should remind the user 1-2 minutes before arrival, and when the ride arrives.
• We should have notifications for saferide vehicle updates (i.e. when driver accepts ride, when about to pickup, etc.)
• Tapping the bus/shuttle notification should zoom into stop on map.

There is currently no option for users to reset their password.

• Users should be able to click 'forgot password' on the log in screen
• An email should be sent to their rpi email address, would have a link to change their password

Is your feature request related to a problem? Please describe. Navigating all the stops in the schedule page kinda sucks.

Describe the solution you'd like Enhancement for the schedules similar to the cdta website's proximity indicator, where we show a bus icon instead of the circle on stops which currently have the bus or are about to. Additionally we should scroll the schedule to the closest stop to the user.

https://www.cdta.org/schedules-route-detail?route_id=87

Is your feature request related to a problem? Please describe. Since rpi requires you to log into a VPN to access email off campus now, signing up for the app with the current email authentication is kinda painful if you're not on school wifi.

Describe the solution you'd like We might want to consider using rpi's CAS authentication service instead, but only if we can ensure the user stays logged in. Probably requires setting up another cloud function to generate auth tokens for firebase.