---
title: "George Fean (@gfean) | Hashnode"
description: "Building Bundle Drop. Writing about React Native, OTA updates & mobile release engineering. Read the latest articles by George Fean on Hashnode."
url: "https://hashnode.com/@gfean"
---

@gfean

# George Fean

@gfean · Tbilisi, Georgia · Joined August 2026

Building Bundle Drop. Writing about React Native, OTA updates & mobile release engineering.

### [Why React Native OTA Source Maps Need Their Own Artifact Identity](https://bundledrop.hashnode.dev/react-native-ota-source-maps-artifact-identity?utm_source=hashnode&utm_medium=feed)

Once JavaScript can change without a new native binary, app version alone is no longer enough to select the correct source map. The deployed bundle, uploaded map, and runtime event need to agree on one immutable OTA identity.

8 min read · [bundledrop.hashnode.dev](https://bundledrop.hashnode.dev/react-native-ota-source-maps-artifact-identity?utm_source=hashnode&utm_medium=feed)

[Oct 6](https://hashnode.com/posts/react-native-ota-source-maps-artifact-identity/6ac56376963bcd8b3c8bd5b6)

### [Release Channels vs App Environments in React Native OTA](https://bundledrop.hashnode.dev/release-channels-vs-app-environments-react-native-ota?utm_source=hashnode&utm_medium=feed)

Why release routing, application context, and native compatibility should remain separate concepts—even when all three use names like development, beta, or production.

9 min read · [bundledrop.hashnode.dev](https://bundledrop.hashnode.dev/release-channels-vs-app-environments-react-native-ota?utm_source=hashnode&utm_medium=feed)

[Aug 31](https://hashnode.com/posts/release-channels-vs-app-environments-react-native-ota/6a957539e5081539589a939c)

### [Why React Native Teams Use OTA Updates](https://bundledrop.hashnode.dev/why-react-native-teams-use-ota-updates?utm_source=hashnode&utm_medium=feed)

Why OTA is really a second release path for compatible JavaScript and assets—not a shortcut around native releases.

10 min read · [bundledrop.hashnode.dev](https://bundledrop.hashnode.dev/why-react-native-teams-use-ota-updates?utm_source=hashnode&utm_medium=feed)

[Aug 17](https://hashnode.com/posts/why-react-native-teams-use-ota-updates/6a82dbae534aed10f9e58994)

### [Patch-Size Downloads Without Giving Up Full-Bundle Reliability in React Native OTA](https://bundledrop.hashnode.dev/patch-size-downloads-full-bundle-reliability-react-native-ota?utm_source=hashnode&utm_medium=feed)

Why patches should optimize React Native OTA delivery without becoming a prerequisite for reaching a valid release.

9 min read · [bundledrop.hashnode.dev](https://bundledrop.hashnode.dev/patch-size-downloads-full-bundle-reliability-react-native-ota?utm_source=hashnode&utm_medium=feed)

[Aug 14](https://hashnode.com/posts/patch-size-downloads-full-bundle-reliability-react-native-ota/6a7e69dab918d1f834de7474)

### [What’s Actually Inside Your React Native Bundle?](https://bundledrop.hashnode.dev/whats-inside-your-react-native-bundle?utm_source=hashnode&utm_medium=feed)

How to use a production JavaScript bundle and source map to identify what contributes to bundle size—and compare two builds to explain regressions.

9 min read · [bundledrop.hashnode.dev](https://bundledrop.hashnode.dev/whats-inside-your-react-native-bundle?utm_source=hashnode&utm_medium=feed)

[Aug 10](https://hashnode.com/posts/whats-inside-your-react-native-bundle/6a79aa1d37ab4ee198552007)
