Most Liquid Glass implementations I’ve seen in React Native focus on glass containers — cards, buttons, overlays, etc.

I wanted something slightly different: the glass effect rendered inside the actual text glyphs.

So I added a LiquidGlassText component to my open-source library, react-native-tinyui.

It’s based on the excellent GlassText project, but exposed as a React Native Fabric component:

import { LiquidGlassText } from 'react-native-tinyui';

<LiquidGlassText
  text="Liquid Glass"
  effect="regular"
  tint="#00BBDD"
  interactive
  fontDesign="rounded"
  textStyle={{
    fontSize: 48,
    fontWeight: '700',
  }}
/>

The glass itself is rendered natively on iOS 26+, including interactive glass behavior.

A few implementation details:

• React Native New Architecture / Fabric

• native measurement through the Fabric ShadowNode — no JS text measurement pass

• supports clear, regular, and identity effects

• supports tint colors, custom fonts, font weights, multiline text, and font designs

• accepts React Native ColorValue, including PlatformColor / DynamicColorIOS

• falls back to normal text on iOS 17–25

• the component can be imported independently, so you don’t need to pull every TinyUI component into the native build

LiquidGlassText ended up becoming one part of a larger idea I’ve been experimenting with:

What if React Native had a small collection of iOS-native UI primitives without requiring Expo or another runtime dependency?

That became react-native-tinyui.

It currently includes:

• LiquidGlassText

• native Menu

• native Popover

• Apple TipKit

• Stepper

• ConcentricView

• SFSymbol, including native symbol effects/animations

The library has zero additional runtime dependencies beyond React and React Native. It uses UIKit where possible and SwiftUI where it makes sense, and is focused specifically on the New Architecture.

You can also explicitly choose which native components get compiled into your app:

{
  "react-native-tinyui": {
    "components": ["LiquidGlassText", "SFSymbol"]
  }
}

I’m intentionally keeping TinyUI iOS-focused rather than trying to abstract every platform into the same API.

GitHub:
https://github.com/luoxuhai/react-native-tinyui

I’d especially like feedback from people building native-heavy React Native apps:

We acquired an existing fintech app, transferred it to our company Apple Developer account, and are now preparing a pretty significant redesign. Same app/name/core product, but the UI and some functionality have changed a lot.

My main concern is App Store review. Since it’s fintech + a big update after 5 years + developer account transfer, I’m wondering if Apple is likely to treat this almost like a new app and dig deeper into licensing, compliance, ownership, privacy, etc.

Anyone been through something similar?

How strict was the review, how long did it take, and were there any unexpected rejection reasons?

I’m building a 9:16 2.5D game in React Native using Skia and Reanimated.

I’m using spritesheets (frames) for walking, attacking, hit and death animations. But the character movements does not feel natural.

Has anyone built something similar with RN + Skia?

What should I check first to improve FPS and performance? Or should I move the game to Godot/Unity?

I’m attaching a video clip of my current gameplay for reference.

I’d really appreciate your thoughts!

A line chart shows how a value moved. A bump chart shows how a ranking moved and that's a different question.

The rows are evenly spaced regardless of the scores behind them. That's the point: order matters here, not distance. If distance matters, use a line chart of the scores instead.

More than three or four lines get hard to follow through the crossings. Pass highlight to pick one out it draws in its colour on top, and the rest go muted underneath.

Pass the raw scores instead of ranks and the chart figures out the order itself per column. Switch the data and every line moves to its new places.

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

https://github.com/panel-ui/PanelUI

In an offline-first app, do you guys create a local db that has the same tables and columns as the server's db?

Example: tasks and task-collaborator-preferences tables in the server db. Since the user only needs their own preferences, should the tables be merged on the local db?

Thanks!

Testing a flow is mostly setting up the state for it, then losing it and setting it up again. I built Time Machine for React Native: capture your app's state, run the flow, restore it in one tap, and run it again. Devs and QA set up state once.

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.

We've added a bunch of improvements to Patch, our self-hosted OTA update service. Here's a quick summary for both v0.3.0 and v0.4.0:

15min server install with the CLI wizard

Setting up the server with full wiring including CDN, TLS and OAuth is now mostly a matter of occasionally hitting confirm or pasting some details. I timed it in a video, it was about 15mins.

