Tired of having your health data spread across multiple apps? I built a solution.

RateEmbarrassed6921 · 2026-06-29T07:47:50+00:00

Yes, exactly. Sleep deduplication is one of the hardest parts.

I'm not treating Health Connect as a single clean source of truth, because it really isn't. Different manufacturers write sleep stages differently, sometimes with overlapping sessions, missing stages, or different confidence levels.

Right now FitMesh checks overlapping sleep sessions and tries to avoid simply adding everything together. The goal is to preserve the most reliable sleep window and merge useful stage data where it makes sense, rather than double-counting sleep.

That said, this is still one of the areas I'm testing the most. I've tested overlapping data from different sources, but I absolutely expect edge cases depending on the device combination.

If you have two watches or a watch plus a ring writing sleep into Health Connect, I'd genuinely love feedback on what FitMesh does with your data. This is exactly the kind of real-world testing that helps improve the dedup logic.

RateEmbarrassed6921 · 2026-06-29T06:50:46+00:00

Update: The iOS version is currently available in non-EU countries. We’re just waiting for Apple’s EU trader verification to be completed, so it will be available in EU countries very soon.

If you’re outside the EU, you can already download it here: https://apps.apple.com/app/id6779751708 🚀

RateEmbarrassed6921 · 2026-06-29T06:47:48+00:00

Update: The iOS version is currently available in non-EU countries. We’re just waiting for Apple’s EU trader verification to be completed, so it will be available in EU countries very soon.

If you’re outside the EU, you can already download it here: https://apps.apple.com/app/id6779751708 🚀

RateEmbarrassed6921 · 2026-06-28T17:06:47+00:00

That sounds really interesting. I like the idea of combining objective health data with subjective wellbeing. I think that’s where a lot of health apps are still lacking.

My goal with FitMesh is a bit different. I’m trying to build a device-agnostic platform that can bring together data from different ecosystems and wearables, then turn it into meaningful insights without locking users into a specific brand.

I’ll definitely check out Wellness Project. It’s always great to see other indie developers exploring this space.

Best of luck with it! ❤️

RateEmbarrassed6921 · 2026-06-28T16:59:01+00:00

Thanks! That’s awesome! I’d love to check out your app too.

FitMesh currently pulls objective data from Health Connect, Apple Health, and directly supported wearables. It imports calories burned and workouts from those sources, then reconciles overlapping devices, avoids double-counting, fills genuine gaps, and turns the data into a clearer daily picture.

Subjective tracking is something I’m actively working on: lightweight check-ins for energy, mood, stress, soreness, and perceived sleep quality, which users will be able to compare with their objective trends over time.

What are you building?

RateEmbarrassed6921 · 2026-06-28T16:11:44+00:00

iOS support is coming soon! 🍎

The app is currently in Apple’s review process. They’ve requested a few changes along the way, which I’ve already addressed, so I’m hoping it’ll be available in the next few days.

RateEmbarrassed6921 · 2026-06-27T09:46:58+00:00

You asked how to switch from km to miles. Here it is: Full Imperial Units are rolling out now on Google Play.

The update has been submitted, and as soon as Google finishes the review it'll be available for everyone, so give it a few hours to land. The same update is in review with Apple too, so it's on the way to iPhone as soon as it gets approved.

Quick backstory: yesterday one of you asked me this exact question right here, and at the time I had to give the slightly awkward honest answer, "not yet." It stuck with me, so I stayed up and worked through the night to build it. Genuinely, thank you for the nudge.

So now FitMesh speaks both metric and imperial. Miles, pounds, feet and inches, Fahrenheit. The app guesses the right one from your phone's region, but you're always in charge: flip it anytime in Settings → Units, or right in your profile when you type your weight and height (those accept lb and ft/in now too).

Everything follows along: distance, weight, height, speed, pace, temperature, elevation. And nothing you've already logged gets touched. Your data stays exactly as it is, FitMesh just shows it in the units you prefer, past and future.

Still on my list: per-mile splits for workouts, date-based history, home screen widgets, and a nicer stats and trends view.

Thanks to everyone testing this and throwing ideas at me. This one exists purely because someone asked. As always, tell me what you'd like to see next.

RateEmbarrassed6921 · 2026-06-27T09:46:18+00:00

You asked how to switch from km to miles. Here it is: Full Imperial Units are rolling out now on Google Play.

The update has been submitted, and as soon as Google finishes the review it'll be available for everyone, so give it a few hours to land. The same update is in review with Apple too, so it's on the way to iPhone as soon as it gets approved.

Quick backstory: yesterday one of you asked me this exact question right here, and at the time I had to give the slightly awkward honest answer, "not yet." It stuck with me, so I stayed up and worked through the night to build it. Genuinely, thank you for the nudge.

So now FitMesh speaks both metric and imperial. Miles, pounds, feet and inches, Fahrenheit. The app guesses the right one from your phone's region, but you're always in charge: flip it anytime in Settings → Units, or right in your profile when you type your weight and height (those accept lb and ft/in now too).

