Stefan Morris

Hi Ishaan, I'm a UX designer / developer and I think we could mutually benefit from working with each other. Send me an email on my website if you are interested! https://www.shustudios.com/contact

I would say UI sells more, however UX will have a bigger impact on retention.

Absolutely. Security should be top of mind for anyone creating a product. I've tried to follow best practices, however I'm no security expert so interestingly enough I have a meeting with a friend today to review the security of my product. I actually plan on getting certified for my CMS SaaS. Apart from hardening your application, I think it's also important to be sensitive to personally...

When I am developing code and I run into a dead end or difficult problem to solve, I go have a shower :). It relaxes me and allows me to explore the problem away from the computer, which often puts me into a vicious cycle. Alternatively, I'll call up a friend to talk about the problem. Even if the person is non technical - having to explain it to them in layman's terms often results in an...

I don't track my time because I follow a routine and I have pretty clear goals. That combination gives me a pretty clear view of my progress. I also set milestones, which I am constantly crosschecking. It's ok to miss a milestone but there should be a very clear (unexpected) reason, otherwise I rethink my estimates and approach to my work. I think a lifetracking app would still be useful to...

In my experience, I find people abuse the concept of MVP - especially those in the marketing / sales department. Slapping together a product and shoving it out the door is not a good approach IMO. With that said, you don't want to be trapped in Scope Creep Hell either, but that is pretty easy to avoid if you are disciplined. I consider a Minimal Viable Product to be one that can hold its own...

Coca-Cola dominates the market, yet is not the only game in town. https://en.wikipedia.org/wiki/Category:Cola_brands You'll be fine if you have a product that people like, I think.

Do you know if they are using your product and not providing feedback, or simply not trying it out? If they're simply not trying it out, then I would not conclude that it is a good or bad product - the issue is more about garnering interest. If they are trying it and not providing feedback (and there is no adoption), I think it's a safe assumption that the product is not quite meeting their...

Interesting... that has not been my experience. However, if I'm posting on Stack Overflow, its because I have exhausted every possible avenue.

34 stairs.. from my bedroom, down to my office :)

Products fail for a variety of reasons, but in my opinion, I think the most common reasons are (a) the product was solving a problem that does not exist, or (b) the product was not capable of fulfilling its promise. For (digital) products that fall into the latter category, it often boils down to server uptime, minimizing bugs and/or customer support. People have a very low tolerance for...

I had a website that scraped automotive listings and looked at the year, model, mileage, options and price to determine if it was a good deal (this was before everyone was doing it) I found the whole process of scraping messy and a bit shady (listing sites really wanted to protect their data) so I eventually abandoned it. Data ownership is a very messy subject which I decided to avoid...

I think if you are looking to get an "engineer" designation, then it absolute matters. Otherwise, it depends on how you prefer to learn and how valuable do you think the accreditation is.

Well it depends on your situation: You have a hard deadline... Identify your MVP and what's needed to achieve it. Fix those critical bugs and focus on hitting your deadline. If your project is buggy to the point of not being very usable, then you may want to try to move your deadline back, but remember "perfection" is the enemy of "done". You don't have a deadline... If you have the...

Learning to be a great designer is much harder than learning to be a great developer, so if you can cover the design side, you've conquered the hard part.

Analytics can help - set up reports on your current UI to measure your site, for example: - time spent on pages or navigating pages - setting up funnels and watching their performance - setting up heat maps to see where the user's cursors tend to congregate - etc Now that you have a baseline, you can run the same reports with your new UI to see the differences.

I started my career as a Graphic Designer over 20 years ago and have been in the industry ever since. I'm now considered a UX/UI designer and developer. My advice: - Learn how to draw You'll be surprised how many transferrable skills you will develop by simply becoming adept at illustrating. Learning how to paint will also be a great help. - Immerse yourself To learn the difference between a...

Definitely use an existing payment gateway unless you are looking to become an expert in that field, then building out your own would be recommended but beware of the repercussions of things going wrong. Stripe is really good - I'm currently using it on my project. I tried using Paypal, but their documentation is a complete mess. Using an existing payment gateway pros: - Leveraging tech from...

If the products are differentiated by features, I would employ a naming system similar to let's say Apple's iPhones, or vehicle models. If they were considered completely different products, then I would name them differently (however I think based on your question, the former is more applicable)

Not using all caps for starters ;) I agree the previous posts - start by listening. Also approach conversations as a collaboration - users often have something of value to add even if it does not appear so on the surface.