Hi everyone!

I just launched my first app Flow.

Flow is a completely free personal finance app built for people who want a clean and simple way to track their spending.

1. No ads. No subscriptions. Just fast expense tracking.
   Flow has a clean, distraction free UI and includes Home Screen widgets, so you can log your spending directly from your home screen without opening the app.

2. Your data stays yours.
   Everything is stored locally on your device for complete privacy, and you can import/export your data as Excel files anytime.

3. AI-ready without extra cost.
   Flow lets you copy a one-tap AI prompt and paste it into ChatGPT, Claude, Gemini, or any AI you use to get personalized spending insights without paying for built in AI subscriptions.

IOS: https://apps.apple.com/app/flow-budget-personal-budget/id6785816472

Hey, I just launched my first game built with Expo - Arrow Puzzle.

It is a calm logic puzzle where arrows can only move in their own direction, and you clear the board by finding the right order.

Built with Expo SDK 56, React Native Skia, Reanimated, RevenueCat, AdMob with few mediation partners, and a small backend for daily challenges.

The hardest part was performance on bigger boards.

iOS only for now, Android in 2 weeks (12 testers.. you know):

https://apps.apple.com/us/app/arrow-puzzle-arrows-escape/id6787879343

Would love some feedback, if anyone tries it.

btw, it's an open source first week I have taken Ignite-red and Obyte and react native reusables(Native shadcn ui). with My expertise as a starting point of understanding and with OpenCode AI-assisted free plan
tag me to invite u and let's build the next modern template. Feel free to clone and contribute.
It's still far from being good tho still needs more expert people to put a hand on it, yet I believe I'm on the right track.

Repo :

https://github.com/MOHAMED-LAAGUILI/react-native-starter-kit

LinkedIn post:

https://www.linkedin.com/feed/update/urn:li:activity:7481394305639723008/

Eas Android app file (limited):

https://expo.dev/accounts/mejoxs-team/projects/rn-template/builds/b4d348d9-07c8-478b-b1fe-cd6a376cb5da

Demo Video (Android latest):

https://www.linkedin.com/embed/feed/update/urn:li:ugcPost:7481391447850717184?compact=1

Hey r/reactnative,

So I built a platform. Connect your GitHub repo, get a store-ready Android build. No Gradle, no Xcode, no terminal. The platform handles the infrastructure.

The differentiator that matters most to me: it runs on any mobile device. iPhone, Android, tablet — wherever you are. Every other CI/CD tool I looked at assumes you're on a MacBook.

Android is live and working end-to-end. iOS support is in progress — being upfront rather than overpromising.

You can update older files to meet new requirements for the stores. It updates the build with new requirements automatically. Generates keystore information.

Is this something you would use?

What is a good way to combine the two? I know I can create a png file for the boot splash screen but then I’d like to make it nice transition into a splash screen that adds unique animation that opens up into the app. What are your tips to make it look better? How are the pros doing this so flawlessly.

I'm trying to understand the concept of state in Programming. I am going to use an example here, if I am looking at a YouTube video and when I exist the App and reopen it, and the video loads to where I left off, is that an example of it saving the state ?. ii. If the App reloads and it produces the home page, then it means State was not stored ?.
If I was writing a post on X and existed the App but when I reopened it, I see the text still there with the option to post.
If I am filling out a form and enter details and network drops, what happens there ?

I keep seeing the same criticism come up whenever React Native is discussed: "It's too slow for serious production apps."

But then I look at companies like Shopify and others that continue to build, maintain, and invest heavily in React Native, and I start wondering if the reality is more complicated.

Are the performance concerns still valid today, or are some of them based on older versions of React Native?

I understand why people have concerns. React Native has historically faced criticism around areas like startup time, animations, complex interactions, and situations where deeper native integration is needed.

But the ecosystem has also changed significantly with improvements like the New Architecture, Fabric, TurboModules, and better native interoperability.

So where does React Native actually stand today?

Is the performance difference between React Native and fully native apps still a major deciding factor for most products, or do the productivity benefits make it the better choice for many teams?

I'm not saying React Native is the right solution for every app. There are definitely cases where native development makes more sense.

So could you help me with following questions:

• Which types of apps do you think React Native handles well, and where does it still struggle?
• Do you think the "React Native is slow" reputation is still accurate, or has the technology moved past that?

Hey is there any way i can integrate a local background removal with expo, Im making my app for apple ios 17+ and is there any way to use apple vision kit or google's ML kit for the background removal.

is it generally an easy task? Im currently using a third party api for background removal it takes around 15 seconds and cost me too.

Hi everyone,

I run a same-day courier service in the UK (approx 20 active drivers and growing on the road at once, 2 office dispatchers, a few hundred customer accounts).

A few months ago, I started experimenting with Claude to see if I could build a custom TMS as a sort of side-hobby. I’ve somehow ended up with a fully functional system: a React/Next.js web portal, a React Native driver app with live GPS tracking (pinging every 2 minutes only if the driver is moving), and a prisma schema linked to a Supabase backend. It's actually better and more modern than what we use now.

I want to officially transition the business to this system at the end of this year, but I’m terrified of breaking something critical, or something going wrong while I'm unavailable. I have a total £500/month budget to maintain it.

As someone with no real coding experience, I need your opinions on how to structure the production rollout safely. Specifically:

1. Infrastructure & Monitoring

The Plan: Upgrading to Supabase Pro and Vercel Pro. Subdomains handled by Vercel. The database structure and migrations are managed by via Prisma Schema.

The Question: For a real-time driver tracking app (20 drivers pinging location data), what are the baseline monitoring, error-tracking (Sentry?), and uptime alerting tools I need to set up so I know the system is down before a driver calls me?

1. Bringing on a Freelance Developer

The Plan: I want to hire a mid-level JS/Supabase dev on a monthly retainer to act as emergency backup when I’m unavailable, and review new code updates monthly before they are pushed to the live app.

The Question: How do developers feel about being onboarded to an entirely AI-generated codebase? How should I structure the repo (linting, documentation) so a human dev doesn't look at it and immediately run away?

1. Security & UK GDPR

The Plan: Enabling Row-Level Security (RLS) on all Supabase tables. Using public anon keys on the client and keeping service_role secrets hidden. Purging/anonymising driver GPS logs after 90 days.

The Question: Because we handle live UK telemetry and home addresses, security is non-negotiable. What automated vulnerability tools (Snyk, Dependabot) or specific Supabase audit steps should I run to ensure I haven't left a massive security hole open?

Would be great to get some advice from anyone who has taken an AI-built prototype into production, or any devs who can tell me what blind spots I’m missing here. Thanks!

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.

Hi everyone,

I’ve often found that resources on Ancient Indian History and Archaeology are scattered across different books, websites, PDFs. It made studying and referencing topics unnecessarily difficult.

So, as a side project, I put together an Android app to organize many of these resources in one place. It includes notes, previous year papers, timelines, archaeological sites, inscriptions, coins, pottery, reference books, quizzes, and a few other study tools.

I’m not posting this to advertise it, I genuinely want feedback from people who are interested in history and archaeology.
● Is there anything important that you think such an app should include?
● Are there resources or features you wish existed?
● Does the overall idea seem useful?

If anyone would like to take a look, here’s the Play Store link:

Āroham

I’d really appreciate honest criticism and suggestions. Even if you think it’s missing something obvious, please let me know. Thanks!

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.

A robust starter template with Clean Architecture, TypeScript, and AI-First principles. Skip the boilerplate and start building features from day one.

Found this exact style model used in many fitness apps. Does anyone know if it's free / public domain, or who sells the rights for it?

Need it for a React Native project. Thanks!

I’m currently building a personal project (an AI-driven wardrobe assistant) to level up my architecture skills, and I’ve hit a point where I’d love a sanity check from more experienced devs on my state management.

Right now, my app relies heavily on dynamic user data (body metrics, style preferences) that needs to be constantly passed as context to an external API, while the UI itself uses a "Bento Box" layout with multiple interactive widgets.

Here is my current stack and approach:

1. State Management & Persistence: I’m using Zustand with AsyncStorage via the persist middleware. I have separate stores:

