Top Ergänzung
A request please.
Response from developer
Thank you very much for the lovely review — I really appreciate it! Regarding long-acting insulin: FLwatch’s current IOB calculation is intended for rapid-acting insulin, as basal/long-acting insulin is normally treated separately rather than being included in IOB. That said, I’ll have a look at whether long-acting insulin could be entered and represented on the graphs in a useful way without making the IOB display misleading. And regarding the “since the last reading” display: I think you mean the indication showing how many minutes have passed since the last glucose value. If so, I can certainly look into providing an option to hide it. Thanks again for the kind words and for the suggestions — feedback like this is very helpful!
Great App! Highly recommended!
I see you added an option to sync to apple health, but the switch to export on the app won’t slide. In settings Apple Health FlWatch is switched on to allow as a source, but still on the app I press y slide on to export the data is not possible. Is it just me?
Response from developer
Thank you for coming back with another review — and I’m glad to hear you’re still enjoying FLwatch! Apple Health support was added after requests like yours, so it’s especially nice to see you using it now. Regarding the export switch: until now, FLwatch required permission for both glucose and insulin data before Apple Health export could be enabled. I recently changed this so the two are handled independently — for example, allowing glucose alone is now sufficient if that’s all you want to export. That improvement will be included in the next release, so what you’re seeing should be resolved there. Thanks again for the feedback and for sticking with FLwatch!
This is an exceptional app.
And a button to hide the ‘since the last reading’ as I keep mistaking it for my clock.
Cheers. I love it and Thankyou muchly.
Response from developer
Thank you very much for the lovely review — I really appreciate it! Regarding long-acting insulin: FLwatch’s current IOB calculation is intended for rapid-acting insulin, as basal/long-acting insulin is normally treated separately rather than being included in IOB. That said, I’ll have a look at whether long-acting insulin could be entered and represented on the graphs in a useful way without making the IOB display misleading. And regarding the “since the last reading” display: I think you mean the indication showing how many minutes have passed since the last glucose value. If so, I can certainly look into providing an option to hide it. Thanks again for the kind words and for the suggestions — feedback like this is very helpful!
Great looking app but it eats battery charge!
I have reverted to SweetDreams app which functions the same but only uses a few percent in the same time. Real shame. 😞
Update. After a rebuttal from the writer, I reinstalled the App just to find that it screws battery life just as bad as before. Over 60% of my battery consumption was the FL Watch app on the first day. Needless to say I’ve removed it again.
Response from developer
Thanks for the feedback. I have since done some additional profiling of FLwatch’s battery usage and identified the Live Activity as one area where consumption could be significantly reduced. In particular, rendering the glucose graph every minute was more expensive than necessary. This has now been reworked with a much more lightweight rendering approach and will be included in the next FLwatch release. In the meantime, users who experience higher-than-expected battery consumption can disable the Live Activity in FLwatch, which should considerably reduce its battery impact while keeping the rest of the app available. One small clarification regarding the percentage shown in iOS Battery settings: this number represents FLwatch’s share of the battery usage attributed to apps during the selected period. It does not mean that FLwatch itself consumed that percentage of the phone’s total battery charge. For example, an app can account for a large percentage of reported app usage even when the overall battery drain during that period was relatively small. Battery efficiency is something I continuously look at as part of developing FLwatch, and improvements like this are made whenever I find an opportunity to reduce resource usage without sacrificing functionality.
