正在加载视频...

视频加载失败

At Uber a big problem for design teams and engineering teams was design source of truth. No one knew what the app truly looked like, so weekly a bunch of designers would get into a meeting room and check that the engineers correctly implemented the figma designs that they...

95,960 次观看 • 1 个月前 •via X (Twitter)

0 条评论

暂无评论

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

相关视频

Let's talk about agentic product design. Every company has its own design process. What has always worked for me is spending long studio hours with our product team, dissecting things into pieces and putting them back together. In those sessions we look at value, usability, simplicity, aesthetics, behavior, storytelling, generics, and emotional mapping. I've been crafting products this way for as long as I can remember. Product work at Lemonade isn't for the faint of heart. This obsession over every detail is hard work, but I believe it yields better results and builds stronger talent. One of the things I love about our design and product team is how this process became a second nature to them. Feedback is fast, professional, and tension free. But in our latest session, something was different. One of our designers used Figma and Cursor to build a mockup that was so advanced, it was almost ready to be shipped. It was an incredible glimpse into a world where a single designer working on top of modern low code infrastructure will be able to launch production grade experiences for products with millions of customers, and with LoCo, I expect this to become a reality at Lemonade in just a few quarters. But there's a problem to watch out for. An interesting phenomenon I've noticed over the years is that the higher the fidelity of the work being reviewed, the more defensive people become. When someone shows up with something polished, they tend to resist feedback. They've already fallen in love with what they built, and it's hard for them to accept rejection. Radical candor feedback works best at an early stage of the project, before people get attached and feel the need to defend their work. This session was no exception. Because the work was so advanced, the review became binary, and its maker became defensive. Happily, we all caught ourselves in time to acknowledge this new dynamic and started figuring out how to go back to obsessing about every corner radius, shade of white, and word. When reviewing agentically coded designs, we'll try having our designers bring in more than one option, as well as the open Cursor project so we can make changes in real time if needed. We'll see how it goes, and if this is of interest, I'll update what we learn.

Shai Wininger

17,558 次观看 • 6 个月前

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 次观看 • 1 个月前

6 months ago we were dropping a new app every week No one cared We’d randomly get 10k users on an app But they came for the app, not the person The thing is, I don’t care about making a retentive app for one audience I want to be a retentive person ~ for my audience What if I was the app? Not a single Paul Thomas Anderson movie is the same Different subject matter, different genres, so you’d assume different audiences However the same people that went to see his last film, came to see One Battle After Another So the demographic isn't dependent on the subject matter The demographic is just, Paul Thomas Anderson fans The software industry has long told that you need to work on one thing, for the rest of your life That’s not how art works tho, is it? Can you imagine telling Jay Z “Great job on the blueprint, now iterate on that same album for the next decade” The landscape of tech haas been stifling the growth of creators by not allowing them to explore other interests 6 months ago I said no to this "requirement", despite what everyone told me, and continued to drop what I liked every week The second a trend was happening on Tiktok, I had the app out that week Somehow 6 months later, the world is conforming to this ideology Instead of software creators limited to making apps for one audience and one niche, there’s a new world of ephemerality and expression What if instead of optimizing for users, we optimized for fans Making apps that are expressive of your life, your commentary, your heartbreak Garnering an audience that will follow you through each step of your story Each of those steps being its own app Why shoot for daily active users when you can get daily loving fans When fans use your app, it’s not just about resonating with the story, the app places them IN THEIR OWN story Here’s an example You’re a 20 year old girl who’s at UMiami You scroll through Tiktoks in your dorm room about “mogging”, a trend to outshine your friend in a photo You laugh and share videos seeing celebrities mog each other, but that’s the extent of it Then at Danger Testing we make an app called mog or not, where you and your friend can upload a photo and AI tells you who’s mogging Now you’re at the bar with your sorority sisters, playing all night, whether your winning or losing it’s the time of your life cause something is finally about YOU ENOUGH OF WATCHING MOVIES LET’S MAKE YOU THE MOVIE LET’S MAKE YOU THE STAR AN APPSTAR

los (appstar)

14,241 次观看 • 8 个月前