clarification or a "use case" example? comparing to tracker, views, activity, etc...

so this seems like an outstanding tool for content rich sites where the emphasis may be on a large contributing user base - but i'm a bit unclear about when i'd use this versus these other options:

views (to create a custom tracker of any kind visible to any/each user, automatically created/vanishes with user creation/deletion)
tracker (the default in core, which also shows everything a 'user' has done in his/her profile, automatically prepopulates and vanishes with new/dead user accounts)
activity (which can be assigned to specific actions, including those beyond this module - like 'favorite nodes' and 'user relationships' - and displayed in profiles, blocks etc - also automatically appears/vanishes with user account creation/deletion)
others (not sure what they are)

when you designed this module, were you looking at tracker as a point of reference, or were you looking at how a user manages the content that he creates within a site? it's a bit unclear and it would be great to see or read an example of where this makes a lot of sense, or what prompted you to design this ...