正在加载视频...

视频加载失败

Everyone's sleeping on image-to-3D AI models. They can make your app look incredibly unique, with just a little effort. Here's how. This is my calorie tracker, built in a week with nothing but prompting. Just Claude Code + a couple APIs. The visuals are all AI-generated. I'll be sharing...

19,931 次观看 • 2 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Wonderland: Navigating 3D Scenes from a Single Image Contributions: • First, we introduce a representation for controllable 3D generation by leveraging the generative priors from camera-guided video diffusion models. Unlike image models, video diffusion models are trained on extensive video datasets. This enables them to capture comprehensive spatial relationships within scenes across multiple views and embed a form of "3D awareness" in their latent space, which allows us to maintain 3D consistency in novel view synthesis. • Second, to achieve controllable novel view generation, we empower video models with precise control over specified camera motions. We introduce a novel dual-branch conditioning mechanism that effectively incorporates desired diverse camera trajectories into the video diffusion model. This enables expansion of a single image into a multi-view consistent capture of a 3D scene with precise pose control. • Third, to achieve efficient 3D reconstruction, we directly transform video latents into 3DGS. We propose a novel latent-based large reconstruction model (LaLRM) that lifts video latents to 3D in a feed-forward manner. With this design, during inference, our model directly predicts 3DGS from a single input image, effectively aligning the generation and reconstruction tasks—and bridging image space and 3D space—through the video latent space. Compared with reconstructing scenes from images, the video latent space offers a 256× spatial-temporal reduction while retaining essential and consistent 3D structural details. Such a high degree of compression is crucial, as it allows the LaLRM to handle a wider range of 3D scenes within the reconstruction framework, with the same memory constraints.

MrNeRF

52,849 次观看 • 1 年前

I learned this the hard way: do NOT use SwiftUI if you want your app to look and feel amazing. At least when coding with AI. (sorry, Apple colleagues reading this 😅) I'm sharing my process vibe coding this calorie tracker. I get a lot of questions about the fluid transition in the video. Here's the whole story. Initially, Claude built the grid with SwiftUI. It was quick and easy, and looked good! But the transition to the day view was a boring navigation push/pop. No fun. I wanted something custom. I asked Claude to make it a fluid transition that remaps the food tiles from their source to destination positions. All hell broke loose. Claude tried a bunch of horrible things. Initially it used matched geometry effects, which worked OK but didn't lend themselves well to gesture-driven animations. So it resorted to SwiftUI preference keys + geometry readers to figure out the source and destination positions and calculate the interpolated position based on gesture progress, coordinating across grid and day views. But this meant it had to write a custom layout because it couldn't reposition tiles inside the native SwiftUI grid. And it had to do an awkward handoff between views, which always created ugly pops or jumps. And don't get me started on trying to put it on a bouncy spring, that only made the math 10x buggier. Fortunately, Claude Fable was smart enough to see that this was becoming a disaster (and discover most of the issues itself, in the simulator), so it pivoted away from SwiftUI. Opus might not be so wise, so you'll have to pay attention and intervene. Ultimately, it rewrote it in plain UIKit and everything turned out great. After that, we moved from 2D images to 3D assets, which introduced a new set of performance challenges and yet another rewrite to a single Metal layer, which is what you see below. I can write more about the 2D-to-3D saga if anyone's interested. If I were to do it again, I'd just say "Don't use SwiftUI" from the very first prompt, and save a few hours of headaches. SwiftUI can be amazing for a human iterating directly in code. But agents don't benefit from any of its advantages. Plus, agents have seen decades of UIKit training data, so they're great at writing it, and it's far more flexible. Here's hoping we see more agent-friendly iterations of SwiftUI in the future. Till then, I'm probably going to avoid it.

Anshu

114,381 次观看 • 2 个月前