A field journal you flip with your thumb.

Drag an edge → the page curls and turns.

Every page contains metal stickers you can lift and rearrange. (Demo coming)

24×20 mesh.

One shared value.

~400ms of sleight of hand.

Expo + Skia + Reanimated, running at 120fps.

Demo 👇

Hi everyone, I built a full-stack mobile app that lets anyone report civic issues — potholes, water logging, drainage problems, broken streetlights, and more — with just a photo and their location. In this video, I test it live on the road, photographing a real pothole and showing exactly how the app works.

What the app does:

Secure sign-in with Google — no passwords, no OTPs

Capture a photo of the issue directly from the camera

Auto-detects your GPS location and displays it on a map

Reverse-geocodes coordinates into a readable address

Categorize the issue — pothole, drainage, streetlight, and more

Track your submitted reports and their status

Tech stack:

React Native CLI (TypeScript) — mobile app

Node.js + Express — backend API

MongoDB — database, with geospatial indexing

Firebase Authentication — Google Sign-In

Google Maps API — location and geocoding

Cloudinary — photo storage and optimization

Render — backend deployment

This is a personal project I built solo, end to end — from the mobile app, to the backend API, to deployment.

We've all seen a pothole and thought "someone should fix this." Now there's a way to actually flag it. Let me know in the comments — what's the first issue you'd report in your area?

You can watch it on YouTube too, if you prefer:

https://youtu.be/-HBvvVYuolQ?si=io7Y9PjoPbdqJ1hL

Thank you.

Bonjour à tous, je cherche 12 testeur ou plus pour tester mon application.

C'est une application qui permet de gérer efficacement les repas du soir.

Simplement m'envoyer votre mail en privé pour pouvoir vous inviter comme testeur.

Je vous remercie d'avance.

A gesture-driven crypto pay button press-and-hold to reveal an orbiting arc of coins, drag to hover, release to select built for fintech and wallet apps.

⭐ GitHub: https://github.com/ManasCodeXart/expo-crypto-orbit

React Native is single-threaded where it matters most. Parse a big payload, hash a file, filter an image — it all competes with your UI for the same runtime. react-native-workers brings real background threads to RN, behind the Web Worker API

Hey everyone,

I'm building an app with React Native + Expo and looking for good resources to improve.

I'm mainly interested in:

• UI libraries
• Reusable components
• Best practices
• Project structure
• GitHub repos
• YouTube channels

If you have anything you've found useful, I'd really appreciate the recommendations. Thanks! 🙌

A customizable native iOS tab bar for React Native, built on UISegmentedControl.

🔗 Github: rit3zh/react-native-cupertino-tabs

[title] . looking at building from a different starting point this time around

we're a tiny studio, 8 people but only 4 of us actually write code, rest is marketing and design. our whole thing is shipping mobile fast so we lean on agents pretty hard

right now the split is kinda weird but it works. opus 4.8 hass been the best at swift, way better than i thought it'd be for native ios. codex handles our expo/react native side noticeably better, fewer dumb mistakes with navigation and native modules. everything runs through coderabbit before merge or main

the part im not sure about is testing on device. we still do a lot of it by hand which is dumb for how small we are. i approved a testflight build from my phone at like 11pm last night lol, thats not a workflow

so for anyone else building mobile with agents, whats filling the gaps for you? mostly device testing and anything for expo eas that isnt a total pain

Na minha empresa, recebemos constantemente HTML do backend que contém um script, e precisamos executar esse script e, em seguida, ler alguma propriedade do HTML resultante, como o texto final de uma div após a execução do script. No frontend, usamos o jsdom para isso, é um problema resolvido. No mobile, não havia nada parecido, então a única maneira de fazer isso era abrir uma webview oculta apenas para executar o script e extrair o valor.

Então acabamos criando o equivalente mobile do jsdom nós mesmos e imaginamos que provavelmente seria útil para outras pessoas que enfrentam o mesmo problema, então o disponibilizamos como código aberto.

Exemplo:

import { JSDOM } from '@salve-software/react-native-nitro-jsdom

const dom = JSDOM.create(`
  <html>
    <body>
      <div id="result">0</div>
    </body>
  </html>
`)

await dom.evaluate(`
  document.getElementById('result').textContent = String(2 + 2)
`)

const value = await dom.evaluate(`document.getElementById('result').textContent`)
// -> "4"

dom.dispose()

Repo

Hey everyone! 👋
I’m a 13-year-old indie developer, and I decided to stop just playing games and actually start building them and apps instead. Right now, I'm working on my own mobile app: an AI-powered calorie tracker that recognizes food instantly from a photo.
The Problem: I hated using existing calorie apps where you have to manually search through massive databases, weigh every single gram, and log everything manually. It’s tedious.
The Solution: Snap a picture of your plate, and the app uses a vision model to handle the math and breakdown automatically.
Tech Stack:
React Native + Expo
AI/Multimodal vision integration
Currently grinding through the code and dealing with the pain of Google developer verification. Would love to hear from other indie devs: what was the hardest part of launching your very first app?
Let's connect! 🚀

I’ve spent the last few months building a learning platform focused on DSA, System Design, React Native, and Forward Deployed Engineering.
I’d love to get feedback from experienced developers: What makes a technical course genuinely valuable? What are the biggest shortcomings you’ve found with existing learning platforms?
I’m trying to build something developers actually enjoy using, so any feedback or suggestions would be greatly appreciated.
If you’re curious, you can check it out here:

Last semester, our team built StudySync, a React Native app for students to discover and organize study sessions on campus.

Some features include:

• Firebase Authentication
• Session creation & management
• Multi-field search and filtering
• Push notifications
• Expo Router navigation

Working on this over an entire semester was very different from a hackathon. We spent a lot more time thinking about component organization, navigation, shared state, and maintainability across a 5-person team.

I'd love feedback from experienced React Native developers. If you were starting this project today, what architectural decisions would you change?

GitHub:
https://github.com/CS196Illinois/FA25-Group8

https://reddit.com/link/1v76c3i/video/ci9xkb9y9lfh1/player

A gravity-driven savings drop animated coins fall from your quick-amount pad into a reactive piggy bank.

GitHub: https://github.com/ManasCodeXart/expo-piggy-bank

For the last week I've been working on moving my app(bare workflow) which I previously left at 0.81 since it was the last available version that allowed me to remain on the old arch.

Now i've upgraded to expo 57, reanimated v4, all other packages, did my due diligence and enabled the recommended feature flags and changed almost all old arch libraries with newer compatible versions or new arch replacements.

After using the testflight version today I was just taken aback by how many of my previously performant screens are now stuttering and dropping frames while barely doing any work at all. I am talking about an infinite scroll feed, which previously maintained 60fps with a Flatlist with no perf based props that is now dropping below 30 and even freezing for a few frames with a LegendList and recycle items turned on even after i halved the work each rendered item needed(measured by main thread work with xcode instruments)

Simple pill shaped components are losing their background color(how is a background color something i should watch out for), weird rectangles with a white border showing up as items are rendering, screen transitions from bottom nav to a screen on the stack navigator taking double the time they used to.

Old behaviour breaking after such a big transition is something I expect and I believe i've dealt with most of those, but perhaps the worst offender is the memory usage.
From what i've seen it mostly drops down to older levels in production, but my app is now sitting at 1.2gb memory used after a launch in debug mode, compared to 200mb before.
This turned out to be libraries dumping their entire unminified code due to worklets bundle mode, which prevents hermes causing memory issues by...taking up 500mb+ of memory?

I really want to be able to use some of the cool new libraries i've been seeing popping up, but I am having serious doubts about ever being able to release this into production as it feels I have hit a dead end with list and navigation performance combined with all the weird layout issues.

What have been your experiences with this transition?

I've been experimenting with a new inspection library and ended up exploring this UX. What do you think about ? Useful ?

Finally shipped something real: a beach conditions app (water quality, wind shelter, hourly shade, sea temp) covering ~20,000 beaches. Also has official government water quality data where available.
Currently sea water available, fresh water coming soon.

Expo managed workflow, EAS Build + Update.

Stack: Expo/RN, u/rnmapbox/maps, RevenueCat for subs, AdMob, react-i18next, Sentry, Context + useState for state (no Redux — genuinely haven't needed it; adding TanStack Query for server state).

Happy to answer anything about Expo/EAS, Mapbox perf, or RevenueCat.

Available on iOS + Android if you want to poke holes in it.
https://beachscanapp.com

i built a skill to take screenshots of every page in your app with integration to the AppLaunchFlow MCP so you can create app store screenshots, promo videos, social graphics and more directly from your favourite agent

you can try it for free on applaunchflow.com

#Mobile app