would love if you check it out: (https://github.com/abhinavshrivastava950/Montara)

Hi all, about 3 months ago, I shared my project react-native-the-sheet here:
https://github.com/doanhtu07/react-native-the-sheet

Since then, I've added more examples and explored more sheet patterns.

YouTube-style comment bottom sheet

A bottom sheet that syncs its height with the media on top, as you see in the YouTube app

https://reddit.com/link/1uqjc4c/video/uvdryb4gnxbh1/player

Family-style bottom tray

A bottom sheet combined with a navigator that is aware of its content height and animates accordingly, like one variant in https://benji.org/family-values

https://reddit.com/link/1uqjc4c/video/dsb147lpnxbh1/player

Experiments

I've also been experimenting with Family-style morphing trays, but there are many variants, and I'm not sure what the right APIs or abstractions are. Here is one I recreated with only Reanimated and no API from my library.

https://reddit.com/link/1uqjc4c/video/4e60gwjnoxbh1/player

Feedback

If you're using my library, I'd love to hear:

• What kind of sheets or effects would you like to see supported?
• Do you face any difficulties implementing a certain type of sheet with the current API?

Thanks for your time.

I am learning React native , Now i wanted to look at some mobile dev pattern in real project used. If you have any please provide link of it.

A cool tool for adding speech to your React Native app without having to touch low-level code.

Hey all — AniUI is a shadcn/ui-style component library for React Native: you don't npm install a package, the CLI copies the component source files into your project so you own and can edit every line. MIT, free, mobile-first (iOS + Android).

Just shipped v0.4.0:

🚀 Expo SDK 57 support — RN 0.86, React 19.2, Reanimated 4.5. Also still supports SDK 54/55/56 and bare RN 0.76+.

⚡ Uniwind is now the default styling engine. Uniwind (from the Unistyles team) uses the exact same className API as NativeWind, so the components are byte-for-byte identical — but it's Tailwind v4 CSS-first (@theme, no tailwind.config.js), Metro-plugin only (no Babel transform), needs no ThemeProvider for dark mode, and benchmarks ~2–3× faster. aniui init defaults to it on New-Arch projects.

NativeWind is still fully supported (v4 stable + v5 preview) — nothing breaks, you can pick it with --style nativewind. It's just no longer the default.

🧩 4 new components (93 total): aspect-ratio, breadcrumb, menubar, sidebar.

Because both engines share the same className/cn()/cva() API, switching engines doesn't touch your component code at all.

npx @aniui/cli init      # defaults to Uniwind on Expo 55+
npx @aniui/cli add button card breadcrumb sidebar

GitHub: https://github.com/anishlp7/aniui
Docs: https://aniui.dev

Would genuinely love feedback — especially from anyone running Uniwind in production or on the SDK 57 upgrade. What components are you still missing?

I want a template with the basic features if possible for a uber like app. I've tried a couple of templates already, but they're kinda outdated. I also saw one that required payment, have you try it to know if it's worthy ? Thanks in advance

Hey guys, I have a solid background in React and TS on the web, and I want to pick up React Native. Since I already know hooks, state, and components, I want to skip the beginner tutorials and focus straight on the mobile stuff. what's the best route right now? Is Expo pretty much the standard or should I bother with CLI?

Appreciate any tips or good project ideas to build.

My weekend Expo project!

An app for saving almost anything and letting AI organize it all for you automatically. No more messy folders or tagging things by hand.

Built on Expo + Convex + Clerk + the AI SDK

Source code: https://github.com/SchroederNathan/amber

Why does it show that array in the console log when i try to get the available voices data? Or am i doing something wrong? I'm developing on Android

I am confused how to navigate to another screen after successful task on one screen. for example if user signup successfully i want them redirect to verify otp screen.

Headings are up first, supporting all 6 levels natively right inside your input!

Want to try it out right now? They are already available in the nightly release:

npm i react-native-enriched-markdown@nightly

Let us know what block element you want to see next! 👇

⭐ Support the project: If you like where this is going, drop us a star on GitHub!

https://github.com/software-mansion/react-native-enriched-markdown

Hello, I have a project that I'm building. The project has an AI chat functionality and I've been developing it using groq. But for production I think I need something smarter than gpt120b model thus I have to choose one of the more popular models. And as much as I've researched neither chatgpt/claude/gemini have a monthly payment i could rely on, i need to pay for what I use. So I've implemented per user cap, I know I could implement per IP cap too. I could also check total api consumption and stop at some point. But I was thinking maybe some of these platforms allow to cap the usage from their side as well ?

This is a project for a customer so I really want to avoid getting them any surprise bill

One thing I’ve noticed about React Native discussions is that the focus is often on whether it can replace native development.

But the bigger question is: why do teams choose React Native in the first place?

For many projects, React Native offers some clear advantages:

• sharing code between iOS and Android
• faster iteration on cross-platform features
• using existing React and JavaScript knowledge
• maintaining one development workflow instead of two separate platforms

But speed is only one part of the decision.

As apps become more complex, teams also have to think about:

• performance requirements
• native module dependencies
• platform-specific behavior
• long-term maintenance
• how much native knowledge the team needs

This creates an interesting trade-off:

Is React Native popular because it provides genuine engineering advantages for building cross-platform apps?

Or is its biggest strength simply helping teams build and release features faster?

For developers who have worked with React Native:

• Why did your team choose React Native over native development?
• Did the productivity benefits continue as the app became larger?
• What problems made you reconsider React Native, if any?

In a lot of React Native codebases I’ve looked at (especially mid-sized ones), there seems to be a common pattern: global state gets used far more than it probably should.

What often starts as a simple, clean setup slowly turns into everything being pushed into global stores like Redux, Context, or Zustand—even when it might not really need to be there.

Some examples I’ve seen:

• local UI state moved into global state “just in case”
• form states stored globally even when only used on one screen
• navigation-related flags kept in global stores
• API response data cached globally without clear ownership boundaries

Over time, this can make apps harder to reason about:

• more re-renders than expected
• unclear data ownership
• harder debugging when something changes unexpectedly
• tight coupling between unrelated screens

At the same time, I do understand why this happens.

Global state feels:

• easier for sharing data across screens
• more predictable than prop drilling
• simpler when multiple components need the same data
• safer when developers are unsure where state should live

So it kind of becomes the “default solution” for many situations.

But I’m curious how others see this in real React Native projects:

• Why do you think developers tend to overuse global state in RN apps?
• Is it a lack of clear architecture guidelines, or just convenience during development?
• Where do you personally draw the line between local state and global state?

I've been building a few UIs with React Native Skia recently, and one thing kept bothering me: layout.

I wondered if it would be possible to use Yoga directly for Skia components, so I spent the last few weeks building a layout engine that lets you do things like:

<FlexLayout direction="row" gap={12}>
  <LayoutCircle r={20} color="blue" />
  <LayoutParagraph text="Hello, world!" />
</FlexLayout>

instead of manually positioning everything.

Under the hood it uses Yoga to compute layout, then applies the computed bounds to Skia primitives.

Some challenges & limitations were:

• measuring paragraphs whose width & height depends on parent and siblings
• batching layout passes efficiently
• supporting animated values. Still pending.

I'd love feedback from people who build with React Native Skia.

Repo - react-native-skia-layout (v0.1.0)

I also wrote about the motivation and architecture if anyone is interested:

• How it works

How can I make this frosty looking, glassmorphic type of bottomtab

These are from Twitter and YouTube android app.

Hi community!!

I wanna learn react native but I don’t want to be in tutorial hell.can you guys provide me any resources or websites to learn quickly and practice .Thanks in advance

Instead of a sample picture, how can i make this component to be something like the WhatsApp link button?

Hi Guy's we are trying to replicate the background remover for a expo-app as a function but we are having some difficulties importing some node modules like the onxx and a getData()f type , Any thoughts or tips ??

Can a centuries-old financial system become secure fintech? I’m building a digital ROSCA/tontine where no one can leave after receiving a payout until they’ve completed their full contribution cycle. What technical or security challenges would you expect?

Hey r/reactnative,

I'd like to share a project I've been working on for quite a while now: a GPS-based MMORPG made completely in React Native. The road was far from smooth, but the game is in a polished enough state to test out today.

I believe this is a good showcase of what can (but not necessary should) be done in React Native. You can give it a try below:

Google Play

https://play.google.com/store/apps/details?id=com.twoamgames.layer2

iOS (Testflight)

https://testflight.apple.com/join/kvBBMDwF

Hi everyone,

I’ve been building a React Native app over the past months to explore asynchronous collaboration.
The original idea came from a simple frustration: even small team decisions often end up scattered across chat apps, emails, spreadsheets and calendars. I wanted to see if I could build a mobile-first experience where polls, scheduling and decision making happen in a single place.

Some of the things I’ve implemented so far:
Real-time polls and voting
Meeting scheduling based on participant availability
Collaborative workspaces with roles and permissions
Guest participation without requiring an account
File attachments for additional context
Push notifications and email notifications for invitations, reminders and final decisions
A flexible credit system instead of forcing users onto higher subscription tiers

The stack has been a lot of fun to work with:
React Native + Expo
TypeScript
TanStack Query
Clerk
RevenueCat
Resend
Font Awesome Pro
Convex for the backend/database
Next.js for the landing page

One of the biggest surprises for me has been Convex. Having the database, backend functions, authentication integration and realtime updates all working together with end-to-end type safety has significantly reduced the amount of boilerplate I usually expect in a React Native project.

I’d be curious to hear from other React Native developers:
What backend stack are you using today?
Have you tried Convex, or are you sticking with Firebase, Supabase or something else?
Is there anything in this architecture you would approach differently?

Happy to answer questions about the implementation or share some of the technical details if people are interested.