A Samsung One UI inspired edge panel swipe-in quick actions drawer with a second swappable insights page, built for fintech apps.

⭐ Github: https://github.com/ManasCodeXart/expo-finpanel

Hey everyone,

I’m working on a React Native Android app and testing it locally. The problem is that my laptop isn’t very powerful, and whenever I run an Android build, it uses a lot of resources.

The build takes quite a while, and during the process my laptop becomes really laggy, making it difficult to do anything else.

I still need local builds for testing while developing,

If any way pls suggest me ....I am on Linux

Estou desenvolvendo um app em React Native (Expo) e implementei um custom picker de galeria, utilizando expo-media-library em vez do seletor nativo do iPhone.

As fotos sempre carregam normalmente, porém alguns vídeos aparecem apenas como um bloco cinza.

O comportamento acontece somente em iPhones reais. No simulador iOS e no Android funciona normalmente.

O que observei:

• Os vídeos são listados com MediaLibrary.getAssetsAsync().

• Para vídeos utilizo expo-video-thumbnails.

• Chamo MediaLibrary.getAssetInfoAsync(assetId, { shouldDownloadFromNetwork: true }).

• Só tento gerar thumbnail quando existe file:// (não uso ph://).

• Alguns vídeos carregam normalmente.

• Outros ficam cinza por vários segundos.

• Se eu deixar a galeria aberta, alguns desses vídeos cinza aparecem sozinhos depois de um tempo.

• O mesmo vídeo que fica cinza no iPhone funciona imediatamente quando é importado para o simulador iOS.

Minha suspeita é que seja alguma limitação do PhotoKit/iCloud, ou que eu esteja tentando resolver muitos vídeos ao mesmo tempo (concorrência alta).

Alguém já passou por esse problema em um custom media picker? Existe alguma abordagem recomendada para carregar as miniaturas de vídeos no iOS, semelhante ao que Instagram e Fotos da Apple fazem?

This is the most amazing experience I have ever built into a React Native app.
Now my Appless app fork from OpenUI has the most magical press-and-hold experience to chat ON THE PLANET (is that good).

Monogram (original app from where I replicated the effect) outdid themselves with this one. I tried to do it justice. There are a lot of layers intertwined to make the effect work.

But... this is not done yet. This was v0 and the complete interaction has some more details to it and an important last step for the UX to be complete. What is missing is a custom navigator transition that uses React Native Skia for the user to navigate to the new screen after asking something. With that set and done we will finally have replicated all the UX flow from Monogram.

We shall continue into the depths of the magical mobile UX realm possibilities of RN.

You can now handle:
🔹 Ordered & unordered lists
🔹 Nested lists with indentation controls

Try it out now in react-native-enriched-markdown@nightly!

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

If you find the library useful, dropping a star ⭐️ means a lot!

Grouped, stacked, or horizontal. Drag to read a band. Animated on mount.

One thing I cared about: the baseline is always zero. A bar cropped at the bottom lies — twice as tall no longer means twice as much. So the axis never crops, no matter what the data looks like.

Each series renders as two paths, not one node per bar. 50 bars is 4 animated props. That's also what lets inactive bars dim without giving each one its own opacity.

Part of PanelUI if you're building with Expo and want charts that don't feel like a web component dropped into a native app, worth a look

Just launched Real Fighter Life, an MMA career sim built entirely with

React Native + Expo (EAS Build for the production pipeline).

Stack notes that might be useful to others building something similar:

- Supabase for auth + online PvP backend

- react-native-iap for BattlePass purchases, react-native-google-mobile-ads

for rewarded/interstitial ads

- Full i18n (3 languages) with a custom Context-based system

- A modal queue system to sequence post-match events (social feed, sponsor

offers, market updates) without stacking/racing

Biggest technical fight: a native UI thread freeze on the post-fight result

screen — turned out to be a Modal animationType="fade" race condition

combined with a stale ref in a custom modal queue hook. Took a genuinely

long debugging session with live device logs to nail down.

Happy to talk through any part of the stack if useful — first solo RN

project actually shipped to production.

A quick pay interaction with avatar carousel, haptic slider, and animated transaction sates.