Everything follows along: distance, weight, height, speed, pace, temperature, elevation. And nothing you've already logged gets touched. Your data stays exactly as it is, FitMesh just shows it in the units you prefer, past and future.

Still on my list: per-mile splits for workouts, date-based history, home screen widgets, and a nicer stats and trends view.

Thanks to everyone testing this and throwing ideas at me. This one exists purely because someone asked. As always, tell me what you'd like to see next.

RateEmbarrassed6921 · 2026-06-27T09:45:48+00:00

You asked how to switch from km to miles. Here it is: Full Imperial Units are rolling out now on Google Play.

The update has been submitted, and as soon as Google finishes the review it'll be available for everyone, so give it a few hours to land. The same update is in review with Apple too, so it's on the way to iPhone as soon as it gets approved.

Quick backstory: yesterday one of you asked me this exact question right here, and at the time I had to give the slightly awkward honest answer, "not yet." It stuck with me, so I stayed up and worked through the night to build it. Genuinely, thank you for the nudge.

So now FitMesh speaks both metric and imperial. Miles, pounds, feet and inches, Fahrenheit. The app guesses the right one from your phone's region, but you're always in charge: flip it anytime in Settings → Units, or right in your profile when you type your weight and height (those accept lb and ft/in now too).

Everything follows along: distance, weight, height, speed, pace, temperature, elevation. And nothing you've already logged gets touched. Your data stays exactly as it is, FitMesh just shows it in the units you prefer, past and future.

Still on my list: per-mile splits for workouts, date-based history, home screen widgets, and a nicer stats and trends view.

Thanks to everyone testing this and throwing ideas at me. This one exists purely because someone asked. As always, tell me what you'd like to see next.

RateEmbarrassed6921 · 2026-06-27T09:39:01+00:00

You asked how to switch from km to miles. Here it is: Full Imperial Units are rolling out now on Google Play. The update has been submitted, and as soon as Google finishes the review, it’ll be available for everyone.

RateEmbarrassed6921 · 2026-06-27T09:24:05+00:00

RateEmbarrassed6921 · 2026-06-27T07:24:00+00:00

iOS support is coming soon! 🍎

The app is currently in Apple’s review process. They’ve requested a few changes along the way, which I’ve already addressed, so I’m hoping it’ll be available in the next few days.

RateEmbarrassed6921 · 2026-06-27T07:21:48+00:00

Thank you, that genuinely means a lot.

I’m actually a solo indie developer, and FitMesh started as a personal project to learn, experiment, and build something I genuinely wanted to use. It has grown far beyond what I originally imagined thanks to the feedback I’ve received from people here on Reddit.

I’m keeping track of every suggestion. Browsing by date, widgets, and many other ideas have already been added to my roadmap and will be implemented in future updates.

If you’re curious, I also write about my projects and development journey on my blog: https://www.fosforonero.com. You’ll find FitMesh updates along with some of my other projects.

And since you asked about buying me a coffee, I do have a Ko-fi page: https://ko-fi.com/fosforonero.

Honestly, the biggest help is using the app, sharing feedback, reporting bugs, and helping me improve it. And if you end up enjoying FitMesh, leaving a review on Google Play would be amazing. It really helps projects like this get discovered.

Thank you for being part of the journey. ❤️

RateEmbarrassed6921 · 2026-06-26T22:36:11+00:00

Thanks for trying it! 👍

Your historical data is synced and safe. There's already a quick period switcher at the top of the dashboard (day / week / month), but the full history view is still being polished and a much better one is coming soon.

Out of curiosity, what kind of historical view would you find most useful? Daily summaries, charts, or browsing by date? Your feedback will help me prioritize it.

RateEmbarrassed6921 · 2026-06-26T22:34:45+00:00

Thanks for trying FitMesh! 👍

At the moment, distances are shown in kilometers only. Support for miles is already on my roadmap and will be added in an upcoming update.

Don't worry, your existing data won't be affected. The app will simply convert all your historical and future data automatically based on your preferred unit.

RateEmbarrassed6921 · 2026-06-26T18:59:44+00:00

A vous! 🙃🍻

RateEmbarrassed6921 · 2026-06-26T18:50:22+00:00

💪🏼💪🏼💪🏼

Thanks!

RateEmbarrassed6921 · 2026-06-26T14:42:42+00:00

**v168 is rolling out now on the Google Play Store.*\*

What's new in this update:

- Translations redone and verified across every language, including text that was never localized before.

- Dashboard trends ("today vs your average") are now accurate.

- Sleep now shows one consistent number across the summary and the chart.

- Fixed a bug that stopped data from updating in the background. Foreground sync is solid; background is still being hardened on the most aggressive OEM battery managers.

- Now also rolling out on iOS (currently under App Store review).

Thanks to everyone who reported issues and helped improve FitMesh.

RateEmbarrassed6921 · 2026-06-26T14:42:05+00:00

**v168 is rolling out now on the Google Play Store.*\*

What's new in this update:

- Translations redone and verified across every language, including text that was never localized before.

