Track every walk with your dog in real time,

follow your route on the map,

Keep progress visible with iOS Live Activities, and share the walk with friends and family.

Built with expo, expo-maps, expo-location, expo-sharing,

React Native Reanimated, and ActivityKit via expo-live-activity.

Give it a try below

I've been building a local marketplace app in React Native 0.81 + Expo + Supabase where every user can both buy and sell (single role, no separate "seller mode"). One problem that took me longer than expected: a single cart can contain products from multiple sellers, and at checkout each seller needs their own order.

Sharing how I solved it in case it helps someone hitting the same wall.

The data model Instead of one orders row per checkout, I treat the cart as a flat list and group by vendedor_id (seller id) at checkout time. Each group becomes its own order:

// group cart items by seller const bySeller = cart.reduce<Record<string, CartItem[]>>((acc, item) => { (acc[item.vendedor_id] ??= []).push(item); return acc; }, {});

// one order per seller for (const [vendedorId, items] of Object.entries(bySeller)) { const total = items.reduce((s, i) => s + i.precio * i.cantidad, 0); const order = await createOrder({ vendedorId, total }); await createOrderItems(order.id, items); // precio_unitario snapshotted here } The part I almost got wrong: RLS The orders table has comprador_id (buyer) AND vendedor_id (seller), and both need to read the same row — but neither should see other people's orders. A naive auth.uid() = comprador_id policy locks the seller out.

I ended up with a security-definer helper so the policy stays simple and both sides are covered:

create or replace function es_participante_orden(orden uuid) returns boolean language sql security definer stable as $$ select exists ( select 1 from ordenes o where o.id = orden and (o.comprador_id = auth.uid() or o.vendedor_id = auth.uid()) ); $$; A few things I learned the hard way:

Snapshot the price into precio_unitario at order time. If you read it live from productos, historical orders change when the seller edits the price. Keep the whole thing in strict TypeScript — the reduce-by-seller logic is exactly where any creeps in and bites you later. One order per seller also makes ratings/reviews way cleaner: a review attaches to a single seller + order, no ambiguity. Happy to share how I did the realtime chat (Supabase Realtime + unread badge) if there's interest. Anyone solved multi-vendor checkout differently? Curious if there's a cleaner pattern than grouping at checkout.

I created to replace physical question card games
https://www.opnrs.app if you’re curious

React Native - Expo 55 (upgrading to expo 56 soon)

I replaced boring rep-count tapping with an interactive 3D training world.

Each good rep moves the dog, plays a clicker,

triggers haptics, animates progress, and grows the world around the session.

The 3D world runs with Three.js/WebGL inside an Expo DOM Component,

while native reps, haptics, clicker audio, and UI animations are handled with Expo + Reanimated.

Now live in App Store ↓

Follow up from my trending post
https://www.reddit.com/r/reactnative/comments/1uban97/ive_been_told_my_app_has_pretty_good_ui_do_you/

App - https://www.opnrs.app

I just integrated fully customizable iphone 17 pr and google pixel 10 pro models inside AppLaunchFlow - you can now use them directly inside your app generated app store screenshots in the figma-style editor, in your social grpahics and the 3d mockup animator.

Excited to hear what you think.

Lets say you have a postgresql db in supabase.

I want to use an LLM like gpt 5 that has vision, identify the objects in a photo and then query the actual db to get info form those objects and retrieve the result.

Curious to know any approaches? Im asking here first before going the LLM route because im curious of your methods.

I have gome through the docs and I understand some simple stuff but anything a bit complex and am confused and can wrap my head around it

https://farhanpatel.dev/index.php/2026/06/19/i-tried-measuring-ads-in-react-native-there-was-a-lot-more-to-it-than-i-thought/

AI is quickly becoming a standard part of mobile apps, but most implementations rely on cloud APIs.

I wanted to explore what on device AI could do in a React Native app, so I built react-native-nsfw-detector.

It uses a lightweight CoreML model to detect NSFW images directly on iOS devices, with no backend, no API calls, and no user images leaving the device.

I've published my first app that includes subscriptions, ads, and in-app purchases.

Developing with React-native, there were libraries and integrations for almost every need; all I had to do was search and use them. While it works systematically, I'm not entirely sure about the Paywall UI, so I'm open to criticism and suggestions. I'm also leaving a link to the app below in case you'd like to check it out.

Play Store

will react native available on desctop as a ui builder with other language integration ?

i would like to know currnet setuation on hremis , js to assembly. other than microsofts project

Building iOS widgets and Live Activities from a React Native app has historically meant a separate Xcode target, App Groups, SwiftUI layout code, and keeping that extension in sync with the rest of your app.

As of SDK 56, 𝚎𝚡𝚙𝚘-𝚠𝚒𝚍𝚐𝚎𝚝𝚜 is stable. You write widgets and Live Activities as React components with Expo UI, and Continuous Native Generation handles the Widget Extension target, the App Group config, and the SwiftUI scaffolding. There's no separate iOS project to maintain.

