Health, home and travel decision

Itemlist

A capable developer can reproduce the core inventory and barcode-scan workflows using existing open-source inventory projects and standard cloud tools, but matching the polished mobile UX, App Store presence, translations, and offline-sync polish of the shipped app is a larger product effort best left to the vendor unless you only need a narrow workflow.

View on the App Store
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off166 h to build

$25/mo6 h/mo upkeep

No published price to break even against.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Itemlist alternatives, with the arithmetic →

What a replacement has to do

  • Design and build an iOS client plus a minimal cloud backend that supports: creating locations/containers/items, scanning barcodes to search items, offline-capable sync with cloud storage, CSV export/import and image attachments, basic user accounts and sharing/permissions.

What it still won’t have

  • Polished, App Store–grade iOS UX and iterative polish
  • Existing App Store listing, ratings and user base
  • Built-in multi-language support and small-feature polish (Siri Shortcuts, drag-and-drop, full-screen image viewer)
  • Developer support and ongoing app updates provided by the vendor

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Itemlist does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal replacement: implement an iOS app in SwiftUI and a small cloud backend in Node.js (Express) + PostgreSQL. Core features in scope: create/manage locations, rooms, containers and items; scan barcodes to search items (use AVFoundation for scanning); offline local persistence with Core Data and two-way sync to the backend; image attachments with uploads to S3-compatible storage; CSV export/import; basic user accounts and location sharing with view/edit permissions. Out of scope: multi-language translations, App Store publication, payments/subscriptions, advanced conflict resolution for concurrent editors. Include authentication, error handling, unit tests for backend endpoints, and end-to-end UI tests for the main flows.
How we checked2 sources · 3/3 runs agreed · evidence score 62

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 2 cited sources+1
  • 3/3 assessment runs agreed+4
  • Evidence score62

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 2

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded