Open JohnRillos opened 10 months ago
The underlying information that vita uses to track "downloaders" is that they are subscribed to the next revision of a desk. When you commit to a desk, all of those subscriptions are fulfilled and your users make a new subscription to the next next revision.
This is the nature of desk sharing in clay. A higher level abstraction could be clearer, but I that might belong in %treaty or something similar. The %vita agent also has a "cumulative" field for downloaders which tracks the total set of users who have ever been a "downloader". But it does not keep track of historical sizes of the cumulative set.
Clarifying all of this nuance into a more intuitive metric like you suggest would be a good feature, but I think it would require some core changes.
This should be possible with a swizzle on the changes in #4. Basically, outdated desks are just the %cult
subscriptions for the full desk that aren't at the latest desk version. Integrating and displaying this data would require some nontrivial changes to %vita
, but I don't think there are any serious blockers.
If I understood it right, currently %vita tracks the number of subscribers that are on the most recent version of an app. I've noticed that whenever I push out an update, the number of "downloads" in the csv craters, before gradually rising again. If I push out an update and keep refreshing the %vita UI, I see the download count go up each time, which is neat.
However, I would like to know not just how many people are up-to-date with my published app, but how many people are subscribed to my desk at all. Assuming this is technically feasible, please include this data somewhere.