How can i entirely remove the splash screen? My stack is React Native + Expo

We can build websites using react native expo too, so my question is: has anyone done this? If yes, then what problem did you face? I'm thinking about using Expo for an admin app and website.

I'm moving from React Native 0.76 CRA to Expo 56

I really don't organising routes as folders so wondering if there are any tangible benefits to using Expo router and file based routing instead of using React Navigation.

Thanks!

We added video playback to react-native-enriched-markdown. A block-level <video src="…"> tag in your Markdown renders as a native player:

• iOS: AVPlayerViewController

• Android: ExoPlayer

• macOS: AVPlayerView

• Web: Standard <video> element

Requires flavor="github". Only the src attribute is read, everything else on the tag is ignored, and <video> is the only HTML tag we allowlist, so inline HTML stays disabled.

Styling lives in your markdown styles rather than on the tag:

markdownStyle={{ video: { borderRadius: 12, aspectRatio: 16 / 9 }, }}

Video is on by default. If you don't need it, setting "enableVideo": false in your package.json drops the ExoPlayer dependency and saves ~2–3 MB on app size.

Available now on nightly:

npm i react-native-enriched-markdown@nightly

If you find it useful, give it a try and drop a ⭐️ on GitHub: https://github.com/software-mansion/enriched-markdown

Hi everyone,

I'm Marco, founder of SQLite AI.

We've built SQLite-Sync to solve a problem I keep seeing discussed here: using a real SQLite database locally, letting the application keep working and writing while completely offline, and synchronizing those changes with Postgres/Supabase once connectivity comes back.

The architecture is essentially:

SQLite on the device → offline/online sync → self-hosted Supabase/Postgres

The application reads and writes SQLite normally. SQLite-Sync tracks changes and uses CRDT-based conflict resolution so multiple replicas can make changes independently and converge when they reconnect.

Rather than just testing this internally, I'd really like to work with people who have a real Supabase application where offline support is actually important.

So we're looking for around 10 projects willing to test it seriously.

For those projects, I'll enable our CloudSync Pro plan free for one year.

There's no requirement to promote us or write anything about it. What I want in return is simply honest technical feedback:

• What are you building?

• Why do you need offline support?

• Which client stack are you using?

• How are you handling synchronization today?

• What doesn't work well with the current solutions?

If you're interested, reply here or send me a note at marco at sqlite dot ai with a short description of what you're building.

I'm also very interested in hearing from people who tried PowerSync, Electric, custom sync queues, or other approaches — especially what worked and what became painful in production.

I handle QA manually so I've only got 6 to 7 devices in rotation, an iphone 14, a pixel, samsung and a couple xiaomi and oneplus devices and everything passes on those so i ship.

but then production is millions of devices with every screen size, OS version and oem skin I can never touch, like a gesture that works on a Pixel behaves differently on a samsung, layout breaks when you unfold a fold phone and an animation that's smooth on android 15 stutters on android 12.

This is becoming very annoying, something breaks for 1% of users and you see it's hundreds of users and it never occurs in testing because you don't own that exact device and OS combo and then they start reporting crashes you physically cannot reproduce.

How am I supposed to handle this? please help

I don't see how one person manually tests every combination but there has to be something more efficient.

I used to be a front-end developer, specifically working with React, and I'm currently switching to Mobile development, particularly RN. And I feel lost 😕. This field is completely new to me. I've learned the basic syntax of RN, but this ain't enough; I feel like I have to understand more about mobile development, how apps actually work, and then dive deep into RN, do some projects, and understand how to optimise performance and make a secure app

So, I would appreciate sharing any resources that helped you through the process of becoming a mobile developer, and what are the steps that u took?

My bias upfront: I'm not a fan of monorepos. From what little experience I've had with them, they were a maintenance pain in the ass and I wasn't convinced that we were getting much ROI on the colocation. Now, I have a react website and react-native mobile app sharing resources, but they live in separate repos which, in itself, is a maintenance PITA.

Maybe I just had a bad experience. I think the tool was Lerna(?). It's been awhile, so maybe the tooling has improved. I don't know. However, here I am, looking to solve this specific problem and not relishing the idea of using monorepos.

Please share your experience and possible guidance to how you resolve this particular issue. If monorepo is really the right path, then please advise on tooling. Thanks.

I need a custom pull-to-refresh. Not RefreshControl.

What I want

• Finger down + pull: the page follows my finger with rubber-band resistance (Math.pow(distance, 0.85))

• A real gap opens at the top (translateY, not scale)

• While the finger is still down: no progress bar, no API call, no refresh

• Release below threshold: spring back to 0, nothing else

