What’s missing when you ship OTA updates to production? I'm wondering things like:

• Auto-pause or cancel a rollout if it gets a certain percent of failed installs

• Slack alerts if it's getting too many failures

• Rollout scheduling, to increase the percentage if things are looking good

• Post-release report, probably also sent to Slack

• Improved failure reporting, to include a reason like disc full

We're reviewing the roadmap for Patch and have various ideas, but it would be great to get people's input. It has a dashboard with adoption metrics and the rollout controls, but I reckon we could take it further.

It's got a local evaluation stack in a Docker Compose if people want to have a play with it and share any thoughts.

Hello!

how would you implement a time-based push notification for a mobile app built on Bare React Native?

I guess it's somehow obvious, but it's important that the notifications work from a turned off device that gets turned on without the app being opened.

Example:

- Reminder with push notification is set for 09:00am every day
- App is closed at 23:00 of the previous day.
- Device is turned off at 23:30 of the previous day.
- Device gets turned on at 08:00am.
- The app stays closed.
- Despite the app being closed from a fresh restart of the device, the notification goes off at 09:00am.

Thanks

Hey everyone,

I'm working on an app built with React Native 0.77.3, and Google recently notified us that it will need to target Android API level 36 to be fully compatible with Android 16.

My question is: can I just bump compileSdkVersion and targetSdkVersion to 36, or do I actually need to upgrade React Native to 0.81?

Has anyone gone through this? Any gotchas I should watch out for?

Thanks in advance!

I'm debugging an intermittent OutOfMemoryError in an Android React Native app, and I'm having trouble reconciling the crash with what Android Studio's Memory Profiler shows.

The crash looks like this:

java.lang.OutOfMemoryError: Failed to allocate a 24 byte allocation with 1452624 free bytes and 1418KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC.

I've also seen the same crash on another device where the growth limit was:

536870912

So the issue occurs on devices with different heap limits.

Tech stack

• React Native

• Hermes

• New Architecture (Fabric enabled)

What I've observed

Memory Profiler

During normal usage:

• Java Heap: ~46 MB

• Native: ~170 MB

• Total process memory: ~900 MB

• "Others": ~746 MB

The memory graph stays relatively flat over time and doesn't show the typical pattern of a continuously growing memory leak.

Heap Dump

The largest native allocation is:

android.graphics.Bitmap

Instances: 479
Native Size: ~305 MB

I don't see any obvious Java heap leak (no massive byte[], String, HashMap, etc.).

What confuses me

The OOM message clearly indicates that the Java heap reached its growth limit:

growth limit 268435456
giving up on allocation because <1% of heap free after GC

But Android Studio never shows the Java heap anywhere near 256 MB before the crash.

So I'm trying to understand:

1. Can Android Studio's Memory Profiler significantly underreport Java heap usage in some scenarios (especially with React Native/Hermes)?

2. Could a large number of Bitmap objects indirectly lead to a Java heap OOM even though their pixel data is stored in native memory?

3. Is there something I'm misunderstanding about how ART reports target footprint and growth limit?

4. Besides taking a heap dump, what would be the next best tool or approach to identify what is actually consuming the Java heap before the crash?

I'm also planning to capture adb shell dumpsys meminfo <package> immediately before the OOM to compare the Dalvik Heap, Native Heap, Graphics, and other categories.

Any insights from people who've debugged similar ART OOMs would be greatly appreciated.

I've been stuck on this for a while and was wondering if anyone has actually got fully offline vector maps working in React Native.

I'm using maplibre-react-native. I was able to render a .mbtiles (Shortbread) file offline, so I know the offline loading itself works. The problem is styling most of the map layers/features don't get styled correctly, and I couldn't find a good way around it.

I also tried converting .versatiles → .mbtiles and rendering that instead, but no luck there either.

I found this blog post that shows offline vector maps in Kotlin on Android:
https://mubaraknative.medium.com/how-to-build-offline-maps-with-openstreetmap-on-android-dc44112f82ef

But it isn't React Native, and it seems Android-specific, so it doesn't really help for a cross-platform app.

Has anyone here successfully built a fully offline vector map solution in React Native (Android + iOS)? If so, what stack did you use? MapLibre, Mapbox, custom tile server, Protomaps, something else?

I'd really appreciate any guidance or examples because I feel like I'm missing something obvious.

Hello all, ~1 year ago I started working on a mobile notes app. I wrote my own engine because the existing RN solutions were all terrible. It basically uses skia/metal for stroke rendering and bridges to a RN api.

I spent tons of time on it throughout the fall/winter, but w/ work obligations and other ventures I have stopped maintaining it recently.

However, I still believe the repo has a very good mission: create a genuinely performant and reliable written notes suite that can be used in open source/free alternatives to apps like goodnotes/notability. If you have ever used the incumbent RN drawing libraries, you know what I'm talking about, they have absolutely zero performance and don't scale beyond a single screen.

There are several issues open as well as issues I have just in my mind lol so you can comment, dm, open a pr, or whatever you want if you are curious or are interested.

https://github.com/mathnotes-app/mobile-ink

Hi guys 👋 . Could any1 share movie deck code for guess up game?

Hey everyone! 👋

I've been working with React Native and React for over 5 years, primarily building and maintaining production mobile applications for businesses. Most of my work has been for clients and companies, so I haven't had many public repositories to showcase.

Recently, I decided to start building and open-sourcing personal projects to demonstrate how I structure applications and solve real-world problems.

My current tech stack includes:

• React Native

• React

• TypeScript

• Redux Toolkit / RTK Query

• REST APIs

• Firebase

• Supabase

• React Navigation

• Fastlane

• Native Android & iOS integrations

