The current method of hiding / showing stations near the user is:

• User denies location tracking (hide stations near user):
  • A height constant (connected to the "Select a station near you" text field and 5 radio buttons) is set to 2. This is not set to 0 because radio button's height cannot be less than 2. This is admittedly a bit hacky 👎
  • "or choose from the list" becomes "Choose a station from the list"
• User accepts location tracking (show stations near user):
  • The height constant is set to 23
  • The choose from list text field is "or choose from the list"

Ideally, remove the text field and the radio buttons from the view when location services are denied, and add them to the view when location services are accepted.

Show alerts for when there are advisories/alerts/etc. This could be especially useful for the current SafeTrack schedules.

Add an indicator to show the estimated time to walk to the station.

Before:
Select a station near you

• Greensboro
• Tyson's Corner
• Spring Hill
• etc

After:
Select a station near you

• Greensboro (6 minute walk)
• Tyson's Corner (10 minute walk)
• Spring Hill (12 minute walk)
• etc

Find a cool dot matrix font and use that to make the widget look exactly like the signage in metro stations.

It would be nice if there was a space separating the trains that travel in opposite directions (known as "groups"). This would make the predictions easier to read, especially in stations with two levels, such as Metro Center.

If a station is selected in settings, and then either the home or work shortcut is used, the next time the widget is loaded, it will show the station selected in settings, and not the home or work station.

Add a disclosure triangle to the application to include instructions to open the widget in Notification Center (open Notification Center, click "Edit", click the + sign next to DC Metro).

The WMATA API key and the Fabric API keys are currently stored inline.

Separate these keys into APIKeys.plist and add it to .gitignore.

The biggest blocker at the moment is figuring out how to populate plist values with other plist's values. The Fabric API key is stored in Info.plist, and will need to be retrieved by APIKeys.plist.

If the selected station is "Woodley Park Zoo-Adams Morgan" (the longest station name), the "W" overlaps with the work favorite button:

Resolve this by either shrinking the text or truncating it with ellipses. I have shortened other names (e.g. shortened "U Street/African-Amer Civil War Memorial/Cardozo" to "U Street"), but I'm not sure what to remove from "Woodley Park Zoo-Adams Morgan."

It would be helpful to see crash reports to gauge how the app is doing in the real world. Implement the Crashlytics Pod to achieve this.

Add support for macOS 10.10.

Use the info button on the upper right corner of the widget to reveal a settings view, which should display the station selection options.

Stations with multiple levels can create a cluttered looking table view:

Create a dropdown menu to filter by line. I think this should include connecting lines, too (e.g. selecting Silver will also show predictions for the Orange line).

Currently, an NSButton reveals the Settings view, since implementing widgetDidBeginEditing() was giving me issues.

The NSButton calls this method:

    @IBAction func clickSettings(sender: NSButton) {
        if settingsViewController == nil {
            settingsViewController = SettingsViewController.init(nibName: "SettingsViewController", bundle: NSBundle.mainBundle())
        }

        presentViewControllerInWidget(settingsViewController)
    }

And this is the current implementation of widgetDidBeginEditing() (yes, I have also tried adding the nil check to no avail):

    func widgetDidBeginEditing() {
        print("began editing")
        // This causes the view to flash back and forth
        //      presentViewControllerInWidget(settingsViewController)
    }

As you can see from the comments, this implementation makes the widget very glitchy, and the Console prints "began editing” and then "ended editing" (widgetDidEndEditing() prints "ended editing") in an infinite loop.

widgetAllowsEditing currently returns false, which disables editing mode until this is figured out.

Replace the NSButton with the correct implementation of widgetDidBeginEditing().