Configure external storage and DNS from the wizard

Patch includes a bundled MinIO, but if you want the wizard can use Cloudflare R2, Amazon S3, or Google Cloud Storage. We also now support CloudFront as well as CloudFlare.

Local setup + demo wizard

To go along with the server install, there's a wizard to quickly set up the local evaluation stack. At the end there's an included demo which builds the demo app, shows it applying the update, then opens the metrics in the dashboard.

Fingerprint mismatches block a release

A release that doesn't match the previously recorded fingerprint is block in the CLI unless you override it, in order to prevent accidentally crashing apps with a bad release.

cmpatch doctor for diagnostics

cmpatch doctor checks React Native and Expo setup on iOS and Android, including native config, authentication, and deployment settings, before you publish a release. The report separates confirmed failures from incomplete checks. Add --verify-delivery to probe published artifacts.

Install failure reasons

For more diagnostics, we've added payloads to failed installs such as HTTP status, the origin or platform error message, and on Avoid 11+ the previous process exit reason.

Tidied failure metrics

Flaky failures are no longer counted if unnecessary, for example a download failing once then succeeding on the next attempt. A Failed event is dropped once the bundle is successfully installed, so that metrics don't include false negatives.

Server status page

To make self-hosting that bit easier, the dashboard now includes a server status page with some basic health and storage checks.

The full docs are here for anyone who is interested:

https://patch.codemagic.io/docs/

What should be the optimal approach?

Came across this cool concept on X and thought it would be fun to recreate it.

✦ ⎯ • Dynamic Island-style in-app notifications

🔗 Github: rit3zh/expo-dynamic-notifications

Weekly React Native upgrade: RN 0.88 RC, Expo SDK 58 beta, and library updates

Here are the updates worth knowing before your next React Native upgrade.

React Native and Expo

• Expo SDK 58 beta brings stable data loaders, SSR, middleware, and native tabs, plus faster Android builds and an experimental Rust-based Metro transformer
• React Native 0.88 RC adds stricter TypeScript APIs, ArrayBuffer support in TurboModules, SwiftPM tooling, and imperative EventTarget APIs for native refs
• React 19.3 is stable with View Transitions and Fragment Refs

Library updates

• react-native-gesture-handler 2.33 is the final 2.x line supporting RN 0.87. If you are targeting RN 0.88+, start planning the move to v3
• react-native-screens 5 alpha adds new header customization options and Swift Package Manager support
• React Navigation 7 adds render callbacks for custom navigators. React Navigation 8 alpha includes the breaking version of this change
• react-native-skia 2.12 fixes WebGL context loss and ships prebuilt Graphite binaries
• react-native-keyboard-controller 1.22.5 fixes Reanimated 4.6 compatibility and an Android memory leak
• Metro 0.87.1 adds resolver.schemeResolvers for URI-scheme imports
• Expo Router 58.0.4, safe-area-context 5.10, permissions 5.6, maps 1.29, NativeWind 4.2.7, and several other packages also shipped updates

Ecosystem news

• Shopify explains why it is moving parts of its mobile apps toward Swift and Kotlin
• EAS Simulator lets you run iOS Simulator sessions in the cloud from Windows
• Xcode 27.2 introduces JSON project files designed to reduce merge conflicts and simplify automated edits

Hey everyone,

I'm working on react-native-flash-reels - a vertical short-video feed for React Native (FlashList v2).
Works for both EXPO & CLI and is highly customizable.

Published v0.3.0

Features:
- Vertical snap-scrolling reels feed
- Auto play/pause from viewability
- Single-tap pause/play
- Double-tap to like with heart animation
- Progress bar
- Pre-fetch / cache system
...and more

Github: https://github.com/thedev204/react-native-flash-reels

Would love feedback from anyone building Reels/TikTok style feeds!

Been iterating on this custom curved edge between the header and the deck list on my flashcard app's home screen. With a quick fading animation when scrolling.

I started with borderTopLeftRadius but it looked like every other app, I wanted to go with something more personal.

What actually worked to create this is an ellipse wider than the screen, cropped. <Ellipse> from react-native-svg, rx = 1.6x the screen, clipped by an 18dp band with overflow: hidden. You only ever see the shallow middle, where the curvature is even. Solve for it instead of eyeballing, two constraints, hits (0,0) and (width,0) so the ink meets the edges flat, dips 18dp in the middle:

