Even if you use Amplitude, this could still be helpful information. I’m not sure what kind of APIs Amplitude provides, but we use it at my job. In my work, the details of Amplitude are abstracted away such that this information is still highly relevant.
At a minimum, this kind of information is relevant to the people creating products like Heap or Amplitude.
At my company, the analytics APIs are provided by a platform team.
I think there’s some utility in a company owning an abstraction away from a third party.
Supposing if Amplitude (or Heap) were to ever go under, or if we were to want to change Analytics providers for whatever reason, it would be extremely helpful if the code didn’t depend directly on these third parties.
On a smaller app, I would mostly likely directly use the Heap or Amplitude APIs.
Is this related to the article? How do you track time spend on page for a single page-visit using Heap? Don't they have to use a similar mechanism as described in the article?
At a minimum, this kind of information is relevant to the people creating products like Heap or Amplitude.