u/GPHdev

Hi everyone!

I built Metribody, an Android app for tracking body measurements and weight over time.

The idea came from a simple problem: body weight alone doesn’t always reflect physical progress, especially when someone is losing fat and gaining muscle at the same time.

Metribody currently includes:

- Weight and body measurement tracking

- Progress charts

- Personal goals

- Complete measurement history

- Measurement guides

- CSV data export

- Local data storage

- No mandatory account

It’s available in English, Spanish, Portuguese and French.

Google Play:

https://play.google.com/store/apps/details?id=com.metribody.app

I’m the developer and I’m actively improving it.

What is the first feature or screen you would change?

https://preview.redd.it/wl50vnrsbthh1.png?width=672&format=png&auto=webp&s=d2e6244520e785ce64f0dfa1e395f6723b88f5d1

Hi everyone!

I've been building a Flutter app called MetriBody over the past few months, and one of my goals from the beginning was to make it work completely offline.

Instead of using Firebase, I decided to build the first version using Hive because I wanted:

• Instant startup

• No authentication

• No internet dependency

• Better privacy

• A simpler architecture for the MVP

The experience has been surprisingly good.

Now that the Android version is live, I'm considering adding optional cloud sync in the future while keeping the app fully usable offline.

For those of you who have built Flutter apps...

Would you still choose Hive for an offline-first app today, or would you start directly with Drift, Isar or another solution?

I'd love to hear your experience and the trade-offs you've found in production.

Hi everyone,

I recently developed and launched an Android app. It's still in its early stages, but I've already had several strangers contact me asking for an iOS version, and a few acquaintances are pushing for it too.

Initially, my plan was conservative: stay on Android, see if the app gains real traction and success, and only then invest the time and money into the Apple ecosystem. I really didn't want to pay the $100 annual fee until I knew the core concept worked.

However, seeing actual interest from Apple users this early has me second-guessing my roadmap.

Pros of jumping in now:

• Validated interest: People are actively asking for it; I'm not guessing if a market exists.
• Higher monetization potential: Historically, iOS users tend to spend more on in-app purchases or subscriptions if I decide to go that route later.

Cons/Hesitations:

• That $100 entry fee is a yearly commitment, and the app isn't profitable yet.
• Splitting my focus on feedback/bug fixes between two platforms early on might slow me down.

For those who have been in this position: What would you do? Would you hold off until the Android version hits specific milestones (like a certain number of active users), or would you strike while the iron is hot and pay the Apple fee to capture those users now?

TL;DR: Launched an Android app. Getting organic requests for an iOS version from users and friends. Unsure if I should drop the $100 Apple fee now to capture them or wait for the Android version to prove itself first.

Hi everyone,

I recently developed and launched an Android app. It's still in its early stages, but I've already had several strangers contact me asking for an iOS version, and a few acquaintances are pushing for it too.

Initially, my plan was conservative: stay on Android, see if the app gains real traction and success, and only then invest the time and money into the Apple ecosystem. I really didn't want to pay the $100 annual fee until I knew the core concept worked.

However, seeing actual interest from Apple users this early has me second-guessing my roadmap.

Pros of jumping in now:

• Validated interest: People are actively asking for it; I'm not guessing if a market exists.
• Higher monetization potential: Historically, iOS users tend to spend more on in-app purchases or subscriptions if I decide to go that route later.

Cons/Hesitations:

• That $100 entry fee is a yearly commitment, and the app isn't profitable yet.
• Splitting my focus on feedback/bug fixes between two platforms early on might slow me down.

For those who have been in this position: What would you do? Would you hold off until the Android version hits specific milestones (like a certain number of active users), or would you strike while the iron is hot and pay the Apple fee to capture those users now?

TL;DR: Launched an Android app. Getting organic requests for an iOS version from users and friends. Unsure if I should drop the $100 Apple fee now to capture them or wait for the Android version to prove itself first.

Hi everyone,

I recently developed and launched an Android app. It's still in its early stages, but I've already had several strangers contact me asking for an iOS version, and a few acquaintances are pushing for it too.

Initially, my plan was conservative: stay on Android, see if the app gains real traction and success, and only then invest the time and money into the Apple ecosystem. I really didn't want to pay the $100 annual fee until I knew the core concept worked.

However, seeing actual interest from Apple users this early has me second-guessing my roadmap.

Pros of jumping in now:

• Validated interest: People are actively asking for it; I'm not guessing if a market exists.
• Higher monetization potential: Historically, iOS users tend to spend more on in-app purchases or subscriptions if I decide to go that route later.

Cons/Hesitations:

• That $100 entry fee is a yearly commitment, and the app isn't profitable yet.
• Splitting my focus on feedback/bug fixes between two platforms early on might slow me down.

For those who have been in this position: What would you do? Would you hold off until the Android version hits specific milestones (like a certain number of active users), or would you strike while the iron is hot and pay the Apple fee to capture those users now?

TL;DR: Launched an Android app. Getting organic requests for an iOS version from users and friends. Unsure if I should drop the $100 Apple fee now to capture them or wait for the Android version to prove itself first.

Hi everyone,

I just wanted to drop by and share some great news: my app has officially passed the closed testing review and is now Live in Production! 🚀

I want to give a huge thank you to this community. The "test-for-test" dynamic really works if we support each other. To everyone who helped me test my app, you guys are awesome.

The best part? Once the 14-day testing period ended and I applied for production, Google approved my app and put it live in the store in less than 3 hours! ⏱️🔥

My advice for those still testing:

- Keep testing other people's apps honestly. Reciprocity is key.

- Make sure your testers actually open the app occasionally during the 14 days; Google tracks engagement.

I’m done with my testing phase, but I will keep testing the apps of those who helped me until your 14 days are up.

Don't give up, you can make it too! Thanks again!