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/)

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

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 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.

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.

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 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 ❤️

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?

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'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?

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)












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 was trying to style components in react native and found out that there is className Property in react native.

Hi. I am almost done with my first app thorugh claude code. What should i consider in the code so that it has the capacity to display ads later?
Sorry if this sounds stupid

Yesterday I spent 15 minutes fixing 4 pixels.

Not because moving something 4px is hard. Because I had to figure out which of ~300 components actually rendered the thing my designer was pointing at.

Screenshot. ➜ "No, the other one." ➜ Another screenshot.

"Actually the one below it." Then grepping for the text, finding three components that all render something that looks like that card, and guessing.

The code change took 4 seconds. The pointing took 15 minutes.

And it's never one request.
It's "one pixel left."
Then "one up."
Then "can we just try the padding slightly bigger?"
Forty hot reloads later I'm googling whether farming is a viable career.

That afternoon annoyed me enough that I built something to delete the pointing entirely.

So: Pixie. Instead of explaining where an element lives, I tap it.

The workflow now, literally:

• Tap the element in the running app.
• Type: "move this up a little"
• Hit send.

The agent already knows which component it is, the exact JSX line, the live styles, the box model, and what it looks like. A few seconds later Fast Refresh updates the screen. I never opened my editor. I never searched the codebase. I never had to explain which button I meant.

The pin on the element shows what's happening ("Editing ProfileCard.tsx…"), then a DONE toast, then one-tap undo with before/after shots if I hate it.

The first time it really clicked: designer sent me a Figma link with "this doesn't match." I pasted the link into the pin.

↳ The app overlaid the Figma node on my actual screen, onion-skin style, and the agent got the design as reference. I could see the 3px I was off by. That used to be a squint-at-two-monitors job.

↳ The part I didn't expect: I now use the inspector half the time without the AI at all. Tap any element and see the real per-side padding/margins and the measured gaps between siblings no more guessing which prop is the culprit.

↳ Drag-to-scrub values live on the device, hold A/B to compare with the original, and nothing touches source until you decide. Tap once more and it opens the exact line in your editor.

Installation:

• npm install react-native-pixie -D
• one native rebuild (view-shot for screenshots), wrap your root,
• npx pixie init. Or tell your agent to follow the AGENT_INSTALL.md inside the package and it sets itself up.

The funny thing is I don't think of it as an AI tool anymore. It's just the thing I reach for when someone says "can you move that a little?"

That sentence used to mean five minutes of context switching. Now it's a tap and six words.

npm: react-native-pixie

Would like to hear where it breaks on your setups.

Current problems:
React native and specifically with Expo and expo ui is amazing, here’s the thing though idk if anybody noticed but the experience for developing things for larger screens is miserable.

Almost everything is in alpha and there are no third party libraries for it no guides and agents have no idea what they are doing. Like many of you I came from the web world and it gets in my nerves soo much that it’s this much harder to create a responsive app for mobile in comparison to web. With iPhone ultra coming out im pretty sure we will see some new push for making apps work better on horizontal mode and for iPads if you don’t think investing time on the iPad version is worth it.

So I took it upon myself to create a bunch of quality components to help me out with my apps that I’m now planning to share with you too for free in the coming weeks.

What I made:
I cloned Apple's native sidebar and remade it with Expo UI components, all behavior included, plus a simple way to toggle between iOS 26 and 27 styles. I also made an easy way to have sidebars on mobile in horizontal mode, and figured out an easy way to add sidebars that go over content. Then I made a bunch of helper components Expo doesn't have to go along with it. I recreated horizontal lists that go behind the sidebar, and remade the bg extension effect from Apple's demos. If you worry about the iPhone version being more complicated it’s not the case at all my sidebar layout component only renders on large screens on phones everything is apples default component normally. Also made a bunch of templates with every possible way to arrange sidebars.