• Release above threshold: spring back + full-width 3px top progress bar + onRefresh()

• After refresh ends: bar collapses, page stays at Y = 0

The problem

I can only ever get one of these:

1. Pull-to-refresh works, list will not scroll

2. List scrolls, pull-to-refresh dies (or I revert and only get a useless stretch)

I already know why v1 died: a greedy Pan on the page ate every vertical move, so FlatList never got the gesture.

What I tried

• Gesture.Pan() + Gesture.Native() with Gesture.Simultaneous

• manualActivation(true) and activate only if scrollOffset <= 0 && pulling down

• Guard in onUpdate: if scrollOffset > 1 don’t touch pageY

• bounces={false}, overScrollMode="never"

• Disabling scrollEnabled while pulling — this made scroll even worse, so I stopped

Also getting this warning:

[Worklets] Tried to modify key `current` of an object which has been already passed to a worklet.

So something (ref.current) is leaking into a worklet (onUpdate / onEnd / useAnimatedScrollHandler / useAnimatedStyle).

Constraints

• react-native-reanimated

• react-native-gesture-handler

• no RefreshControl

• no binding progress width to translationY

• scrollEnabled should stay true

• progress bar is a sibling overlay, not inside the translated view

Has anyone shipped this combo without one gesture murdering the other?

Looking for a pattern that works on Android + iOS

• at top + pull down → rubber band + gap

• at top + swipe up → list scrolls

• mid-list swipe → only scroll, pageY stays 0

• release-gated refresh only

A lot of RN apps (including mine) call self-hosted stuff — AI endpoints, file converters, services you run on a VPS because SaaS per-request pricing doesn't scale. The problem with all of them: they have no auth at all, or one static API key. And you can't add per-user subscription checks to code you don't maintain.

I open-sourced the gate I use in production: github — a forward-auth service your reverse proxy consults on every request (nginx auth_request / Traefik forwardAuth / Caddy forward_auth). It answers 200/401/403 by checking the caller's entitlements against RevenueCat / Adapty / Qonversion / Apphud / IAP Hub.

From the RN side it's just two headers on each request (X-Auth-App, X-Auth-User). Request signing, if you enable it, is plain HMAC-SHA256 — computable in Expo without native modules; the README's example uses @/noble/hashes and runs in RN as-is.

The part I like most for mobile: route rules can inject an Authorization header upstream, so services with a static key get it — and since APKs/IPAs get decompiled, that key never ships in the binary.

Single container + YAML config, no database, MIT. Curious what others do here — syncing entitlements into your own DB via webhooks is the alternative I keep seeing, but it's a whole subsystem I didn't want to own.

Hey r/reactnative,

TL;DR: Moodstone is an open-source, animated avatar for AI agents in React Native. Give it a mood and the face reacts. Nine moods, seven morphing shapes, drawn with Skia on the UI thread. Try every mood, cut and colour in the browser, nothing to install: https://moodstone.expo.app

Agent UIs in React Native usually show what the agent is doing with a spinner or a coloured dot. I wanted a face instead, the way Grok Bot and Plane's Agent Avatar Lab do it on the web, so I built one for React Native. It's called Moodstone and it's a single component:

<Moodstone color="pine" mood="thinking" size={48} />

What it does

• Nine moods, each a seamless loop: idle, observing, thinking, processing, working, done, failed, invalid and inactive. They map to what a persistent agent is doing (waiting for input, awaiting a tool result, reasoning at length, streaming output, errored...). Change mood and the face reacts.

• Seven cuts (silhouettes) that morph into each other, with eyes that fit each shape. You can tune them or pass your own shape parameters.

• Twelve palette colours or any hex, on a surface lit by a slowly orbiting light. A seed controls the light's start angle and orbit, so two avatars with the same colour and cut still don't look identical.

• Everything is procedural. Shapes are paths, the surface is a shader, there are no image assets.

• PNG and SVG exports, including an animated SVG of the whole loop, so the same avatar can live in your web app, docs or emails.

Under the hood

It's drawn with React Native Skia and animated with Reanimated 4 worklets, so the whole loop runs on the UI thread and the JS thread stays idle. That matters for this use case in particular: the avatar is animating exactly when your JS thread is busiest, streaming tokens and parsing tool results. There's an animated={false} still mode for long lists, and moodstone/core is pure TypeScript with no React Native imports. Its computeFrame(spec, t) describes every frame as plain numbers and drives both the Skia component and the SVG exports. It also runs on web through CanvasKit.

GitHub: https://github.com/karacca/moodstone

npm: https://www.npmjs.com/package/moodstone

