Should the found item list be public so owners can browse it?

No. A public list invites false claims — anyone can describe a visible item. Keep items staff-only and have owners describe what they lost; staff then match the description to the item. Matching on details only the owner would know is the whole security model.

How long should items be kept?

Let each venue set its own retention period, and check local rules, since some places have legal requirements for found property. The app enforces the venue’s own policy with a disposal list and a record of what happened to each item.

How to Build a Lost and Found App with AI (2026)

What a lost and found app needs

Log a found item with photo, category, where and when it was found
Search and filter the item list by category, colour, and date
Owner claim form with a description to match against items
Handover record with who collected the item and when
Disposal list for items held past the retention period

The screens

Screen	What it does
Items	Found items with photo, category, location, and days held
Log Item	Photo, category, colour, location found, finder name
Claims	Open owner claims with suggested matching items
Handover	Confirm the owner, record name and signature, close the item
Disposal	Items past the retention period to donate or discard

The data model

Venue: name, retentionDays
Location: venueId, name
Item: venueId, locationId, category, colour, description, photoUri, foundAt, foundBy, status (held, claimed, returned, disposed)
Claim: venueId, ownerName, ownerContact, category, colour, description, lostOn, status
Handover: itemId, claimId, returnedAt, staffName, signatureUri

The build prompt (copy this)

Paste this into ShipNative and it becomes a working React Native app with these screens, navigable in a live preview, in about two minutes:

“A lost and found app for staff at one venue such as a gym, school, or hotel. Items lists every found item with a photo, category, colour, the location where it was found, and how many days it has been held, filterable by category, colour, and date range. Log Item is optimized for a busy front desk: take a photo, pick a category and colour from chips, pick the location from a list, add an optional description, save. Claims holds owner reports of lost items, entered by staff or through a simple public form link; each claim shows suggested matching items by category, colour, and date so staff can compare quickly. Handover records returning an item: confirm the match, record the owner name, collect an on-screen signature, and mark the item returned. Never show the public which items are held — only staff see the list, so people cannot claim things that are not theirs. Disposal lists items held longer than the retention period set for the venue, to donate or discard with a record. Staff sign in; roles are staff and admin. Screens: Items, Log Item, Claims, Handover, Disposal.”

Then iterate with small, screen-specific prompts (“make the primary button bigger”, “add an empty state”), preview on your own phone, and export the full Expo project whenever you want. The full method: how to build an app with AI.

How it makes money

Sell to organizations, not individuals: a monthly subscription per venue, priced low for a single gym and higher for multi-site hotel groups or school districts. Venues value the audit trail more than the item list — a record of who handed over what, and when, protects them when a guest says something went missing.

Implementation and the revenue math for every model: how to make money from an app. When you’re ready to ship: App Store and Google Play publishing guides.

Build it now

The prompt above is free to run at shipnative.dev — working lost and found app on your phone today, full code export, no credit card.

How to Build a Lost and Found App with AI