Documentation / Architecture Flow

Behind the Build

How I Built floosak.

Every project is a series of choices. Here is a heatmap of the critical paths I took, the hurdles I cleared, and what I’d do differently today.

Core Path 1

Building a simple, solid API

I needed a way for different parts of the system to talk to each other without getting tangled up.

The Logic

I went with REST because it’s a reliable, industry-standard way to keep things predictable.

The Upside

The API is easy to document and integrates perfectly with almost any tool.

The Struggle

Sometimes it sends a bit more data than needed, but I prioritized simplicity and consistency over micro-optimizing every bytes.

If I did it again

“I’d likely use tRPC now for contract safety between frontend and backend automatically.”

GraphQL

tRPC

Serverless single-purpose endpoints

Other forks in the road

The takeaway:How... to send it.

Core Path 2

Next.js for a blend of speed and power

We needed good initial load without committing to only SPA or static site.

The Logic

Next.js allows evolving the rendering strategy per route without full rewrites.

The Upside

Everything feels fast, with flexibility per page.

The Struggle

Running a real server adds deployment complexity.

If I did it again

“Use ISR and image optimization to improve premium UI performance.”

Pure SPA (React)

Static Site Generation only

Other forks in the road

The takeaway:UI/UX... for premium brands.

READY TO AUDIT THIS CODE?

This flow is derived directly from production metadata. You can explore the source code or initiate a live demo to verify these architectural patterns.