MVP
An MVP is the first version of a product, carrying the fewest features needed to test the idea with real users. The aim is to confirm the most critical assumption at low cost before building everything. The feedback decides the next step. Few features does not mean careless: it must do its job well.
- Area
- Web and software
- Also called
- minimum viable product
- In Turkish
- MVP
- Read more · Service
- Web and software
Why it matters
An MVP reduces the risk of building every feature and then learning that nobody wants it. Early feedback from a few users makes sure the budget goes to the right work. When misunderstood, an MVP is shipped as a half-finished, careless product, which loses user trust.
Example
Say an entrepreneur plans a food ordering app. Instead of a full app, they set up a simple page that takes orders through one form in a single neighbourhood. In the first 3 weeks, 60 orders arrive and it becomes clear which feature is really needed.
Related terms
- CMSA CMS is software that lets a site’s pages, articles and images be added and updated from an admin panel without writing code.
- Design systemA design system is the single place where the colours, typefaces, spacing and components of a brand’s digital products, such as buttons, forms and cards, are defined with their rules.
- DNSDNS is the system that translates domain names into the numeric addresses of servers.
- Headless CMSA headless CMS is a CMS that separates the panel where content is managed from the front end that shows it.
- SaaSSaaS is the model in which software is used online by subscription instead of installed on the user’s computer.
- AccessibilityAccessibility is a site being usable by everyone, including people with visual, hearing, motor or learning difficulties.
The definitions are general information. If you think one is incomplete or wrong, write to us and we will reply within one working day. Get in touch
From our journal
From what we have written on Web and software; they show how the term turns up in the work.
- Core Web Vitals explained: how to read LCP, INP and CLSThe three thresholds, the gap between field and lab data, and which row to look at in Search Console and PageSpeed Insights, step by step.
- How to brief a digital agency: seven headings on one pageThe one-page document to write before you ask for proposals: goal, current numbers, audience, what has been tried, constraints, who decides and the deadline. Plus a template and how to compare proposals.
- How to build a multilingual website: a 6-step decision listURL structure, one address per language, the language switcher, translation quality, the forgotten parts and a workflow that keeps versions in step: the decisions to make before you build.
- Website security checklist: 8 steps for ownersHTTPS and HSTS, updates, admin accounts and two-step sign-in, a backup you have restored, form spam, security headers, what Google does and the first hour after a breach.