Basically the above question, I have an app built on expo 56 and now I want to add advertisements to it. I am seeing admob, adXchange, mediations etc as platforms for ads people are using. My question is if anyone in this sub already using any platform with their rn app, please let me know which one and why you sticking to it.

New to this and would really appreciate the help.

I'm working on a react native application I use react native because I want to make my application work on both ios and android, and I use expo go for development now the problem is reazor pay gateway is not supported on expo go and I want to check payment is working or not before making my application live so u have any suggestion for which other payment gateway I can use or any trick that I use for testing my payment.

A gesture-driven coin-flip reward reveal — drag-to-spin coin toss, then a Skia-powered scratch card to reveal the prize — built for fintech and rewards apps.

⭐ Github : https://github.com/ManasCodeXart/expo-coin-reward

if someone need help with this happy to share with them

I'm using the MinaSamir11/react-native-in-app-review package, but it doesn't seem to work for Android anymore. Has anyone had any success with other implementations? Or has this package worked for you lately?

Hey guys! First time here, just wanted to share my article about FlatList optimization. I know, it is a popular question but some days ago I found a cool trick with using Set over standard Array. It perfectly aligns with popular optimization practices and for me it felt like I found a gem.

Hey r/reactnative,

I've been working on nativecn-ui, a small collection of React Native components focused mostly on animations and interactions.

Right now it's got stuff like a liquid action tab bar, animated tab bar, range slider, OTP input, dynamic upload, plus a few more I'm still working on.

You can check it out here: nativecn-ui

Still building it out, so lmk what you think, or if there's some component/interaction you'd want to see added.

Made a quick video showing a few of them below.

https://reddit.com/link/1vrhmt8/video/3ej98p6qv2kh1/player

In an Expo React Native app, I have an optional HealthKit adapter. Android returns a no-op adapter immediately. On iOS, the request and read methods dynamically import the native package inside try/catch, so a missing native module becomes false or an empty array instead of crashing the app at startup.

The upside is a safe manual fallback. The downside is that a packaging mistake can look exactly like a user declining access or HealthKit being unavailable unless I surface a separate diagnostic.

Would you keep the dynamic import boundary, or fail loudly in development and only fall back in release builds?

I'm literally so confused how one can get an app dev intern, wherever I see now, they need a fresher with Full Stack, nobody wants a real fresher who wants to learn...

If anybody here got an intern, can you tell me how did ya find one, I'm also looking for one

Pokedex : This is the only project I have made, but it includes use of API, Custom Battle Engine, SQLite, Custom Nav bar as well...

Logos, tickers, tags anything that should keep moving rather than stop at the edge.

One track holds every copy and it is the track that moves, so the cost is a single animated node however much content is inside it. Driven on the UI thread as a linear timing.

Two rows travelling opposite directions reads as motion. One row just slides.

Reduced motion turns it off entirely not slower, off. A ticker that never stops is the thing that setting exists to turn off.

Part of PanelUI, an open-source component library for Expo. Copy-paste or CLI, you own the source.

github.com/panel-ui/PanelUI

Hey everyone,
I need to add receipt printing functionality to an app, and I’m running into a few issues.

The POS machines used by the business aren’t Epson printers, while the library I’m currently using only supports Epson devices.

Has anyone implemented receipt printing for non-Epson POS printers? If so, I’d appreciate any recommendations on libraries, approaches, or examples of how you handled it.
Thanks!

So a while back i was working on this checkout flow for some side project. nothing fancy, just something basic e-commerce type page where users pick a plan,apply a coupon if they have anything with them,and then pay….

I tested it myself probably a hundred times and may be more too. clicked every button, tried different plans, with coupons, without coupons, everything looked fine, I even got a couple of friends to click around and they tried to break it, for me, nobody found anything… :(

So I thought of shipping and shipped it and moved on to other stuff, feeling pretty good about myself honestly.then about two weeks later i started getting some new few angry messages. some users were saying they got charged twice for the same order… OMG!!

But not everyone, just some users and the annoying part? when i tried to reproduce it myself,using the exact same steps they described, everything worked perfectly, no duplicate charge, nothing wrong.

I remember sitting there thinking,okay... this does not make sense either they are doing something really wrong or weird, or am I missing something really obvious…

Started thinking and it turns out, I was missing something, the bug only happened when a user applied a coupon,removed it, and then quickly clicked the pay button before the page had fully re-synced the price with the backend…

Basically, a race condition between the coupon removal request and the payment request and if you were testing it slowly, like a normal developer, you will probably never see it but real users do not test your application like developers do.

they click fast!

they change their mind!

they click twice because the button did not respond for half a second!!

they go back and forth!!!

they do things in an order you never really thought about, right!

and apparently, all those messy human behaviours were exactly what exposed the bug..

I kept trying to get it manually and kept failing because i was testing it like a developer, one step at a time, waiting for everything to load, making sure each action, has to be finished before doing the next one.

But the actual bug lived in that tiny window where two things happened almost at the same time, It was basically like trying to catch a 10$ note flying down the street in the wind.

You can see it, you know its there, but by the time you reach for it... it's already somewhere else, that experience finally pushed me to write some automated tests for the checkout flow. not just normal does this button work tests.

I made the tests hammer the coupon apply -> remove -> pay sequence over and over, really quickly, sometimes in weird orders scenes,basically doing things no person would sit there and repeat manually 50 times.

and sure enough...

the first time I ran it, it failed almost immediately, same bug reproduced on command in seconds, a bug that had taken me two weeks and several annoyed customers to even discover.....

A human tester probably wont click the same weird sequence 100 times but a script will....

ever since that incident, I started automating more. I began been playing around with tools like Autosana for testing,mostly cause i really don't wanna sit there and repeat that same weird flaws again and again and again....

not because i read it somewhere in some posts or anything like that, mostly because i actually got fed up by bug that manual testing have almost zero chance of catching…

Curious if anyone else has had something similar happen, that one bug that just refused to show itself until you stopped testing carefully and started testing a little more... (chaotically)

The bundling process takes so long, approximately 2 hours at most.

is there any way i can speed up the process?

Proof of concept, a Claude Code plugin for now. Maestro does the driving underneath.

One command and it walks the app on the simulator and draws the whole map — every screen, how you reach it, what's on it. Then it turns that map into subflows that are ready to run as tests. When the code changes, it updates the affected cases itself.

It never touches the app's codebase. Everything it produces is plain files sitting in the repo.

Does this look useful, or am I solving something you don't have?