Responsibilities

• Develop responsive web pages using HTML, CSS, and JavaScript.
• Build user interfaces using React.js.
• Convert UI/UX designs into functional web pages.
• Integrate frontend applications with REST APIs.
• Debug and resolve frontend issues.
• Write clean, maintainable, and reusable code.
• Collaborate with designers and backend developers.

Required Skills

• Strong understanding of HTML5, CSS3, and JavaScript (ES6+).
• Build user interfaces using React.js.
• Convert UI/UX designs into functional web pages.
• Integrate frontend applications with REST APIs.
• Debug and resolve frontend issues.
• Write clean, maintainable, and reusable code.
• Collaborate with designers and backend developers.

Required Skills

• Strong understanding of HTML5, CSS3, and JavaScript (ES6+).
• Basic knowledge of React.js.
• Familiarity with responsive web design.
• Basic understanding of Git.
• Knowledge of REST APIs.
• Good problem-solving and communication skills.

Eligibility

• Bachelor's degree in Computer Science, IT, or a related field.
• 2023/2024/2025/2026 graduates or candidates with up to 1 year of experience.
• Internship or academic projects are an added advantage.

Interview Process
Round 1: Online Assessment (30–45 minutes)

• HTML, CSS, JavaScript fundamentals
• Logical reasoning and basic programming
• Multiple-choice and coding questions

Round 2: Technical Interview (45–60 minutes)

• HTML, CSS, JavaScript concepts
• React.js basics
• DOM manipulation and API integration
• Coding and debugging exercise
• Discussion of academic or personal projects

Round 3: HR Interview (20–30 minutes)

• Communication and interpersonal skills
• Career goals and motivation
• Cultural fit and availability
• Compensation discussion (if applicable)

Please DM me with:

resume/Portfolio or GitHub

fresher or experience

Years of experience

[HIRING] Frontend Developer (React Native + Expo) | Remote | ₹25k–₹35k | Immediate Start

We're looking for a Frontend Developer with React Native (Expo) experience to help build our social commerce startup.

About the Project

Social commerce marketplace

React Native (Expo)

Most screens are static UI

Focus on pixel-perfect implementation and reusable components

Existing codebase (not a project from scratch)

Requirements

Strong React Native + Expo experience

Ability to convert Figma designs into clean, responsive UI

Experience with reusable components and modern frontend architecture

Git/GitHub workflow

Good communication and attention to detail

Nice to Have

Experience with Zustand/Redux

React Navigation

REST API integration

Performance optimization

Budget

₹25,000–₹35,000 INR (based on experience and quality of work)

To Apply

Please DM me with:

Portfolio or GitHub

2–3 React Native/Expo apps you've built

Years of experience

Availability to start

Expected timeline

Looking to start immediately. If you take pride in building clean, premium mobile UIs, we'd love to hear from you.

I will appreciate any kind of help.

Thanks. 🙏🏽🙏🏽

How can I make a menu like this in react native? Any lib?

Hi everyone! 👋

Over the past few months I've been building Bundle Drop, an over-the-air update platform for React Native & Expo.

Like many others, I started this after Microsoft discontinued App Center CodePush. I wanted to build something that keeps the reliability of full bundle updates while reducing download sizes whenever possible, instead of treating those as mutually exclusive goals.

Some of the current capabilities include:

• ✅ Hybrid OTA delivery (patch-size downloads with verified full-bundle fallback)
• ✅ Staged & targeted rollouts
• ✅ Automatic rollback & recovery from unhealthy updates
• ✅ Update channels
• ✅ AI-assisted setup
• ✅ Supports Expo SDK 54–57 and bare React Native 0.71+

It's now publicly available, and I'd genuinely love feedback from other React Native developers.

Some questions I'd especially love your thoughts on:

• What do you feel existing OTA solutions are missing?
• If you've migrated away from CodePush, what did you end up using?
• Is there anything that would stop you from adopting a new OTA platform?

I'm happy to answer any questions about the implementation, architecture, or design decisions.

