It prints; you drag; the totals roll. Settle tears it off.

Expo · Reanimated · Gesture Handler

Hi everyone! 👋

I’m currently exploring new job opportunities as a React Native Developer and would appreciate any leads or referrals.

I have 4+ years of experience in React Native mobile app development, working on building, maintaining, and optimizing applications for both Android and iOS.

My technical skills include:
React Native and JavaScript
Android and iOS app development
REST API integration and backend communication
State management, debugging, and performance optimization
App releases, production support, and troubleshooting
I’m looking for opportunities where I can contribute to building scalable, high-quality mobile applications and continue growing as an engineer.

📍 Preferred location: India / Remote / Open to relocation | Current Location is Jaipur

If your company is hiring or you know of any relevant openings, please comment or DM me. Referrals and suggestions would be greatly appreciated!

Thanks in advance! 🙏

Most RN errors aren't hard once you know which layer broke. This is the routine that saves me the most time:

1. Read the first error, not the last line. Red screens and build logs usually end with something generic. Scroll up to the first real error and the top stack frames that point into your own files.

2. Name the layer. Metro couldn't bundle (Unable to resolve module), JS crashed at runtime (Text strings must be rendered within a <Text>), a native module is missing (works in a dev build, crashes in Expo Go), or Xcode/Gradle failed to compile. Each has different fixes.

3. Check how you run the app. Expo Go only has the native code bundled into it. If a library ships its own native code, you need a development build, and if you added it after building, you need to rebuild.

4. Clear caches before anything deeper. npx expo start --clear fixes a surprising number of resolution errors after moving files or changing Babel config.

5. Align versions. npx expo-doctor and npx expo install --fix. SDK/library mismatches are behind a lot of both runtime crashes and EAS build failures.

Two sneaky ones worth knowing:

• {count && <Badge />} renders 0 as raw text when count is 0, which gives you the "Text strings must be rendered within <Text>" error. Use {count > 0 && ...}.
• localhost on a phone is the phone. Use your machine's LAN IP for a local API.

What's the error that cost you the most time?

I'm researching an Expo starter kit for developers who want to build subscription-based mobile apps.

I'm particularly interested in the setup around authentication, Firebase, RevenueCat and store builds. Before building the kit, I want to understand where people actually get stuck.

If you've built an Expo app recently:

- What part of the initial setup took longer than expected?

- Did you start from scratch or use a starter kit?

- What would make a starter kit worth paying for?

I'm at the research stage and would appreciate honest answers, including if you think a paid starter isn't useful.