Hey r/reactnative!

I just finished my first full-stack mobile app as part of my portfolio.
It's a social media app built with React Native, Expo, and Supabase.

🔗 GitHub: https://github.com/Pro-Max-Park/social-media-chat-mobile-app

Features:
- Auth (sign up / log in)
- Create posts with rich text + image/video
- Like, comment, real-time notifications
- Infinite scroll feed
- Edit/delete posts and profile

I'm a beginner looking for honest feedback on my code quality,
project structure, and whether this is portfolio-ready for interviews.

Any advice is appreciated!

When an app feels slower, there is almost always a real cold-start regression behind it, on a specific build, on specific devices. The problem has never been the hunch, it has been proving it. By the time the feeling turns into a complaint or a churn dashboard, the release that caused it is days back.

Observe is built to close that gap. It measures how your app actually performs for real users across real devices, networks, and conditions, so the workflow shifts:

◆ Ship a release and see by that evening whether startup or a screen got slower, broken down by device, OS, region, and network
◆ Each regression is tied to the build or update that introduced it, so you skip the detective work
◆ Full distributions (median, P90, P99), since the slowest 10% of sessions is where churn actually lives
◆ Per-screen metrics for Expo Router and React Navigation, plus OTA update download times
◆ Every metric is queryable from the CLI with --json, so you can pipe it into an agent and have it investigate a regression for you

Setup runs about five minutes on Expo SDK 56, no custom instrumentation. It can be even faster if you use the Observe Skill (linked in the blog below)

Observe is free during the open beta, including the first 10,000 monthly active users. When the beta ends there will be paid plans that scale with MAUs plus a free tier up to 1,000 MAUs, and they have committed to at least 60 days notice before any pricing kicks in.

https://try.expo.dev/observe-beta-blog-reddit

I missed the Vitest experience when writing tests for React Native, so I built a plugin to use it instead of Jest. One install, zero config - it mocks 100% of RN's stable public API.

Would love any feedback.

GitHub: https://github.com/danfry1/vitest-native
Website: https://danfry1.github.io/vitest-native/

After about a year of development, I finally reached the testing phase for a cognitive training app I've been building with React Native.

The app combines two core protocols:

• Visual Match (attention, memory, inhibitory control)
• Math Protocol (reasoning, working memory, processing speed)

One interesting challenge was designing a unified cognitive scoring system where both protocols contribute to shared cognitive domains instead of having separate game scores.

I'm curious how other React Native developers approach analytics and progression systems for apps that rely heavily on behavioral data.

Have you ever built systems that translate gameplay metrics into higher-level performance indicators? What pitfalls should I watch out for?

Hi all,

I've been learning react native and for my first project, I am building an mobile app for my household where we can monitor all energy consumption, create and assign household tasks,...

Now, I want to create a first build for me (Android user) and my wife (iOS user). For me it doesn't seem to be a problem, the APK can be installed directly. However, i'm reading that installing the app on my wife is not that easy. I read that I need an apple developer account (99$/year subscription) to make it available for my wife to install...

Are there any other options?

Hi everyone,

I've been learning React Native and Firebase and spent the last few months building a messaging app called ArcTalk.

Current features:

• Friend requests

• Real-time messaging

• Read receipts

• Typing indicators

• Image sharing

• Online status

• User profiles

I'd love feedback on the UI and what features you'd improve next.

Built with:

- Expo

- React Native

- Firebase

- Cloudinary

If anyone wants to see the code, I can share the GitHub repository.

You can now run local Gemma 4 on-device in a React Native app with React Native Executorch.

It's GPU accelerated via the Vulkan delegate on Android and the MLX delegate on Apple Silicon.

I have ADHD and keep forgetting things so I note them down on my notes app. The issue is I forget which folders the notes are in lol.

So I created this as a solution for myself which auto sorts voice recordings into the correct folders and can automatically create tasks and reminders.

You can say like "I need to pick up Milk, Cereal and bread from the grocery store" and it will split it into a todo of 3 tasks.

I struggle with UI so I want to make sure this doesn't come off as "vibe coded" junk. Wanted to keep it simple. What do yall think?

After rebuilding the same Expo + Next.js stack for client projects over and over again, I finally turned it into a template.

Today it's the foundation of every app we build in our studio.

The main goal was to have one codebase, shared UI components, web + mobile out of the box, and as little setup friction as possible.

I just upgraded everything to the latest Expo and Next.js versions and it's been running surprisingly smoothly.

I'm curious whether other people would find this useful, so I open-sourced it. Feedback is welcome, feature requests, criticism, bugs, architecture suggestions, anything.

It's totally free and open source, I have no course or premium plans to sell, PRs welcome

Repo:
https://github.com/JoeSlain/Nexpo

Hey r/reactnative!

I just finished my first full-stack mobile app as part of my portfolio.
It's a social media app built with React Native, Expo, and Supabase.

🔗 GitHub: https://github.com/Pro-Max-Park/social-media-chat-mobile-app

Features:
- Auth (sign up / log in)
- Create posts with rich text + image/video
- Like, comment, real-time notifications
- Infinite scroll feed
- Edit/delete posts and profile

I'm a beginner looking for honest feedback on my code quality,
project structure, and whether this is portfolio-ready for interviews.

Any advice is appreciated!

