This is for people who need an app to monitor whenever they alt + tab or just look at other distracting windows.
Below are previews of some of the functionality the app offers:
Starting from versions 0.3.1 and above, there will be a subprocess running in the background that the app uses, as can be seen below:
This subprocess has been updated in
v0.3.4!
And since version 0.3.2, an issue with these subprocesses that stemmed from version 0.3.0 should be fixed.
The issue was how the handling of the subprocess hanged the app, as it was running and stopping its process every second, which isn't very good. The fix? Just make sure to make it run it and keep it in the background, then let it send updates once a second. With that, a new system has been made to handle the data and the subprocess for the expected data.
| Feature | Description | Implementation |
|---|---|---|
| Window Check | The app will check if look at "distracting" apps by checking the name of the executable. | Since version 0.1.1 |
| Distraction Timer | Everytime you look at "distracting" apps, it will increment this timer. | Since version 0.1.1 |
| Customizable Keyword List | You can add your own custom keywords to detect when using the app. | Since version 0.2.0 |
| Additional Menu Settings | App behavior is now also customizable. | Since version 0.3.0 |
| Enhanced Keyword Matching System | The config file that is used by the app to check for "productive" and "distracting" apps are now overhauled. It can fuzzy match, partial match, and more! | Since version 0.3.0 |
| Productivity Timer | Everytime you look at "productive" apps, it will increment this timer. | Since version 0.3.0 |
| Feature | Description | Progress |
|---|---|---|
| Customizable List for Used Keywords in Detection | The user can edit a file to add their own keywords that they wish to detect. | 100% |
| Sound Effects | A sound effect will play everytime the app catches the user slacking off. | 0% |
| Overhaul Keyword Matching System | Rework the entire system to support multiple keyword checking systems, including the config file for it. | 100% |
Go to the releases tab to the right, and download the latest version, and follow the instructions written there.
Simply open the executable, and the app will immediately check if you're slacking off. Specific app behavior can be modified within the app's popup menu.
If it doesn't detect anything (including itself), run the executable as administrator.
That's it.
If you wish to run the files yourself, you can just clone the repository, then use a package manager like uv.
uvpackage manager (download in your global environment).
If you have uv then, you can just let uv handle the project dependencies. If you don't know how to use uv, you can do this command:
uv sync
uv lock
uv run flet runIt will automatically download the missing dependencies. If it doesn't download properly, add an additional flag; --prerelease=allow just like this:
uv sync --prerelease=allowThen check if you have flet with:
uv flet --versionThen do the first 3 commands again.
Yes, this app is safe.
"Are you sure?"
If you're doubting me, you can take a look at the source code, which is literally in this repository. The only things that this app may tamper with your files, is where the config files will be stored. By default, this will be stored in the ./AppData/Roaming/MetaDusk/ directory. If you can't locate it, you can open this folder by doing win + r then typing %appdata% which will bring you to this exact directory, where you will now just search for the MetaDusk directory, which is where the config files will be stored.
The other concern you might have, would be:
"How does this app detect what app you're looking at?"
Basically, this app works by using a library that only provides the window's names, process ids, and such, which are easily locatable manually as well (mostly for the names). And that's the system that this app uses; it simply checks the currently focused window's name against a list of keywords.
| No. | Issue | Description | Solution | Severity |
|---|---|---|---|---|
| 1. | Stuck on Loading Screen. | This could be because your device is struggling to run the app. | Simply close then open the executable again. | Easily fixed. |
| 2. | App Window Appears Stretched | This could be a flet rendering issue. |
Simply restart the app. | Should be fixed now for v0.3.3 |



