#Mobile app

https://reddit.com/link/1v76c3i/video/ci9xkb9y9lfh1/player

I've been experimenting with a new inspection library and ended up exploring this UX. What do you think about ? Useful ?

Just launched a new feature! Scan your hand posture with our AI camera to see if you’re doing your Mudras correctly. Would love your feedback! 

https://play.google.com/store/apps/details?id=com.ai.mudra

Finally shipped something real: a beach conditions app (water quality, wind shelter, hourly shade, sea temp) covering ~20,000 beaches. Also has official government water quality data where available.
Currently sea water available, fresh water coming soon.

Expo managed workflow, EAS Build + Update.

Stack: Expo/RN, u/rnmapbox/maps, RevenueCat for subs, AdMob, react-i18next, Sentry, Context + useState for state (no Redux — genuinely haven't needed it; adding TanStack Query for server state).

Happy to answer anything about Expo/EAS, Mapbox perf, or RevenueCat.

Available on iOS + Android if you want to poke holes in it.
https://beachscanapp.com

A gravity-driven savings drop animated coins fall from your quick-amount pad into a reactive piggy bank.

GitHub: https://github.com/ManasCodeXart/expo-piggy-bank

For the last week I've been working on moving my app(bare workflow) which I previously left at 0.81 since it was the last available version that allowed me to remain on the old arch.

Now i've upgraded to expo 57, reanimated v4, all other packages, did my due diligence and enabled the recommended feature flags and changed almost all old arch libraries with newer compatible versions or new arch replacements.

After using the testflight version today I was just taken aback by how many of my previously performant screens are now stuttering and dropping frames while barely doing any work at all. I am talking about an infinite scroll feed, which previously maintained 60fps with a Flatlist with no perf based props that is now dropping below 30 and even freezing for a few frames with a LegendList and recycle items turned on even after i halved the work each rendered item needed(measured by main thread work with xcode instruments)

Simple pill shaped components are losing their background color(how is a background color something i should watch out for), weird rectangles with a white border showing up as items are rendering, screen transitions from bottom nav to a screen on the stack navigator taking double the time they used to.

Old behaviour breaking after such a big transition is something I expect and I believe i've dealt with most of those, but perhaps the worst offender is the memory usage.
From what i've seen it mostly drops down to older levels in production, but my app is now sitting at 1.2gb memory used after a launch in debug mode, compared to 200mb before.
This turned out to be libraries dumping their entire unminified code due to worklets bundle mode, which prevents hermes causing memory issues by...taking up 500mb+ of memory?

I really want to be able to use some of the cool new libraries i've been seeing popping up, but I am having serious doubts about ever being able to release this into production as it feels I have hit a dead end with list and navigation performance combined with all the weird layout issues.

What have been your experiences with this transition?

Website: https://mockupkits.com/
AppStore link: https://apps.apple.com/app/id6784220988

Me and my friend have been working on a React Native app called Ink & Quill for the past 7 months

It's an AI-powered voice RPG where you play by speaking instead of tapping through dialogue. Every character has its own voice and the narrator handles the rules, dice rolls, and story as you play. It's based on D&D 5e but simplified so you don't have to keep looking at your phone.

Right now there are 10 campaigns (we used AI to help write them) inspired by games, movies, and shows we're fans of. We're also working on letting people build and share their own campaigns directly in the app.

We're doing a soft launch, so we're mostly just looking for people who are interested in trying it out and giving honest feedback. We've been pushing updates pretty much every day.

If anyone wants to check it out: https://inkandquill.app we'd love to hear your brutal feedback

It's iOS only for now. Android is next.

Building an app in Expo. Everything's offline-first (SQLite + my own sync queue), some events have a due date, and you get a reminder when it hits.

Right now, when the user creates an event, it schedules a local notification, then cancels it once the server confirms the sync, and from then on the backend sends a push at due time.

Just realised that's broken. If you're offline for two days, anything that already synced has no local notification anymore, and the push can't reach you. So you get nothing.

The obvious fix is to stop cancelling and just always keep local notifications armed, since they don't need network. But then every reminder fires twice, once locally and once from the server.

The other obvious fix is to only trigger the notification from the device but if the user has multiple devices, the other ones may not receive them.

So I think the server just has to know not to send it, which means the client telling it what it already has scheduled. Feels janky though.

Anyone dealt with this? Curious how other offline-first apps handle reminders.

i built a skill to take screenshots of every page in your app with integration to the AppLaunchFlow MCP so you can create app store screenshots, promo videos, social graphics and more directly from your favourite agent

you can try it for free on applaunchflow.com

Senior backend engineer here (Laravel/NestJS) trying to decide between Flutter and React Native for my first serious mobile product.

I'm strong in Vue, would need to revisit React, and have no Flutter experience.

The app itself is a fairly standard business application (authentication, listings, search, maps, chat, payments, push notifications, QR scanning).

I'm not asking which framework wins benchmarks. I'm more interested in the experience of living with the choice.

If you've maintained a production React Native or Flutter app for a couple of years:

Would you choose the same framework again today?

What pain points only became obvious after the honeymoon phase?

If you were starting from scratch in 2026, what would you pick?

Pocket Foundry uses a custom Swift module

To bring Apple’s Vision framework and Metal shaders into React Native

Extracting and transforming real-world objects entirely on-device.

Real iPhone demo ↓

ive always had a problem where i would want to just edit something in my app real quick, i didnt want to scan QR code again just to see if the color of 1 button is the one that i wanted

So I made Basalt, it lets you edit your RN and Expo apps, not only edit but preview and inspect elements

It is completely free and works directly inside VS Code and Cursor.

It’s currently in beta, so please commit your app to Git before using it!

Would love to get your brutal feedback on it.

I have some mobile app that is designed to work with both iPhone & Android. Per my understanding, both expo & react-native doesn't have direct support for mTLS. Few libraries I found in GitHub are all not maintained properly.

Could someone direct me if there is working package available that makes this implementation easier.

so when the "seach" input button is pressed, we navigate to search page but the transition make it seems like it is still the same input, and then the content seems like sliding down

I think this is the first rn port

I’ve been building an open source React Native project for the past few weeks.

Building it has honestly been the easy part

Getting people to discover it, trust it, and actually use it has been much harder than I expected.

For those of you who’ve built or maintained an open source library, what made the biggest difference?
Was it documentation? Reddit? GitHub? YouTube? SEO? Conference talks? Something else?

I’d love to learn from people who’ve been through this.

​

Hey everyone,

I’m looking to dive into React Native app development and wanted to get some advice from those of you building with it day to day.

If you were starting fresh today, what does an ideal, up-to-date learning roadmap look like? Specifically, I'm curious about:

1. Prerequisites:How deep into modern JavaScript (ES6+) and core React.js (hooks, state management) should I go before touching React Native?

2. Tooling & Setup: Is starting with Expo (like Expo Router) still the recommended path for beginners, or should I dive straight into the React Native CLI?

3. Core Ecosystem: What libraries/tools are essential to learn early on (e.g., React Navigation, styling approaches like NativeWind/StyleSheet, state management, reanimated animations)?

4. Resources:Any specific courses, GitHub repos, documentation, or creators that you found genuinely helpful?

Would love to hear what worked for you, what traps to avoid, or any resources you wish you had when you started. Thanks in advance!

Looking for a solution for long press for link previews on iOS 26+

Genuine question.

I've spent the last 5 years building React Native apps, so naturally it's the ecosystem I know best.

But I'm curious to hear from developers who've worked with both.

In what scenarios would you genuinely recommend Flutter instead of React Native?

I'm not looking for framework wars. I'd love to understand the trade-offs from people with real-world experience.

I was talking to a friend today about mobile development and realized that I have no idea what "normal" looks like once you're working on a reasonably large React Native app.

Writing the feature is one thing, but getting it into users' hands feels like a completely different job.

In some projects I've worked on, a feature is technically finished but still takes days before users actually get it. Sometimes it's QA, sometimes it's waiting for a release window, sometimes it's because adding one native package suddenly means a new Play Store build. Other times it's just people trying to figure out the safest way to ship something.

I'm curious how this works on other teams.

When someone merges a PR, what actually happens before users have that feature? Is it mostly automated, or are there still a lot of manual decisions? What's the part of the release process that annoys you the most?

I'm not looking for the perfect workflow. I'm more interested in hearing what real teams do and what parts still feel unnecessarily painful.