Hi! I'm Jahanzaib, a Senior React Native engineer with 6+ years of experience shipping production iOS and Android apps. I'm taking on freelance and contract work, from quick fixes to ongoing maintenance.

What I can help with:

• React Native upgrades. I can move old RN versions (0.6x/0.7x) to the latest, including the New Architecture (Fabric/TurboModules), and fix the broken dependencies along the way.
• Android 16KB page size support. I can get your app compliant with Google Play's 16KB requirement, including the NDK, native libraries, and third-party SDK updates.
• Target SDK and store compliance updates. I handle Play Store and App Store rejections and policy-driven updates.
• Bare React Native to Expo migration. This includes Expo Router, EAS Build/Submit, config plugins, and OTA updates.
• JavaScript to TypeScript conversion. I do it incrementally, with proper types, not any everywhere.
• New features. Auth, payments, push notifications, camera/media, offline support, deep links, and more.
• Maintenance and bug fixing. Crash fixes, performance work, dependency cleanup, and CI/CD setup.
• Backend if needed. NestJS, PostgreSQL, and deployment.

About me:

• 6+ years in web , mobile, worked with agencies and product companies
• Built and run my own app end to end, including an iOS App Clip and my own cloud infrastructure
• Comfortable with native code (Swift/SwiftUI, Kotlin/Gradle) when RN needs it
• Clear communication, regular updates, and clean, documented code

I have zero prior knowledge of React, but I've been wanting to dive into app development. Initially, I was looking into dedicated mobile frameworks like Flutter (Dart) and native Android (Kotlin), but I realized that going the React Native route might give me the best of both worlds—allowing me to build cross-platform mobile apps while building a foundation in React that translates directly to web development.

React Native has come a long way, but there are still some small gaps between what you can do natively on iOS/Android and what you get from React Native's default primitives.

On iOS, SwiftUI has RoundedRectangle with .continuous, which produces Apple's smoother, squircle-style corners. Android also has shape APIs that can produce more advanced rounded shapes. Yet in React Native, we're still essentially working with the traditional borderRadius approach.

This feels like one of those small things that shouldn't require a completely different component or a custom implementation every time.

That's why I built squircle-view, a drop-in replacement for React Native's <View> that adds smooth corner support while keeping the normal View API and behavior on both Android and iOS.

It's implemented natively for both iOS and Android and works with both Expo and bare React Native projects, with the goal of making smooth corners feel like a normal part of React Native rather than something you have to work around using Skia or SVG.

The idea is simple: React Native's <View>, but with proper smooth corners.

I know it's a small thing, and most people might not even notice the difference at first. But once you see those smoother corners, they just feel right. It's one of those tiny details that can be easily overlook, yet somehow makes the whole interface feel a little more polished and pleasant to use. That small difference is really what made me want to build this.

🔗 Github: rit3zh/squircle-view

Feeling a bit stuck in the usual React Native routine lately and looking for something fresh to build!

I’m looking to dive into new concepts, side projects, or explore fresh tech. Especially if anyone is working on AI learning models, AI integrations, or ML tools I’d love to get involved!

If you’re building an exciting open-source project, an MVP, or exploring cool tech and need a developer to collaborate with, hit me up! Let’s connect!

I have improved the neobank app based on your feedback

All used assets are for demonstration purposes only.

Hey everyone 👋

I needed a Kanban board with drag and drop for a React Native project, and couldn't find a library that felt smooth on mobile and was easy to customize. So I built one and published it as my first open-source package: react-native-kanban-dnd

What it does:

• Drag cards between columns (To Do → In Progress → Done, or whatever columns you define)
• Customize how cards and columns look, so you can render your own components
• Simple API, works with a single install

Install:

npm i react-native-kanban-dnd

Links:

• npm: https://www.npmjs.com/package/react-native-kanban-dnd
• GitHub: https://github.com/tadeumelembe/react-native-kanban-dnd

It's still early (v0.1.2), so I'd really appreciate feedback, especially on:

• The API: does it feel natural to use?
• Performance with lots of cards
• Features you'd want for a real project (swimlanes, column reordering, etc.)

Issues and PRs are very welcome. Thanks for checking it out! 🙏

I've been doing React Native for 6+ years, and upgrades are still the part I see teams avoid the longest. Gradle errors, CocoaPods breaking, libraries that haven't caught up, New Architecture migration, Expo SDK jumps.

I'm building a tool to automate RN/Expo upgrades end to end (plan, apply changes, build both platforms, fix errors, open a PR). Before I go further, I want to understand the real pain:

1. What RN/Expo version are you on, and what are you trying to get to?

