creative engineer working where ai systems, onchain primitives, and craft‑forward interfaces overlap — usually alone, occasionally in small teams.
jakarta, id — working with teams in SF, NYC, and across EU.
making theedges ofthe web feelgood to touch.
eight years shipping interactive surfaces for agencies, research labs, and independent teams. these days most of the work sits between autonomous agents, onchain value, and interfaces that respect the eye.
work.
four projects that demonstrate range — not the full archive. each is live, each has a case study, each is the kind of thing i want more of.
full archive / 24 →the internetis flooding withaverage.
generative tools are cheaper than decisions. the bottleneck moved from "can we build it?" to "should we ship this?" — i work at the inflection: taking systems that can write infinite mediocrity and shaping them into tools where the human touch still costs the most and matters the most.
interfaces should respect the intelligence of the person using them.
no onboarding tour, no reassuring copy, no crutch text. the user is smarter than the worst case, not the best one.
ai should make people feel capable, not dependent.
the best input after a prompt is a cursor, not more prompt. the second most useful output is silence.
open source is the default; ownership is the feature.
if i build something you can host yourself, i will. lock‑in is a failure mode, not a business model.
services.
four overlapping surfaces. i prefer 4–10 week engagements, solo or in small teams. i say yes to work that will still matter in 18 months.
credits.
eight years, a handful of real teams. subtle credits, not a logo wall — each of these was a long stretch of work, not a passing‑by.
hi, i'm
dev.
i design and engineer interfaces — usually at the intersection of ai systems, onchain primitives, and craft‑forward web work. about half my day is typography, the other half is making systems that feel inevitable.
i spent the last four years shipping across an agency, a seed stage lab, and an open‑source toolkit. before that, i studied architecture — which made me allergic to the grid obsession and the allergy to making interfaces feel lived‑in, all in 200ms on a 3g connection in a crowded coffee shop.
these days i'm most interested in ai systems that preserve the user's agency, onchain primitives that treat attention as a first‑class resource, and the unglamorous work of making interfaces load in 200ms on a 3g connection in a crowded coffee shop.
notes.
short pieces on what i'm building, making, and reading — usually on fridays, sometimes a full essay about a single decision.
subscribe → rss · lettersfaq.
i read every email. if it's a real question from a real person, you'll hear back within 24 hours — usually faster than my own mother.
ask directly · abdullahdevrangga@gmail.com →let's buildsomething quiet.
the best way to reach me is email. i read everything. if it's a real project from a real team, expect a reply within a day. if it's a cold pitch for web3 casino design — expect a slower reply.
