ahmed_sulajman

Not as much for the UX, but at least for UI when you need to implement designs, I use Claude Code with Figma MCP and Chrome Dev tools MCP. So that it can take screenshots and compare to expected design as part of the acceptance criteria.

For a more targeted fine tuning of the UI I also started using Agentation https://github.com/benjitaylor/agentation if I'm working on React-based app

Thank you! Yeah I tried Zen a while ago. It was generally awesome and I saw they invested a lot in the experience lately. Need to give it another try for sure If only it wasn't Firefox-based, that would have been perfect :)

Right now Always on Top options can be enabled only when you're not in the "attachment mode". Because when the app is attached to browser window it shows the sidebar only when it becomes active. I'll see if I can find some solution

As for importing from other browsers, this is definitely on my list (at least Chrome and Firefox). I just did Arc first because that's where I wanted to migrate from

Nice! Thank you! Let me know what you think

It's quite an early version, but I've been using it for the last few days and it's really nice to have bookmarks so close to the browser

For sure! I briefly looked into integrating more with browsers, for example, to better what's currently opened in different windows. But so far the only way I found was to rely heavily on macOS accessibility API to get some bi-directional data flow between the browser and the external app.

Or alternatively try to do this kind of integration via a browser extension. I know Raycast is doing something similar with their browser extension, when the extension acts as a proxy between the app and the browser to deliver different context to the app

Thank you! I have similar issues with bookmark managers overall. When they are too far from where I use them, it turns into a list of links I never read

In Arc, I'd organize links in dedicated workspaces for each project (personal or work). So whenever I work on a specific project, I'd open that workspace and have all the necessary links right there. For example, I tend to check Product Hunt often, and I have a dedicated workspace where I'd store products organized by my personal use cases. So next time I'm looking for a tool for something, I'd just open that workspace and search

For some reason, when building a product for a 2nd platform, reaching feature parity is agreed to be a good milestone. At first, it might seem like a great idea because you provide a universal experience. But what if people don't need that?

On top of people's circumstances, you should also know the business goal. What are the business expectations for the product on a new platform?

For example: 1. Driver – increase the product's usage and expand the audience 2. Accessory – enhance the existing experience for users on another platform 3. Utility – a part of the core experience.

Building in Public movement brought a lot of valuable insights for indie makers. But the term itself doesn't really convey the nature of how products being build.

Real-time chat (aka Slack) doesn't always work well for teams because they expect people to ask other team members for the information they need. The opposite of this model would be the passive consumption of relevant information.

Wow! Looks like an awesome opportunity for the personal design portfolio site.

Wow, thanks for sharing! This collection helped us a lot. We really hope fellow makers will find it useful as well.

Also, we'd be glad to hear any feedback or thought you, folks, have.