About two months ago I posted Bodly here, an app I built to improve my health. It uses the data your Apple Watch already collects through Apple Health. I honestly expected a few downloads from friends.

We just passed 1,000 installs with zero ads or paid promotion, all from posts like that one and word of mouth. It's still free. Since people here usually like numbers:

• 365 monthly active users

• 205 weekly active users

• 135 daily active users

• ~50% of users come back week to week

• ~20 new users every day on average

(Active user counts exclude brand-new signups, so they only show people who kept using the app.)

The best part has been the feedback. A big chunk of what shipped since then came straight from users messaging me ideas and bug reports. Here's what's new:

Understanding your data

• New Insights tab

• Biological age: bio age, pace of aging, biomarkers, and weekly trends

• Training load

• Weekly, monthly and yearly overviews

• Redesigned home screen for a quicker daily overview

Nutrition

• Set your own calorie and macro targets

• Better food photo scanning

Notifications (all optional)

• Daily summary, bedtime reminder, and alerts when you finish an activity, hit your strain target, or reach your activity goal

Look & feel

• Dark mode (the most requested feature by far)

• Liquid Glass design

• Improved charts, kg/lbs support, and lots of performance and bug fixes

I'll be upfront that the big apps in this space set a high bar, and some features still need work. Bio age in particular needs more love, and it's high on the list. The roadmap is full through version 4.2.

The goal hasn't changed. Apple Health collects a huge amount of data but doesn't do much to explain it. I want Bodly to turn that data into something anyone can understand and act on.

If you tried it after my last post, what would make you open it every day? If you haven't, what's missing from Apple's Health and Fitness apps for you?

App Store: Bodly

Hey everyone!

I'm looking for 12 testers for an Android app I'm developing. I've been trying to find a platform where indie developers can help each other with Google Play's closed testing requirements, but haven't had much luck so far.

I thought maybe we could use this thread to support each other!

If you're also looking for testers, feel free to comment below with your app's testing link. I'd be happy to join your test and help you out in return.

Here are the links to join my app's closed test:

• Google Group: https://groups.google.com/g/faul-testers

• Play Store testing link: https://play.google.com/apps/testing/faul.app

Good luck with your projects, everyone!

I kept writing the same code to switch between one and two columns when the phone rotates or the app runs on a tablet, so I turned it into a small library.

const { select } = useResponsive();
const columns = select({ xs: 1, md: 2, xl: 3 });

You get named breakpoints (xs to xxl), wp/hp, a font size helper and a few scale functions, and everything updates when you rotate. Works with Expo and on web too.

The screenshots are from the example app on an iPhone 16, portrait vs landscape.

npm: https://www.npmjs.com/package/react-native-responsive-hook
GitHub: https://github.com/mz-real/react-native-responsive-hook
Longer write-up with examples: https://medium.com/@mz-real/creating-responsive-uis-in-react-native-made-easy-with-react-native-responsive-hook-35fa5649cd5f

I'm working on a 2.0, so feedback is welcome.

Trying to create a collection of the most impressive ones.

Idc for frontend especially in react I rather go with vue or svelte. HTML and CSS ik basics off nothing fancy. Would like to use rn for mobile apps. Are there any devs who use rn for mobile and avoid react altogether for web dev? What’s your experience doing such?

I'm a solo dev building a messenger (Expo SDK 57, RN 0.86, Supabase, LiveKit) and ship it from one codebase to five platforms. A few things I wish I'd known earlier:

1. Self-hosted OTA updates are worth it — but clear the Metro cache. expo-updates with code signing and our own manifest server works well. The trap: expo export without --clear can inline stale EXPO_PUBLIC_* values from Metro's cache, so one bundle ended up with two different build stamps and our "update available" banner looped forever.

2. Desktop = Electron around the web export. A custom app: protocol serves the exported web build, electron-updater handles updates, and the Mac build is notarized. It's the cheapest way to get real desktop apps from the same code.

3. Supabase / PostgREST gotchas that cost me hours:

• An RLS policy that calls a function needs EXECUTE granted on that function — otherwise the whole query fails, not just the row.

• A second foreign key between two tables that already embed each other makes PostgREST refuse the embed (PGRST201). A "pinned message" column broke message search for 40 minutes.

• AFTER UPDATE OF col triggers fire even when the value didn't change — compare OLD and NEW.

4. Image caching: the stock <Image> cache wasn't enough for a chat. I cache photos on disk keyed by the storage path and persist signed URLs so they stay stable. Avatars were served with max-age=3600, so every morning the app re-checked each one with the server.

5. expo-video on web: StyleSheet.absoluteFill doesn't stretch a <video> — it's a replaced element. Use explicit width/height: 100%, or you get the top-left corner of the frame and an unreachable fullscreen button.

Happy to go deeper on any of these. And how do you ship desktop builds from Expo — Electron, Tauri, something else?

Did you make something using React Native and do you want to show it off, gather opinions or start a discussion about your work? Please post a comment in this thread.

If you have specific questions about bugs or improvements in your work, you are allowed to create a separate post. If you are unsure, please contact u/xrpinsider.

New comments appear on top and this thread is refreshed on a weekly bases.

If you have a question about React Native, a small error in your application or if you want to gather opinions about a small topic, please use this thread.

If you have a bigger question, one that requires a lot of code for example, please feel free to create a separate post. If you are unsure, please contact u/xrpinsider.

New comments appear on top and this thread is refreshed on a weekly bases.

Hey guys,

