Personal build
Nikonomu
A matcha ordering app with a simple checkout flow, practical order management, and notification hooks for day-to-day operations.
ReactLaravelWhatsAppDiscord
Open project Portfolio / 2026
Hello, I'm Fahmiko
- —Fullstack Engineer building fast, scalable, and useful digital products
- —Frontend-focused engineer with 6+ years shipping real products
- —I build web apps, cloud systems, and automation that reduce manual work
Personal work
A few selected projects
Smaller builds where I had more room to test ideas and shape the product directly.
Expertise
How I work
Not just the stack, but how I usually think about product work that gets used every day.
Frontend
- •Vue.js
- •Nuxt.js
- •React
- •Tailwind CSS
- •Responsive UI
Backend & integrations
- •Laravel
- •Node.js
- •REST API
- •Firebase
- •Workflow automation
Execution style
- •Product-minded implementation
- •Maintainable code structure
- •Interaction and motion with restraint
Professional work
Products I have worked on
Some products and internal systems I have contributed to over the last few years, mostly on the frontend, product UI, and delivery side.
SPMB.id
Frontend Engineer
A university admissions portal that brings multiple selection paths into one flow that is easier for students to navigate.
Nuxt.jsPrimeVueTailwind CSSNitro
Visit site AXSI.ai
Frontend Engineer
A public-service chatbot product for government institutions, focused on clear conversational UI and maintainable delivery.
VueViteChat widget
Visit site Masook.id
Lead Developer
A biometric attendance system for institutions that need cleaner attendance records, location validation, and reporting.
Vue.jsNuxt.jsVuetifyInternal tools
Visit site ASIQ.id
Frontend Engineer
An AI-assisted learning platform for teachers, designed around simpler material creation flows and a clearer product experience.
ReactViteChat widget
Visit site Contact
If the project feels relevant, we can talk.
I am open to freelance work, consulting, or frontend-heavy product work that needs clear and realistic execution.
How I usually start
Good projects usually start from a clear problem.
If you already have a brief, great. If not, a short message with the context and the target is enough to start.
Scope first, visuals second
Interesting interaction should still come from a clear product flow, not the other way around.
Motion with purpose
I use animation to add hierarchy, feedback, and energy, not just decoration.
Still maintainable
Even when the UI feels richer, the implementation still has to stay maintainable.