Bill W:
I realized that the apps ability to detect and log events generated internally by the delivery apps was more useful than i originally thought. if the app could log this stuff for the USER’S benefit, than maybe it had extra purpose. For example, giving the user a clear undependent log of their timing during a delivery.
Chad G:
S2-06 gave the app a short memory of its own behavior.
The diagnostic system was designed to retain roughly seven days of activity information, including app events useful for troubleshooting and, where enabled, relevant DoorDash or Uber notifications. The user could inspect the log and send a copy to themselves. Retention and delivery were designed so logs would not simply accumulate forever.
The reason was practical. Intermittent bugs are notoriously hard to describe after the fact. A driver may only remember that ‘something weird happened Tuesday.’ A rolling diagnostic record gives developers a chance to reconstruct the surrounding sequence without asking the user to reproduce the problem on command.
We also kept diagnostic logging conceptually separate from recording and from research participation. The aim was troubleshooting, with bounded retention and user visibility, not creating a hidden permanent diary of everything the phone was doing.
@@@
