Adnan
@adnansahinovich
mobile tech lead & security ops • ex native dev • @reactnative community contributor • building app security tool
The #1 reason React Native is winning: @expo closed the gap between web and mobile development
Last year, I asked 100+ candidates the difference between authentication and authorization, and only four got the right answer. These are the most fundamental concepts you need to understand. Don't be the coder only, don't let the AI replace your typing skills #cybersecurity…
Keyframes revolutionized video editing in the 90s, transformed the web in the 2000s, and now in 2025, they’ve arrived in @reactnative. Huge props to @swmansion for Reanimated 4 👏
React Native Reanimated 4 is now stable and ready for production 🐎 Featuring CSS Animations & Transitions, multithreading with React Native Worklets and more.
Every @typescript interview eventually leads to this: What’s the difference between interface and type?
UI frameworks like @react @angular @vuejs are for presentation, not business rules. Keep your logic where it belongs: backend
If people don’t like React, why does @reactnative exist and not AngularNative or VueNative
Had my @expo shirt on while exploring Kotor 🇲🇪 and randomly met a few @reactnative devs - this community is everything
Want to get hacked the easy way? Just drop your @stripe keys in @expo .env files and ship it. One adb pull and they’re gone. Your app’s a public repo. Treat it like one.
99% of the keys ever added are prefixed with PUBLIC because @expo doesn’t expose unprefixed env vars to the JS runtime and it's an “easy” fix to add prefix for most devs
API keys in the .env are never exposed to the client unless prefixed with EXPO_PUBLIC_. Use API routes and server functions to securely interact with environment variables in Expo.