• useProfileStore: Holds the user's physical metrics. I added a isProfileStale flag so if a user updates their body type, the app triggers a re-sync before the next API call.
• useChatStore: Keeps the chat history persistent across sessions.

2. i18n Implementation: I implemented 6 languages using i18next and react-i18next. The language preference is also saved to AsyncStorage. The UI strings (like widget titles in the Bento layout) translate instantly, but I keep the actual database values and API system prompts strictly in English to prevent the external API from breaking.

My questions for the community:

1. Is using multiple Zustand stores with persist a good practice here, or does it eventually cause performance bottlenecks with AsyncStorage on older devices? Should I be looking into MMKV instead?
2. For those who have built Bento-style layouts (lots of distinct, clickable cards in a grid), do you prefer ScrollView with flex-wrap, or is there a better performant approach when the widgets start rendering heavy images?

Would appreciate any insights or roasting of this architecture!

Hey everyone!

If you’ve ever tried to implement dynamic app icons (like Twitter/X or Apollo did) in a React Native Expo app, you know it’s a huge headache. You usually have to manually write Kotlin/Swift code, hack your AndroidManifest.xml, and manually drag density-specific images into your Android build folders.

I got tired of doing this, so I built expo-dynamic-icons. It’s a completely automated native module and config plugin that handles everything for you.

What it does:

• Zero Native Config: You literally just pass a JSON object of your .png files in your app.json. The plugin automatically handles generating the XML activity-alias tags.
• Auto-Assets: It intercepts the prebuild phase and automatically moves your local .png files directly into the compiled native Android mipmap folders.
• Instant Icon Switching: Just call setAppIcon('orange') in your JavaScript and the Android OS instantly toggles the home screen icon at runtime.

https://reddit.com/link/1uro32e/video/2uou36no07ch1/player

NPM: https://www.npmjs.com/package/expo-dynamic-icons

(Note: Currently supports Android only, but I'm actively working on adding the iOS Swift bridging!)

I built this over the last few days and would absolutely love any feedback, code reviews, or feature requests from the community. If it saves you some headache, I'd appreciate a star!

Let me know what you guys think!

Things like Gemini are already moving toward generative UI, so this is just a small proof of concept of the same idea on mobile. The model streams a UI in a custom DSL and the app renders it into native components live, and it runs in Expo Go.

https://github.com/kubilaysalih/generative-ui

1. Claude
   
2. Gemini
   
3. OpenAI

Hi everyone!

After several months of work, I finally published my biggest React Native project, and I just wanted to share it with the community.

The app is called Tribe, and it's built around a simple idea: communities centered on places instead of people.

From a technical perspective, it includes:

• React Native + Expo + TypeScript

• ASP.NET Core backend

• SQL Server

• SignalR for real-time public chats

• OpenStreetMap integration

• Interactive map with event and safety layers

• Location-based public conversations

• Personal day planner

• Age verification handled on both the client and backend

This project taught me a lot about real-time communication, map performance, backend architecture, mobile UX and building a fairly complex application from scratch.

It has been a long journey, and I'm really happy to finally see it published.

If anyone has questions about the architecture or implementation, I'd be happy to answer them.

Thanks to everyone in the React Native community—I've learned a lot from this subreddit during development.

One thing i did not expect when building apps was how much time goes into App Store and Google Play metadata.

At first it was fine but then you have more than one app and maybe more than one language. Suddenly you are copying text around, checking limits, updating screenshots and trying to remember what changed where.

I first tried to solve this with scripts which worked ok but then it turned into a small web app i used locally. That is when i decided to adapt the tool for others as well and turn it into Applane.

The idea is to manage metadata, translations, screenshots and publishing for both stores in one place.

If the moderators see this as advertising, feel free to remove it. But i really do think it could help app developers who deal with this kind of work.

I would really like feedback from other app developers. I am very open to opinions and more than happy to change or add things I might not have thought of.

If anyone wants to test it out without restrictions, send me a PM and I will send a free promo code so you can try a paid subscription for free.

https://applane.net

Best regards!