You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+28-2Lines changed: 28 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,8 @@
1
1
# SpeedHive
2
2
3
-
A desktop application focused on accurate and lightweight internet speed measurement. SpeedHive is built using **Tauri** for the desktop shell and **React** for the frontend UI. This project is in its **first development phase**, focused on core functionality: measuring **download** and **upload** speeds.
3
+
A desktop application focused on accurate and lightweight internet speed measurement. SpeedHive is built using **Tauri** for the desktop shell and **React** for the frontend UI.
4
+
5
+
🎧 This project was created through **vibe coding** — built with good music, flow state, and AI-assisted development.
4
6
5
7
---
6
8
@@ -13,6 +15,30 @@ A desktop application focused on accurate and lightweight internet speed measure
13
15
14
16
---
15
17
18
+
## 📊 How Speed Measurement Works
19
+
20
+
### Download Speed
21
+
22
+
SpeedHive measures download speed by fetching data from a remote server and tracking how much data is received over time.
23
+
24
+
1. The app connects to a test server and starts downloading a file
25
+
2. Every 250ms, it calculates the current speed: `(bytes received × 8) / elapsed seconds`
26
+
3. The test runs for up to 10 seconds
27
+
4. The final result shows your actual download throughput in **Mbps** (Megabits per second)
28
+
29
+
### Upload Speed
30
+
31
+
Upload speed is measured by sending data to a remote server and tracking how much data is transmitted.
32
+
33
+
1. The app sends chunks of data (up to 200 MB total) to a test server
34
+
2. Every 250ms, it calculates the current speed: `(bytes sent × 8) / elapsed seconds`
35
+
3. The test runs for up to 10 seconds or until 200 MB is uploaded
36
+
4. The final result shows your actual upload throughput in **Mbps**
37
+
38
+
> **Note:** Results may vary based on server location, network conditions, and time of day. For best accuracy, close other bandwidth-heavy applications during the test.
0 commit comments