Loading video...

Video Failed to Load

Go Home

SplitPaneKit This is something I've wanted to componentize for a while. We've seen this pattern appear in a few apps now, I even use it at Abode. It has a couple "gotcha" moments with performance and optimisation while animating separate or child views with the drag and translation of...

23,654 views • 1 year ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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

116,615 views • 4 months ago

I just launched a brand new channel with an INSANE strategy. I'm calling it the Launch Loop. I've been working on this channel for over a year, and took the actually massive risk to hold off on posting until I had all 5 launch videos ready. Each idea was carefully selected for this strategy, and each one was carefully written to execute it. I view this channel launch, and these videos, not as individual videos but as a season of a new show. The plan was this: come up with video ideas that fit together, and write the end of each video to smoothly blend into the next. I treated the conclusion of each video as if it was the intro of the next video, so that if people enjoyed what I made and wanted to see more, they could click the next video on the End Card This was inspired by work I've done in the past: a few years ago on my YouTube strategy channel, I posted a video about Ryan Trahan's thumbnail strategy which has gotten over 2M lifetime views. But at the end of that video, I carefully wrote a transition showing video my comprehensive breakdown of 21 thumbnail formats. The End Screen video CTR on that video is 29.4% 🤯. I'm convinced that some of those 2M views must have come from the success of that end screen. I've come to believe that it's really important to bring in an audience to your CHANNEL, not just one video. That was a mistake I made in another channel I worked on before! Getting virality on individual videos, but not keeping viewers for the long term or growing an actualy community. So I thought, what if I launched a channel where every video pointed to the next, in a loop? Maybe there will be a flywheel where success on one brings success on the next, and the next, and the next... But for this plan to work the videos I made have to actually be good 😅

Tyler Fleischman ⏸️

75,616 views • 27 days ago

I’m a human 3D artist. My Attack on Titan fan-made short film is a project I started in 2022 and released in June 2024. I redesigned all of the Titans myself. I didn’t use any AI, and I never made any money from this short film. To be honest, I originally didn’t want to talk about this. In order to discuss it, I actually had to subscribe to X Premium. Throughout 2025 and 2026, I started seeing more and more comments like this on my YouTube channel: “Your one and a half years of work? I can make that with AI in 30 seconds.” “I can do it in one minute.” “I can do it in 90 seconds.” So I started looking into it. The first AI short film I found was actually made by modifying footage from my original film, while being presented as an AI-generated work. I felt pretty disappointed. If you think AI can make something better than what I made, then please create something better from scratch. I’ve always found it difficult to accept being mocked while my work is also being taken and reused. Since 2018, I’ve been focused on creating the things I genuinely love. I’ve done it simply because I love creating, and I’ve never made a single cent from these works. As a result, my financial situation has actually been quite difficult. For a while, I was really struggling with the thought that maybe I should have spent the past few years trying to make as much money as possible. Was trying to make a living by creating the things I love just a foolish fantasy? Then I watch Orb: On the Movements of the Earth. There’s one line in the series that really stayed with me: “Being wrong doesn’t mean it was meaningless.” So recently, I’ve slowly started to accept something. If I don’t make the things I love, I don’t think I would be happy even if I had a job. I’ll keep looking for a way forward. Whether that means working harder, finding ways to make money so I can continue making short films, or finding some other way, I still want to keep creating the things I love.

XieBoli

424,819 views • 24 days ago

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

elvis

18,374 views • 5 months ago