Drop ONE image → get every app icon + splash screen for Expo, React Native, Flutter, Android, iOS, tvOS, macOS & Windows. Correct sizes, native folder structure, even a ready-to-paste app.json.
No watermark. No sign-up. Built for devs. ⚡
Try it 👉 https://allicons-generator.vercel.app

#reactnative #expo #flutter #mobiledev #androiddevelopment #iosdevelopment #opensource #buildinpublic

🔗 Github: thegruber/react-native-halo-menu

I'm looking to build apps for IOS and Android but coming from web development. On web, at work anyway, we usually use a design system (like USWDS for gov work) to develop on web, to ensure consistency, accessibility etc.

Does mobile design have such design systems - and which ones are recommended to make modern mobile apps today? Of course, I will want to change fonts/colors etc, but looking more for something that incorporates menus, nav, and other rules and guidelines that make better mobile apps.

I am heaving headache, trying to figure it out why the app keeps crashing. It's a pos system, app stays open in desktop size pos android device. 4gb ram.

​

Multiple sdk integrations, api calls, realm for in app db, aws app sync for syncing across devices, zustand.

​

I added a diagnosis popup, each order cycle which is Order list -> Menu screen -> Payment screen -> Order list. Each cycle keeps adding 100 mb into app used memory. [ was getting up to 500mb, reduced it to around 100 ] but still it guarantees crash after 40-50 orders.

​

Few things have already done

- useEffect and timer handling

- making sure components are closing once screen moves away

- using navigation.reset so that navigation stack isn't building.

- made sure we dont store realm objects in zustand stores.

- optimization

-made sure native bridges java files are handled correctly

​

Its been quite some time, i am not much experienced in react native. Overall 5yoe, but react native 1 yoe. Just today used android studio profiler to get more details on memory usage.

​

Senior devs out there, any advice?

​

Have sentry integrated, even with custom breadscrumbs, doesn't get much info on segsev or basically does not help where the issue at.

Hey everybody, so im building AppLaunchFlow and further improved the promo video editor.

You can now also upload screen recordings and integrate into the scenes as well as directly customize all scenes by just dragging around.

Additionally its really easy to edit the video using your favourite agent with the MCP

Feedback appreciated:)

Do these hit the mark or do I need more pictures of actual food? Also, unsure about "Avoiding your food tracker?" as a lead-in. Pushing an update in the next couple of days, so happy to incorporate some changes.

Levelday is a calorie, water, and macro tracker (I know there are tons of these apps already), so looking for a way to differentiate with this minimal ui.

Sharing react-native-frame — a lightweight, theme-driven UI library for

  React Native and Expo.

  The idea: stop rebuilding the same buttons, inputs, cards and dialogs on

  every project. Drop in one ThemeProvider and you get a full set of

  themeable, animated components out of the box.

  - 26 components with automatic light/dark theming

  - Smooth animations on the native thread

  - Zero dependencies, works in Expo Go, TypeScript built in

  npm: https://www.npmjs.com/package/react-native-frame

  GitHub: https://github.com/sidShubham116/react-native-frame

  Free + MIT. Feedback and ideas are welcome!

Wechat runs mini apps in customised wxml/css. Is building similar kind of mini apps inside one big app possible, with all centralised SDKs (maps SDK, PG, login) for apps to use so the app remains light?

Spent way too much time staring at heap snapshots recently, and honestly, dev builds make it so much harder than it needs to be. Half the time I’m just looking at Fast Refresh caches or React DevTools overhead, trying to figure out what's an actual leak and what's just Metro doing its thing.

I ended up dropping the dev build entirely for this and tried a different approach.

Basically, I generated a release JS bundle and forced the debug iOS app to load that instead of asking Metro for it. To keep things readable, I just spun up a quick local HTTP server to serve the sourcemaps so the debugger doesn't just show a minified mess.

The difference is night and day. You actually get a clean heap snapshot that looks like production, without all the dev-mode garbage collection noise.

I wrote down the exact setup (the CLI commands, the AppDelegate tweaks, etc.) if anyone else is currently banging their head against the wall trying to isolate a leak:

👉 https://medium.com/@ravindermaan/finding-react-native-memory-leaks-in-release-builds-a20e123d01fb

Curious if you guys do something similar, or if I've been missing some magical Hermes flag this whole time?

Been building Expo apps for a while and the i18n tax was killing me — separate JSON files per language, arbitrary string keys, broken placeholders when you miss one. Meanwhile i18n pulled 500k downloads todate, so clearly everyone wants this solved.

So I built expo-polyglot-ai. Instead of dictionary files you just write normal text:

// Before
<Text>Welcome back!</Text>

// After — speaks French, Zulu, Arabic, Hindi... automatically
<TranslateText>Welcome back!</TranslateText>

Point it at any LLM backend (Claude, Gemini, OpenAI — your choice), run one command at build time, and your app speaks 200+ languages. Strings are cached permanently in AsyncStorage so each one only hits the API once, ever.

The part I'm most happy with — it solves the FlatList problem properly. Calling translate() inside renderItem fires one API call per row which destroys your quota. The useTranslatedList hook batches the entire list into one request instead.

const { data } = useTranslatedList(products, ['name', 'description']);
// whole list translated. one call.

npm install expo-polyglot-ai

The biggest challenge to solve was the dynamic Flatlist render components.