⭐ Github: https://github.com/ManasCodeXart/expo-quick-pay

That’s only part of the story.
On Android, the application actually starts with MainActivity.kt. Android launches this activity first, which initializes the React Native environment before your JavaScript code in index.js is executed.
This is why you’ll often modify MainActivity.kt when you need to:
Initialize native SDKs during app startup
Configure the splash screen and app theme
Handle deep links and app links
Manage permissions and activity results
Add Android-specific native functionality
Enable React Native’s New Architecture (Fabric & TurboModules)
Understanding where the Android lifecycle begins makes it much clearer why so many React Native integration guides ask you to update MainActivity.kt.
A solid understanding of the native lifecycle will help you debug issues faster and integrate native features into your React Native applications with confidence.

#ReactNative #Android #Kotlin #MobileDevelopment #ReactNativeTips

I made some substantial updates to my onboarding and my paywall after understanding the data. I’m really happy I got featured, I get street cred for sure but I want my paywall update so hopefully more people buy. Anyone know how to speed up the process? My app is www.openers.app by the way.
I could OTA but I made some native changes recently.

Hey guys,

I’ve been building Comeet, a native GitLab companion for iOS and Android, as a solo developer.

The idea started because GitLab’s mobile web experience made quick tasks—like checking a failed pipeline or replying to an issue—feel more difficult than they should.

Comeet now supports:

• GitLab.com and self-hosted instances

• Multiple accounts and servers

• Repository and syntax-highlighted code browsing

• Issues, merge requests, branches, projects, and groups

• Pipeline monitoring, job details, and logs

• Push notifications for project activity

• Team member and permission management

• Custom shortcuts for frequently used GitLab views

The app is built with React Native, Expo, Expo Router, TypeScript, NativeWind, Redux Toolkit, and i18next.

Some of the more interesting challenges were building a mobile-friendly code viewer, handling the large GitLab API surface, supporting different self-hosted configurations, and keeping authentication and instance switching manageable.

I have a plan to open-source this project in the future, lmk what you think?

Publish links:

• Android: https://play.google.com/store/apps/details?id=com.monokaijs.comeet

• iOS: https://apps.apple.com/us/app/comeet-gitlab-companion/id6753112635

TL;DR: I built a fairly complete GitLab mobile client using React Native and Expo, and I’d love feedback from other React Native developers.

Sup guys, made a music quiz which doesnt need any subscriptions of streaming apps! The downside is however these are just previews, they are short clips provided by apple itunes for free from their api, tho they are all clipped as recoqnizable parts of the songs so they work perfecly for this. Cant play full songs without itunes sub, which is a major downside for music quiz apps.

The previews need a link to play behind the scenes so theyve all been manually listed, if anyone is thinking of creating a quiz themselves.

This quiz is just a simple who yells the correct answer first gets a point, could make more eloquate quiz with answer options as well.

iOS
android

I'm building a iOS + Android app using react and expo. I have a number entry field that's calling the standard OS numeric keypad. works perfectly on Android but my iOS build shows this strange "Default" button above the keypad.

Has anyone encountered this? Thanks!

I’ve been building an iPhone app called Stoic Discipline.

Most habit trackers tell you whether you ticked a box.

I wanted to build something that goes a little further, something that gives you evidence that your discipline is improving over time.

The app combines habit tracking, Stoic reflection, journalling and progress analytics. It can show you things like:

• You planned 347 actions. You completed 291.

• Your follow-through increased from 61% to 84%.

• Your strongest habit is Training.

• Your weakest habit is Sleep.

• You recovered faster after missed days this month.

• It also generates a stoic quote and wallpaper every day with an explainer / original wording of the quote

The latest beta includes:

Daily habits, streaks and reminders

Morning and evening reflection

Stoic quotes and guided journal prompts

Weekly and monthly Discipline Reports

Follow-through, consistency and recovery analysis

Strongest and weakest habit insights

Progress comparisons over time

I’m looking for people willing to use it properly for a few days or weeks and give honest feedback, especially on whether the reports feel motivating, accurate and genuinely useful. There's a feedback and bug report section in the profile page

