Case study · Marketplace

A services marketplace with badges, chat and disputes.

Providers list services and bookings; customers post requests, book, bookmark and chat; disputes and transactions are handled in an admin.
Client
LYNXNET
Sector
Marketplace
What we built
Marketplace app for iOS and Android, API with payments, admin with disputes.
Platform
Flutter app with sockets, Node.js API with Stripe and Firebase, Next.js admin.

In short

LynxNet is a two sided marketplace. Providers create and edit services and take bookings, customers send out requests, book a service, bookmark providers and chat, and reputation is carried as badges. When something goes wrong there is a dispute form in the app and a dispute desk, transactions and documents in the admin.

The brief

Two sides, and a referee.

A marketplace only works if both sides trust it, and trust is built by what happens when a booking goes wrong as much as when it goes right.

What had to be true

  • Services and bookings

    Providers create, edit and manage services; customers create bookings and follow their detail.
  • Requests out to the market

    Customers broadcast a request and providers respond.
  • Reputation and shortlist

    Badges on profiles, bookmarks for customers, chat between the two.
  • A desk for disputes

    Dispute form in the app; disputes, transactions and documents in the admin.

What we did

We built the happy path and the unhappy path together.

Every booking has a dispute route, and every provider has a reputation that reflects both.
01

Marketplace core

Services, bookings, requests, bookmarks and chat in one API with sockets for live updates.

The two sides, connected.

02

Badges from behaviour

Badge lists on profiles derived from activity, so a shortlist means something.

Trust from data.

03

Dispute desk

Dispute form in the app; dispute cards, overview, transactions and documents for the admin to resolve.

The referee is built in.

What changed

A marketplace that handles its own problems.

What the platform covers.

Both sides

providers and customers in one app

Badges

reputation shown on profiles

Disputes

raised in app, resolved in the admin

Technology

What this was built with.

Chosen to fit the problem and the team who owns it now.

01Mobile

  • Swift
  • Kotlin
  • Flutter
  • React Native

02Web

  • React
  • Next.js
  • TypeScript
  • Node.js
  • Laravel
  • WordPress

03Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5verified reviews on Google