Skip to content
005
live

FiX Ai

Construction supply app that joins site management, a materials catalogue and a supplier map on one platform.

Ownership
Company · solo developer · AI PORT
Role
Solo developer — product, UI, server actions, shared-backend integration
Period
Feb 2025
Open link
Live
https://fix.aiport.tr№ 005
FiX Ai — web
FiX Ai — mobile

Context

On a construction site three problems occur at once: finding the right material, finding the nearest supplier, and knowing what is left in stock. FiX Ai joins the three on one platform: a 21-segment materials catalogue, a supplier map and a per-site stock / purchasing panel. A repair request flow that needs no membership opens the platform to individual users as well.

Constraints

  • Supplier data is entered by users; without quality control the catalogue becomes a dump (admin approval).
  • Site crews use it from a phone; map and catalogue must stay fluid on mobile.
  • One developer; scope was pinned to four clear flows: discover → map → site → request.

Architecture

Four user flows, one data model; requests and supplier entries pass through the approval queue.Materials catalogueSupplier mapSite panelRepair requestAdmin approvalSpring Boot · MongoDB
Four user flows, one data model; requests and supplier entries pass through the approval queue.

§ Decision log

DecisionAlternativeWhy
01Repair requests are accepted without signing inMembership required to submit a requestSomeone with a leaking tap does not fill in a registration form; take the request first, attach an account later. Admin approval handles spam.
02Supplier discovery on a map, from the same data model as the catalogueKeep the catalogue and the supplier directory as separate listsOn a construction site the question is "where is this material nearest"; product and location must be answered by one query.
03Admin-approved publishingSupplier entries go live instantlyEarly on, catalogue quality is worth more than growth speed; an approval queue is a cheap quality gate.

§ Outcome

21
Catalogue segments
1
Developers

§ Retrospective

What I would do differently today

TODO: What would you do differently today?