Randall Luc

[Randall Luc @LucRandall71]

I have published an article that explains how you can update the versions of your Android and iOS applications using @expo with just one command 🎉.

https://t.co/2Q0FXhbtKM

[nishan (o^▽^o) @nishanbende]

Jamie just announced expo-desktop. Build macOS and Windows desktop app with expo!

https://t.co/5JLEOSpkEJ

[Rucha @_ruchiii]

React native >>>>>>>> Flutter

[DROID @droidbuilds]

Claude Code: “Usage limit reached. Resets in 6 hours.”

Me 0.2 seconds later 💀

[Peter Piekarczyk (🥧🚗🐥) @peterpme]

Do you think we can get every react native dev in the world to like this?

[Seb ⚛️ ThisWeekInReact.com @sebastienlorber]

Happy Birthday, React Native 🎂

[NZ ☄️ @CodeByNZ]

The longer you spend in tech, the stronger the urge to buy a farm and never touch a computer in your life again.

[Evan Bacon 🥓 @Baconbrix]

Nothing’s official agentic app platform is powered by React Native.

Expo/React Native have quickly become the de-facto solution for generating mobile apps with AI, and now platforms are adopting it directly.

Always bet on React.

[CG @cgtwts]

engineers worst nightmare has come true, they all have to become product managers

[render @infinterenders]

react fiber is honestly one of those things that people think they get until they actually look under the hood and then suddenly the whole thing feels like some alien technology living inside javascript. everyone parrots those same shallow lines like “fiber is the new diffing engine” or “fiber is concurrent rendering” and it’s just… no man, it’s so much deeper and way more deranged than that. the old react, the stack one, was like this innocent recursive tree walker that just kept diving into components like some happy kid climbing down a ladder, except that ladder was welded directly to the javascript engine’s callstack, so once you’re halfway down you can’t stop, you can’t turn around, you can’t take a break, you can’t do shit except finish it. so if you had big trees, like some giant UI with thousands of nodes, react would just lock the entire main thread and choke the browser until it was done. you typed into an input? too bad, the browser can’t react because react is too busy react-ing. it was legit painful. and the browser’s like “pls, bro, i need to paint” and react’s like “nah bro, i’m in the middle of rendering this dumb component”.

so the react team basically looked at that mess around 2016 and realized the entire approach was screwed. like no amount of small optimizations could fix the fact that recursion is not interruptible in JS. the JS engine owns the stack, not you. and if you can’t pause, you can’t avoid jank, it’s just physics. so instead of fighting it, react just said screw the whole model and built their own stack. not metaphorically, literally. that’s what fiber is. it’s not some “algo”, it’s an entire fake callstack implemented as a linked structure of nodes. each fiber is like a tiny memory cell react controls completely, storing the component type, props, state, the children pointer, sibling pointer, parent pointer, priority info, effects flags, and all this other internal stuff. it’s like react turned every component into a little OS task.

and the crazy part is that because it’s all controlled manually, react finally got freedom from the JS callstack. instead of recursive rendering, it’s this iterative stepping through fibers one by one. and that suddenly means react can pause. like just literally stop mid render, drop everything, let the browser repaint, handle input, chill, take a breath, then pick up exactly where it left off inside that huge UI tree. no more “oh no i’m stuck deep in recursion”. you can’t get stuck because react isn’t using the builtin stack anymore. it’s rolling its own.

this is where the whole scheduling thing comes from. people think scheduling is some abstract idea but it’s literally react walking the fiber graph and deciding which updates matter more. typing is urgent. animations are medium. background data fetching is low. old react treated everything the same and that's why old apps felt like garbage when doing heavy work. fiber changed that whole world. suddenly react could say “yo, someone typed into an input, drop the low-priority render, resume later.” and the app stays smooth even if you have 50k components.

and because fiber creates this double-tree thing, the current tree and the work-in-progress tree, react can run through the whole render phase in like a simulation mode. this is the wild part most ppl dont realize: when react is “rendering”, it’s not touching the dom at all. it's building this offscreen imaginary version of what the UI should look like. and only when the whole thing is done, consistent, no half-finished nodes, react switches to the commit phase and actually mutates the real DOM. like how game engines draw everything in a hidden buffer then flip it. that’s why the UI never shows broken half-updated states. fiber gives react the room to compute the perfect frame before actually showing it.

and dude, this is exactly why suspense works. why transitions feel smooth. why server components can be streamed in and stitched into the client ig

[Catalin Miron - keyframer.dev @mironcatalin]

Running at 60fps

[Bun @bunjavascript]

@thdxr @jarredsumner

[Jamie Birch @birch_js]

Announcing my new personal docs site, Birchdocs! 🍾

Here I'm sharing everything I've learned over 10 years as a software engineer.

I plan to cover React Native, Expo, web dev, Node.js dev, native platforms, and more. And all advanced topics, not shallow stuff. Link below!

[Tzvetan Mikov @tmikov]

Introducing proof of concept React Imgui! The name is a joke, but it is accurate enough.

In the last few days I have been working on a prototype of React driving Dear ImGui using Static Hermes.

The result is a fully native app written almost entirely in JavaScript, using unmodified React, typed JS, plus a very small amount of glue C++ code and unmodified Dear ImGui and Sokol.

The actual renderer translating React into Dear ImGui is written entirely in typed JS using zero-cost FFI.

Of course this wouldn't be possible without React's great design and flexibility. I find it really fascinating that I was able to take literally unmodified React, write a little extra JS, and get a functional fully native app so quickly.

Of course everything is unoptimized, and prototype code quality, and who knows how buggy, but it seems to work well enough.

Please, watch the video to see it in action.

If there is interest, I will write a more detailed article.

[Meta Open Source @MetaOpenSource]

🚀 Big news! Today marks the formation of the React Foundation — a new home for React, React Native, JSX, and the broader React ecosystem.

Let’s celebrate a new chapter for React and the open web!

🔗 Read more: https://t.co/GV2n6A4VXr

#React #OpenSource #WebDev #ReactNative

[Amazon Developer @AmazonAppDev]

Meet Vega OS and Vega Developer Tools!

Starting with our Fire TV 4K Stick Select, Vega OS will power all future SMPs.

Vega Developer Tools features:
🔧 React Native framework
🌐 Web app support
📚 Comprehensive documentation

Read the blog to learn more➡️ https://t.co/YlckKOfwOi

[Programmer Humor @PR0GRAMMERHUM0R]

everyDevelopersDream https://t.co/wCvDi1PVZC

[Jamie Birch @birch_js]

After 6+ years of failed experiments, it's finally working. Direct native API access from JS in React Native 🥹

Access the full iOS SDK – like a native dev.
Cross threads – like a native dev.

Today, my brother in JavaScript, you are a native dev.

[Randall Luc @LucRandall71]

🫶

[Beto @betomoedano]

🎉 Thank you, everyone!

With your contributions to @expo SDK 54, this release brings us a step closer to a true native feel and platform expectations. Can’t wait for SDK 55, Jetpack Compose Beta, and more in the future :)

[Randall Luc @LucRandall71]

@LLCoolChris_ @_smontlouis C’est le cas depuis un moment déjà