Problem
Local repair and service requests died in chats and groups.

Case study
An app connecting people who need a craftsperson or service with those who provide it.

From Google Play


Local repair and service requests died in chats and groups.
A services marketplace from request to the job.
Flutter · Backend APIs · Maps / location
Service request · Craftspeople / providers · Multiple trades · Request tracking
Keep the request simple without ignoring trust.
A local job as a product path, not a group ad.
Which request fields attract a serious provider?
Request and reply first.
Short form, clear status.
Two-sided mobile product for demand and supply.
Flutter, two roles.
Requests, accounts, location when needed.
Not the core. Automation later only if it speeds matching.
A request cycle to close.
Google Play.
Matching after real behaviour.
Result
Live on Google Play as Bricool.