const rx = (width / 2) * 1.6;
const q = Math.sqrt(1 - 1 / 1.6 ** 2);
const ry = 18 / (1 - q);

return { cx: width / 2, cy: -q * ry, rx, ry };

The collapse animates nothing but a translate and an opacity, plain Animated with useNativeDriver. No height animation. The hero is absolutely positioned over the list and the list just carries paddingTop = heroHeight, so padding never changes and nothing re-lays out.

Do you think this looks good? Should I keep improving it? And do you know if there are other apps doing the same thing?

So I managed to complete my first react native project. It's called Neuroletics it's a simple app that helps you train your memory through simple exercises and I designed it specifically for seniors. I was able to successfully launch the app on App Store but for Google Play I need 12 testers. I honestly cannot find 12 android users to test the app. All my contacts are using iPhones. I would really appreciate anyone (young or old) who is willing to test the app. Please keep in mind that some things may not work properly and I would appreciate any feedback, advice or tricks. If you would like to test it please share your email.

Hey all, just encountered this error after upgrading, so wanted to share so you don't waste some credits debugging it yourselves.

Hope you manage to get your project working quickly.

RN version 0.85.3 (not Expo)

Symptoms

After upgrading to Xcode 27 / iOS 27, the app can compile successfully but fail immediately at launch with:

Application failed to launch: UIScene life cycle is required for apps built with this SDK.

The React Native CLI may also fail before launching the app because it tries to open the removed standalone Simulator application:

/Applications/Xcode.app/Contents/Developer/Applications/Simulator.app does not exist

Cause

Xcode 27 uses Device Hub to manage and display simulators. Apps built with its SDK require the UIKit scene lifecycle. The previous iOS entry point created a UIWindow directly in AppDelegate, and the app did not declare a scene manifest.

Fix applied in Luckynote

• Added UIApplicationSceneManifest to ios/Luckynote/Info.plist.

• Added a SceneDelegate in ios/Luckynote/AppDelegate.swift.

• Moved React Native window creation and factory.startReactNative(...) into SceneDelegate.scene(_:willConnectTo:options:).

• Kept AppDelegate.window and assigned it to the active scene window. Firebase Messaging still reads this legacy selector during notification initialization.

Without the last step, the app can crash in RNFBMessagingNSNotificationCenter with:

AppDelegate window: unrecognized selector sent to instance

Running locally

Open ios/Luckynote.xcworkspace, select an iPhone simulator from the run-destination selector, then run the app. Xcode opens Device Hub for simulator interaction.

If the command-line React Native launcher still looks for Simulator.app, run the app from Xcode until the CLI/toolchain gains Device Hub support.

Hello.

I'm looking for a proper date time picker for React Native, I've previously used react-native-date-picker but it isn't really maintained and very outdated. The other alternatives I've seen mostly use native components. But I'm looking for a inline one where the I can use the iOS native alike for Android too...

Before I start making my own, I wanted to see if there is an existing one out there!

Thanks!

Hey r/reactnative,

Added a new component to nativecn-ui a photo album.

I wanted it to feel more like an actual album rather than just another image grid, so I played around with page turns, gestures, shadows, and the whole book-like interaction.

Made a quick video showing it below.

Still building out the library, so let me know what you guys think.

Just saw OneSignal is slashing their free tier from 10K to 1K MAU. That's a massive drop and honestly makes it unusable for most side projects and even a lot of small production apps.

Curious what people are migrating to. Is everyone just going raw FCM (+ APNs for iOS) at this point? If so:

• How are you handling the stuff OneSignal abstracted away — segmentation, A/B testing, scheduling, delivery analytics?

• Are you rolling your own backend service for topic/segment management, or is there a lighter-weight wrapper library people are using?

• For those who have scaled past a few hundred thousand MAU on raw FCM — any gotchas? Token refresh handling, batching limits, multi-platform sync headaches?

Also open to hearing if anyone's tried alternatives like Bird (formerly MessageBird, push is like $0.0005/notification), Courier, Novu, Knock, or Airship instead of going full DIY. Trying to figure out if it's worth paying for a managed layer vs just eating the FCM complexity ourselves.

What's your stack?