Launched my wearable-data app on iOS this week. Live everywhere except the EU. Here’s the build, the pricing bet and the regulatory wall.
I’m a solo founder (studio: Fosforonero). Over the past few months I’ve been building FitMesh Sync, an app that brings health data from different wearables into a single dashboard.
The idea came from a simple frustration. Most people who use more than one wearable end up with their health data spread across several apps that don’t communicate with each other. Galaxy Watch, Garmin, Fitbit, Apple Watch, smart rings… each has its own ecosystem.
FitMesh brings everything together into one place while keeping users in control of their data.
The milestone
This week I finally launched the iOS version. Android came first on Google Play, and now users can use the same account and the same dashboard on both platforms.
The technical challenge
One feature I’m particularly proud of is that FitMesh doesn’t just read Apple Health. It can also write compatible data from Android wearables into Apple Health, including sleep stages, resting heart rate, SpO₂ and steps.
Writing the data wasn’t actually the difficult part.
The real challenge was preventing sync loops and duplicate records when multiple devices reported the same activity. Getting that logic right took far more work than integrating the APIs.
The pricing bet
I decided not to follow the usual pricing model for this kind of app.
FitMesh is available as a one-time purchase (€3.99 on Android and €4.99 on iPhone). For users who prefer it, there’s also an optional Pro subscription for about €1.19 every six months.
Instead of relying on expensive monthly subscriptions, I’m betting that fair pricing, flexible purchase options and a privacy-first approach will resonate with users. All data stays on European servers and is never sold.
The first 1,000 users also receive FitMesh Pro Lifetime for free as founding users.
The unexpected part
The app went live worldwide.
Just not in the place where I live.
It’s currently unavailable in the 27 EU countries because Apple’s Digital Services Act trader verification is still in progress. My App Store Connect dashboard simply says “Verification in progress.”
So I launched globally, but I still have to tell people in my own country to wait a little longer.
Two things I learned
- Regulatory approvals are now part of your launch timeline. They deserve the same attention as development and App Review.
- If you’re launching globally, make sure your website and store copy can handle regional availability without promising something users can’t access yet.
I’m curious what other founders think.
If you were launching a utility app today, would you go with a one-time purchase, a low-cost subscription, or a traditional monthly subscription? Why?
And if you’ve been through Apple’s DSA trader verification, how long did it take before your app became available across the EU?
Small milestone: FitMesh is now available worldwide 🌍
A quick update on my solo founder journey.
Over the last couple of weeks I’ve been sharing FitMesh across Reddit and other communities to get real user feedback instead of building in isolation.
A few things happened:
✅ FitMesh is now available worldwide on both Google Play and the Apple App Store, including Europe after completing Apple’s DSA verification.
✅ The first users have already started testing it with Apple Watch, Oura, Fitbit, Garmin and smart rings.
✅ I’ve received pages of incredibly detailed feedback, not just “looks good.”
One thing surprised me.
I thought people wanted more charts, metrics and dashboards.
Instead, almost everyone asked for the same thing:
“Help me understand my data.”
People don’t want another recovery score.
They want to know:
That completely changed how I think about FitMesh.
Originally I was building a unified dashboard for wearable data.
Now I realize the bigger opportunity is helping people make small daily improvements based on that data.
Some of the improvements already planned thanks to user feedback include:
One feature that has received unexpectedly positive feedback is Share with AI.
Instead of building another AI chatbot, FitMesh lets users generate a structured summary of their health data and send it to ChatGPT, Claude, Gemini or any AI they already use.
The idea is simple:
Bring your own wearable.
Bring your own AI.
Own your own health data.
Still a long way to go, but this has been one of the most valuable weeks since starting the project.
If anyone has experience building health, fitness or wearable products, I’d love to hear what you think users actually need beyond dashboards and scores.