Ankit Pandit

One thing I keep struggling with while building products is figuring out which features are actually worth spending time on.

I sometimes come up with ideas that sound great, but then I wonder whether anyone would really use them. I also don't want to spend days building something that people don't actually need.

I'm trying to get better at understanding user needs before jumping straight into coding.

For those who've built and launched products, how do you usually decide what to work on next? Do you talk to users, look at feedback, or just build your ideas and see what happens?

I ve been trying different tools to find competitors for my product, but most either show irrelevant results or miss similar products entirely.

Curious how other founders approach this. Do you rely on tools, Google searches, or manual research?

I m also wondering if there s a better way to solve this. Would love to hear your thoughts and recommendations.

As a developer, I use a terminal throughout the day. I kept finding parts of the experience I wanted in different terminals, but not the combination I needed for my everyday work. I wanted those pieces in one place, ready when the task called for them.

That idea became xtty a native macOS terminal built around the work I actually do.

The workflow I wanted

• Open the saved SSH hosts I need together.

• Start a second, independent session on the same remote host and return to the same directory, without retracing my steps.

• Arrange sessions in tabs or split panes.

• Send input only to the panes I explicitly choose.

• Transfer files with sz and rz.

• Find the right Claude Code or Codex session when it needs attention.