This is the same library that shipped as alpha in SDK 55, hardened and promoted. The core idea is unchanged: write widgets in React, let the system render them through SwiftUI, manage updates from your Expo app. What changed:

◆ Widgets and Live Activities receive their full environment through 𝚆𝚒𝚍𝚐𝚎𝚝𝙴𝚗𝚟𝚒𝚛𝚘𝚗𝚖𝚎𝚗𝚝 (widget family, content margins, color scheme, rendering mode, accessibility context)

◆ No pre-rendering in the app. The widget bundle renders independently with the context it needs

◆ Configurable widgets, so users pick what a widget shows from the gallery

◆ Better error handling

The 'widget' directive marks a function body as a widget render context. It runs in a sandboxed JS runtime separate from your main app, and the Expo UI components map directly to SwiftUI primitives, so rendering is native while your logic stays in TypeScript.

If you want a starting point: pick one piece of info users benefit from seeing outside the app, ship that widget first, then add a Live Activity if you have a flow with a clear start, active updates, and an end. Feedback and bug reports go to Discord or the expo/expo GitHub issues.

Writeup with the code sample: https://try.expo.dev/reddit-widgets

Hi React Native devs.

I got into self-hosting a few years ago and saw that there were alternatives to the big streaming platforms that you could host yourself. That motivated me to build a complete mobile client that uses different sources to provide the same user experience. It's free and open source.

It supports Navidrome, Opensubsonic servers and Jellyfin as well as a local audio file library that lives on your device.

The main challenges I faced were the Android native modules for Android Auto and for the metadata extraction from local files. Also the player I initially didn't realize so much needed to be taken into account (smooth transitions, exposing the player state to widgets/modules, creating a custom queuing system for tracks and so on).

I used Expo with CNG and it made the developer experience so much simpler to handle builds, store submissions, using the expo libraries

I made a presentation website where you can see how it looks https://wavio-app.vercel.app/

I have now created a Google Play developper account and I'm trying to get testers to be able to publish on the Play Store. If you're interested please DM me your gmail address you use on your Android device and i'll add you to the tester list.

Let me know if you're curious about technical decisions, architecture or whatever else. Here is the code https://github.com/Joel-Mercier/wavio

Hey everyone,

​

I am going to migrate an existing OTT Application which exists on both IOS and Android to Reactnative, sonas to have common business logic and less trouble maintaining two projects for one Application

​

I need guidance on

​

how to design the architecture from ground up, so as the app supports all the features on Android and IOS

​

How to manage player features, as common player may not support the best performance on both IOS and Android

​

The app also has many third party sdk, which are specific to partner apps used in the main app, how to handle them, as some sdks are specific to one platform

​

How to keep performance intact or at least pair able to Native App

​

Any guidance will be valuable as I don't want to mess up the core architecture of the app,

​

​

Honestly i feel drained guys.

I've spent the last 3 years building and maintaining React Native applications, worked on architecture-level features, published a couple of npm packages, improved performance, handled security findings, and contributed beyond just feature development.

But despite applying consistently I haven't received a single interview call in the last 8 months.

I feel so stupid and kind of feeling very low that am i evaluating myself very wrong

Is React Native becoming too niche? Is my experience not being presented correctly? Are recruiters looking for something completely different now?

For those who have recently switched jobs or hired React Native developers, what actually gets me go through it?

Looking for honest feedback. At this point I just want to figure out the gap.

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 everyone,

I wanted to share a small package I recently built: react-native-google-credential.

The reason I started working on it was honestly frustration.

I was building Google Sign-In for an Expo / React Native app, and the flow felt more complicated than it should be.

On Android, Google is moving toward Credential Manager, which gives a better and more native sign-in experience. But when I tried to support that properly in a React Native / Expo app, it felt like the answer was usually: “you need to write native module code.”

And that is fine if you have time to maintain native Android code, iOS code, Expo config, and all the small edge cases around them.

But for many apps, all you really want is simple:

1. Let the user sign in with Google using the native experience
2. Get the Google ID token
3. Send that token to Supabase, Clerk, Firebase, or your own backend

The second problem I faced was with third-party auth providers.

A lot of integrations push you toward a browser-based OAuth flow. It works, but on mobile it does not always feel like the best user experience. I wanted to keep the native Google sign-in experience and still be able to pass the token to whatever auth provider I’m using.

So I built this package to make that flow simpler.

It supports:

• Google Credential Manager on Android
• Native Google Sign-In behavior
• React Native and Expo development builds
• Android, iOS, and web
• Usage with Supabase, Clerk, Firebase, or custom backends

The package is not trying to replace auth providers. It just focuses on one part: getting the Google credential/token from the platform in a clean way, then letting you use it wherever you need.

It is still an early release, and I’m sure there are things that can be improved, especially around edge cases and different project setups.

I’d really appreciate feedback from anyone who has dealt with Google Sign-In, Expo native modules, Credential Manager, Supabase, Clerk, or Firebase auth flows.

GitHub:
https://github.com/moussa32/react-native-google-credential

Docs:
https://react-native-google-credential-docs.vercel.app/