-
Notifications
You must be signed in to change notification settings - Fork 91
Virtual User Feedback
Citygram is in eleven cities now, and brought more cities online in 2015 than were present for launch in 2014. Now that so many cities are online, it makes sense to examine how Citygram can deepen impact in its host cities, as well as broaden it. This page is meant to capture brainstormed ideas regarding how best to fix it.
Issue #239 goes into this in some detail.
To start, basic statistics could be made public, with a summary table showing (for each city):
- Number of registered users per day/week/month
- Number of unsubscribed users per day/week/month
- Number of notifications pushed to users per day/week/month
This can include dataset sparklines: does this dataset publish 10 events daily? 100 events every two weeks? Some other, irregular pattern? A sparkline would be useful for users to see, and helpful for admins in knowing whether there's an error (big change in the sparkline) without having an explicit threshold (e.g. 500).
Citygram endpoints are up and down throughout their lives for a variety of reasons. A general sense of endpoint health, as well as if there are any current outages to track would be a great thing for a city admin to see.
In some cases like Miami's 311 data, the feed does not update in real time, but rather as a chunk. As a result, folks may get a batch of text messages at 6am for multiple alerts which may not be an ideal user experience. You could batch these requests as one "super request" OR it may be better to set a time as to when users should be notified. (Or you can just let folks deal with it on their own through the phone's Do Not Disturb Hours feature.)
Right now this is all managed by Google Form, but if requests were brought inside the app, it would be a positive way to see where the requests were within the city.