Documentation
Operating notes for the 0.1.0 desktop collectors, Android application and local console.
First run
- Launch Lemon Tracking.
- Read the consent screen.
- Select Start Tracking to enable collection, or Exit to leave it stopped.
- Use the tray menu to pause, resume or reopen the application.
The collector begins after consent is stored.
Record model
| Field | Meaning |
|---|---|
| application | Process identity, for example code or chrome. |
| start / end | Local timestamps for observed sessions. Aggregate estimates use duration without start/end timestamps. |
| duration | Seconds or minutes represented by the record. |
| afk | Idle state from the system timer. |
| source | automatic, manual, estimated or imported. |
| confidence | Optional confidence for retrospective estimates. |
Platform collectors
| Platform | Collector | Foreground adapter | Idle adapter |
|---|---|---|---|
| Windows x64 | Desktop collector | Win32 foreground window and process identity | Windows last-input timer |
| macOS Apple Silicon | Local agent | System Events through osascript | IOHIDSystem through ioreg |
| Linux x86_64 | Local agent | X11 xprop | xprintidle when installed |
| Android | APK | UsageStatsManager through Usage Access | Current-day foreground summary |
Android: open Lemon Tracking. If the device displays a restricted-setting message, open App info and select Allow restricted settings. Then open Usage Access, enable access in system settings, return to the app and select Refresh today.
Local files
Each collector uses the current user's local application-data area:
The folder contains consent state and activity records. Windows Settings opens the folder; the macOS and Linux agent prints the path at startup. Android stores records.json in the application's private files directory.
Data path
The collectors and the public documentation site use separate paths. The record model and local storage details appear above; data boundary questions appear in the FAQ.