Sector01
Motion earns the frame
Transitions should explain hierarchy, feedback, or continuity. If they only decorate, cut them.
Front-end Developer / Ha Noi, Vietnam
On product
Cinematic UX with production React systems.
On chain
DeFi surfaces, wallet flows, and data-heavy frontends.
On systems
ERP discipline, maintainability, and delivery cadence.
Reference-led practice
The interface direction is sharpened through critique loops, restrained motion, trustworthy patterns, and components that hold together when the happy path breaks.
Transitions should explain hierarchy, feedback, or continuity. If they only decorate, cut them.
Interface patterns are chosen for the job they solve, then pressure-tested against real product behavior.
Components need focus paths, reduced-motion fallbacks, and enough disclosure to stay legible under edge cases.
What's Up On Socials
Capturing the intersection of engineering and design.
Editorial proof, not filler
This chapter needs one frame with enough weight to stop the scroll before the smaller references and links take over.
Lead proof
Cinematic Dashboards
Signal readout
The proof chapter needs one frame with enough weight to stop the scroll before the smaller references and links take over.
Proof 02
Engineering Flow
A supporting frame that reinforces the same authored system without competing with the lead proof image.
Proof 03
Strategic Precision
A supporting frame that reinforces the same authored system without competing with the lead proof image.