Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

A technically interesting challenge when building Pengu was generating transparent images for each user’s unique Pengu. With over 350 clothing items and countless possible combinations, plus varying device sizes, pre-generating images in the cloud quickly became infeasible. To solve this, we moved the computation to the device itself by...

28,696 görüntüleme • 11 ay önce •via X (Twitter)

18 Yorum

dennis profil fotoğrafı
dennis11 ay önce

if you stop sharing these insights i'll 🔫

Fabian Kamberi profil fotoğrafı
Fabian Kamberi11 ay önce

Saturday means Kanye on all speakers at the office

Daehyeon Mun profil fotoğrafı
Daehyeon Mun11 ay önce

Interesting. This is a similar approach I tried for Callie 😸

NicheGuys profil fotoğrafı
NicheGuys11 ay önce

sunday! we are waiting GitHub link =))) <3

Sebastian Penafiel profil fotoğrafı
Sebastian Penafiel11 ay önce

This one was quite the challenge to come up with at the time. 🔥

enes profil fotoğrafı
enes11 ay önce

I 🐧 pengu

Max profil fotoğrafı
Max11 ay önce

Remember it quite well. Was an interesting system design challenge 🔥

Nnaemeka.dev profil fotoğrafı
Nnaemeka.dev11 ay önce

🔥

小贺 profil fotoğrafı
小贺11 ay önce

👏

Trent profil fotoğrafı
Trent11 ay önce

That’s a clever workaround. I had no idea Pengu was even made in Godot

Nico profil fotoğrafı
Nico11 ay önce

Cool name

Zen profil fotoğrafı
Zen11 ay önce

omg @Sidaelle this is how they built pengu!!!!!

Mohamed Rasheq profil fotoğrafı
Mohamed Rasheq11 ay önce

Interesting challenge. 🔥🔥

Alzea | Orenji Studio profil fotoğrafı
Alzea | Orenji Studio11 ay önce

This is cool man 👀

Frozair profil fotoğrafı
Frozair11 ay önce

So this only works for react native? What's the difference when using gdscript and targeting mobile devices?

Parav profil fotoğrafı
Parav11 ay önce

is that similar to how offscreencanvas works on web?

AtheX Web3 profil fotoğrafı
AtheX Web311 ay önce

wen docs?

Jannis Ringwald profil fotoğrafı
Jannis Ringwald11 ay önce

Checkout my latest post

Benzer Videolar

Build uncompromising high-performance, high-fidelity apps with React. What you see is not the Apple Messages app, nor is it meant to be 1:1. Rather it serves as an aspirational and real example of UI/UX that is possible. Every detail from the bubble animations to keyboard gestures to scroll view insets and safe areas to parallax timestamps required care and attention. Quality UIs come from caring hard. The little chat bubble tails that morph away when the next message animates in. Timestamps that scroll at a different rate than the bubbles. Peek gestures powered by UIKit that lift a chat bubble, tail and all, with a gentle haptic pulse. The subtle shadow of the text composer and responsively sliding down the keyboard in pixel-perfect concert. The composer shrinking its width to fit iPhone’s rounded bezel. The beautiful Liquid Glass refractions have the level of glassiness chosen by the user (new in iOS 27). Scroll view insets that adjust to fit the home bar and keyboard dynamically, creating a sense of depth as the chat bubbles are slightly visible as they scroll under the keyboard. Keeping the keyboard on screen if the prior screen already presented it. Sliding the keyboard and composer with the screen when the user drags to navigate back. I am excited to explore using the new iPhone Duo view controllers natively with React when the time comes. There is always room for innovation and improvement. This chat demo runs at 120 FPS on iOS 27 even on my phone that’s four versions old now. There are several approaches to high-performance lists. I explored a new Expo scroll view that uses the native gesture systems along with react-native’s VirtualView (codenamed “Fling” to reflect the speed of flinging a scroll view), which Meta’s React team designed to prioritize scroll momentum with React’s scheduler. There are tradeoffs with other scroll strategies for how the scroll views gracefully degrade, and they can be swapped out based on what’s best for your app’s use case. And, by virtue of using modern React, high-priority events like user gestures can preempt lower-priority ones like a network response. Let us dispel any myth that using React requires compromising on beautiful, smooth, user-friendly UI/UX that Uses the Platform. Let us dispel any myth frame-perfect UI coordination is not achievable. The Hermes thread and the UI thread can coordinate when needed, like for controlled text inputs. Let us dispel any myth that React Native’s performance is impacted by a bridge, let alone has a bridge. Bridgeless JSI and the Fabric renderer are here for apps that use the New Architecture. What about Android? The app runs and I’ll share a screenshot from my cloud agent’s emulator. With some attention to detail dedicated to Android I’m confident crafted UX is attainable. I’ve spent my tokens once and have a structural head start everywhere. One more thing! Most of this chat’s application code is written with , , , and other familiar elements. The styling is mostly CSS, including linear-gradient(), background-attachment: fixed, and semantic platform colors that adapt to dark mode. Not just appearance - CSS Animations and CSS Transitions run entirely natively. There are a handful of custom native components written in Swift and Kotlin, like the chat bubbles and a custom CAShapeLayer and UIBezierPath for the tails. Native coding is a first-class feature. The way to think about building beautiful apps this way is React and Native, not React vs. Native. Aspire high and raise your ambitions for what is possible!

James Ide

141,012 görüntüleme • 1 ay önce