To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.
- name: workmentor
- description: Workmentor is an employee time-tracking desktop application (Electron). The user checks in explicitly with a webcam and location punch. The app then measures worked and idle time, the active application and browser usage, and keyboard and mouse activity counts (never keystrokes or clipboard content), and takes periodic screenshots, all gated by settings the organization’s admin controls. It is overt monitoring: it lives in the tray and the user can see its state. It is also published on the Microsoft Store (https://apps.microsoft.com/detail/9n3nn39hr7s3) and a Mac App Store submission is in progress.
- snapcraft: ‘PRIVATE’
- upstream: ‘PRIVATE’
- upstream-relation: The publisher of the snap is the developer and maintainer of the upstream project.
- supported-category: None of the listed supported categories (compilers, debug tools, IDEs, shells and so on) fits. We are requesting classic under the Criteria list: access to resources not yet supported by snapd, namely system-wide keyboard and mouse input monitoring, reading the foreground application and browser tab of other applications, and a persistent user-level background service.
- reasoning: (1) Global input activity: idle detection counts keyboard and mouse events system-wide, from any application, and only counts are kept. No strict interface provides a global input hook. (2) Active window and browser usage: the app reads which application and browser tab is in the foreground across the whole desktop to report time per application. (3) Screen capture: periodic screenshots of the whole desktop at an interval the admin sets. (4) Background daemon: time must keep being tracked when the main window is closed, so a small Node daemon is registered as a systemd user unit that starts at login and shares state files with the main app under ~/.config/Workmentor. A strict snap cannot install or keep a user-level service outside its own sandbox. (5) Power and session events: sleep, lid close and lock events are used to count idle time correctly. Items 1, 2 and 4 are the core of the product and cannot be provided by existing interfaces. We also publish AppImage, deb and tar.gz builds, but want the snap as the supported, auto-updating channel for Ubuntu users.
[x ] I understand that strict confinement is generally preferred over classic.
[ x] I’ve tried the existing interfaces to make the snap to work under strict confinement.
Note that snappy-debug can be used to identify possible required interfaces. See https://snapcraft.io/docs/debug-snaps for more information.