milljez

try again and again and again and again then try again @kaikulabs

[milljez @milljez]

i'm aiming so high i keep forgetting i'm already living my dream

[milljez @milljez]

this is nuts, can't wait to try it

[Margelo @margelo_com]

We just released react-native-runtimes! 🥳
👉 Render React components on separate JS Runtimes
👉 Share state (Zustand) across Runtimes, synced in C++
👉 Dual-Thread-approach for rendering/business logic
We plugged this into MetaMask which made the app start substantially faster:

[milljez @milljez]

@margelo_com looks fresh🧊

[milljez @milljez]

@ChmalSzymon I'd love this. Would love to see benchmarks in a big production app!

[milljez @milljez]

@margelo_com 😍

[milljez @milljez]

@javisantana did this in a project recently, performance skyrocketed and we removed like 5 dependencies

[milljez @milljez]

@Turbo_Szymon been thinking about this for ages, would be a game changer to be able to do that

[milljez @milljez]

@0xaniol 🙏🏽

[milljez @milljez]

actually, people with a brain are earning much more and living in one of the best places on earth

not hating on people who leave for better opportunities, but you can work hard to stand out and get much better salaries (it's not that hard since the average level is not too high, sadly)

[milljez @milljez]

@obnol1 @liuyi0922 bro woke up and chose to spit some facts

[milljez @milljez]

@BoazWith For now I've just tested the old path in emulators. Will be doing much more testing in the upcoming weeks to ensure everything is stable.

[milljez @milljez]

react-native-cover got a huge release for Android🥳

v0.1.3 fixes reliability issues when showing the cover on Android.

The module is starting to look very stable. Will do some monitoring in the next few weeks.

https://t.co/HLyDa4zGqT

[milljez @milljez]

@BoazWith Yep, exactly! Had to gate it by API 30+. Older Androids fall back to the previous path, which works fine, since the snapshot is captured later.

[milljez @milljez]

@BoazWith It was both. There was a race condition, since some devices captured the Recents snapshot faster than the cover was shown. The fix was to use SurfaceControlViewHost.

[aniol @0xaniol]

new app dropping this week

[milljez @milljez]

It’s so hard to get it right. It can’t be achieved in the JS thread by listening to `appState` changes.

On iOS, you have to accept the tradeoff of showing it when state changes to `background`, not `inactive`, since the latter is triggered by biometrics, permissions, etc.

Android is very tricky. You have to listen to home and recent tap events, because the activity stopped event fires too late to update the UI. Activity paused event has the same problem as `inactive` on iOS. Even with this, I still have to polish it, since the home event sometimes fires too late as well (Android things 🙃).

Modals were pretty straightforward.

I’m sure it can be improved a lot, but it’s good enough for a 0.x version.

Feel free to DM for more details or check the code in the repo (critiques welcome).

[milljez @milljez]

Introducing react-native-cover🔒

Stop sensitive data from leaking into the iOS App Switcher and Android Recents.

⚡ Fully native, zero JS overhead
🎨 Solid color, image, or blur
🌗 Light & dark mode
💫 Customizable fade animation

[milljez @milljez]

@asendra_ @obnol1 This was the third time I had to implement this in an app so I finally decided to create a package haha

[milljez @milljez]

Powered by nitro modules⚡

@margelo_com

[milljez @milljez]

https://t.co/UqwnEk5Ssi

[milljez @milljez]

🤩

[Expo @expo]

We just cut the SDK 56 beta 😅

◆ 50%+ faster iOS builds (precompiled XCFrameworks) ◆ 40% faster cold starts on Android
◆ Expo UI is stable
◆ iOS widgets are stable
◆ expo-router rebuilt from scratch
◆ Inline native modules
◆ Brownfield multi-app support

The obvious themes are speed and stability. But there are a lot of other interesting changes (like Expo Router decoupling itself form React Navigation). Get all the nuance and detail in the changelog below ↓