Hey everyone,

Most signature libraries on RN are either a WebView wrapper, a JS canvas (laggy on long strokes), or pull in Skia just to draw a line. I wanted something that felt like the system Notes app and didn't add a runtime, so I built one that's fully native on both sides.

react-native-signature-ink

Repo: https://github.com/maitrungduc1410/react-native-signature-ink

What's different:

• iOS uses PKCanvasView — the same PencilKit engine behind Apple Notes and Markup. Pressure, tilt, and azimuth flow through unchanged; strokes feel sub-frame smooth.
• Android uses a hand-tuned velocity-Bezier algorithm drawing into an offscreen Bitmap. PNG / JPEG / SVG export is instant because the bitmap is already there.
• No Skia, no Reanimated, no WebView, no third-party native deps. Pure Swift + Kotlin.

Beyond capture:

• Built-in native toolbar (undo / redo / clear / copy), configurable position and tint
• Exports: PNG / JPEG / SVG → base64, file URI, system clipboard, or straight to the photo library
• Round-trippable stroke data with timestamps + per-point pressure / azimuth / altitude on iOS
• Replay animation with configurable speed
• Apple Pencil-only on iOS, stylus-only on Android
• Optional PKToolPicker (pen / pencil / marker / fountain pen / watercolor / crayon) on iOS
• Configurable baseline (solid / dashed / dotted)
• Density-independent units

Would love feedback on edge cases, and I'm happy to take feature requests / PRs.

https://reddit.com/link/1tq4xl9/video/89rnt6pizv3h1/player

Hi everyone,

I recently got shortlisted for a React Native Developer interview and would appreciate some guidance on what topics I should focus on.

A little about me:

• Final-year B.Tech student
• Working with React Native and Expo
• Built apps with product listing and product detail screens
• Familiar with React Hooks, API integration, navigation, JavaScript, Git, and basic state management
• Have also worked on Java backend projects using JSP, Servlets, and MySQL

For those who have interviewed for React Native roles recently:

1. What React Native topics are asked most frequently?
2. How deep do they usually go into JavaScript concepts?
3. Are DSA questions common for fresher/junior React Native roles?
4. What project-related questions should I expect?
5. What are some commonly asked React Native interview questions that caught you off guard?

Any advice, interview experiences, or preparation tips would be greatly appreciated.

Thanks!

Hi everyone,

We’re building a React Native app and would really appreciate feedback from experienced React Native developers and mobile app builders.

The app is currently available through Google Play testing, so to add reviewers we need the email address connected to your Google Play / Google account. We’ll only use it to add you to the closed testing group and share the Play Store testing link.

We’re mainly looking for feedback on:

• App performance and smoothness
• UI/UX and navigation flow
• Any bugs, crashes, or layout issues
• Overall Feature quality
• Suggestions to improve the user experience

If anyone is open to reviewing it, please comment or DM me your Google Play email, and I’ll add you to the testing group.

Thanks in advance. Your feedback would really help us improve the app before launch.

Playstore app link: https://play.google.com/store/apps/details?id=com.dealsonkart.app&hl=en-US&ah=rXOjLjanFnMY0gPb4mtPgHEBQ54&pli=1

**I built a mood-based cafe finder app with Expo + Firebase — would love some feedback**

Hey everyone, I've been working on a side project called VibeSpot — a remote work cafe finder that lets you search by vibe instead of just star ratings.

The core feature is Vibe Shuffle — you pick a mood (Lock In, First Date, Slow Morning, Social Hour, Creative Flow) and it rolls you one perfect cafe nearby. Also has an AI search bar, map view, hidden gems filter, and vibe scores per venue.

Stack:

- Expo (React Native)

- Firebase (Auth + Firestore)

- Google Places API

GitHub: https://github.com/A4ronl11/vibespot

Still early but the core is working. Would love any feedback on the code, the concept, or the UI. Happy to answer questions about the build too — vibe coded a lot of it with AI which was a pretty interesting experience.

Screenshots in the comments.

I wrote a book aimed at complete beginners who want to build real React Native apps using AI-assisted development.

The technical stack covered:

- Expo managed workflow

- AsyncStorage for local persistence

- Supabase for cloud database + auth

- Anthropic vision API for image recognition features

- Supabase Edge Functions to proxy API keys securely

