Development

App / Kerfi Rough Estimate

Use skjárs, roles, notifications, vinnuferlis, and integrations to build a quick rough estimate.

See best / likely / worst ranges, MVP cuts, and a shareable URL without leaving the browser.

  • Skjárs, roles, and integrations are all weighted
  • Best / likely / worst are calculated automatically
  • MVP cuts are ranked by impact
  • Browser-only, no server upload
Open verkfæri The initial load does not rewrite the URL. Use the share button to create a link.

What this verkfæri shows

  • Build a base effort estimate from skjárs, roles, vinnuferlis, and external integrations.
  • Add-on flags for offline support, notifications, audit skráging, and multilingual work adjust the difficulty.
  • Yfirferð effort, duration, cost, and MVP cut candidates together.

How to use it

  1. Open the verkfæri and choose the verkefni type and target platform.
  2. Enter skjár count, role count, vinnuferli count, and integration count.
  3. Toggle offline support, notifications, audit skráging, and multilingual work as needed.
  4. Adjust design level, QA level, the daily rate, and the decimal display setting.
  5. Yfirferð the estimate, then use the MVP preset, copy niðurstaða, or share URL actions.

Samples

Standard business app

Inntak

8 skjárs, 2 roles, 1 vinnuferli, 1 integration, Web, standard design, standard QA, JPY 100,000 / day

Úttak

About 11.5 person-days, 3 days, ¥1,150,000. Best 9.2 / worst 15.0.

Feature-rich multi-platform kerfi

Inntak

18 skjárs, 5 roles, 4 vinnuferlis, 3 integrations, offline, notifications, audit skrás, multilingual, Web + Mobile, premium design / strict QA

Úttak

About 71.1 person-days, 16 days, ¥7,111,000. Best 56.9 / worst 92.4.

Estimate inntaks

App / Kerfi Rough Estimate

Your inntaks stay in this browser and are never sent to the server.

Settings

  • Verkefni type - Switch the starting difficulty and delivery style.
  • Target platform - Web, mobile, and multi-platform verkefnis carry different effort.
  • Design level - Reflects how polished and custom the UI work will be.
  • QA level - Reflects test coverage, verification cycles, and fix loops.

Breakdown

  • Skjár count - Total list, detail, form, and settings skjárs.
  • Role count - How many roles you need, such as admin, user, or approver.
  • Vinnuferli count - Increase this when samþykkis branch or have multiple steps.
  • Integration count - API, webhook, and external SaaS connections.

Estimate

Best - person-days
Likely - Estimate
Worst - Best is 80% of likely; worst is 130% of likely.
Team capacity - 4.5 person-days / day

MVP cuts

The most expensive items appear first.

No obvious cuts from the current inntak.

  • Offline support - Offline support needs state sync and reconnect design.
  • Multilingual - Multilingual work adds copy and validation effort.
  • Audit skrá - Strict QA often adds áætlunning and fix loops.

Athugasemdir

  • This is a rough-estimate helper, not a substitute for a formal tilboð or contract scope.
  • Integrations often add coordination work, API auth, webhook handling, exception paths, and retries.
  • Offline and multilingual work expand the implementation and verification scope beyond skjár count alone.
  • Real verkefnis should also account for legacy assets, reuse rate, and stakeholder yfirferð cycles.

Algengar spurningar

Can I use this as a formal tilboð?

No. It is a áætlunning-stage rough estimate. Replace it with a formal tilboð once the assumptions are fixed.

Can cost go up even when the skjár count stays low?

Yes. Multilingual work, integrations, strict QA, and multiple platforms all increase effort.

What does the MVP preset do?

It applies a smaller starter configuration that is closer to an initial release.

What is stored in the share URL?

Inntaks, selected options, decimal display, and query sync settings are stored.

Does the calculation send anything to the server?

No. Everything runs locally in the browser.

Related links