Загрузка видео...

Не удалось загрузить видео

На главную

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 просмотров • 11 месяцев назад •via X (Twitter)

Комментарии: 18

Фото профиля dennis
dennis11 месяцев назад

if you stop sharing these insights i'll 🔫

Фото профиля Fabian Kamberi
Fabian Kamberi11 месяцев назад

Saturday means Kanye on all speakers at the office

Фото профиля Daehyeon Mun
Daehyeon Mun11 месяцев назад

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

Фото профиля NicheGuys
NicheGuys11 месяцев назад

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

Фото профиля Sebastian Penafiel
Sebastian Penafiel11 месяцев назад

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

Фото профиля enes
enes11 месяцев назад

I 🐧 pengu

Фото профиля Max
Max11 месяцев назад

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

Фото профиля Nnaemeka.dev
Nnaemeka.dev11 месяцев назад

🔥

Фото профиля 小贺
小贺11 месяцев назад

👏

Фото профиля Trent
Trent11 месяцев назад

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

Фото профиля Nico
Nico11 месяцев назад

Cool name

Фото профиля Zen
Zen11 месяцев назад

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

Фото профиля Mohamed Rasheq
Mohamed Rasheq11 месяцев назад

Interesting challenge. 🔥🔥

Фото профиля Alzea | Orenji Studio
Alzea | Orenji Studio11 месяцев назад

This is cool man 👀

Фото профиля Frozair
Frozair11 месяцев назад

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

Фото профиля Parav
Parav11 месяцев назад

is that similar to how offscreencanvas works on web?

Фото профиля AtheX Web3
AtheX Web311 месяцев назад

wen docs?

Фото профиля Jannis Ringwald
Jannis Ringwald11 месяцев назад

Checkout my latest post

Похожие видео

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 просмотров • 1 месяц назад

AG-UI makes building agentic applications dramatically easier. Here's how it works. This is a model for a simple chatbot: User → LLM → Response But interactive agents that render UI, pause for approvals, and ask users for input need a much more complex model. When building these agents, a response from the LLM will include a series of state changes as the agent runs: • Agent started a task • Agent called a tool • Agent updated its state • Agent streams these tokens • Agent is waiting on a human • Agent is resuming the task The Agent-User Interaction Protocol (AG-UI) treats the LLM response as a stream of events rather than a text endpoint. In practice, here is what you get as an agent runs: 1. Lifecycle events so your UI knows where the agent is. 2. Text messages that stream tokens. 3. Tool calls so your UI can prefill a form with any required arguments. 4. State updates that keep your UI in sync with the agent. 5. Special events for human approvals, rich media, and custom needs. All of these events travel over standard transports (SSE, WebSockets, or plain HTTP) as JSON. As a result, you can build a frontend that stays in sync with the agent's progress without having to invent a custom process to make this happen. For example, building a human-in-the-loop workflow becomes an off-the-shelf component you can integrate rather than build from scratch. CopilotKit🪁 is the creator of AG-UI, and you can use it when building frontend applications pretty much anywhere: • React • Angular • Vue • React Native • Slack • Teams • Discord • WhatsApp • Telegram Here is the link for you to check it out: Thanks to the CopilotKit team for partnering with me on this post.

Santiago

17,438 просмотров • 3 месяцев назад