@5harath the current generation of (successful) founders is quite good at understanding the importance of design. It's way better now than when I first started working in tech but there is still progress to make. There are so many startups selling the same thing, similar features, same services, with similar pricing... Potential customers don't care how nice your code is. They rarely care how many new features you've launched last quarter. They choose to use a product because it looks clean and safe. Because the experience is pleasant. Because the branding looks reassuring. Because the startup listens to their needs and designs features they need. All of this is design: visual design, user experience, branding, product/feature design. We've moved from design being "a coat of paint" to "design can make my startup stands out" I hope more founders will think "design is the key differentiator between us and our competitors"

@chrismessina We've recently hired new people and built a team dedicated to mobile apps. What I can tell you is that they started working on the apps and are rebuilding them from scratch to create native experiences on iOS and Android. @ahiggz herself is leading product for the mobile experience! I don't want to speak for her or the team and share a timeframe but things seem to be moving fast and they just got started ⚡️

@ahiggz @syswarren sweet! Need a beta tester? 😉

@ryangilbert On Mondays, my cat wakes me up long before my alarm goes off. Then I get ready, workout or go for a walk, buy food for lunch, go back home, clean things a bit, and go to my desk to start working. In the morning, I try to answer questions and ensure I'm not blocking anyone's progress on a project. Then, if I have time, I'll do design work before taking a break for lunch. In the afternoon, I'll either do design work or be in meetings. Then suddenly, it's Friday. ⚡️

@ryangilbert @syswarren I like how quickly its Friday!

@kylerjphillips I see prioritization a bit like when you're building a LEGO. If you know what you want your LEGO (product) to be like at the end, you can prioritize which blocks (features) you have to put first... otherwise, the other pieces will float in the middle of nowhere. It's difficult to decide what needs to be done first if you don't understand where you're going. Does that make sense? As for measuring success, it really depends on the feature. Sometimes, success is not moving any metrics but laying the foundations that will help build faster in the future, or just making users happy.

@jjassal Done is when we've solved the initial problem and the design is usable. This is why it's important to define the scope at the start of a project. Things can always get better, but blocking the launch of a new feature because it's not "perfect" yet, especially in web and software, where we can push updates regularly, isn't the best strategy. I hope it helps!

@alecdewitz My favorite part is "being in the zone" when you're going with the flow, and things come naturally, and it's exciting and moving fast. For me, the draining/challenging one is the wait between having an idea and having the time and resources to work on it.

@jmsuth My work is very varied, so I can use many different tools depending on what I’m working on. I’ve tried to list my main tools here 👇 User research: Dovetail for qualitative research  Zoom to talk to people Typeform for large surveys  Invision to share designs and collect feedback from the community   UX/UI/IxD design: Sketch Framer primarily to prototype mobile experiences  Whimsical for early collaboration on wireframes and user flows  Communication and collaboration: Notion this is where I take notes  Pitch to formally present ideas  Loom to present designs and ideas asynchronously  Slack for gifs mainly (and to talk with my team)  Asana to follow projects and work together  Testing and tracking: Stark to test designs for accessibility Koa11y to test live pages' accessibility  Hotjar occasionally to test how people use features  I'm not listing analytics tools like GA, Looker, or Periscope because although I use data, I do not set these up. As a team, we certainly use more than this, but these are the tools I use personally.

@jmsuth @syswarren Do you use anything to manage user feedback? I've recently been questioning the value of the platform I use and think I would be better off going back to something a little more analog. I currently use ProductBoard if that helps clarify what I'm asking.

@jmsuth @aaron_chiandet To me ProductBoard "customer feedback" feature is primarily used to manage feature requests, which is a bit different from user feedback. We've been using Dovetail for research — outside of unprompted feedback — but it's possible to manually add feedback there. But really, you could simply use a Google doc, or Airtable to list feedback and tag them.

@jonathanm It's funny because it's usually the most random design decisions that have the biggest impact. You change a small thing, and suddenly, it impacts the whole system. This happened a few years ago with the upvote buttons on Product Hunt. We simply moved the upvote button, and people started upvoting 20% more. It's important because upvotes highlight good products to visitors, which impacts returning visitors, page views… and traffic sent to the product's website, and potential new users for them, which encourages Makers to keep working on their product and launch new things... I am mostly proud of the decisions where the effort was minimal and the impact significant.

@griveau Probably the 2L of Diet Coke I drink every day. I've a ton of side projects ideas, I just need to find the time to work on them 😅

@jackbingham While I really enjoyed UI work earlier in my career, the most exciting for me now is uncovering opportunities. I love connecting the dots between user needs, product possibilities, and business opportunities. I also enjoy getting others motivated to work on a project. I see a lot of products launch every day, and that's an inspiration, but sometimes, I just need to take a step back, go for a walk, watch a movie or read a book to find inspiration.

@sylvainramousse In most cases, you'll only receive unprompted feedback from users who are either unhappy users or power users. Unhappy users have issues and bugs to fix. You solve the problem, and everyone is happy. On the other hand, power users can lead you in a direction you think is correct, but they use the product in a way that's very different from how 99% of people use it. Power users can be the most active users of your product. Or people with industry knowledge. Or anyone who has the power to lead you in a specific direction. One single user's feedback shouldn't change how you think about your product. However, if it does, you should talk to more users and do more research before changing your product strategy. Occasionally though, we receive feedback from people saying they landed their first job, or they were inspired to build their own product, or they found their co-founder on Product Hunt, or that something negative happened to them... and it's always a good reminder that we're not just building products, we're directly impacting people's lives and the decisions we make have to be thought through.

@heffendi UI and UX are two different things that can't be used interchangeably but should be used together. UI is the road, the traffic signs, and scenery: are the signs clear? Can you read what's on them? Is the road smooth? Is it adapted to your car? Is the scenery pleasant? UX is the journey: Is it taking you where you want to go? Do you feel safe, calm, happy? Do you have the information you need to reach your destination? Or are you being stopped all the time?

@oli_vbc Noted!