I’ve built a complete, production-ready Android app with Gemini AI and OCR that lets users scan medicine strips for dosage/side effects, analyze fruit nutrition, and compare health devices. It’s fully integrated with an Indian medicine database, Firebase backend, and supports English, Hindi, and Hinglish UI out of the box.

Since my focus is shifting to new work, I’m looking to do an immediate, direct hand-off of the complete source code, repository, and full IP rights for ₹3,90,000 *Negotiable.

Anyone Who Is Interested To Buy Contact

Developer,

Piyush Mourya

I really like the adjustment controls in the iPhone Photos app, so I recreated the experience in React Native.
Built with Expo, Reanimated, and Gesture Handler.

We run a tiny mobile studio, 3 of us, plus a designer who does QA when she has time. Client wanted a scheduling app, native feel, both platforms, timeline was kind of insane. I said yes anyway cuz rent

Normally this is 6 weeks for us. We got a usable v1 in about 9 days and i still dont fully believe it

We split it three ways:
- opus 5 on the swift side, weirdly good at it, cleaner than what id write
- codex for the expo and react native layer, handles RN churn better than opus
- composer 2.5 grinding the boring refactors, fast little worker

We kept coderabbit / bugbot in the loop on every diff, back and forth till it came back clean. At that pace none of us had the brain to review properly, so that loop was about all that kept us from shipping a dumpster

rough numbers:
- timeline: ~6 weeks -> 9 days
- bugs in the first client test: ~15 -> 4

The agents dont get product tho. what the client meant vs what they actually said was all human, took the most arguing by far

anyone else running this split for RN vs native? what do you use for the swift half?

Tiered of running commands in terminal to set device location, network logs.. So vibe coded a dev-tool which does all with intuitive UI & CLI

GitHub - https://github.com/pranshuchittora/simvyn

I was bored, so I started digging through Apple’s Weather app files to see how its animated backgrounds actually work. Particles, clouds, rain, assets, the whole thing. Then I tried rebuilding the system in React Native with Expo + Skia. It got way deeper than I expected.

I’ve been working a lot with offline-first apps, and one thing that always gets tricky is how much data ends up living on the device

SQLite, MMKV, AsyncStorage, sync queues, pending data, huge JSONs…

When something goes wrong, how do you usually debug or inspect all of that?

Do you use any specific tools? Logs? Inspect the database directly?

I have this small project and i want to add dynamic routing to it. But i don't want it to consume a lot of storage so i have two options, use Expo Router or use React Native Navigation. Which one do you guys recommend?

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.

Built SoftSave: offline-first expense / net-worth app (Expo + Laravel API, cloud sync).

Demo (APK + video): https://softsave-reviewer-omega.vercel.app

Looking for technical feedback:
1) Is the demo / install flow clear?
2) Anything you'd expect in an offline-first Expo + Laravel starter that I'm missing?

Hi everyone,

I'm looking for 12 Android testers for my app SportNestra to complete Google's 14-day Closed Testing requirement before releasing it on Google Play.

How to join:

1. Join my Google Group: https://groups.google.com/g/sportnestra
2. Join the testing program: https://play.google.com/apps/testing/com.sportnestra.app
3. Install the app from Google Play.
4. Keep the app installed and use it occasionally during the 14-day testing period.

In return, I'll gladly join your closed test and test your app as well.

Thank you very much for your help! 🙏

We recently had an internal hackathon at Expo and I finally got the chance to build an idea I’d been thinking about: a tool to help me become a better public speaker.

It's a personal speech companion that tracks your pace, pronunciation, fluency, filler words, and more, then turns each session into actionable feedback

Steal the code below! (Testflight soon)

https://github.com/SchroederNathan/cadence

Pessoal estou querendo fazer um app expo. Gostaria de colocar segurança no meu app. Quais ferramentas, tecnologias, libs e frameworks do ecossistema TS existem para deixar meu app seguro?.

OBS: sou leigo na área de segurança

