Original Summary

Short version of the story, with the parts that surprised me: KingSmith pads speak a proprietary protocol, polled, and the firmware silently drops commands sent less than 700 ms apart. The belt keeps its counters through a pause and only clears them ~30 s after stopping, so "speed = 0" doesn't mean the walk ended. My first version filed one session per pause. Health Connect once took 8 minutes to answer a write. A whole walk started and ended during that wait, and I lost it. Now the walk goes to the local DB first and Health Connect gets it separately. FitShow pads (WalkingPad N1 Pro and a lot of generic ones) use a different framing with an XOR checksum. FTMS is the open standard, but it doesn't count steps, so the app estimates them from published cadence data and labels them as estimated. Result: Zancada, an Android app (Kotlin, Compose) that controls the pad and writes each walk to Health Connect. No servers at all. Monetisation: three free walks, then a one-off payment. https://play.google.com/store/apps/details?id=com.victorfalcon.zancada&utm_source=reddit&utm_campaign=r_sideproject It's been live for a couple of weeks with ~10 installs a month and 0 sales so far, so any feedback on the listing or the pitch is welcome too.   submitted by   /u/victoor89 [link]   [comments]

  • 情报分类：综合情报
  • 分类依据：内容未命中明确的垂直分类规则，归入综合情报
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/11 15:58:03