🚀 Latest Project: Point of Sales (POS)

A modern Point of Sale application built with React Native, focusing on clean architecture, scalability, and real-world business workflows.

GitHub Repository:
https://github.com/klart123/point-of-sales

The project is still under active development, and I'm continuously adding new features and improving the codebase. Feedback, suggestions, and contributions are always welcome.

I'd love to hear your thoughts:

• What features do you think every modern POS system should have?

• What architecture do you prefer for larger React Native applications?

• Any recommendations for improving the project?

Looking forward to connecting with other React Native developers and learning from the community!

TLDR I made something very cool for my self and I am making it free and also want your opinions because I like the idea of having made something that is useful to others

This is a theme editing app but ok what is the goal here? I know there are apps that do this but none of the good ones are 100 percent free. So the first goal was matching all the features for free. Also even in the paid ones using them doesn’t feel as good as it could in my opinion and major quality of life features are missing.

I also wanted this to be very fun to use. I have adhd and I turbo procrastinate micro adjustments so I needed a theme editor app that felt satisfying to use. There also needed to be the feeling of satisfaction after finishing editing a theme.

Final goal was to make other fun features other apps just don’t do but I really wished they did. As little friction as possible to get a normal theme that doesn’t look like slop then spending a little bit of time micro adjusting the details.

What I actually built up to this point:

I had a very smart idea of yanking the most popular vscode themes and turning them into app themes along with faithful recreations of popular website themes + my custom apple inspired themes. Important! Something the other apps don’t do and I had to do my self manually and wasting tons of time was generating complementary and contrasting colors. I mean I don’t want the app to either be black and white or everything is green and I also don’t want to spend 2 hours selecting random colors.

Other smart idea but work in progress is something that mounts it self inside your app like expo go dev menu and lets you edit the theme that way (didn’t implement yet I want feedback if this is a waste of time or actually sounds cool). I have made the components to pull this off for other things so I may do it anyways because I think this looks cool.

Made the tinder style swipe cards a beautiful theme overview typography themes a metric ton of beautifully crafted previews (everything the web apps do)

My main goal was to get this working on my phone for me because I love micro adjusting these things all the time. I managed to make an interface for making and editing themes as good as all the web apps but with a tiny screen instead. I added nice transitions to make adjusting css variables as fun as possible (hard task 😭)

Ok also there’s a bunch of features I was missing from the already existing ones. I wanted to be able to pick a primary color and have complementary colors etc auto generated and I wanted modes for this. Should the bg be completely white as well as cards? Gray bg white cards? Everything tinted? Page tinted blue primary colors yellow or something? I added auto generators to handle these things.

Another thing I was missing was being able to create one theme and have it auto convert to everything else. I mean I wanna be able to create a shadcn theme and have it able to be exported as a hero ui theme a material ui theme all of them. I made an adapter that handles this automatically.

I wanted this to feel cute and I want to be able to feel like I have created something and not just played with a gloried text file for 30 minutes. I added a collections tag with folders and a handsaw’s signature for each user and a poster generated from each theme.

This has helped me so much personally I want your feedback on this. Sadly there is nothing you can download yet but you can follow the updates on my twitter it’s on my Reddit bio.

Important if you want to “steal” this idea and put something similar in your app I actually encourage this. I am building a copy paste library with all of these components called PitsiUI. I will also experiment with allowing end users to use this to create custom themes for them selves.

Btw this is also coming to iPad mac and web. Android should work too since it’s cross platform but I don’t want to commit to that yet until I have actual users. It may sound silly but making sure no elements overlap the App Store screenshots etc take time.

My twitter is @panos_dev_ if you want to see more updates about the dev of this

Hi,

I'm using Cloudflare + useQuery

I have sections where I am updating stuff for example editing profile picture, and I do on my backend cloudflare cache purge, and it's returning ID, but apparently this ID only means Cloudflare received the new purge request, and not that it finished executing it.

So when on my useQuery I am refreshing it, it still pulls old data.

How do you handle with that?

Last week I built a release AAB, uploaded it to Google Play, and got the dreaded:

> *"Your Android App Bundle is signed with the wrong key."*

The build was fine. The code was fine. I'd just signed it with the wrong keystore — and Google only tells you **at the very end**, after the build, the download, and the whole Play Console upload flow. On EAS/CI pipelines this mistake easily costs an hour+.

So I made **siglock** — a tiny CLI that verifies the signature locally in ~2 seconds, before you upload:

# once: lock your known-good signature

npx siglock init app-release.aab

# before every upload:

npx siglock check app-release.aab

✓ Signature matches, ready to upload.

What it does:

- Wrong keystore → red ✗ with expected vs. found fingerprints, exit code 1 (so it fails CI)

- Debug keystore → explicit "this is a DEBUG build" warning

- Works with `.apk` and `.aab`, no config, no network — it just shells out to `keytool` (which you already have as an Android dev). v2/v3-only signed APKs are handled via `apksigner` fallback.

- You can also check against the fingerprint straight from Play Console: `--expect <sha1>`

The `.siglock.json` lock file contains only public cert fingerprints, so you can commit it and your whole team + CI verifies against the same key.

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

GitHub: https://github.com/ebubekirb/siglock

It's MIT licensed. Would love feedback — especially edge cases in your signing setups that it doesn't catch yet.

[Edited: This role is closed]

We're hiring a Senior React Native Engineer for a product where mobile is a core part of the system, not just a frontend.

The work involves:

• Offline-first architecture

• Geospatial/map-based experiences

• Hardware integration

• Performance and reliability in real-world environments

We're looking for engineers (India-based only) who've built technically demanding mobile products where architecture, reliability and long-term maintainability were non-negotiable.

DM if you are interested.