I design interfaces. Lately, I've been learning what happens after Figma.
Hey, I'm Dani, a product designer in Jakarta. I'm currently designing at Abadikan and working independently through SyroPixel.
Most of my work is still product design: flows, interface details, components, and handoff. I'm not calling myself a finished design engineer. I'm moving in that direction by building the work, not only describing it.
That means opening the browser, writing HTML and CSS, prototyping the interaction, and seeing which decisions survive real content. Code gives me a faster way to test the parts that a static frame can hide.
The tools and field notes on this site are my practice log. Some ideas are useful now; others will get revised when the work teaches me more.
Where I am now
- 2025 — now Founding Designer · Abadikan Brand, marketing, product UI, and the shared system underneath. I work with a small founder and engineering team.
- 2023 — now Product Designer · SyroPixel Independent product and interface work for startups and studios. One project was an early computer-vision MVP for construction teams.
Where I've been
- 2024 — 2026 Product Designer · The Design Factory (London) SaaS and company-profile projects with weekly feedback from the Creative Director. London hours, Jakarta desk.
- 2023 — 2025 Dribbble Shot Team · Kretya Studio Mobile, web, and dashboard concepts for the studio's public portfolio. A useful place to practice visual range and consistency.
- 2023 UI Designer (Crypto) · Kretya Studio Crypto wallets. Security-first interfaces. My first real design system, end to end.
- 2023 — 2024 UI/UX Designer · Upwork Client work across websites, mobile apps, and dashboards. This is where I learned to write clearer handoffs.
- 2021 — 2022 UI/UX Designer · Lumoshive Landing pages, mobile apps, and CMS work. This is where I first learned to organize a Figma file for someone else to build.
- 2020 — 2021 Graphic Designer (Intern) · Hypernet Technologies My first real job. Made me realize brand and product can't live in two different folders.
What I write about
I write practical notes about interface craft: typography, content pressure, spacing, motion, and feedback states. Some notes also become installable skills so I can reuse the same checks in future projects.
- Field note Every gap needs an owner A method for finding duplicate spacing and fitting corrections to the system already there.
- Field note Your layout has not met its content yet Long names, translation, zoom, and narrow containers as part of the design—not edge cases.
- Field note Every line break is a layout decision A small guide to balance, pretty, and text that survives real content.
The browser is where the interface stops being hypothetical.
Things I believe (subject to change)
A polished frame is useful. A component that survives real content is more useful.
Small decisions add up: one spacing owner, one clear loading response, one interaction that can reverse without breaking.
I would rather show a working example than add another adjective to my bio.
The basics
What I'm focused on this week is on /now. The tools I actually use are on /uses. How this site is built — and why — is in /colophon.
That is the current version. It will change as the work does.