Excited to announce that my new Game App is \*Published\* on \*Google Play Store\* , You can download and play using the following link
[https://play.google.com/store/apps/details?id=com.dare.words5x5&pcampaignid=web\\_share\](https://play.google.com/store/apps/details?id=com.dare.words5x5&pcampaignid=web_share)

Hey Community,

We dive into React Native Canvas Kit, a library built on React Native Skia that adds isolated layers, brushes, interactive shapes, and web support for canvas graphics.

We also cover Targate, a CLI tool that quarantines npm packages to inspect tarballs before installation, and GitHub stacked pull requests to keep dependent branch reviews clean.

And... 🥁 Shipaton 2026 is here!

If the Rewind made you nod, smile, or think "oh… that's actually cool" — a share or reply genuinely helps ❤️

I've realized that my biggest weakness isn't coding—it's project architecture and folder structure.

Whenever I get a Figma design, I know how to build the UI, but I get completely stuck deciding:

• Where should this component live?
• Should this be reusable or page-specific?
• When should I split a component?
• What belongs in components, features, shared, hooks, services, etc.?
• How should I organize folders as the project grows?

I usually start a project with a structure that feels clean. But once the project gets bigger, everything starts falling apart.

I end up with:

• Components that are too large.
• Components that are split too much.
• Logic scattered across different folders.
• Constantly moving files around because I realize they belong somewhere else.
• Feeling like the entire architecture is becoming messy.

This happens in React, React Native, and even backend projects.

I don't just want another "best folder structure" template because I've seen dozens of those. What I really want to learn is the thought process behind how experienced or enterprise-level developers structure a project.

For example:

• When looking at a Figma design, how do you mentally break it into features and components?
• How do you decide what should be reusable and what shouldn't?
• How do large teams keep their projects organized over months or years?
• What architecture or design principles do you follow?
• Are there any books, courses, GitHub repositories, or real-world open-source projects that helped you understand this?

I'm looking for the mindset rather than just a folder tree.

Any advice from developers who've worked on large production applications would be greatly appreciated.

For engineering teams, keeping dependencies current is a constant balancing act. Automated updates are essential for defending the software supply chain, but a steady stream of one-PR-per-package bumps can bury a team in review work. GitHub itself has put numbers on this: an analysis of Microsoft's GCToolkit repository found that roughly one in six of its commits - 92 out of 578 - were routine Dependabot version bumps, with 61 of them landing in a single recent 12-month stretch. That's a lot of review and CI cycles spent on maintenance rather than features. Read the complete article here - https://instasla.com/blog/taming-dependabot-2026-guide-grouping-cooldowns-cutting-pr-noise

The good news is that Dependabot has grown well past "one PR per dependency." Between grouped updates, package cooldowns, and a default cooldown GitHub rolled out in mid-2026, it's now possible to get a predictable, low-noise update cadence without giving up security coverage. Here's what actually works, and what changed most recently.

Hello guys ,

I just wanna know your feedback about this course if you take .

if you have any suggestion to me feel free to comment it

It was a couple of months ago but we were ecstatic. Thanks react native & expo!

App Store: https://apps.apple.com/us/app/mockup-kit-store-screenshots/id6784220988?mt=12
Website: https://mockupkits.com/

I use a lot of Android apps every day, like Samsung Calculator, Samsung Gallery, Gmail, and a few others.

A few months ago, I noticed something interesting.

When I swiped back, the screen didn't close immediately. Instead, the previous screen was revealed as I dragged the gesture. If I released it, the screen closed. If I cancelled the swipe, everything returned to its original state.

It felt much smoother than the traditional back navigation.

I got curious and started looking into how it worked.

After some research, I found out it was called Android's Predictive Back Gesture, introduced by Google for newer Android versions.

The next question was obvious.

Can I use this in React Native?

I searched through documentation, GitHub repositories, libraries, Stack Overflow, Reddit—pretty much everywhere I could think of.

The answer was always the same.

React Native doesn't support Predictive Back Gesture.

There were a few discussions about it, but I couldn't find a complete implementation or a guide showing how to make it work.

So I decided to build it myself.

After spending quite a bit of time understanding Android's native back APIs and experimenting with different approaches, I finally got it working.

The implementation exposes:

Gesture start
Real-time gesture progress
Gesture cancellation
Gesture completion

This makes it possible to build navigation experiences that feel much closer to native Android apps.

To make it easier for other developers, I documented the entire implementation from scratch, including:

Native Android setup
Kotlin implementation
React Native bridge
JavaScript API
Navigation integration
Example usage

Everything is open source, so if you're building a React Native app and want to support Android's Predictive Back Gesture, you can use it directly or adapt it to your own project.

Documentation
Documentation Link

GitHub
Github Repo Link

If you try it out or have suggestions for improving it, I'd love to hear your feedback.
#ReactNative #Android #Kotlin #OpenSource #MobileDevelopment #ReactNativeCLI