ThinkBuildRefine
Laravel • MySQL • Next.js
Aksa
I enjoy coding websites
Scroll through a few favorite projects I have built, from payment flows to learning systems and ecommerce interfaces.
01 / System Intent
Aksa Xiterz
Built to make delivery less manual.
Aksa Xiterz is my own digital license store. I built it so orders, payments, and key delivery do not depend on repeated chats.
02 / Product Logic
Aksa Xiterz
The catalog is part of the system.
Packages, stock, and delivery rules are visible early so the interface reflects what the backend can actually fulfill.
03 / Payment State
Aksa Xiterz
Payment state stays readable.
Because real customers pay through it, QRIS keeps amount, expiry, order ID, and status checks close together.
04 / Strict Rules
Aksa Xiterz
Crypto checkout needs firm edges.
I made the network, amount, address, and warnings explicit so the system has fewer ambiguous states to recover from.
05 / Fulfillment
Aksa Xiterz
Delivery is backend logic.
When an order is paid, the license should be ready without me manually pasting keys into chat.
06 / Traceability
Aksa Xiterz
History is part of trust.
Customers can trace status themselves: what happened, what is waiting, and what needs attention.
07 / Support Surface
Aksa Xiterz
Repeated questions should become tools.
The guide area came from noticing support patterns and turning the same setup fixes into something users can follow alone.
08 / Continuity
Aksa Xiterz
The flow continues after payment.
Files and companion tools stay organized by product so the system does not end at the invoice screen.
01 / Learning Hub
EduVest
A learning app needs a clear path.
With EduVest, I focused on turning finance material into a route people can follow, not a dashboard full of loose blocks.
02 / Content Shape
EduVest
Structure makes learning calmer.
I grouped stock, crypto, and finance basics into tracks so the user always knows what kind of lesson they are entering.
03 / Video Flow
EduVest
The interface follows the lesson order.
The playlist model keeps the learning flow sequential, which fits how I like building apps: state first, decoration later.
04 / User State
EduVest
Progress should be easy to resume.
Belajarku is less about showing numbers and more about remembering where the learner should continue next.
05 / Next Action
EduVest
Focused screens make decisions lighter.
The active course list keeps title, category, lesson count, and continue action close because those are the decisions that matter.
06 / Product Context
EduVest
A complete product still needs restraint.
I kept FAQ, updates, and feedback close to the learning story instead of letting the page turn into a generic landing page.
01 / Composition
BRLFashion
The page needed visual order.
For BRL Fashion, I paid attention to hierarchy: brand, search, categories, and product mood all needed room to breathe.
02 / Browsing Rhythm
BRLFashion
Product browsing should feel guided.
I treated the catalog and gallery as a rhythm problem: enough movement to explore, enough structure to stay oriented.
03 / Editorial Layer
BRLFashion
Content can soften the interface.
The blog area adds care notes and context, giving the storefront an editorial layer without pulling focus from products.
04 / Human Signals
BRLFashion
Feedback gives the layout a pulse.
Customer notes and service questions help the page feel inhabited, but I kept them secondary to the product structure.
05 / Support UI
BRLFashion
Support should stay close, not loud.
The FAQ and assistant sit near the shopping flow so help is available without becoming the center of the interface.
06 / Dense UI
BRLFashion
Small details carry the buying decision.
Price, stock, size, quantity, and action placement matter because ecommerce UI is mostly a sequence of small choices.
07 / Checkout Shape
BRLFashion
Checkout has to feel composed.
I kept delivery, payment, cart state, and totals in one readable flow so the final step does not feel like a separate app.
