First of all, thanks for the integration or, more specifically, the blog post about it. That’s how I learned about Focusmate in the first place. I like it!
Now, the integration does not currently differentiate between 25 and 50 minute sessions and I wish it did. There’s arguments for and against and, really, I wish it didn’t count the number of sessions but the time I spent using it and if @shanaqui’s poll is any indication, I am not alone in this. In fact, @dreev touched on this point, too.
Cheap way out of this
Make the integration add the session’s length in the comment, so rather than “Session at 15:45 with Jimmy H. [Auto-entered via Focusmate]” it could read, e.g., “Session at 15:45 with Jimmy H. for 50 minutes. [Auto-entered via Focusmate]”.
Bonus points if you make this info available via the API, too, in, say, some extra json property that is returned for a datapoint.
Yes, this is somewhat of a hack and I’d much rather have the integration simply count the minutes rather than times. But I know how much the Beehive likes its quick UVIs and this certainly sounds like one and it doesn’t (I would assume) break anything. However, converting all goals that use the integration to “time spent” does not sound too difficult either. Obviously this depends on things like, does the Focusmate API even provide this info. I suppose @davidaugustus might know more about this. I at least could not find a publicly documented API for Focusmate.
this is something I’m thinking about doing in the near future, barring other priorities.