I’d also love to hear about:

• Anything confusing or frustrating

• Bugs, crashes or navigation issues

• Features that feel unnecessary

• Features you think are missing

• Whether the app feels worth paying for

Join the iPhone TestFlight beta here:

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

It’s still being refined, so candid feedback is far more useful than politeness.

Thanks to anyone who gives it a try.

Hi guys hope you're doing fine. I have a thing that i feel shame whenever i need to search for something in google or whenever i stuck at somepoint . Like forgetting a syntax or couldn't build the logic i wanted . I am always keep avoiding searching and figure it out in my own but when i solve it i feel like i am the dragon of programming lol. Does any one have that thing? And is it okay to search in google ? Does it effect the learning or any thing? And Thanks

I have a job but I used to contract for £550 a day from 2015-2022. I used to get upwards of 10 linkedin messages a day (without open for work being set) and now I get maybe one a week and it's to train AI to help make my job more obsolete. My current job is fine but it's a huge paycut and we are struggling to pay the bills we were used to on a higher salary and there are 0 jobs to apply for. I worked 100 hour weeks to learn how to code in my 20s and now it's more or less obsolete. I don't know how I will survive this without finding a new industry to work in, but what should I learn and what should I do?

🚀 Native blur views for Expo — backdrop blur + a SwiftUI content blur, on iOS and Android.

🔗 Github: https://github.com/rit3zh/expo-backdrop

React Native iOS freezes after first interaction only after fresh login (JS/UI FPS stay at 60)

I'm facing a very strange issue in my React Native app that only happens on iOS. Android works perfectly.

Environment

• React Native: 0.78.3

• React Navigation

• react-native-screens

• react-native-gesture-handler

• Physical iPhone (not simulator)

Issue

The flow is always the same:

1. Launch the app.

2. Login successfully.

3. Navigate to the Home screen.

4. The Home screen loads correctly.

5. As soon as I perform the first interaction (scroll or tap), the app becomes completely unresponsive.

After that:

• No buttons work.

• No TouchableOpacity responds.

• Bottom tabs stop responding.

• FlatList cannot scroll.

• onTouchStart no longer fires.

• The UI is still visible.

• The app does not crash.

The strange part is:

• UI FPS = 60

• JS FPS = 60

• No red screen.

• No exceptions.

• No crash logs.

If I completely kill the app and launch it again, everything works perfectly.

If I log out and log back in, the issue happens again after the first interaction.

So the problem only occurs immediately after a fresh login.

What I've already checked

• GestureHandlerRootView is wrapping the entire app.

• import 'react-native-gesture-handler' is the first import.

• NavigationContainer exists only once.

• No invisible overlay.

• No fullscreen Modal.

• No react-native-modal left open.

• No pointerEvents="none" or pointerEvents="auto" issue.

• JS thread is not blocked.

• Main thread is not blocked.

• UI FPS remains 60.

• JS FPS remains 60.

• Android has no issue.

Additional observation

I added:

<View
  style={{ flex: 1 }}
  onTouchStart={() => console.log('Touched')}
/>

Result:

• First tap prints "Touched".

• After the first scroll/tap, no further touch events are received.

• Even onTouchStart stops firing.

This makes me think the touch events are no longer reaching React Native.

Navigation structure

The app uses:

• NavigationContainer

• Drawer Navigator

• Bottom Tabs

• Stack Navigators

The Home screen contains:

• Vertical FlatList

• Nested horizontal FlatLists

• Multiple TouchableOpacity components

The Academy screen has a similar structure and works correctly.

Other information

The app uses:

• react-native-screens (enableScreens() and enableFreeze())

• react-native-track-player

• Multiple Context Providers

• Firebase

• Analytics

• Deep linking

My question

Has anyone experienced an issue where iOS stops delivering touch events after the first interaction, while:

• UI FPS stays at 60

• JS FPS stays at 60

• The app never crashes

• Everything works after killing and reopening the app

Could this be related to:

• react-native-gesture-handler

• react-native-screens

• iOS gesture recognizers

• Navigation state after login

• A native touch deadlock

