Muhammad Jahanzaib's profile on Product Hunt

About

Enthusiastic and detail-oriented Full Stack Web Developer with expertise in building responsive, user-friendly applications using React.js for the frontend and PHP Laravel for the backend. Skilled in designing modern, intuitive interfaces with Tailwind CSS and Figma, while leveraging Mockoon and Postman for efficient API development, testing, and collaboration. Proficient in modern workflows with Jira and GitLab, ensuring smooth project management and version control. Recognized for strong communication skills, teamwork, and adaptability, with a passion for creating seamless user experiences, writing clean and efficient code, and contributing effectively within agile, cross-functional teams to deliver high-quality results.

Badges

Tastemaker

Gone streaking

Forums

•

11h ago

Do you actually publish a public roadmap, or just hope users don't hold you to timelines?

Been thinking about this a lot lately. Every time we plan the next quarter, there s an internal debate: do we put our feature plans out in the open, or keep them internal until code actually hits production?

Do you think early-stage products need a public roadmap even a simple Trello board? Or does that only backfire the moment priorities shift and a promised feature gets delayed?

Should it live on a public page like Canny or Notion? Be sent out in monthly newsletters? Or is sharing upcoming plans just setting yourself up for unnecessary pressure?

In our case, we ve started realizing that being brutally honest about why something got delayed actually builds more trust than making shiny timeline promises.

•

7d ago

Do users open fewer support tickets when you focus on action results instead of UI guidance?

Spent a month adding tooltips and progress bars to smooth out our onboarding but support messages actually went up.

Turns out people weren't confused about where to click. They were just scared of accidentally sending emails or deleting client data without knowing what would happen next.

Once we changed the UI text to clearly explain the final result of each button click support requests dropped by half.

Has anyone else noticed that reassuring users about outcomes matters more than guiding their clicks?

•

28d ago

What can your AI agent do without asking you first?

An agent can have permission to use a tool without having enough context to make the business decision behind it. That's the boundary I'd want to define before giving it write access.

For me, drafting a customer email and sending it are separate permissions. Recommending a budget change and applying it are separate decisions. The useful question is what the agent can commit you to, and who carries the consequence if it gets that wrong.

I'd define the allowed action, the affected people or systems, the spending limit where relevant, and the point at which a named person must approve. I'd also want that person to see what will change before agreeing.

Rollback helps, but it doesn't erase every consequence. You can restore a price after someone has bought at it. You can correct an email after someone has acted on it. Neither returns you neatly to the starting position.