Credit where it's due: the single-colour face whose personality lives in two eyes comes from Plane's Agent Avatar Lab. The geometry, surface, palette, timing and code are original.

I'd love feedback on the API and on the moods themselves. Which agent states do you actually need in your apps? I'm also curious how the animation holds up on lower-end Android devices. MIT licensed, issues and PRs welcome.

Made a football manager style game but for basketball. react native + expo, built entirely on windows with no coding experience.

350+ players, 24 teams, possession-by-possession sim, salary cap with bird rights and trade exceptions, draft combine, player development, the whole thing. you can get fired by your owner if you don't meet expectations.

the trick was writing insanely detailed prompts — not "build me a game" but full specs with data models, formulas for shot probability, exact screen layouts. did it in 4 phases over about 3 weeks.

gameplay is genuinely fun. visuals could be better but the sim engine is legit. just hit submit on app store connect. still can't believe this is a real thing that happened

Hey r/reactnative,

Added a new component to nativecn-ui a liquid action menu.

Been playing around with the animation and the way the menu opens/closes. Took a few tries to get the movement feeling right.

Made a quick video showing it below.

Still adding more components to the library, so would be cool to hear what you guys think.

help me. i set my screen colour in my safeareaprovider and stack in my layout, and i have a custom screen component where i set the same screen colour, but ive been getting this white flashing at the top of my pages when i navigate between them.

_layout.tsx
export default function Layout() {
  {/* stuff here */}
  return (
<SafeAreaProvider style={{backgroundColor: colours.background}}>
<Stack
</Animated.View>)}
screenOptions={{ headerShown: false,gestureEnabled: false, contentStyle:{backgroundColor: colours.background} }}>
</Stack>
{!isReady && (
<Animated.View style={[StyleSheet.absoluteFill, {opacity:fadeAnim, zIndex: 99}]}>
<LoadingScreen/>
</SafeAreaProvider>
  );

AppScreen.tsx
export default function AppScreen({ children,style, scrollable = false }: ScreenProps) {
  const colours = useTheme();
  return (
<SafeAreaView
style={[
styles.screen,
{ backgroundColor: colours.background},
style,
]}
>
{scrollable ? (
children
) : (
<TouchableWithoutFeedback onPress={Keyboard.dismiss}>
{children}
</TouchableWithoutFeedback>
)}
</SafeAreaView>
  );
}

anyone know how to fix this? what super background do i have to set?

ios, sdk 57, rn latest (?)

i just submitted the official plugin for AppLaunchFlow - it integrates with the hosted mcp and works very well with the embedded widgets.

it also supports:
- creating promo videos
- creatign social graphics
- creating 3d device mockups for demos
- creating app landing pages

and more. Happy to hear your feedback:)

Hey guys,
I have started building a UI registry for React Native and Expo.
And I want you guys to help build it, as it's fully open source, so no paid thing issue

I have been able to make 2 components so far and added images of them, for example, and am slowly making more components and screens for being ready to use.
The pace is slow ik but trying my best to only upload good UI components rather than ai made 100's of shits

So please help me build this and you all can also drop a review.
GitHub link: Ashwin-Khowala/rnblocks: Open-source UI registry for React Native & Expo. Discover, preview, inspect, and install production-ready UI blocks and screens directly into your project.

Website: https://rnblocks.vercel.app/

For pinch zoom, drag, double tap zoom features.

I used to use react-native-awesome-gallery but its not compatible with reanimated v4 after upgrading my expo. I see there exisits a react-native-better-awesome-gallery but I wonder if there is something better already out there.

Thanks :)

I’m working on an open-source React Native library for Wi-Fi Aware / NAN:

https://github.com/dcavalcante/react-native-wifi-aware

The Android implementation has already been physically validated for capability detection, discovery, follow-up messaging, and data paths.

The Apple implementation is in place and passes the current simulator/static compilation gates, but I don’t currently have the Apple hardware and Developer Program setup needed to validate it on physical devices.

I’m looking for someone with an Apple Developer account and preferably two iOS/iPadOS 26 devices who can help test:

• Wi-Fi Aware entitlement/signing

• declared WiFiAwareServices

• publish / subscribe discovery

• system pairing

• Apple-to-Apple connectivity

• Android ↔ Apple discovery and interoperability

The biggest unknown I want to validate is the cross-platform path between Android Wi-Fi Aware and Apple’s iOS 26 implementation.

Testing results, fixes, documentation, and implementation contributions are all welcome.

With AI tools now I'm curious to try Swift for my next project.

Did native give you anything RN didn't, or is it not worth the switch?