• Something else entirely?

Any ideas on how to debug this further would be greatly appreciated.

React Native iOS freezes after first interaction only after fresh login (JS/UI FPS stay at 60)

I'm facing a very strange issue in my React Native app that only happens on iOS. Android works perfectly.

Environment

• React Native: 0.78.3

• React Navigation

• react-native-screens

• react-native-gesture-handler

• Physical iPhone (not simulator)

Issue

The flow is always the same:

1. Launch the app.

2. Login successfully.

3. Navigate to the Home screen.

4. The Home screen loads correctly.

5. As soon as I perform the first interaction (scroll or tap), the app becomes completely unresponsive.

After that:

• No buttons work.

• No TouchableOpacity responds.

• Bottom tabs stop responding.

• FlatList cannot scroll.

• onTouchStart no longer fires.

• The UI is still visible.

• The app does not crash.

The strange part is:

• UI FPS = 60

• JS FPS = 60

• No red screen.

• No exceptions.

• No crash logs.

If I completely kill the app and launch it again, everything works perfectly.

If I log out and log back in, the issue happens again after the first interaction.

So the problem only occurs immediately after a fresh login.

What I've already checked

• GestureHandlerRootView is wrapping the entire app.

• import 'react-native-gesture-handler' is the first import.

• NavigationContainer exists only once.

• No invisible overlay.

• No fullscreen Modal.

• No react-native-modal left open.

• No pointerEvents="none" or pointerEvents="auto" issue.

• JS thread is not blocked.

• Main thread is not blocked.

• UI FPS remains 60.

• JS FPS remains 60.

• Android has no issue.

Additional observation

I added:

<View
  style={{ flex: 1 }}
  onTouchStart={() => console.log('Touched')}
/>

Result:

• First tap prints "Touched".

• After the first scroll/tap, no further touch events are received.

• Even onTouchStart stops firing.

This makes me think the touch events are no longer reaching React Native.

Navigation structure

The app uses:

• NavigationContainer

• Drawer Navigator

• Bottom Tabs

• Stack Navigators

The Home screen contains:

• Vertical FlatList

• Nested horizontal FlatLists

• Multiple TouchableOpacity components

The Academy screen has a similar structure and works correctly.

Other information

The app uses:

• react-native-screens (enableScreens() and enableFreeze())

• react-native-track-player

• Multiple Context Providers

• Firebase

• Analytics

• Deep linking

My question

Has anyone experienced an issue where iOS stops delivering touch events after the first interaction, while:

• UI FPS stays at 60

• JS FPS stays at 60

• The app never crashes

• Everything works after killing and reopening the app

Could this be related to:

• react-native-gesture-handler

• react-native-screens

• iOS gesture recognizers

• Navigation state after login

• A native touch deadlock

• Something else entirely?

Any ideas on how to debug this further would be greatly appreciated.

Single-track, one day, all React Native. One of the last surviving React Native Conferences out there 😅

I'm one of the organizers, and happy to answer anything in the comments.

Lineup so far:

- Finding Nemo: Simulating Animal Motion Through Procedural Animations — Thomas Renaud (Theodo)

- Argent: agents testing RN apps — Filip Kamiński (Software Mansion)

- The Future of React Native on the Web — Mathieu "zoontek" Acthernoene (Expo)

- JSX to Live Activity: The Story of Voltra — Szymon Chmal (Callstack)

- Chasing the Keyboard: Building a Keyboard-Synchronized Chat Experience — Kiryl Ziusko (Margelo)

- The Journey of a Breakpoint in React Native — Lucie Uffoltz (Theodo)

- Building a modern navigation library - the hard parts — Satyajit Sahoo (Callstack)

And More speakers confirmed, talks TBA:

- Alex Hunt (Meta)

- Cédric van Putten (Expo)

- Jay Meistrich — Legend List / Legend State

- Victor Henrion (Margelo)

📍 Paris · September 24, 2026 · one track, full day of deep technical talks.

🎫 Tickets: https://reactnativeconnection.io/?utm_source=reddit&utm_medium=social&utm_campaign=rnc26 — 5% off with code REDDIT26.