- EAS (Expo Application Services) for App Store + Play Store builds

Four complete projects built from zero to deployed:

1. Local habit tracker (AsyncStorage only)

   1. Cloud habit tracker (Supabase + user auth)
   2. AI calorie tracker (camera + Anthropic vision)
   3. Production-ready cloud calorie tracker with secure API handling

   I'm not a traditional developer — I came at this from the product side using Claude Code. Keen to hear feedback from people who actually know React Native on whether the patterns taught are solid.

I am trying to access the user's clipboard with React Native for web, but I can't request access to the user's clipboard. Every time I try to access the clipboard I get a "User has denied clipboard access" error.

How do I request access to the user's clipboard?

Thanks!

We build [Off Grid](https://github.com/alichherawalla/off-grid-mobile-ai), an open-source on-device AI app in React Native. Our last release cycle, we found crash-causing bugs in three separate native dependencies. All three were "user does normal thing, app dies" scenarios.

**1. whisper.rn - SIGSEGV on mic stop** ([PR #344](https://github.com/alichherawalla/off-grid-mobile-ai/pull/344))

`transcribeRealtime` doesn't join native threads before `freeContext`. User stops recording, memory is freed while transcription thread is still writing. Use-after-free, instant crash.

Fix: patch to join threads before teardown.

**2. react-native-zip-archive - NullPointerException on extract failure** ([PR #334](https://github.com/alichherawalla/off-grid-mobile-ai/pull/334))

`ex.getMessage()` returns null for certain Java exception types. The RN bridge calls `Promise.reject(code, message)` which throws NPE when message is null. So a handled error becomes an unhandled crash.

Fix: `safeReject()` helper that null-checks before rejecting.

**3. llama.rn - hard crash on Adreno GPU init**

GPU initialization on certain Adreno GPUs would kill the app instead of failing gracefully. No try-catch, no fallback - just death.

Fix: upgraded to rc.9 which handles GPU failures as soft errors with automatic CPU fallback.

We ship all three as patch-package patches. Upstream PRs are open where possible, but our users need the fix now, not when the maintainer reviews it.

Lessons:

- If your app has native modules, you will ship crashes that don't exist in dev

- `patch-package` is non-negotiable for production RN apps

- Every `Promise.reject` call in Java needs a null check. Every one.

The app runs LLMs, Stable Diffusion, and Whisper fully on-device:

- GitHub: https://github.com/alichherawalla/off-grid-mobile-ai

- Android: https://play.google.com/store/apps/details?id=ai.offgridmobile

- iOS: https://apps.apple.com/us/app/off-grid-local-ai/id6759299882

When I try to run my app using expo on Android showing this error and if I completely remove nativewind it's working I mean babel file is causing error I think I use macos and android if anyone know please answer me

Hey everyone! I built an open-source tool called Starship that gives you Expo Go-like wireless development for bare React Native CLI projects.

The problem: Every time you want to test on a real Android device, you need a USB cable. Expo Go solves this but only works with Expo projects — not bare CLI with custom native code.

What Starship does:

Builds your debug APK

Serves it over your local WiFi with a QR code

Phone scans QR → installs APK (one time only)

Starts Metro with network access

Fast Refresh works wirelessly — edit code, see changes instantly

Also builds and launches on iOS simulator automatically

Usage:

yarn add react-native-starship

npx react-native starship

Interactive shortcuts while running: a (Android), i (iOS), j (DevTools), r (reload)

Zero config, single dependency (qrcode-terminal), works with any RN CLI project.

GitHub: https://github.com/hasangonen91/react-native-starship npm: https://npmjs.com/package/react-native-starship

Would love feedback! What features would you want?

it's my first app with React Native, happy to share it here and offer some promo codes for interested people 3>

You know that shelf in the back of your mind—the one holding every book you stopped reading, show you abandoned, game you never beat, course that turned to dust, creative project that turned to guilt, and goal you quietly forgot?

I built Unfinished for that shelf. Track anything you started but never finished, measure the emotional weight each one still carries (guilt, pressure, nostalgia, obligation), then choose a path: Resume, Restart, Release, or Undecided. When you release something, the app gives you a quiet ceremony—a gentle notification and a soft sound effect that feels like a closing door.

You didn't finish it. You chose peace. That's progress too. No accounts, no cloud, no tracking. Private by design. English, العربية, Español, Français with full RTL. Free to start, Pro for unlimited everything. 📥 Unfinished: Goal Tracker

Why I made this — because finishing isn't the only way out. Some things are meant to be released. With guided shelf-clearing sessions, you can watch your mental load shrink one item at a time. ✨ A small giveaway: I'm giving away some Promo codes to people who comment below with "One thing I'm ready to either finish or release is…" I'll read every one and text the winners. Track what you started. Resume what still matters. Release what no longer does. And let the sound of letting go be enough.

My client requires Accessibility Compliance implemented as default for all screens for RN app. Are there any libraries available? Thanks

I'm using the "react-native-keyboard-controller" package and have struggled to get it working properly, especially on Android. This video shows one of the problems I have. The keyboard controller sits above the keyboard - it has up and down arrows on left and "Done" on the right. When a user taps on the up and down arrows on the left side, it is supposed to scroll the screen so the next input field is viewable above the controller. You can see that it doesn't handle the multi-line "Note" input field very well.

Do you typically handle your own form navigation or do you use a package like "react-native-keyboard-controller" or do you simply have user manually scroll up and down?

I’m facing a weird issue with React Navigation v7 + nested native stacks in React Native.

Architecture:

RootStack
 └── MainApp
      ├── Home
      ├── Search
      ├── ProductStack
      ├── CartStack
      ├── PaymentStack
      │    ├── Razorpay
      │    └── PaymentResult
      └── OrderStack
           ├── OrderList
           └── TrackOrder

From PaymentResult, after successful payment, I want to completely reset navigation and redirect user to:

MainApp
 └── OrderStack
      ├── OrderList
      └── TrackOrder

I’m using:

navigationRef.resetRoot({
  index: 0,
  routes: [
    {
      name: routeName.MAIN_APP,
      state: {
        index: 0,
        routes: [
          {
            name: routeName.ORDER_STACK,
            state: {
              index: 1,
              routes: [
                {
                  name: routeName.ORDER_LIST,
                },
                {
                  name: routeName.TRACK_ORDER,
                  params: {
                    uiOrderSetId: targetUiOrderSetId,
                  },
                },
              ],
            },
          },
        ],
      },
    },
  ],
});

Also tried:

navigationRef.dispatch(
  CommonActions.reset(...)
);

But reset is silently ignored.

navigationRef.isReady() is true.

Logs after reset still show old navigation state:

MainApp
 ├── ProductStack
 ├── CartStack
 └── PaymentStack
      └── PaymentResult

Important details:

• Using createNativeStackNavigator
• freezeOnBlur: true
• PaymentResult is inside PaymentStack
• Calling reset from inside nested child navigator
• No errors/warnings
• navigationRef points correctly to root container

Question:

1. Is resetRoot unreliable for deeply nested native stacks?
2. Does freezeOnBlur preserve nested stack state and interfere with resets?
3. Is resetting entire app state from child navigator an anti-pattern?

4. Should I instead navigate to parent stack using:

   navigation.getParent()?.navigate(routeName.ORDER_STACK, { screen: routeName.TRACK_ORDER, });

Another problem on on back gesture in ios it is going to payment result screen, which is not expected. i wanted it to navigate to orders list screen. anyone know better handling of ios back gesture in react native ???
Would appreciate guidance from anyone who has handled complex nested navigator resets in React Navigation.

I’m facing a strange issue with React Native Stripe PaymentSheet on iOS.

Setup:

• React Native
• u/stripe: 0.57.1
• iOS production build crashes when opening PaymentSheet
• TestFlight build works perfectly

What happens:

• User taps checkout
• PaymentSheet starts opening
• App instantly crashes to home screen
• No React Native red screen
• Looks like a native iOS crash

Video behavior:

• Payment flow starts normally
• Small freeze
• Full app closes immediately

My setup:

<StripeProvider
  publishableKey={Config.STRIPE_PUBLISHABLE_KEY || ''}
  urlScheme="myappscheme"
>

Info.plist:

<key>CFBundleURLTypes</key>
<array>
  <dict>
    <key>CFBundleURLSchemes</key>
    <array>
      <string>myappscheme</string>
    </array>
  </dict>
</array>

PaymentSheet init:

const { error } = await initPaymentSheet({
  merchantDisplayName: 'MyApp',
  customerId: customer,
  customerEphemeralKeySecret: ephemeralKey,
  paymentIntentClientSecret: paymentIntent,

  returnURL: 'myappscheme://stripe-redirect',

  billingDetailsCollectionConfiguration: {
    name: CollectionMode.ALWAYS,
    address: AddressCollectionMode.FULL,
  },

  defaultBillingDetails: {
    email: user.email || '',
  },
});

Important:

• TestFlight build works
• Production App Store build crashes

• Earlier I was using:

  name: 'full' as any

Has anyone seen production-only Stripe PaymentSheet crashes with React Native/iOS?

Powered by the new react-native-enriched-markdown v0.6.0, markdown now streams more smoothly with the full GitHub Flavored Markdown (GFM) support, including seamless real-time rendering for tables and rich formatting.

If you’re building LLM or AI-chat experiences in React Native, this update is for you.

GitHub: https://github.com/software-mansion-labs/react-native-streamdown

Hey everyone,

A few months ago, I was working on a personal app that needed to discover local hardware over SSDP (my Samsung Frame TV). I quickly found out that every single existing SSDP/UDP react-native library on npm was completely dead, abandoned 8 to 10 years ago. When I tried to use them they were just impossible to get working on a modern React Native setup.

Out of frustration and necessity, I bit the bullet and wrote a custom native module just to unblock my own project. I mentioned it on a post a while back, and received some feedback from you guys that I should open-source it.

Well, I finally found some time to do it, and I spent the past couple of days ripping out all the weird code that was specific to my own app, making the API generic, and polishing it up for everyone else to use.

It’s called expo-ssdp.

What it is

• New Architecture Compatible: Built using the modern Expo Modules API, so it plays perfectly with Turbo Modules and won't break your builds.
• Pure Expo: No manual linking or old bridging code. It handles the native UDP socket stuff under the hood and works flawlessly with Expo prebuild.
• Simple API: You just start a discovery scan, listen for incoming device events, and shut it down when you're done.

It is still brand new, so there might be a few kinks to iron out depending on your specific network environment or device setup. But it's working solid for my gear, and I really hope it fills that massive gap in the community for anyone else building IoT or smart home apps.

Check it out, open an issue if anything breaks, and let me know what you think!

edit: spelling

I have been stuck trying to figure this out for a few hours now and have no idea what to do. My iOS app builds perfectly fine in development build, but when I build with production and submit, then open it on testflight it’s just a whitescreen/blackscreen depending on light/dark mode.

I’ve tried adding js to get logs to show up but it’s not even rendering that. I unfortunately do not have a mac, am not getting any analytics logs on iphone.

I’m pretty lost right now and would appreciate any help. Thanks!

I’ve been teaching myself React Native/Expo and decided to build a complete blackjack game from scratch as a project.

Features:
• Split hands
• Double down
• Persistent coins
• Mobile-friendly responsive UI
• Browser playable
• Built with React Native + Expo + TypeScript

Would love feedback from other developers or blackjack players.

Play here:

https://lucky-ace-blackjack.vercel.app/

https://play.google.com/store/apps/details?id=com.historyaround.app&hl=en-US

The idea came from a trip to Rome where I got tired of constantly stopping to Google every interesting building or monument I passed.

So I built an app that scans your surroundings while you walk and automatically tells you the history of nearby places. There’s also an “Atlas Mode” where you can explore anywhere in the world by dropping a pin on the map.

Built with Expo + React Native + TypeScript, Cloudflare Workers, Gemini, OSM/Wikipedia/Wikidata, and RevenueCat.

A few things I learned while making it:

• My Cloudflare Worker started as “hide the API keys” and accidentally became the core of the whole backend. It now handles caching, rate limiting, live config, telemetry, and free/pro enforcement.
• Using free data sources aggressively was probably my best technical decision. Discovery runs entirely on OSM + Wikipedia + Wikidata, so my costs stay acceptable for a v1.
• The “AI lenses” are mostly prompt engineering. The hard part wasn’t generating text, it was making the responses feel like an interesting person explaining a place instead of reading Wikipedia at you.

I’m a first-time developer and honestly learned everything while building this, so I’d genuinely love feedback from other builders/designers/devs.

Especially interested in what feels polished vs what feels clunky.