... point, there are more users, and their expectations start to differ. So how do you decide which features will, or won t, be implemented? The most common approaches I ve personally seen are: Whether the request comes from paying vs. non-paying users Whether the feature aligns with the product vision (and isn t just fluff) How demanding the feature will be to build How many people are asking for it (size of demand) I worked in technical support ... ... figured other users could benefit. Whether or not I am correct will ultimately be determined by 1. Good marketing (for which I need help ... did I say HELP), and 2. User adoption. There's also a Users "needs vs

... based in Argentina. I've spent my career working as a Product Designer for US-based tech startups. The job is great, pay is good, and I'm greatful for it. But I realized I was becoming a "pixel pusher" for someone else's vision while my own ideas sat in Figma files gathering dust. I always dreamt with having my own business, grow something I came up with.  So that's why 2026 is the year that will ...