Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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,455 Aufrufe • vor 11 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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,284 Aufrufe • vor 1 Monat

I built a clone of the Yeezy store with Next.js. This was a fun challenge — the site has some smooth animations and feels very fast. But it was bothering me that I couldn't use the browser back button. Can we do better? So I rebuilt the site with v0 and Motion. Here's how it works: 1. When you click on a product, Motion is able to animate the original position of the product in the grid, to the zoomed in product detail page. 2. During this transition, we also shallow update the URL with the `/p/slug` route for the page. 3. If you press the back button in the navbar, or use the browser back button, or press escape — all options will take you back to the main product listing page. 4. If you reload the page while looking at a product, or someone sends you a link to a specific product, it still works! This is the best parts of a SPA and MPA mixed together. In the future, I can make this even better with View Transitions (I wasn't able to get the product animation just right, but if you can I'd love to see it!). I also took some creative liberties from the original design. The whole 1/2/3 size thing, where you needed to click the "?" to see SM/MD/LG was strange, so I just went directly to those sizes. Similarly, I prefered the more traditional style sheet/modal with the background color change, versus the full screen takeover. If you wanted to actually hook this up to Shopify now, you can swap the cart implementation with Next.js Commerce, which has all the APIs you need + optimistic writes 🔥 Should I make a video walking through the code?

Lee Robinson

148,725 Aufrufe • vor 1 Jahr