Hi Paulien,
- Probably the best usecase I could think of.
- Notifying the developer
- A caught exception: Maybe not the best usecase but: imagine a userexception that frequently turns up and doesn’t make sense to the user, but should be changed or fixed (maybe the third bullet is a better for this)
-
number of calculations: what would you use this information for?
I can imagine you want to log the number of calculations (or maybe better: calculation time) neccesary (e.g. for a iterative calculation) so you can quantify if the solving algoritm needs to be improved. Also as developer you can log how many times a certain app is actually used to quantify if the app is (financially) viable. - change-request/ bug-report : this could be a way to solve: Add an issue/bug tracker to apps. I imagine a top-level entity where a user can submit feedback directly inside the app-workspace.
- Again this is maybe not the best use case (I just tried to think of multiple usecases). But I can imagine that someone who really wants to keep track of changes on a specific project(Entity). Keeping up with the group activity is not really user friendly, because a group could (potentially) be a lot of people.
Does this help?
Regards,