It may prove useful to have details on which stops are most popular, and when

Submitted by Cardiff Bus Android App on 1 March 2011 at 07:20

There are a few ways to achieve this server-side

Non-identifying

Add counters for each stop to show how often the each display is shown. Maybe add an indication of how the load occurred (click from stop list, prev/next, refresh, click from favourite list (when implemented))

Pros: Easily done with no user interaction.
Cons: Not user specific

Identifying

Add a UID to each installation (hash of phone number?) and send this with each request

Registered Users

As above, but connected with issue 3

There are a few ways to achieve this client-side

Non-identifying

Add counters for each stop to show how often the each display is shown.
Maybe add an indication of how the load occurred (click from stop list, prev/next, refresh, click from favourite list (when implemented))

Pros: Easily done with no user interaction.
Cons: Not user specific. Takes space and cpu to store and use. Lost at uninstall

Persistent non-identifying

As above, but prompt to send the data in anonymously once in a while

Identifying

As above, but allow the data to be identifyable