FitCloudPro

FitCloudPro is a companion application designed to connect budget-tier and original equipment manufacturer (OEM) smartwatches with mobile hardware. Developed by topstep (associated with Hetang Smart), the application functions as an intermediary middleware layer, converting raw sensor data from wearables into actionable daily health metrics on mobile devices. The platform is broadly deployed across white-label wearable ecosystems, most notably providing official software support for KUMI smartwatch lines, including models such as the GT6 Pro, GW16T Pro, KU3 Max, and KU3 Meta. Rather than operating as a closed ecosystem tied to a single premium hardware brand, FitCloudPro serves as an accessible management dashboard for cost-effective wearables, handling biometric telemetry, system configurations, and notification forwarding.

At its core, FitCloudPro establishes connection channels using Bluetooth Low Energy (BLE) GATT protocols. The software regularly processes data streams from optical photoplethysmography (PPG) sensors and tri-axial accelerometers. These inputs are compiled into key metrics, including continuous heart rate, pulse oximetry, total step count, active caloric expenditure, and sleep phase distribution. Beyond basic biometric tracking, the app manages wearable device settings. Users can download custom watch faces from a cloud repository, set sedentary alerts, schedule hydration reminders, set local alarms, and customize do-not-disturb periods directly from the mobile interface.

An evaluation of FitCloudPro’s operational design highlights notable technical tradeoffs. To maintain reliable notification mirroring for incoming calls, SMS messages, and social media updates from platforms like Facebook and Twitter, the app relies on Android’s NotificationListenerService and persistent background execution. Consequently, it requests explicit exemptions from battery optimization restrictions, along with system access to location data, contact lists, and call logs. While these privileges are necessary to maintain continuous BLE connections and push notifications, they result in a heavy system footprint. Mobile security analyses indicate that the app transmits telemetry over unencrypted channels, lacks end-to-end payload encryption, and incorporates several third-party tracking software development kits (SDKs).

Algorithmic performance also shows functional limitations. User feedback indicates that the sleep tracking engine uses rigid, hardcoded temporal rules—frequently defaulting to a start time around midnight regardless of actual sleep onset. Additionally, stationary states can cause phantom sleep records when the wearable is off-wrist. These software limitations reflect the broader challenges of low-cost wearable ecosystems, where advanced algorithmic refining is often omitted to maintain low production costs.