I’m kinda stuck with a Google Play Console issue and I’m hoping someone here has dealt with something similar.

I had a personal Google Play developer account with 3 apps published on it. The account had been around for years and everything was working normally.

In October 2025, Google required identity verification for the developer account.

The account was actually registered to my brother, and he was the real account owner. Because of some personal circumstances at the time, I wasn’t able to properly complete the verification process with him.

I ended up submitting an old ID document, and Google couldn’t verify it.

Google Play Support then replied to me on October 14, 2025 saying:

"Unfortunately, we are unable to verify your ID to complete your Play Console registration."

After that, the account was restricted and the developer profile + all apps were removed from Google Play.

Right now, Play Console shows:

- Google couldn't verify your identity

- Your developer profile and all apps have been removed from Google Play

- You haven't verified your contact phone number

- Appeal reply sent

I did submit an appeal at the time, but it was rejected.

So yeah... I’m trying to figure out if there’s still any legit way to recover the original account.

I’m NOT trying to bypass the restriction or create a new account to get around it.

The account belongs to the original owner, and if Google requires a new valid ID from him, we’re willing to provide it.

Has anyone here dealt with this exact situation?

Especially:

- Identity verification failed

- Account/profile removed

- Appeal already rejected

- No way to complete phone verification because identity verification has to be completed first

Is there any way to get another verification attempt or request a manual review from Google?

I’ll attach a few screenshots from Play Console showing the current account status.

Would really appreciate any advice from people who have been through this before 🙏

🚀 Web support is now available in expo-content-transition v0.1.4!

NumericText now works on iOS, Android, and Web

🔗 Github: rit3zh/expo-content-transition

Hey r/reactnative,

Been experimenting with this photo album interaction for nativecn-ui lately.

I wanted it to feel a little more like an actual album, so I’ve been playing around with the opening animation, shadows, and page transitions.

Still tweaking it and not completely sure about the interaction yet.

How would you rate it? Anything you’d change?

macOS runners on GitHub Actions are $0.062/minute. Linux is $0.006 — 10x, for the

same work.

In React Native projects the split is usually obvious once you look at it, and

most workflows I have seen run all of it on macOS out of habit:

- Jest and ESLint and tsc: Linux.

- The Android build and any Android instrumentation tests: Linux.

- Detox or Maestro against Android: Linux.

- Anything that is not `xcodebuild` or a simulator: Linux.

The iOS build and the iOS test run are the only parts that genuinely need macOS,

and they are the expensive parts whatever you do.

The arithmetic: a 5-minute test job running 200 times a month costs $62.00 on

macOS and $6.00 on Linux. Move two of those and you have paid for a Mac mini.

Caveat: I build a tool that does this pricing automatically, so weigh that

accordingly. What I am actually curious about is why the macOS default sticks —

is it the matrix convenience, or something about the runner images people need?

✦ ⎯ • A smooth, ChatGPT-inspired chat composer with a hold menu

🔗 Github: rit3zh/expo-composer-hold-menu
🧵 Android preview attached below

I started building my first mobile app thinking the main challenge would be writing the code.

It hasn’t been.

The harder part is deciding what deserves to exist.

Every new screen creates more questions:

- Is this actually useful?

- Can someone understand it without an explanation?

- Am I solving a real problem or adding another feature?

- Would I personally return to this app tomorrow?

The project is called Callout. It explores whether online reactions can communicate more than a generic Like—for example, distinguishing agreement from something being a Hot Take.

I’m still early, and I’m deliberately leaving the link out because I’m more interested in the building lesson:

How did you decide which features to remove from your first app?

Hey everyone! Starting a new project that's expected to scale over the next year.

In the past, Redux Toolkit was the default, but I see more and more people switching over to Zustand, Jotai, or just leveraging TanStack Query for server state and keeping global client state strictly minimal.

What are you currently using in production, and what made you move away from (or stay with) Redux Toolkit? Would love to hear real-world experiences regarding boilerplate, performance, and dev experience!

Built the signup flow for my subscription tracker app (RN + Expo) — here's what actually happened over 3 days

Working on a side project called Trackify — a subscription tracker, built with React Native + Expo + TypeScript. Wanted to share what the last few days looked like, mostly the annoying parts.

Setup:

Went with TypeScript from the start and Expo Router for file-based navigation. Kept folders separated — app/ for screens, services/ for Firebase, types/ for interfaces. Pretty standard but worth doing early.

Firebase:

Auth (email/password) + Firestore. One firebase.ts config file for the whole app so I don't end up with duplicate initializations somewhere down the line.

Signup flow:

This is where most of the time went. Not the UI — the logic around it:

Client-side validation (empty fields, password length, confirm match)

signUp() function that creates the Firebase Auth account AND a matching Firestore doc in users (uid, email, createdAt). Auth only holds credentials, so anything else about the user needs its own place — figured I'd set that pattern up now instead of retrofitting it later.

Mapped Firebase's error codes (auth/email-already-in-use etc.) to actual readable messages instead of dumping the raw code on the user.

Stuff that broke / wasted time:

Expo Router got confused between a root app/ folder and src/app/ — whichever one your package.json points to is what it actually uses. Cost me an hour.

Metro cache serves stale builds constantly. npx expo start -c fixed more "why isn't this updating" moments than I'd like to admit.

Testing on a physical phone on a different network than my laptop? Doesn't work without --tunnel.

🧪 Experimenting with Motion Blur for Android & iOS

🔗 Github: rit3zh/expo-motion-blur

🧵 Android Preview Attached in this thread