Tithi Mondal

20 questions

Startups: questions answered

Direct answers from Tithi Mondal, UI/UX Designer in West Bengal, India. Each one is taken from a longer guide, linked below the answer. See all startups guides.

How many features should an MVP have?

There is no fixed number. Keep only the features needed for one user to finish one important task. Many first versions have 4 to 8 core screens.

From: MVP Design: What to Build First in Your Startup App

Is an MVP the same as a prototype?

No. A prototype is a clickable model used to test an idea, and it has no working code behind it. An MVP is a real product that real users can use.

From: MVP Design: What to Build First in Your Startup App

Should an MVP look polished?

It should look clean and trustworthy, but it does not need every visual detail. Clear layout, readable text and working buttons matter more than animations.

From: MVP Design: What to Build First in Your Startup App

When should I add the features I cut?

Add them when real users show a need, for example when they ask for the same thing repeatedly or when a manual step becomes too slow to continue.

From: MVP Design: What to Build First in Your Startup App

Is an app redesign cheaper than a rebuild?

Often yes, because a redesign changes screens and flows while keeping working code. The exact cost depends on the number of screens, user roles and the research needed.

From: App Redesign or Rebuild: How to Decide and Roll Out

How long does an app redesign take?

A redesign usually takes a similar time to a new app design, since the screens still need mapping, wireframes and testing. Development time after that depends on how much code changes.

From: App Redesign or Rebuild: How to Decide and Roll Out

Will users leave if I change the app design?

They may, if main actions move without warning. Keep the most-used actions in familiar places, release in stages and tell users what changed in plain words.

From: App Redesign or Rebuild: How to Decide and Roll Out

What is a UI refresh?

A UI refresh updates the look of an app, such as colours, icons and type, without changing how it works. It suits apps that function well but look old.

From: App Redesign or Rebuild: How to Decide and Roll Out

Is a Figma prototype enough for an investor demo?

Yes, for most early-stage pitches. A clickable Figma prototype shows the product idea clearly. It does not prove that the product is built or that users will pay.

From: App Prototype for Investors: What to Show and Skip

How long should a pitch demo be?

Aim for 2 to 3 minutes of clicking through one main journey. Keep extra screens in a backup file for questions.

From: App Prototype for Investors: What to Show and Skip

Should I build a working app before meeting investors?

Not always. A prototype can be enough to explain the idea. Whether to build first is a business decision for you and your advisers.

From: App Prototype for Investors: What to Show and Skip

Can I use real user data in the prototype?

Use made-up names and numbers instead. Real personal data should not appear in a demo that you share with others.

From: App Prototype for Investors: What to Show and Skip

What is role based access in a SaaS product?

It means each user sees and changes only what their role allows. For example, an owner can change billing, while a supervisor can only mark attendance.

From: SaaS Product Design: Roles, Setup and Empty Dashboards

How many user roles should a first SaaS version have?

Start with 3 or 4 clear roles. Add custom roles later, only if customers ask for them.

From: SaaS Product Design: Roles, Setup and Empty Dashboards

What is an empty state in a dashboard?

It is the screen a user sees before any data exists. A good empty state explains what will appear and gives one clear button to start.

From: SaaS Product Design: Roles, Setup and Empty Dashboards

How long should SaaS onboarding be?

As short as possible. Aim to get a new account to one useful result in a few steps, then ask for more details later.

From: SaaS Product Design: Roles, Setup and Empty Dashboards

How long is a design sprint?

The common format is 5 days. Shorter versions of 2 to 3 days also exist for smaller questions.

From: What Is a Design Sprint and Do You Need One? A Plain Guide

Who should attend a design sprint?

A small group of about 5 to 7 people, including a decision-maker such as the founder, someone who knows customers, and a designer.

From: What Is a Design Sprint and Do You Need One? A Plain Guide

Is a design sprint the same as a hackathon?

No. A hackathon aims to build working software quickly. A design sprint aims to test an idea with a prototype before building anything.

From: What Is a Design Sprint and Do You Need One? A Plain Guide

Can I do a design sprint for a small business?

Yes, in a lighter form. One or two focused days, a simple prototype and a test with a few customers often give most of the benefit.

From: What Is a Design Sprint and Do You Need One? A Plain Guide

More questions

Have a question that is not here?

Ask Tithi directly. I reply to every enquiry within 24 hours.