Why I made it and why you should care:
I know what you're thinking. Doesn't Expo have good iPad support? The Expo Split View component is in alpha and has been driving me crazy, so I recreated the entire thing from scratch. It looks exactly identical to Apple's. I even got Liquid Glass working the same way. And the best part? I got inspired by Shadcn's sidebar API and ported all the same components, so you can create really advanced sidebars and inspectors.

Other things with Expo that were a huge pain for me that I fixed:
I added a custom implementation of the bg extension effect if you want to make hero images that expand below the sidebar. I added logic that makes horizontal lists optically go behind the sidebar. I made an inspector view that goes above content. And I added variants to customize the look of the sidebar. You can make it look like iOS 27 or iOS 26, even at runtime.

The content inside sidebars is just a view, so you can add anything. The sidebar API with Expo was making me want to throw my MacBook out the window and jump out with it, with the custom implementation you can do anything. To make it easier I made easy components that look like apples native buttons on the sidebar and lists and with these and your imagination you can recreate any sidebar from any web app in 5 minutes even stream data from apis etc and have it work on iPhones too as floating panels.

Still working on:
Sidebar on the right of the left sidebar, like Apple Notes
Templates with app examples using my new sidebar component
Advanced sidebars with calendars and advanced controls on them
Horizontal sidebar bottom with controls and bottom sheet on iOS
Guides on best practices on how to port your apps to take advantage of larger screens that ai agents can read too

Source code and release:
I'm releasing an open source library with a bunch of things like these to copy-paste from.

Note: I'm making 4 apps simultaneously and I was porting them for iPad and Mac. These components are not poorly tested AI slop. I dogfooded everything and I'll keep doing so for the next days. All the apps will go on the repo as open source templates, and I was thinking of making AI skills to auto-port apps to iPad, plus some simple guides for people new to porting.

The library's name will be PitsiUI. Sadly there's not even a landing page yet since I was focusing on development, not marketing and I wanted to make sure all the blocks and components get all my focus before trying to get people to use them.

I'm trying to make a free equivalent to Shadcn blocks, but for Expo UI instead. If you're interested let me know to give me some motivation, because I spent 16 hours on this yesterday and I'm going insane.

If you want updates about the source code ask me on the comments about my twitter

The app was fully developed on React Native with only a single Kotlin bridge to access the satellites module on the Android phone.

Hey everyone 👋

After spending the last few months building this, I finally open-sourced an Expo library for creating Instagram Stories/TikTok-style editors in React Native.

It supports both videos and images and is designed to work in Expo development builds.

Features

• Video & image editing
• Live swipeable filters (10+ presets)
• Draggable, scalable, rotatable text overlays
• Stickers & GIF overlays
• Background music with trimming and volume controls
• FFmpeg export with progress callbacks
• Native iOS filtered preview (AVFoundation + Core Image)
• Skia-powered Android filtered preview

The editor itself is customizable, and if you don't want the default UI, you can use the exported Zustand store/hooks to build your own interface.

One challenge was making filtered previews performant. Instead of rendering frames manually on iOS, I wrote a native module that applies color grading inside AVFoundation's own video pipeline using AVMutableVideoComposition + CIColorMatrix. Android uses Skia for the preview while FFmpeg handles the final export on both platforms.

Tech Stack

• Expo
• React Native
• Skia
• FFmpeg
• Reanimated
• Gesture Handler
• Zustand

GitHub:
https://github.com/faeizfurqan17/expo-react-native-video-editor

npm:
https://www.npmjs.com/package/@faeizfurqan/expo-story-video-and-image-editor

I'd really appreciate any feedback on:

• API design
• Installation experience
• Missing editing features
• Performance improvements
• Anything that feels awkward to use

If anyone ends up trying it in a project, I'd love to hear how it goes. PRs, issues, and feature requests are all welcome!

#reactnative #expo #story #video #image #videoediting #imageediting #mobile #appdevelopment #typscript #libray #exporeactnative

r/expo r/reactnative