Work / Entry

Tingavi

A mobile-first way to estimate second-hand value, create better listings from photos and prepare adverts for any marketplace.

Founder · Product design · UX/UI
Product strategy · Information architecture · UX/UI · Brand direction · Front-end development · Beta testing · Accessibility · SEO
React · TypeScript · GitHub · Lovable Cloud · Supabase
Tingavi visual identityFrame / 001
Introduction

Second-hand selling is a string of small decisions: what is the item worth, which details matter, how should it be described, and where should it go? Most tools only help with one of those steps.

I designed Tingavi to connect them. The mobile-first experience combines Buy and Sell workflows with an independent listing library. Users can check an estimated value, prepare an advert from photos and save it until they decide to publish on a marketplace.

Tingavi is currently in beta. The pricing guidance is an estimate, not an appraisal; uncertain authenticity and market values should remain visibly uncertain.

CH.01

The problem

Turn an item into a usable advert, without platform lock-in.

Second-hand selling happens across disconnected steps: identifying an item, deciding a plausible price, describing its condition, choosing a marketplace and keeping track of unfinished adverts. Each handoff increases effort.

The design challenge was to make those steps feel like one continuous task, without locking the user into any particular selling platform.

Make preparation easier, without deciding for the seller.

CH.02

Two modes. One system.

Buy, Sell and a shared listing library.

Buy starts with a photo and a few details, then prioritises an estimated second-hand price and the reasoning behind it. The result is meant to be readable immediately, with additional context further down the page.

Sell turns photos and basic information into a suggested listing. Suggested price levels give users room to decide how quickly they want to sell. Important checks belong in a separate seller checklist, not inside the advert itself.

The listing library is the product's organising principle: prepare several adverts, save only the ones you choose, and publish them when and where it suits you. Text is easy to copy and images are ready to download for use across marketplaces.

CH.03

Trust through clarity

Estimates, authenticity and user control.

A price estimate is only as useful as the information behind it. The interface separates the suggested value from its explanation and avoids presenting uncertainty as certainty.

Collectible items can raise additional questions about authenticity. Tingavi is designed to communicate that uncertainty and ask for relevant details or additional images when needed, rather than presenting a visual guess as a certification.

The product deliberately keeps final pricing and publishing decisions with the user.

A price is more useful when you know why.

CH.04

Building in public beta

Iterative UX decisions and responsible product development.

I developed Tingavi through repeated interface revisions and early user testing. The priorities are practical: put the valuation first, reduce effort when writing an advert and make saved listings easy to retrieve. When more information is needed, the interface should ask for it clearly.

The experience includes an interactive demo to help new visitors understand what the app does before signing up. Development also considers authentication, privacy, access limits and search visibility.

This case study describes design intentions and current beta functionality, not measured commercial results. Usage numbers and performance claims will only be added when they can be verified.