--- title: "Chloe (@smithchloe) | Hashnode" description: "Chloe (@smithchloe) writes on Hashnode. Read their latest articles and follow their work." url: "https://hashnode.com/@smithchloe" --- @smithchloe # Chloe @smithchloe · London, UK · Joined September 2026 ### [Should You Start Your Next React Native App From a Boilerplate?](https://smithchloe.hashnode.dev/should-you-start-your-next-react-native-app-from-a-boilerplate?utm_source=hashnode&utm_medium=feed) Most mobile apps don't fail because of the hard parts. They stall in the first three weeks, spent wiring up auth, navigation, theming, environment config, and a backend before a single user-facing fea 5 min read · [smithchloe.hashnode.dev](https://smithchloe.hashnode.dev/should-you-start-your-next-react-native-app-from-a-boilerplate?utm_source=hashnode&utm_medium=feed) [Oct 15](https://hashnode.com/posts/should-you-start-your-next-react-native-app-from-a-boilerplate/6ad096a40c32058e7e508cd2) ### [Mobile App Retention: Why 77% of Users Churn in 3 Days (And How to Fix It)](https://smithchloe.hashnode.dev/mobile-app-retention-why-77-of-users-churn-in-3-days-and-how-to-fix-it?utm_source=hashnode&utm_medium=feed) You spent six months building the app. You spent $4 per install acquiring users. Three days later, 77 of every 100 of them never open it again. This is not a worst-case scenario. It is the median outc 15 min read · [smithchloe.hashnode.dev](https://smithchloe.hashnode.dev/mobile-app-retention-why-77-of-users-churn-in-3-days-and-how-to-fix-it?utm_source=hashnode&utm_medium=feed) [1](https://hashnode.com/posts/mobile-app-retention-why-77-of-users-churn-in-3-days-and-how-to-fix-it/6acf464b6e6370184925d52a) [Oct 14](https://hashnode.com/posts/mobile-app-retention-why-77-of-users-churn-in-3-days-and-how-to-fix-it/6acf464b6e6370184925d52a) ### [Deploy a Supabase-Compatible Backend as a Single 58 MB Binary with Tinbase](https://smithchloe.hashnode.dev/deploy-a-supabase-compatible-backend-as-a-single-58-mb-binary-with-tinbase?utm_source=hashnode&utm_medium=feed) Running Supabase locally means pulling down a 12-container Docker stack that takes up over 2 GB on disk. That's fine on a powerful laptop. It's painful on a $5 VPS, a CI runner, a preview environment 6 min read · [smithchloe.hashnode.dev](https://smithchloe.hashnode.dev/deploy-a-supabase-compatible-backend-as-a-single-58-mb-binary-with-tinbase?utm_source=hashnode&utm_medium=feed) [Oct 13](https://hashnode.com/posts/deploy-a-supabase-compatible-backend-as-a-single-58-mb-binary-with-tinbase/6acdf9c4f0a7ef3d7dc9a235) ### [React Native New Architecture in 2026: What Developers Need to Know](https://smithchloe.hashnode.dev/react-native-new-architecture-in-2026-what-developers-need-to-know?utm_source=hashnode&utm_medium=feed) For eight years, every React Native app in the world shipped the same compromise: a JavaScript bridge that serialized every call between your JS code and the native platform as JSON, then shipped it a 14 min read · [smithchloe.hashnode.dev](https://smithchloe.hashnode.dev/react-native-new-architecture-in-2026-what-developers-need-to-know?utm_source=hashnode&utm_medium=feed) [Oct 12](https://hashnode.com/posts/react-native-new-architecture-in-2026-what-developers-need-to-know/6acc8b48b829361a646ab92e) ### [How to Build a Video Calling App with React Native and WebRTC](https://smithchloe.hashnode.dev/how-to-build-a-video-calling-app-with-react-native-and-webrtc?utm_source=hashnode&utm_medium=feed) A FaceTime-quality call looks like one feature. Underneath, it is five systems that have to work in perfect sequence: camera capture, codec negotiation, NAT traversal, a signaling channel, and connect 15 min read · [smithchloe.hashnode.dev](https://smithchloe.hashnode.dev/how-to-build-a-video-calling-app-with-react-native-and-webrtc?utm_source=hashnode&utm_medium=feed) [Oct 9](https://hashnode.com/posts/how-to-build-a-video-calling-app-with-react-native-and-webrtc/6ac89643092d1a25fb44a0c5)