Skip to content

Commit 68c0580

Browse files
0xbrayoErikBjare
andauthored
Update _posts/2024-05-13-introducing-tauri.md
Co-authored-by: Erik Bjäreholt <[email protected]>
1 parent f06073a commit 68c0580

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/2024-05-13-introducing-tauri.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ With Tauri, they have handled most of the heavy lifting, and make it easy to pro
2222

2323
## User Experience
2424

25-
`aw-tauri` aims to consolidate much of the functionality that is currently implemented in [`aw-qt`](https://github.com/ActivityWatch/aw-qt), [`aw-server-rust`](https://github.com/ActivityWatch/aw-server-rust), and [`aw-notify`](https://github.com/ActivityWatch/aw-notify).
25+
`aw-tauri` aims to replace the functionality that is currently implemented in [`aw-qt`](https://github.com/ActivityWatch/aw-qt) and [`aw-notify`](https://github.com/ActivityWatch/aw-notify). Creating a new Rust-powered entrypoint for running ActivityWatch and its modules. With [`aw-server-rust`](https://github.com/ActivityWatch/aw-server-rust) as the default server, it leads to a reliable and highly performant application. Reliability and performance is very important for apps like ActivityWatch, which always run in the background and collect data that is otherwise lost.
2626

2727
- It houses its own webview, no need to visit `http://localhost:5600` in your browser anymore.
2828
- Watchers can be started and stopped right from the trayicon, just like in `aw-qt`.

0 commit comments

Comments
 (0)