First version

MVP development that is actually a first version

MVP development fails when “minimum” still includes every investor slide. A real MVP is a slice a user can finish: one loop, store listing or a URL, enough backend to be true. CodeLoop Studio builds those first versions as a Sarajevo product studio — mobile (native, Flutter, React Native) and web (Next.js) — then stays for v1.1 if the slice works.

If everything is in v0, you do not have an MVP

MVP development fails when “minimum” still includes every investor slide. A real first version is a slice a user can finish: one loop, a store listing or a URL, enough backend to be true. CodeLoop Studio in Sarajevo builds those versions — mobile (native, Flutter, React Native) and web (Next.js) — then stays for v1.1 if the slice works.

A grocery comparison search that works in one market. A QR menu guests can open. A measurement flow that writes to Excel. Not a platform with six roles. We cut with you in discovery so the calendar can be shorter than a full product. Typical studio work is still 3–9 months idea to launch; MVPs sit toward the short end when the cut is real.

Cost follows the cut — see app development cost. Calendar honesty lives on how long to build an app. Proof that a sharp job can ship: cijene.me. A written estimate within 24 hours of a brief, including what we refuse to put in v0, via the online estimate.

The cut is the deliverable. The cathedral waits.

A grocery comparison search that works in one market. A QR menu guests can open. A measurement flow that writes to Excel. Those are MVPs because a stranger can finish a loop on a store listing or a URL. A platform with six roles and a redesign of email is a full product with worse planning. We write down what is out of v0. Features you love go on a version list. If everything is in v0, we will say you do not have an MVP — we will not relabel a nine-month app to make a slide prettier.

Founders validating a market, operators replacing a paper process with a narrow tool, companies that need a store presence before they fund the cathedral: that is who this is for. US, UK, EU, and Bosnian teams. English (or Bosnian) delivery, named owner, weekly demos. Stack after the slice: Flutter, React Native, native, or Next.js picked for the frozen features. Cost follows the cut. A focused MVP often lands around three months when the slice is frozen. Full products at CodeLoop typically take 3–9 months from idea to launch.

cijene.me, Koliko, and seeQRmenu started as a sharp job, not a universe. You do not need a 40-page spec. Discovery freezes the loop, then design for the slice only, then iterations you can tap. QA on the real surface. The studio can remain for v1.1. Handover is not a vanishing act. If nobody outside Slack can use it, it is a prototype. Say the loop.

What we will put in v0 — and what we park

One loop a stranger can finish

If nobody outside Slack can use it, it is a prototype. Store listing or a URL is the test.

Enough backend to be true

Accounts if you need them. A fake success screen is not an MVP. Data has to survive the demo.

The cut, in writing

What is out of v0 is the deliverable. Features you love go on a version list. That is the job.

Stack after the slice

Flutter, React Native, native, or Next.js — picked for the frozen features, not for a blog post.

QA on the real surface

Phones for apps. Thumbs for web. We do not ship a cathedral of unchecked boxes.

Stay for v1.1

The deferred backlog is intentional. The studio can remain. Handover is not a vanishing act.

Freeze, build, prove

  1. 01

    Discovery workshop

    You do not need a 40-page spec. We freeze who uses it and what “done” means. Restaurants and bars are in this family — seeQRmenu and Koliko are the shape we mean.

  2. 02

    Frozen backlog

    v0 and a parked list. If everything is in v0, we will say you do not have an MVP.

  3. 03

    Design for the slice only

    Not a redesign of email and onboarding for six personas. Screens for the loop.

  4. 04

    Iterations you can tap

    Then device QA, then launch. A focused MVP often lands around three months when the slice is frozen.

  5. 05

    Measure usage, then v1.1

    The parked list comes back in order. We will not call a nine-month app an MVP to make a slide prettier.

MVP versus full product — use this in a board pack

VersionYou should have
Estimate · 24 hours

A range and a proposed cut. What we refuse to put in v0 so the date survives QA.

MVP · around 3 months

One loop, measurable usage, store or URL. cijene.me, Koliko, and seeQRmenu started as a sharp job, not a universe.

Full product · 6–9 months

Extra roles, integrations, polish. Typical CodeLoop products still sit in the 3–9 month band idea to launch.

Post-MVP · ongoing

The backlog you deferred on purpose. Cheaper than pretending it was always in v0.

Case study

cijene.me

A comparison product that started as search, filters, and a decide screen — not a platform with every retailer on day one. That is the cut we mean.

Open case

Frequently asked

A focused MVP often lands around three months when the slice is frozen. Full products at CodeLoop typically take 3–9 months from idea to launch. We will not call a nine-month app an MVP to make a slide prettier.
Good. We run a short discovery, freeze an MVP, then design and build. You do not need a 40-page spec.
Yes. seeQRmenu and Koliko are the kind of sharp jobs we mean. Start from the case studies, then we scope your variant.
Yes if scope is smaller. Cost follows features and platforms. Get a 24-hour written range at /online-estimate.
We park them on a version list. That is the job. If everything is in v0, you do not have an MVP.

Related

MVP Development | Ship a Slice Users Can Touch | CodeLoop Studio