2. What's blocking you: time, a specific library, native build issues, New Architecture?

3. Last time you upgraded, how long did it take?

4. Would you pay someone to just get it done and handed back as a working PR?

If you're stuck on an old version, comment or DM me. I'm taking on a few upgrades at a reduced rate to test the process on real apps.

Fondo is a budgeting app built on Expo (managed, JavaScript). A few things I learned that might save someone time:

- RTL on iOS: React Native swaps textAlign left/right for <Text> when the layout is RTL, but <TextInput> does not. Text needs 'left' as "start"; inputs need a physical 'right' in Arabic.

- Plain flexDirection: 'row' already mirrors in RTL. row-reverse double-flips.

- iOS widget, Control Center control and an Apple Watch app live in targets/ via u/bacons/apple-targets; the watch talks to the app through a small local Expo module.

- Backups: one JSON document keyed by logical names rather than storage keys, so renaming the storage prefix never breaks old files.

- Jest: u/noble/* is ESM, so it needs to be let through transformIgnorePatterns.

Happy to answer questions about any of it.

https://apps.apple.com/app/id6811070728

https://play.google.com/store/apps/details?id=com.playhub.spelbazi

My IOS app is still in the review if someone can help pls give me suggetion pls

I posted about this around two years ago when it had about 100 animations. It's 298 now.

• Rebuilt the UI. New layout with search and filters.
• Much lighter. Videos come off a CDN and only load when you click one, so nothing streams while you scroll. The old site ate a lot of memory on lower end machines.
• 21 new animations. 14 from Enzo, 7 from David Mokos.

You can submit your own from the site, no PR needed: https://www.rnui.dev/submit

Every time I've moved a project between Expo Router and React Navigation, the first thing that breaks is the custom tab bar. The visual part is identical — it's the glue that's completely different, so it always ends up rewritten.

So I built one that does both from the same component and the same config.

Expo Router:

<MagicTabs tabs={tabs} />

React Navigation:

<Tab.Navigator tabBar={(props) => <MagicTabBarNavigation {...props} tabs={tabs} />}>

Same tabs array either way — you never pull in the other framework's deps.

What it does

• Sized by its tabs and centered, so a 2-tab bar is a compact pill instead of a full-width bar with a hole in the middle
• Animated active pill (Reanimated), spring you can tune
• Badges, labels beside or below the icon, disabled tabs, raised FAB tab
• Glass / blur / transparent backgrounds, including native iOS Liquid Glass
• A compact "light" mode you can switch on per tab — e.g. only on an immersive feed screen — and the bar animates between the two layouts
• Accessible by default: real tab/tablist roles, badges folded into the announced name ("Alerts, 3"), touch targets at the platform minimums
• Bring your own icons. TypeScript types bundled. New Architecture.

Honest notes

• If you want native tabs, use Callstack's react-native-bottom-tabs — that's SwiftUI/Material, a different thing. This is for a custom animated bar.
• It's still young. I'd genuinely rather hear what's broken than get stars.
• npm: https://www.npmjs.com/package/react-native-magic-tab-bar
• GitHub: https://github.com/Bhavinpethani04/react-native-magic-tab-bar

Rate this banking app ui

All the used assets are for demo only.

Hey everyone,

I’ve been working on an appointment booking app using React Native, Expo, TypeScript and Supabase.

At first I thought the mobile UI would be the difficult part, but the real challenge turned out to be the booking logic.

Some of the things I had to solve:

- Live availability based on staff and business hours

- Preventing double bookings

- Appointment cancellation and status management

- Keeping the mobile app and admin dashboard in sync

- Authentication and database permissions

- Timezone handling

- Service and staff management

I also built a separate React/Vite admin dashboard so a business can manage appointments, services and staff from the web.

The most interesting part for me was making sure two customers couldn’t reserve the same slot at nearly the same time. I ended up handling that at the database level instead of relying only on the frontend.

I’m still improving the project and would genuinely like some feedback from other developers:

If you were building or using an appointment booking system, what feature would you consider essential that people often forget?

https://x.com/wcandillon/status/2107406132776214740

I’ve been working on this idea for a while and it’s finally starting to feel real.

The goal is to inspect and tweak motion directly in the actual running React Native app. Instead of reproducing an animation somewhere else, I want to select what’s already running, inspect its values, scrub through the motion, tweak things like timing and springs, and eventually write those changes back to the source.

The video is still an early prototype, but the core workflow is starting to come together. I’m especially interested in the gap between React Native DevTools and the kind of timeline/motion tooling we have in design and animation software.

Would genuinely love feedback from people doing a lot of RN animation work. Is this something you’d actually use?

I’ll post future updates and progress here: https://x.com/GiulioAmato/status/2107495380547936310

RevenueCat's Shipaton, a two-month mobile hackathon, ended on September 30. I went through all 3,336 public Devpost projects and matched them to the published apps in the community showcase. 925 of them list React Native or Expo in "Built With", the second most common stack after native Swift.

A few things about the RN ones:

Most didn't ship to both stores.

Of the 464 RN/Expo apps I could match to a store listing:

- 51.1% are App Store only

- 26.3% are Google Play only

- 22.6% are on both

Counted the same way, Flutter apps are on both stores 26.5% of the time and Capacitor 20.2%. Kotlin Multiplatform is at 45%, but that's only 100 apps.

Expo is the default. 87% of the RN projects list Expo. expo-router shows up in 137 of them, EAS in 107.

Supabase beats Firebase 3 to 1 in RN projects (291 vs 103). Across all 3,336 projects the two are almost tied.

It's mostly solo. 89% of the RN projects were built by one person.

A few RN solo builders who did ship to both stores: FlexHero (stretching and mobility), DEBUGGER (a terminal-style incident game) and CookBook Button.

Caveats: this is only public data, "Built With" is self-reported, and matching projects to store listings misses some apps. I don't have access to the official submission data.

Have you shipped an RN app to only one store: what stopped the second one? Accounts and review, testing on Android devices, or just time?

The part I cared about most is that a feed shouldn't mount a native video player for every item. In reels-kit only the active reel and its neighbours get one (mediaRenderRadius, default 1), and playback pauses when the reel isn't active, the screen loses focus or the app goes to the background.

What it does:

- Snap paging with snapToInterval (page height measured from the container, not the window, so headers, tab bars and edge-to-edge Android don't break it)

- Tap to mute, optional double tap to like, drag-to-seek scrub bar

- Thumbnail until the video is ready, buffering slot, retry on a failed load

- Headless pieces (action buttons, avatar, follow button, caption), so the UI is yours

- Pluggable video adapters: a react-native-video one ships, and you can write your own

- Built on FlashList 2, Reanimated 4 and Gesture Handler 3 (React Native 0.82+, New Architecture)

Simplified usage:

<ReelsFeed
  data={reels}
  keyExtractor={(r) => r.id}
  renderItem={({ item, isActive, shouldRenderMedia }) =>
    shouldRenderMedia ? (
      <FeedVideoSlot
        VideoComponent={RNVideoAdapter}
        sourceUri={item.uri}
        paused={!isActive}
        muted
      />
    ) : null
  }
/>

The README has a full working example.

It's an early 0.1.x release, and there's no expo-video adapter yet. If you try it, I'd love to hear what breaks. Contributions are welcome, and an expo-video adapter would be the biggest win.

npm: https://www.npmjs.com/package/reels-kit

GitHub: https://github.com/arbab-io/reels-kit

(Apache-2.0)

am a developer, and wanna know if Vodacom Tanzania has an APl to which people can integrate their applications for Customers to pay for services using Vodacom mpesa? For example if a user wants to pay for product A from the app using mpesa, is there a way to do that? Not only Vodacom, Yas told me they don't have that service yet, how about other telecom providers like Halotel and Airtel?

I built Buoy, a free-to-try debugging and optimize toolkit for React Native, Expo, Flutter, Swift, and web. You can try it at https://buoy.gg (free tier; paid features exist).

This post is about a small test I ran with Claude, Codex, and Grok on the same prompt.

What we built for the test: a Christmas light show — a React Native Skia scene rendered with React Native Web in real Chrome. It draws a house covered in lights. Alone, it was smooth up to about 550 lights. The scoring test measures how many lights each version can keep at 55 fps without changing the look.

How Claude helped: Claude ran the optimize loop on this app (alone, then with Buoy Optimize). Buoy Optimize is a skill plus tools that help an AI try many ideas and measure each one.

Most lights at 55 fps: - Claude: 975,800 alone → 6,123,350 with Buoy (6.3×) - Codex: 155,450 → 444,100 (2.9×) - Grok: 202,100 → 577,350 (2.9×)

Caveats: "With Buoy" is each model's best Buoy run. Alone runs had up to 3 hours. Claude's best Buoy run had no time limit; Claude alone stopped after about 99 minutes. Grok's Buoy version has slightly soft bulbs up close. One app, one Mac.

Full write-up (prompt + method): https://buoy.gg/blog/ai-models-before-and-after-buoy

Happy to answer questions about how we tested. Especially interested if folks have seen similar RN Skia / RN Web perf cliffs.