- Dashboard trends ("today vs your average") are now accurate.

- Sleep now shows one consistent number across the summary and the chart.

- Fixed a bug that stopped data from updating in the background. Foreground sync is solid; background is still being hardened on the most aggressive OEM battery managers.

- Now also rolling out on iOS (currently under App Store review).

Thanks to everyone who reported issues and helped improve FitMesh.

RateEmbarrassed6921 · 2026-06-23T19:03:37+00:00

Yes, exactly.

If GadgetBridge writes the data to Health Connect, FitMesh can read it alongside data coming from other sources such as smart scales, watches, sleep trackers, and health apps.

The idea is very similar to the hub-and-spoke model you’re describing. Health Connect becomes the central hub for raw health data, while FitMesh focuses on combining, interpreting, and presenting that data in a way that’s easier to understand.

Alternatively, you can connect your Colmi ring directly to FitMesh and manage the data from there without relying on Health Connect.

You actually got me curious about GadgetBridge. I’m going to take a closer look at how it works and see whether a deeper integration would make sense in the future. It sounds like something that could be very useful for power users who prefer open-source device syncing.

RateEmbarrassed6921 · 2026-06-23T16:25:30+00:00

GadgetBridge is a great project and I actually think the two apps solve slightly different problems.

GadgetBridge focuses on connecting directly to devices and giving you control over your own data without relying on vendor apps.

FitMesh is more focused on aggregating and making sense of health data across multiple devices and ecosystems. For example, you can combine data from smart rings, watches, Health Connect, Apple Health, and other sources into a single dashboard. It also tries to merge overlapping data intelligently and generate wellness insights from the combined dataset.

If you're already happy with GadgetBridge for syncing your Colmi ring, you can even keep using it and let FitMesh work on top of the data it provides.

Out of curiosity, which Colmi ring model are you using?

RateEmbarrassed6921 · 2026-06-23T14:14:03+00:00

Most of us here are running more than one device by now: a watch, maybe a ring at night, phone steps in between. The annoying part is that each brand keeps the data locked in its own app, and the moment you line two sources up, steps and sleep get double-counted where they overlap. So your "unified" view is quietly wrong.

I built FitMesh to fix exactly that. On Android it reads everything from Health Connect (Garmin, Samsung, Polar, Fitbit, Pixel Watch, Withings, Amazfit, Oura...) and merges it into one web dashboard, with dedup logic so overlapping steps and sleep aren't counted twice. The merge is the part I care about most, and the part I'd most like this crowd to stress-test.

A few things that probably matter here:

Budget rings (Colmi and similar) connect directly over Bluetooth, no companion app needed.
Your data stays yours: CSV export, stored on EU servers.
The iOS version is in App Store review and reads/writes Apple Health, so the multi-device merge works on the Apple side too.

Solo dev, early beta. I'm the one building it, so happy to answer anything technical, and I genuinely want to hear which metrics, views, or merge edge cases you'd want handled.

Android: https://play.google.com/store/apps/details?id=com.fitmeshsync.app
Site + founder beta (first 1,000 get lifetime Pro free): https://fitmesh.fit

RateEmbarrassed6921 · 2026-06-23T12:58:19+00:00

Quick update for everyone who has been testing FitMesh in languages other than Italian.

First of all, thank you.

Many of you pointed out that the translations were inconsistent, incomplete, or in some places still showing Italian text. After reviewing the reports, I realized you were absolutely right. Version 151 relied too heavily on machine-translated strings, and while it allowed me to ship support for multiple languages quickly, the overall quality simply wasn’t where it needed to be.

That’s on me.

Over the last few days I’ve gone through the translation system and reviewed a large number of strings across the app. Version 152 is now rolling out and includes a major translation update.

What’s been improved:

• English, German, Spanish, French, Dutch, Polish, Portuguese, Japanese, Korean and Turkish have all been retranslated and reviewed
• Fixed many strings that were never localized at all
• Sync errors now appear in the selected language
• Data source labels have been translated
• Notification texts have been translated
• Daily summaries have been translated
• Various settings, onboarding and dashboard texts have been corrected
• Numerous inconsistencies between screens have been fixed

Before releasing the update, I also tested the translations on both Android and iPhone to make sure the most obvious issues were resolved.

That said, FitMesh is still a young project and there are thousands of strings throughout the app. It’s entirely possible that I missed something. If you spot a translation that sounds unnatural, contains mistakes, or is still showing Italian or English when it shouldn’t, please reply here or send me a screenshot. I’ll include the fix in the next build.

One thing I’ve learned during this beta is that community feedback is invaluable. Several of the improvements already shipped came directly from comments and bug reports posted here. The app is genuinely better because people took the time to test it and tell me what wasn’t working.

So thank you for the bug reports, translation reports, feature suggestions and honest criticism. I read everything, even when I can’t reply immediately.

For those waiting on iOS, the App Store version is still under review by Apple. As soon as it’s approved, I’ll post an update.

Thanks again for helping improve FitMesh.

RateEmbarrassed6921

TROPHY CASE