Show the static GTFS schedule so riders can plan their trip further in advance.

If a user opens the app out of Ames, it is useless to have the map move to them. Setup a rule to not move the map to the user if they are outside Ames.

Here is the function that automatically moves to the user's location on Map load.

Proposed borders

West longitude: -93.79180211954629
East longitude: -93.50245309137533
North latitude: 42.11249786499128
South latitude: 41.94664427464395

Tapping on a stop occasionally crashes the app. The behavior is not consistent or reproducible, but has been observed on multiple stops.

Often times, bus users follow a schedule each week. Allowing the user to configure a default route to be shown based on their location and/or time of day would improve user experience.

The user should be able to specify multiple settings:

• Days of week
• Time of day
• Location (maybe a pin on map or draw a region?)

Example user goals

"I want to get on 21 Cardinal whenever I am at my apartment at Freddy Court."
"I want to see 1 Red West when I am near student services on Wednesdays from 10:00am - 12:00pm."

Add the ability for a user to subscribe to a notification X minutes before a bus arrives.

Steps to Reproduce

1. Open the app
2. Select Gold South
3. Select the stop at Friley

Expected Behavior

The app shows upcoming arrivals at Friley.

Current Behavior

The app crashes.

Add an option to the map that shows all stops. This way the user can find routes near them, no matter where they are in Ames.

Reported by Google Play Store crash reporter.

Looks similar to:
expo/expo#17426

If you are unsure what bus you need to take, the ability to see all routes and stops on the map at one time would be useful.

When the user opens the application, all routes are flashed temporarily before switching to favorites. Nothing should be shown before making the decision.

When marking a route as favorite, it can be difficult to press it. The touchable area should be larger.

The app randomly breaks and gets stuck on loading screen. Clearing app data seems to fix the issue.

"When opening the app, it loaded to the map screen like normal but then jumped back to the loading screen."

Affected version: 1.2.0

Anyone able to reproduce, please share!

Test the current user experience when using TTS and optimize the experience.

Route sorting is not always correct.

See image below. Correct order is North, South, regular.

When people click to email from the app, %20 is included in the subject and isn't automatically converted to a space.

Prior to selecting a route, the map is buttery smooth. Once a route is selected, it is glitchy.

Reproduced on a Galaxy S10+.

A few things have changed since last updating app screenshots. They should be updated in the Readme file and the Play Store.

The minutes until a bus arrives can differ from the time shown due to hidden seconds. The number of minutes until a bus arrives should be shown based on the expected time of arrival.

On Brows South, the route is different on the weekend.

When a user clicks Brows South, it should show the proper map of the route, instead of the weekday route.

This will require determining the correct pattern to follow when showing a route.

Steps to Reproduce

1. Open the app
2. Select Gold South
3. Select the stop at Friley

Expected Behavior

The app shows upcoming arrivals at Friley.

Current Behavior

The app crashes.

Now that #89 is in, screenshots need to be updated in the README and for the app stores.

If you hit the home button, wait 30 seconds, then switch back in, the vehicles are outdated for up to 5 seconds. When the app is switched back into, it'd be great to automatically refresh before the 5 second interval.

Depending on internet connectivity and speed, the routes can be slow to load.

When viewing upcoming arrivals for a certain stop, add a user configurable option to show only arrivals from favorite routes.

Why?

When looking at the list of upcoming arrivals, there can be many irrelevant buses shown. This allows the user to focus on what is important to them - finding the bus that meets their needs.

Proposal

A small icon is shown on the drawer that appears when a stop is selected. It allows the user to toggle between showing all arrivals and only those for their favorite routes.

There needs to be an easy way to display a banner to users.

Context: The company contracted to monitor CyRide busses is currently experiencing an outage. It would be great to be able to show a short message to users explaining why the app is not working.

Yellow arrivals are at the top of list when they shouldn't be present at all.

A favorite stop would display on the map, even without a route selected.

The app was published to the Play Store on October 1.

https://play.google.com/store/apps/details?id=com.demerstech.amesride

Currently, the app works fine but an exception is thrown internally.

Possible Unhandled Promise Rejection (id: 0):
Error: Not authorized to use location services.

Seeing a number of occurrences of the following error:

