Ari Pramana
Frontend Engineer
Building interfaces that feel fast, layered, and quietly precise.
Bandung, Indonesia
Showcase
Products, systems, and a few experiments. Filter by what kind of work it was — the list rearranges rather than reloading, so you keep your place.
5 projects
An operations console for a logistics fleet: live map, shipment timeline, and a command palette that keeps dispatchers on the keyboard all day. Rebuilt the data layer around streaming updates so the table never blocks on a refetch.
−62%time to dispatch
Lead frontend
Token pipeline and component library shared by four product teams. Figma variables compile to CSS custom properties, so a colour change lands in code the same day it lands in design.
48components shipped
Design engineer
Bookkeeping for small studios. The hard part was not the maths — it was making reconciliation feel forgiving, so a mistake is always one obvious step from being undone.
3.2kmonthly active studios
Product engineer
A small playground for testing easing curves against real components instead of a lone moving square. Curves export straight to CSS or Motion config.
1.4kGitHub stars
Author
An ambient focus timer that reads the room: it dims, softens contrast, and mutes its own chrome as a session runs long. Built to see how far an interface can recede while staying useful.
12 minmedian session gain
Solo build
The same three passes on every project, whether it runs three weeks or a year.
01
Before any interface exists, agree on what the user is trying to finish and what currently stops them.
02
Structure, states, and data flow first. If it works as unstyled HTML, the styling has something honest to sit on.
03
Depth, translucency, and transitions go on last — and only where they explain something the layout cannot.