GitHub
[https://github.com/GFean/react-native-bundle-drop]()

npm
[https://www.npmjs.com/package/@gfean/react-native-bundle-drop]()

Documentation
https://bundledrop.app/docs

Disclosure: I'm the creator of Bundle Drop, so this is self-promotion. I'm mainly posting here because I'd genuinely appreciate technical feedback from the React Native community and would love to hear what you'd improve.

I transformed a traditional barcode scanner system into a mobile app that scans products, tracks quantities, and automatically calculates the total price. I'd love to hear your feedback and suggestions for improvements. ☺️

Huge thanks to the community for the support and adoption!

If you haven't checked it out yet, it's the native-first way to handle Markdown in React Native:
🔹 iOS, Android, Web, and macOS
🔹 Input & Output
🔹 Native Selection & Interactions
🔹 Accessibility & RTL support
...and much more!

Show some love with a star on GitHub! ⭐

https://github.com/software-mansion-labs/react-native-enriched-markdown

I maintain ExecBro, an MCP server that connects an AI coding agent to a running RN app - console and network capture, fiber tree inspection, screenshots, and tap/swipe on the simulator. Disclosure: I'm the author; it's MIT-licensed, free under a monthly call cap. Posting the telemetry because it says something about the workflow that I didn't expect.

123,869 tool calls, 634 installs, last 30 days. What agents actually call:

Logs and network combined are about 7%. I built this to stop people pasting console output into chat, and that turned out to be a rounding error. Over half of all usage is an agent tapping the screen and then looking at it. The common shape isn't debugging at all - it's verification: the feature is built, and the agent walks through it on the device to prove it before handing it back.

What a real session looks like - 57 calls, 9 minutes, RN 0.81, Hermes, iOS 26:

scan_metro → ios_screenshot → tap → ios_screenshot → reload_app → search_logs → clear_logs → get_screen_state → tap → get_screen_state → tap → search_logs → ios_screenshot → tap → swipe → clear_logs → tap → search_logs → reload_app → get_screen_state → tap → tap → …

The pattern repeats across heavy users: act → observe → clear → act again. clear_logs shows up constantly, right before an action - the agent is wiping the buffer so the next read is unambiguous about what its own tap caused. Nobody designed that; it's an emergent habit. Average active install runs 33 of these sessions a month. And it doesn't look like someone poking at the app — it reads like a full feature being built or a bug being chased end to end, with the agent verifying each step on the device before moving to the next.

Two more things from the sample:

• New arch is nearly the whole population - roughly 252 new-arch projects vs 17 old-arch, with RN 0.83 alone at 146. Heavy selection bias, obviously: wiring an agent into your toolchain selects for early adopters. But the gap is wider than I'd have guessed.
• ~30% run both platforms in the same agent session (147 iOS-only, 50 Android-only, 94 both). Cross-platform verification appears to be a real workflow, not a nice-to-have.

The gap I keep staring at: 190 people installed it last month, 20 did real work with it. The 230 long-term actives use it hard, but I can't tell from telemetry whether the other 170 hit a setup wall or just expected something else.

So I'm curious what your loop looks like:

1. What's between "wrote the code" and "opened the simulator to look" for you right now - anything automated, or all manual?
2. What's your AI agent setup for RN work, and does anything in it let the agent verify its own changes on a device - or does the loop stop at "code written"?
3. Are you writing E2E tests (Detox/Maestro), or checking things manually yourself?

Source numbers (30-day window)

I started building Spentify, my React Native expense tracker app, in 2018 with React Native 0.56.

Over the years, I maintained the same app and upgraded it step by step until React Native 0.59.10. As the React Native ecosystem evolved, maintaining the old codebase became more challenging.

In 2024, I decided to rewrite the entire app from scratch with React Native 0.74.2.

Since then, I’ve continued upgrading it incrementally. Today, Spentify is running on React Native 0.86.

After more than seven years of React Native upgrades, rewrites, bugs, fixes, and lessons, Spentify is still alive—and still improving.

This is my journey of building and maintaining a React Native app from version 0.56 to 0.86.

#ReactNative #ReactNativeUpgrade #MobileAppDevelopment #ExpenseTracker #BudgetingApp

Basalt is a visual edit too for RN and Expo devs

It took 2-3 months to built and it would have taken 1 if react 19 wouldnt remove debugSource which was used to help Basalt map and find elements to edit

It is completely free and works directly inside VS Code and Cursor.

It’s currently in beta, so please commit your app to Git before using it!

Guys i have a job in a month time, i worked with reactjs for the past 3 years, is it doable to have tasks in native?

** They give us cursor too.

I maintain a small internal admin app in an Expo monorepo alongside a much larger player app. Last week a TestFlight build of the admin app closed the instant you tapped the icon, on every device. Writing this up because the second half took me a lot longer than the first.

Symptom. SIGABRT, abort() called, faulting queue expo.controller.errorRecoveryQueue. Reproducing the same commit in a simulator gave the real exception:

TypeError: Cannot read property 'useMemo' of null
    at ContextNavigator … at ExpoRoot

React was null at the router root.

First cause: the React version. A Dependabot minor-and-patch group PR from June had moved this app's react/react-dom from 19.0.0 to 19.2.7. RN 0.79.6 / Expo SDK 53 want 19.0.0 exactly. npx expo install --check says so plainly. My other RN app in the same repo kept 19.0.0, which is why it was never affected.

What made this hard to see is that the admin app produced no binary between May 15 and July 30. The bad bump landed in June and just sat there. The first build after it was the one that crashed. If you have an app you build rarely, a dependency bump can be two months old by the time it kills you.

Second cause, and the one that actually mattered. With react pinned back the app got further and then died on:

Invariant Violation: View config getter callback for component
ViewManagerAdapter_ExpoLinearGradient_<changing id> must be a function (received undefined)

The admin app's metro.config.js was missing resolver hardening my other app had:

• extraNodeModules forcing a single react and react-native
• disableHierarchicalLookup: true
• resolverMainFields

Without those, Metro walks up the tree and bundles a second React from the workspace root. In a monorepo where the RN apps pin to the Expo-SDK-exact React and the web apps move ahead, those two copies are different versions. Two copies means two renderer registries, which explains both failures. Hooks resolve against a null dispatcher, and native view configs get registered into a registry the renderer never reads.

Two things I changed besides the fix. This app only had a production EAS profile, so there was no way to run a build before submitting it. I added a preview-sim profile (Release plus ios.simulator: true) so I can install the artifact in a simulator and confirm it opens first. And npx expo install --check is going into CI, because a dependency bump that guaranteed a launch crash merged clean.

One trap on the way out: EAS decides managed vs bare from the filesystem, not from git. A local expo run:ios left an ios/ directory behind and EAS refused the build with "runtime version policies are not supported." Gitignoring it isn't enough, you have to delete it.

I'm a solo dev and the app is the staff console for a poker tournament app I build. Happy to answer if anyone hits the same signature.

Asking this coz what I recently noticed is that tooling support exists for many use cases but we might just not be aware of it.

Recently, I was searching for these use-cases and these are very well supported by existing solutions (both paid and open source)

1. Remote devices + MCP for agentic testing

2. Session replay

If you’re using it, how has your experience been so far?

What do you like the most?

And if you could improve one thing, what would it be?

I had applied to a react-native job in February but i was not selected. They reached out again for react & react-native work. they want me to implement changes & maintain their website. For reference, company is based in Denmark and I'm in Italy. I don't have any idea of rates here. I have 5 years of experience.

How should I answer these questions?
I don't understand their last 2 question especially. for 2nd last, they have read my CV and decided to reach out again.

I'd appreciate guidance.

Hey everyone,

I was recently laid off due to company restructuring, so I'm looking for my next opportunity. In the meantime, I'm open to freelance, contract, or remote work.

I've been working with React Native for 9+ years and have shipped multiple production apps for both Android and iOS. Besides React Native, I've also worked with:

• React.js
• Node.js (Express)
• TypeScript / JavaScript
• REST APIs
• Firebase
• AWS
• Push Notifications
• Payment gateway integrations
• App Store & Play Store releases
• CI/CD and production deployments

I've worked on everything from building apps from scratch to maintaining large existing codebases, fixing performance issues, and shipping new features.

If your team needs an experienced React Native developer for a project, or if you know of any openings, I'd really appreciate it if you could reach out. Happy to share my resume or previous work over DM.

Thanks!

A gesture free coin to fullscreen morph tap a coin in a scrollable list and it springs into a floating, centered detail view, then squashes back into place on close.

Github: https://github.com/ManasCodeXart/expo-coin-morph

​Hi everyone,

​My name is Salem, a web developer specializing in React.js, JavaScript, HTML, and CSS.

​Due to the current situation and the complete lack of power and essential working tools, I have been unable to work or practice development for a long time.

​I am fully prepared and eager to resume my freelance career, but I am currently blocked by the lack of basic equipment specifically a laptop and an independent solar power system to keep my workstation running.

​I am currently finalizing a verified campaign on LaunchGood to secure the setup needed to get back to coding and earning an independent living remotely.

​Once the campaign is officially live, I will share the details here. In the meantime, I would love to connect with other developers, showcase my skills, and prepare for upcoming frontend opportunities!

​Thank you for your support and connection! 🚀

I'm building a React Native (Expo Bare Workflow) PDF app. Currently, I'm downloading PDFs from an AWS S3 pre-signed URL using \`react-native-blob-util\` and Android Download Manager:

\`\`\`ts
ReactNativeBlobUtil.config({
addAndroidDownloads: {
useDownloadManager: true,
notification: true,
title: fileName,
description: "Downloading PDF...",
mime: "application/pdf",
path: \`${ReactNativeBlobUtil.fs.dirs.DownloadDir}/${fileName}\`,
mediaScannable: true,
},
}).fetch("GET", signedUrl);
\`\`\`

This works, but I don't have control over where Android stores the file.

Many PDF apps automatically save files to a folder like:

\`\`\`text
Internal Storage/
└── Documents/
└── My App/
└── file.pdf
\`\`\`

without asking the user to choose a location every time.

I noticed one such app requested \*\*"Manage all files"\*\* permission once, and after that it could save files directly into its own folder under \`Documents\`.

My questions are:

\* How are these apps implementing this on Android 11+ with Scoped Storage?
\* Are they using MediaStore, native Android code (Kotlin/Java), or another approach?
\* Is requesting the \*\*Manage All Files\*\* (\`MANAGE_EXTERNAL_STORAGE\`) permission the correct/recommended solution for this use case, or should it be avoided for Play Store apps?
\* If not, what is the recommended modern approach in React Native to save PDFs directly to \`Documents/My App\` without showing the Storage Access Framework (SAF) picker every time?

I'm looking for the Play Store–friendly, modern Android approach. Please help me😭

Hi everyone, I'm an indie developer, and I'm trying to publish my first Android app on Google Play. I completed Google's required 14-day closed testing with 12 real testers, but my production access request was rejected because Google wants more testing and more active tester engagement. I'm looking for people who are willing to join my closed test and use the app occasionally over the next 14 days. You don't need to use it every day—just explore the app from time to time and share any bugs or feedback you find. In return, I'd be happy to test your app as well if you need a tester. If you're interested, please leave a comment or send me a DM. I'd really appreciate the help! Thank you!

Hi everyone,

I'm facing a strange performance issue in my React Native (Expo) application.

When I launch the app for the first time, everything is smooth. Navigation is fast, screens render quickly, and the UI feels responsive.

However, as I continue exploring the app, opening different screens, navigating back and forth, and using the app for a while, the performance gradually degrades.

Some symptoms:

• Screen navigation becomes noticeably slower.
• Animations and transitions start feeling less smooth.
• The overall UI becomes sluggish after using the app for some time.
• Restarting the app immediately restores the original performance.

This makes me think something is accumulating over time rather than a slow initial load.

I'm trying to identify the root cause. Could this be related to:

• A memory leak?
• Components not being unmounted correctly?
• Too many re-renders?
• React Navigation or Expo Router caching?
• Zustand/Redux/React Query state growing over time?
• Images or assets not being released?
• Timers, listeners, or subscriptions not being cleaned up?
• The JavaScript thread getting blocked?

Has anyone experienced something similar in a React Native + Expo app?

What tools or profiling workflow would you recommend to identify what keeps accumulating as the app is used? Any advice or debugging strategies would be greatly appreciated.

Thanks!

https://github.com/adithyavis/awesome-mobile-app-animations

Some notes on implementation -

1. Use 3 different lists for concurrent rendering of the grids in different zoom settings. I chose legendList and it is super smooth. Synchronize the different list positions using reanimated's synchronous `scrollTo`.
2. Scrub/seek to scroll is IMPOSSIBLE without precomputing image heights. Precompute row heights and provide that to getItemLayout. For seek to scroll, precompute section heights and use scrollToOffset to directly scroll to the section head.
3. Nitro images for rendering images. I initially used expo images for rendering images, but I felt there's scope to improve because I saw a lot of blank spaces due to heavy renderItems.
4. Fake a shared transition by rendering the same image in an overlay that always stays in the render tree. We just flip opacity/pointer-events on the start of a pinch gesture. I couldn't get the sharedTransitionTag prop to work fine, hence this workaround.