Spping is a freight platform in the Southeast Asia where shippers can book carriers for their shipments across countries. For MVP, admin manages these two users and release payment manually at certain stages of the delivery.
As my first AI-development project, I took home plenty of pearls of wisdom with this freight Saas project. Multitude of tools and technologies were used:
SQL: Supabase
PostgreSQL database
Supabase Auth
Role-based Access Control
Globe.gl
Three.js
WhatsApp Cloud API
Next.js 14
TypeScript
Honestly, coming from a design background, these terms are foreign to me and didnt mean anything. Although I relied heavily on Cursor to build this product, a lot of thinking goes into crafting the PRD to ensure the user experience is accurate logically.
Quick demo logging into Admin Dashboard
My creative process:
Why Claude 4 sonnet to build?
Understands big code → Can read and work with long files or projects without forgetting.
Follows rules well → If you say “use Python only, no imports,” it actually does it.
Good at debugging → Spots mistakes and explains how to fix them.
Writes cleaner code → Produces code that’s easier to read and maintain.
Explains clearly → Breaks down tricky code or concepts step by step.
Works across languages → Can switch between Python, JavaScript, Java, etc.
Faster + cheaper → Runs quicker and costs less than the biggest model (Opus) but still very smart.
I don't see Figma in the creative process
While Figma can be useful for conceptualising and handing off frontend designs to Cursor, my priority in this project is ensuring the backend functions smoothly with fewer bugs.
I’m confident in my frontend skills, but the backend’s intricacies are what concern me most. For that reason, I relied heavily on AI models to refine ideas and generate mockups aligned with the Product Requirement Document.
Total number of code lines:
38,314 lines 👀
Typical code lines for a logistics/freight platforms: 25,000-60,000