Daniel Solberg (@without_daniel) header
Daniel Solberg (@without_daniel) profile picture

Designer and dad joke connoisseur 🤓

San Francisco Bay Area
Joined May 2020
I was using @Replit for something at work today and noticed an interesting design decision. Each type of agent action has its own icon, and the icon appears every time the agent performs that action, even if that means repeating the same icon over and over within a single response. I’ve attached a few examples from my session. The first time I saw all the duplicates side by side, I thought it was glitching. I’m not sure how much value all the repeats add. They could probably get away with showing just one icon per action type in each response, or even none at all. Just the logo animation they have plus "Thinking..." could be enough without adding the current clutter or confusion, plus all the aforementioned icons are shown in the expandable action history anyway.
49
I was a little iffy at first on how the Claude Code desktop app’s sidebar peeks in on hover, disappears when you move away, and stays pinned once you actually click it. The more I’ve used it, though, the more I’ve come to really like it as an interaction pattern. Claude made fairly quick work of building something similar for a project I’m working on at OpenComp. I still need to get the tooltip delays just right so they don't clash with the sidebar's movement, but I like it so far.
1
151
Love this but have never understood the reasoning behind the alignments pointed to here. The indentation of these elements in particular should align with the left side of the "Product" section title. In the current state it feels like the Issues and Projects icons are floating in an odd in-between.
there should be vertical/horizontal rhythm. Either be left-right positioning, or centering. So first top bar should be aligned or vertically centered with the traffic lights the left side panel should have padding and either left icons aligned or centered then generally you want either round or rectangle buttons or fields. you might mix if there is some special case you can also send apple HIG to your agent to try to follow the rules developer.apple.com/design/h…
7
5
254
27,679
Something I've been experimenting with on a recent project: Using stripped-down, verb-based action phrases as what's visible by default, then progressive disclosure to reveal the actual controls once intent has been shown by toggling on a respective switch.
1
80
Yesterday we launched an overhauled navigation UI at OpenComp, designed entirely by me, and also built entirely by me using Claude Code. Our previous nav bar was a dark marine color (a dark shade of one of our brand colors) that felt heavy, and utilized horizontal nav tabs that felt dated. Having the old nav along the top also took up a lot of valuable vertical real estate, especially for being a SaaS app where maximizing screen real estate is critical. It was long past time for us to move into the future and adopt a collapsible sidebar instead. Now, with the new sidebar implemented, both vertical AND horizontal space can be maximized. I intentionally went with muted colors for the sidebar so that colors throughout the app's main pages can draw users' attention the most. I wanted the navigation to fall back and be there when it's needed rather than competing to be the star of the show. Hierarchy was interesting in the sidebar because the user can access different, what we call "scenarios" (think different copies of the same general environment) in the app, each of which has the same set of nav tabs accessible within them. So each scenario 'encompasses' the navigation, but users aren't changing scenarios very often, so the scenario switcher doesn't need to command a lot of attention. I solved for this by making the scenario switcher sit above the nav tabs and be slightly taller than the nav tabs themselves. These two design decisions give it some dominance in the hierarchy through placement and size while keeping those cues subtle. There's also intentionally no BG color on the selector until it's hovered so it doesn't draw attention or act as a constant visual anchor. Some other things I really like about the new sidebar: • The OC logo and the icons stay in their exact positions between both the expanded and collapsed states. This makes closing and opening the sidebar feel nice in the sense that those elements aren't shifting around while the movement is happening, even while other elements appear and disappear. • Not pictured here, but an 'upgrade' card sits nicely in the lower left corner above the Settings and Need Help buttons for users who are on free accounts or free trials. • With the transitions between the open and closed states, it was my first real foray into transition timing. The scenario selector, Settings, and Need Help buttons all appear smoothly as the sidebar expands (rather than instantly), which was a cool detail to focus in on. I still need a lot of practice with transitions and movement, but I'm glad to have dipped my toes in a little bit. I actually worked on this project 4-5 months ago, but it wasn't released until now for other reasons. It was a huge confidence boost as my first "real project" using Claude Code, and one that has now ended up in our customers' hands. My creativity and productivity have really taken off ever since, and I'm now deep in some even more ambitious OpenComp projects with Claude that I'll share more about soon. To be able to hammer out this new sidebar with no dev support needed outside of the code reviews was so exciting and such a cool feeling. I can't wait to keep building! 🚀
6
1
6
723
Building on yesterday's project, I added another layer of polish inspired by something I saw in @emilkowalski's animations.dev course. Originally, the "Defaults restored" confirmation appeared instantly in the center once the "Restore defaults" button was clicked. It worked and looked fine, but I felt it could be better. Taking a cue from a concept in Emil's course, I had Claude instead keep the confirmation message in the same spot as the button and add a blur during the transition, so the two feel like they morph into one another. Thanks for the idea and guidance, Emil! I think this looks badass.
1
68
It's amazing how Claude Code lets me, a designer with just basic coding knowledge, add polish as I build. Today I was implementing a component for a project at OpenComp that lets users set their own visual preferences for a data table. Once the switches were in place, I started clicking through them myself and noticed that people tend to toggle settings on and off quickly while they figure out what each one does. Having the "Restore defaults" button suddenly appear after every click, then immediately vanish again when a switch was toggled back, felt jolty. So I had Claude add a slight debounce that lets the clicking settle before triggering the button's appearance, and a transition that smoothly slides it in or out. Then I noticed that clicking "Restore defaults" made the button slide away instantly. It felt abrupt, and it didn't give me a satisfying confirmation that the defaults had actually been restored. So I designed a quick success state, intentionally centered and gray to set it apart visually from the button itself, and had Claude display it for a few moments after the click. These are exactly the kinds of small details that would have been easy to overlook, or get lost in translation, before Claude made it possible for me to implement them myself.
1
2
106
BTW we now support multiple accounts in the Claude mobile app
1
51
I snapped this in the Vatican grottoes at Saint Peter’s Basilica. Am I artsy yet? 😄
2
98