iFoundIt: a visual-first home inventory app

Problem

People lose track of their own things: documents, chargers, keys, the box the router came in. The tools that exist for this are inventory systems: text-heavy, complex, built for businesses. iFoundIt is the opposite: a visual-first app for everyday home use.

Household organisation fails because logging an item is more effort than just risking losing it. Any solution has to make capture almost free, or people won’t do it twice.

Target users

• Busy professionals who forget where they filed a document or stored an accessory
• Students in shared apartments who need to keep track of their own things
• Families managing a lot of stuff across a household

Evidence / research

The existing tools are built for warehouses and small businesses: fields for SKUs, quantities and suppliers, and rows of text. They ask for a lot of input before they give anything back, which is the wrong trade for a phone charger. That set the hypothesis the whole app is built on: if logging an item costs less effort than losing it, people will actually do it, and do it again.

My role

I designed and built the app solo, covering research, information architecture, UI and interaction design, prototyping, testing and the App Store release.

Constraints

The project ran in a four-week research-to-launch cycle. Capture had a target of under ten seconds, and each saved item still needed enough information to be found later. The shipped platform was iOS.

Options considered

Form-first entry is the inventory-app default: name, category, location, then an optional photo. It produces tidy data, but it front-loads exactly the effort that stops people logging things. A text list is denser and easier to sort, but you scan your own belongings by sight, not by the name you typed months ago. And a longer setup, rooms and categories configured before the first item, would make the data cleaner, at the cost of the first session, which is when someone decides whether the app is worth keeping.

Decision

Photo before form. The first thing you do is take the picture; everything else is secondary and mostly optional. This is what gets capture under ten seconds.

A grid, not a list. You recognise your own stuff by sight faster than by name, so the primary view is images.

Strip onboarding to the bone. Fewer steps before the first item; retention is set in the first session.

Design

What I did

• Designed the capture flow to hit a hard target: add an item in under ten seconds. Photo first (camera or gallery), then name, category and location, notes optional.
• Made the app visual-first: the item list is a grid of photo tiles with category and room, not rows of text.
• Kept search and category / location filters one tap from the list.
• Designed onboarding to be minimal: get to a first item fast so users can try the capture flow before investing more time in setup.
• Designed the empty, account and auth states (sign up / sign in / reset password).

The list is the home screen and the whole point: a grid of photo tiles, not rows of text, because people recognise their own things by sight faster than by name. Tapping one opens the record, photo, category, location and note, everything needed to relocate the item without a second guess.

Adding an item is the step that has to be almost free, or people stop doing it after the first few. Photo comes first; name, category and location are the only fields standing between that photo and a findable item.

Two more states carry their share of the design: a first-run empty state with exactly one next action, and the account screen, usage at a glance before the settings underneath it.

Collaboration / implementation

I took the product from Figma to production myself in a four-week cycle: research, design, build, test and launch. Owning both design and implementation kept the scope tied to what I could ship.

Measurement

The metrics that matter are still early, so I hold them as targets, not results: activation (users who add a second item in the first session), week-two return, and review sentiment. Retention is the real test, since a home inventory only pays off once there’s enough in it to search.

Result

Designed end to end and shipped to the App Store, built around a sub-ten-second capture target.

What I learned

Shipping in weeks instead of quarters taught me that the first honest feedback arrives while the decisions are still cheap to undo. What I’d change now: capture is tuned for the first item, but the people who stay are managing dozens, so the next pass is bulk entry, stronger categories, and search built for a full house, not an empty one.