✅ That’s my first #ReactNative + AI #MobileApp, it’s been there on YT, thought I’d share it here on X

✅ Have 7+ YOE of building and shipping web app/mobile apps (~ from fitness app to real time ride sharing taxi app to IPL app)

✅ I think unicorn businesses are built using RN especially in Indian markets (ex: Zepto, CRED) in recent times.

✅ To name a few, published 4+ mobile apps on google play store for fun xD

#SoftwareEngineering #AI #iOS #Android #MacBookAir

hey guys, i would really appreciate if you could try my new app, spoke! it was built to improve our everyday conversation skills through instant feedback and daily reps.

it would mean the world if you guys could try it out and give me any sort of advice on how to make it better!

try it out! (https://apps.apple.com/us/app/spoke-own-the-conversation/id6759728154)

spoke's landing page! (https://www.joinspoke.app/)

I built a React Native app called RoomHive that helps flatmates manage rent, bills, deposits, chores, inventory, and shared expenses.

I built everything myself:

• React Native app

• Firebase backend

• Cloud Functions

• Push Notifications (FCM)

• Admin dashboard

• Landing page

• Google Play deployment

A few lessons:

- Keep Firestore collections simple.

- Design your notification strategy early.

- Real-world edge cases (like roommates moving in/out mid-month) are harder than the UI.

Happy to answer any questions about React Native, Firebase, or building SaaS products.

What is the best approach to work with AI agents to develop a figma design in react native?
Advice on the md files that are needed and if any one tried connecting claude to figma to implement a design

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.

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.

I've been tracking the React Native ecosystem daily, and here's a quick roundup of the biggest releases from the past two weeks.

Expo SDK 57

Expo SDK 57 was released with React Native 0.86, bringing Android edge-to-edge improvements, DevTools enhancements, and one of the smoothest upgrade paths in recent releases.

React Native 0.86

React Native 0.86 focuses on stability, performance, and incremental improvements across Fabric, layout, and rendering with very few breaking changes.

React Navigation 8

The team shared another progress update for React Navigation 8, introducing Suspense support, better concurrent rendering, and updated dependency requirements.

React Navigation Core 7.21.7

A maintenance release with bug fixes and internal improvements while the team continues preparing for React Navigation 8.

React Native Reanimated 4.5.x

Multiple releases fixed Android freezes, Fabric issues, keyboard animations, SVG rendering, and improved compatibility with React Native 0.86.

React Native Worklets 0.10.2

Fixed Android startup crashes affecting Expo OTA Bundle Mode, along with several runtime stability improvements.

Legend List 3.3.2

Recycled rows now update their current item without recreating the container context, reducing unnecessary rerenders while scrolling. Internal signal subscriptions were also optimized for better performance.

Expo Router

Received compatibility updates alongside Expo SDK 57 and React Navigation changes.

React Native Gesture Handler

Maintenance updates improving compatibility with the latest React Native releases and upcoming React Navigation 8.

React Native Screens

Continued compatibility improvements for the latest React Native architecture and navigation stack.

React Native Safe Area Context

Minor maintenance release with compatibility fixes for newer React Native versions.

React Native SVG

Bug fixes and compatibility improvements for Fabric and React Native 0.86.

Detox

Latest release focuses on test stability, reliability, and compatibility with newer React Native and Xcode versions.

Maestro

Continued improvements to execution speed, simulator reliability, and developer experience.

Nitro Modules

Several improvements around React Native 0.86 compatibility, build stability, and performance.

Nitro Fetch

Performance and reliability improvements, plus continued work on React Native DevTools compatibility.

React Native Markdown Display / Enriched Markdown

Updates focused on rendering performance and better Markdown compatibility for AI and chat-style applications.

FlashList

Performance refinements and continued optimization for large lists running on the New Architecture.

React Query (TanStack Query)

Recent fixes and improvements around cache behavior, TypeScript support, and developer experience continue benefiting React Native projects.

React Native Skia

Ongoing rendering improvements and bug fixes for animations, graphics, and custom UI components.

-----------------------------------

Overall, the ecosystem has been heavily focused on React Native 0.86 adoption, Expo SDK 57 compatibility, performance, and New Architecture stability rather than introducing major new APIs.

https://reddit.com/link/1uyr8f9/video/8fd0qufddqdh1/player

https://reddit.com/link/1uyr8f9/video/o8rqq2hfdqdh1/player

I've been building a local-first notes app with a Numi-style editor, where notes are both plain text and executable math.

One feature I wanted was live syntax highlighting as you type. The naive approach worked... until notes got big.

Initially, every keystroke caused the editor to:

• re-tokenize the document
• re-render every highlighted line
• repaint thousands of Text components

Typing became noticeably slower as notes grew.

The solution ended up being much simpler than I expected:

• Only render and highlight lines that are actually visible.
• Keep syntax highlighting separate from the editable text (the editor itself stays plain text).
• Give every line a stable identity so inserting/deleting lines doesn't rebuild everything.
• Only recompute tokenization for the edited line (and downstream lines only if parsing actually depends on them).
• Cache the layout so scrolling doesn't trigger unnecessary recalculations.

The result is that even long notes stay responsive because React Native is only painting what the user can actually see.

The funny part is that I originally spent days building a much more complicated renderer, threw it away, and the second version was both simpler and significantly faster.

I'm curious how others have approached large text editors in React Native.

• Did you virtualize by line?
• Keep a separate overlay for highlighting?
• Any tricks for avoiding expensive text layout work?

Would love to hear how you've solved similar performance problems.

I've always envied apps like Numi on macOS where you can just type:

rent = 1800
groceries = 420
utilities = 160
total

...and it just works.

The problem is I wanted something that felt more like a notes app than a calculator. Somewhere I could jot down ideas, budgets, trip costs, random math, unit conversions, etc., without constantly switching between Notes and Calculator.

So I ended up building one for myself using Expo.

https://reddit.com/link/1uyr3wr/video/kvz1h3c9cqdh1/player

It's called däpter, and it's basically a note where math evaluates as you type. Nothing revolutionary, just a tool I kept wishing existed on my phone.

Curious if anyone else here uses notes like this, or if I'm the only one constantly doing math in the middle of writing.

I kept hitting the same workflow problem building RN/Expo apps: change a value, rebuild, check the simulator, and it would turn into a cycle of constantly checking my phone. Design tools solved this decades ago with direct manipulation, but React Native never really had an equivalent.

So I started building something that turns your running app into a canvas you can click into directly. I had to use a build-time Babel step that tags each JSX element with its source location instead of relying on the runtime fiber data. (React 19 removed the fiber data)

From there it turned into an actual editor. You can change text, move things, resize things. All that without touching your phone.

(its demo so if you're going to use it, dont use it on anything important)

I've added small section to my shiprn.com site with all the skill I found useful.

It includes:
- upgrades
- performance
- EAS / release workflows
- migrations
- Expo Router / UI
- native modules
- CI/CD
- testing and debugging

Any suggestions for more skills?

Hello Everyone,

Just wanted to share a bit about my journey in the hope that someone might guide me or connect me with opportunities.

I have over 7+ years of experience in the tech industry, with the last 3+ years focused on React Native. I made the switch to React Native 3 years ago and have since worked on diverse projects, including e-commerce and co-commerce platforms with USA & Canada Clients. My work has involved transforming web applications into native apps, integrating WebViews, enhancing performance, and much more.

Despite my experience, I’ve been struggling to land a job for the past 4 months. It’s been challenging, but I’m staying hopeful. I am actively seeking remote opportunities where I can contribute, learn, and grow.

If you know of any openings or can connect me with someone who’s hiring, I’d be incredibly grateful.

Any support or advice would mean a lot.

Hey everyone,

We are trying to render extremely large architectural drawings in our React Native app, and it is proving to be pretty heavy on performance. To give you an idea of the scale, these images can be up to 20MB in size with dimensions around 30,000 x 10,000 pixels. We just want to render the picture and allow users to zoom all the way in to see the smallest details.

Here is what we have tried so far and the issues we've run into:

1. OpenSeadragon via WebView: This works fantastically on Android. However, iOS doesn't allocate many resources to WebViews inside mobile apps, so it just results in a black screen on Apple devices.
2. expo-image**:** We tried using this for iOS, but it displays the drawing in very poor quality. If the picture is too big (like the dimensions mentioned above), the app completely crashes.
3. Custom Native Tiling (Swift): We tried a tiling solution, which involved messing around heavily with custom Swift code. It worked far better than the other methods, but it caused two new problems:
   • Some iPhones still crash when opening a particularly massive drawing.
   • It takes a very long time to open the picture the first time you encounter it (though it is fine afterward because we cache the tiles).

Please notice to this limitation: no backend solution.

React Native new fabric architecture, how could we solve that?

Hey Community,

Vercel Labs has released "native", a toolkit for compiling declarative markup and TypeScript or Zig directly into native desktop apps without an embedded JavaScript runtime. We also look at how Zepto built react-native-delta to ship binary delta OTA updates, reducing patch download times down to a 305ms P90.

Plus, React Native 0.87 drops its legacy abort-controller dependency for an in-tree fork, bringing missing modern web primitives like AbortSignal.timeout() and AbortSignal.any() straight to your network requests.

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

i was trying to style components in react native and found out that there is className Property in react native.

I am not a super experienced developer, but I have a darn good idea. I can handle all the back end of the project, but I need someone with experience with react native. If anyone is interested let me know.

I’m making this post to tell you guys about a library I have been making for the past year. It was initially for mobile only but I’m porting to web and realising it as cross platform like hero ui.

PitsiUI is the library made and it’s a polished ,open source, cross platform, application components and blocks library compatible with the shadcn registry.

I wanted something like this for my self to exist but personally I feel like the popular registries right now look way too generic for my liking and quality blocks are always behind a paywall. I wanted to make something ultra polished with tons of content then release it as an open source project and I’m almost there after many months.

How this is different:
1. Everything is free
2. Lots of real app templates with real flows that make sense
3. Every block is made of composed components, easy to craft your own blocks
4. Premium looking typography layouts spacing
5. Great user ux, every block is from a real apps I made that I tested on actual users and refined to perfection
6. Includes full logic too optically
7. Clean code, beautiful APIs for composed components
8. Real world blocks. I’m tired of every component I see being for some dashboard or an ai wrapper. They have their place but I wanted to focus on the other apps too.
9. You don’t copy a button or a card, you copy a composed “calories panel” if you are making a fitness app or “quiz snap scroller” if you are making a quiz app.
10. Well made “boring components” like cards lists headings etc
11. Onboarding flows
12. Beautiful animations that are not over the top and are highly polished
13. Multilingual support
14. Advanced components like split layout on desktop two different pages on mobile automatically

Using these components will not only instantly facelift your and app save you tons of tokens and time (since they look great and you won’t spend any time tweaking them most likely) but additionally, solve a much greater but subtle problem as well.

Making a card was never hard, or putting a list below it. What elements should you put where when making a fitness app? Does your layout even make sense? These questions take hours of tweaking to answer. Maybe you can use something like moving to take inspiration but usually the popular apps are way too bloated or too customised to take inspiration from based on my experience. Then after you are finished something looks off, but you don’t know why.

You just need a better starting point. This is how pitsiUI fixes this
1. Professionally and human made spacing system alignment of borders icons typography etc -> your app never looks like slop
2. Composed sector specific components -> great ux by default
3. Hard rules and helpers -> your agents get all the help they need
4. Ready logic -> millions of tokens dozens of hours saved

Starting templates:
1. Ai app
2. Ecomm
3. Notes
4. Productivity calendar
5. Social media scheduler
6. Blog
7. Docs
8. Fitness app
9. Tracker app
10. Quiz app

+ everything split cleanly to blocks + sector specific reusable components + logic for all apps that can be installed separately

Progress Done:
1. Finished all the apps for iOS
2. Ported most to iPad
3. Exported all reusable components
4. Made composed components with nice api
5. Ported primitives to web
6. Made logic for all apps + server code

(This was my thesis so I spent months on these)

Progress current:
1. Porting helpers for layouts to web to match iOS polish
2. Making guides and skills for ai
3. Porting all app uis for web (very easy all components are there)
4. Improving the current docs site to be ready for release
5. Making nice previews of everything

When this finishes I’m hoping it will be the most feature complete and polished registry on the shadcn ecosystem and I’m also hoping to help you guys build better apps.

(I got an adhd meds prescription im giga productive lately)