Bazaaro — a project by Ahsan Mahmood
A trust-first classifieds marketplace (OLX alternative) with escrow, verified identity, and SafeMeet pickup zones for buyers and sellers.
Everyone who has used classifieds knows how they fail.
The listing that is too cheap. The account created yesterday. The buyer who agrees a price, arranges a time and then stops replying.
The meeting in a car park that you think about more than you would like to. None of that is an edge case. It is the ordinary texture of the thing, and it has stayed that way for years because trust is expensive to build and nobody is punished for leaving it unbuilt.
Bazaaro is an attempt at the expensive version.
The design puts four things at the centre rather than at the margins.
Money held in escrow until the buyer confirms. Identity that has been verified, carrying a trust score. Geofenced pickup zones, so the meeting happens somewhere chosen rather than somewhere suggested. And an evidence locker for when a dispute happens anyway.
Each of those inverts a risk that currently sits with the person who has the most to lose.
Escrow makes the seller wait instead of the buyer gamble. Verification puts a cost on creating an account for a single fraud. A designated pickup place removes the negotiation that most often ends with somebody agreeing to a location they are not comfortable with.
Now the part that has to come before any of that is admired.
None of it is running. The record says the signed-in marketplace is planned and not yet live, and what builds green today is the scaffold, a design system, internationalisation, a graceful-degrade service layer and the public marketing site. The trust machinery is architecture and intention. A page describing it in the present tense would be describing a product that does not exist.
What is built is built emerging-markets-first, and that is a structural decision rather than a preference.
Right-to-left layout, multiple currencies and cash-on-delivery paying into escrow are not features bolted onto a finished marketplace. Right-to-left reaches into every layout assumption.
Currency reaches into the data. Cash-on-delivery reaches into the payment flow and changes what escrow even means. Products that treat these as a later export problem find out that the assumptions underneath were load-bearing.
The service layer degrades rather than breaking.
It runs without paid API keys, returning something sensible when a service is not configured instead of failing at boot. That is what lets a marketplace this size be developed at all by one person, because the alternative is needing every third-party account provisioned before the first screen renders.
One codebase targets web, mobile and desktop, which is a claim worth qualifying.
Sharing a source tree across three delivery shapes saves the duplication, and it does not make three products from one. Each still needs its own packaging, its own store relationship where a store is involved, and its own decisions about what belongs on that surface. What is shared is the logic. What is not shared is the finishing, and the finishing is where the time goes.
What it cost is the gap between the idea and the software.
Trust-first is a genuinely good argument and the marketing site makes it well, which is exactly the situation where a portfolio page becomes misleading without meaning to. The concept is complete. The scaffold is real. The thing that would make either matter is not built, and saying so is the only version of this page worth publishing.
What it does, and what that costs to build
- Trust-first design with escrow that holds money until the buyer confirms
- Verified identity and trust score system (planned)
- SafeMeet geofenced pickup zones and evidence-locker disputes
- Design-system shell with themed accent customizer and branded error pages
- Multi-language i18n with RTL support for emerging markets
- Public marketing site with Home, Pricing, and Safety pages
- Graceful-degrade integration layer that runs without paid API keys
- Cross-platform codebase targeting web, mobile, and desktop
Built with
- React 19
- TypeScript
- Vite 6
- Tailwind CSS v4
- shadcn/ui
- Zustand
- TanStack Query
- React Router 7
- react-hook-form
- Zod
- Firebase Firestore
- i18next
Worth knowing
- classifieds
- marketplace
- escrow
- trust-and-safety
- react
- firebase
- capacitor
- cross-platform
What of Bazaaro is actually built?
The scaffold, a design system, internationalisation, a service layer that degrades gracefully without paid keys, and the public marketing site. The record is explicit that the signed-in marketplace is planned rather than live. So the trust machinery that the entire concept rests on, meaning escrow, verified identity and the pickup zones, is designed and not running. That is the first thing a reader should know and the last thing a marketplace page usually says.
What problem is it aimed at?
The failures buyers and sellers already expect from classifieds: scams, fake accounts, people who vanish mid-conversation, and fees that feel extractive. Those are not edge cases on existing platforms, they are the ordinary experience, and they persist because trust is expensive to build and cheap to leave unsolved. Whether this design would fix them is untested, since the part that would do the fixing has not shipped.
How is escrow supposed to work here?
Money is held until the buyer confirms, rather than moving when the seller asks. That inverts the usual risk: the seller waits instead of the buyer gambling. It is designed alongside cash-on-delivery paying into the same escrow, which matters in markets where cards are not the default and a purely card-based design excludes most people. All of that is architecture and intention. None of it is currently taking anybody's money.
Why build for emerging markets first?
Because retrofitting is worse than starting there. Right-to-left language support, multiple currencies and cash-on-delivery are not features added to a finished marketplace; each one reaches into layout, data and payment flow. A product built the other way round tends to treat them as an export problem later and discovers the layout assumptions are load-bearing. Starting from that constraint costs early effort and avoids a rewrite.
Does Bazaaro work on iPhone?
There is no iOS release. The codebase targets web, Android and desktop from one source, and the record lists iOS among the intended Capacitor targets, which describes the setup rather than anything published. There is no Apple Developer account here and nothing I build has shipped to the App Store. What exists to open today is the public marketing site, which a phone browser reaches like any other page.
https://aoneahsan.com/projects/com.aoneahsan.bazaaro