Exception java.lang.RuntimeException:
  at android.app.ActivityThread.performResumeActivity (ActivityThread.java:4657)
  at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:4690)
  at android.app.servertransaction.ResumeActivityItem.execute (ResumeActivityItem.java:52)
  at android.app.servertransaction.TransactionExecutor.executeLifecycleState (TransactionExecutor.java:176)
  at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:97)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2267)
  at android.os.Handler.dispatchMessage (Handler.java:107)
  at android.os.Looper.loop (Looper.java:237)
  at android.app.ActivityThread.main (ActivityThread.java:8167)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:496)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1100)
Caused by java.lang.reflect.InvocationTargetException:
  at java.lang.reflect.Method.invoke
  at expo.modules.ReactActivityDelegateWrapper.invokeDelegateMethod (ReactActivityDelegateWrapper.kt:237)
  at expo.modules.ReactActivityDelegateWrapper.onResume (ReactActivityDelegateWrapper.kt:126)
  at com.facebook.react.ReactActivity.onResume (ReactActivity.java:58)
  at android.app.Instrumentation.callActivityOnResume (Instrumentation.java:1454)
  at android.app.Activity.performResume (Activity.java:8111)
  at android.app.ActivityThread.performResumeActivity (ActivityThread.java:4647)
Caused by java.lang.NullPointerException:
  at java.util.Objects.requireNonNull (Objects.java:203)
  at expo.modules.location.LocationModule.handleForegroundLocationPermissions (LocationModule.java:844)
  at expo.modules.location.LocationModule.lambda$requestForegroundPermissionsAsync$2$expo-modules-location-LocationModule (LocationModule.java:195)
  at expo.modules.location.LocationModule$$ExternalSyntheticLambda17.onResult
  at expo.modules.adapters.react.permissions.PermissionsService.createListenerWithPendingPermissionsRequest$lambda-22 (PermissionsService.kt:271)
  at expo.modules.adapters.react.permissions.PermissionsService.$r8$lambda$Xtr9_3ibuLGU1WXILaGyswj4Ze0
  at expo.modules.adapters.react.permissions.PermissionsService$$ExternalSyntheticLambda0.onRequestPermissionsResult
  at com.facebook.react.ReactActivityDelegate$2.invoke (ReactActivityDelegate.java:198)
  at com.facebook.react.ReactActivityDelegate.onResume (ReactActivityDelegate.java:123)

Show a tooltip when a button is held down.

The main button I'm thinking this is needed for is the filter icon that is displayed on the stop details component.

When selecting a favorite route, there are issues if the routes were not added in descending order.

Steps to reproduce:

• Clear your favorites
• Favorite 1 Red West
• Favorite 1 Red East
• Click the top most row, 1 Red East

Notice 1 Red West shows up as being selected.

Seeing a number of occurrences of the following error:

Exception com.facebook.react.common.JavascriptException:
  at com.facebook.react.modules.core.ExceptionsManagerModule.reportException (ExceptionsManagerModule.java:72)
  at java.lang.reflect.Method.invoke
  at com.facebook.react.bridge.JavaMethodWrapper.invoke (JavaMethodWrapper.java:372)
  at com.facebook.react.bridge.JavaModuleWrapper.invoke (JavaModuleWrapper.java:188)
  at com.facebook.jni.NativeRunnable.run
  at android.os.Handler.handleCallback (Handler.java:942)
  at android.os.Handler.dispatchMessage (Handler.java:99)
  at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage (MessageQueueThreadHandler.java:27)
  at android.os.Looper.loopOnce (Looper.java:226)
  at android.os.Looper.loop (Looper.java:313)
  at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run (MessageQueueThreadImpl.java:228)
  at java.lang.Thread.run (Thread.java:1012)

When switching from a route with buses to a route without buses, the buses from the original route are not removed from the map.

When arrivals are being fetched, show a small loading line to indicate they are being updated.

Add a pre-commit hook to format code.

Settings page should be navigated to through a hamburger menu (slides out from left).

On settings page, there should be (at this point)

• link to GitHub repository
• email for user feedback/bug reports (is there a better way to do this than having a gmail?)
• Disclaimer that data is provided by GMV Syncromatics. Accuracy not guaranteed.

When in a different timezone than Central, the minutes until arrival are incorrect. These should either be passed from the backend or calculated on the frontend while respecting timezone differences.

Current Behavior

If the bus is arriving in 10 minutes, someone on the west coast will see 130 minutes due to being two hours behind.

Expected Behavior

If the bus is arriving in 10 minutes, someone on the west coast will see 10 minutes until arrival.