Ship, then refine
A working version teaches more in a day than a month of speculation.
About
Engineering with intent
Computer Engineering graduate, Flutter developer and web engineer. I care about interfaces people can feel and systems other developers can read.
From Flutter widgets to shaded pixels
I am Nabin, a full-stack engineer & flutter developer based in Kathmandu, Nepal. My journey began with UI/UX design and graphics (4+ years experience, started early in engineering studies), building an intuitive eye for user interfaces. Evolving into full-stack web engineering, I mastered React and Next.js (4+ years experience), and later expanded into cross-platform mobile apps with Flutter (3+ years experience). Today, I build end-to-end intelligent systems, with AI integrations and workflow automation using n8n as a 2 years active focus.
I care about two things above everything else: interfaces that feel inevitable, and systems the next developer can read. That is why this portfolio is a set of small, documented modules rather than one large file: data lives in data/, design tokens in app/globals.css, and motion in reusable primitives under components/animations.
This is the fifth build of the same portfolio. Every version taught me something about performance, accessibility, and how much a person can learn by shipping instead of planning. The work that followed, the roles and the numbers all live on the experience page; this page is the story that got me there.
Performance is design
Motion that stutters is worse than no motion. Frame budgets come first.
Accessible by default
Semantic markup, keyboard paths and reduced-motion support are not extras.
Write it down
Docs, comments and naming are part of the deliverable.
Journey
How I got here, in four moves
Design first, then the web, then mobile, and now AI and automation. Each phase added a tool, but also a way of thinking about the work.
Phase 01
Early engineering
UI/UX & graphics foundations
Started out in the early engineering years doing visual design: posters and brand layouts first, then wireframes, user flows and screen specs. Designing before building never left the process, and it is why the interface still comes before the code on every project I take on.
- Wireframing
- Visual design
- Brand layout
- Figma
Phase 02
Web chapter
Frontend web engineering
Moved into web development and stayed: React.js and Next.js for single-page apps and marketing platforms, with component architecture, routing, caching and Core Web Vitals treated as part of the design rather than an afterthought.
- React.js
- Next.js
- TypeScript
- Tailwind CSS
Phase 03
Mobile chapter
Mobile development
Expanded into cross-platform mobile work with Flutter and Dart: clean architecture, Bloc and Riverpod state machines, offline-first storage and release builds that behave the same on both app stores.
- Flutter
- Dart
- Firebase
- Clean Architecture
Phase 04
Current focus
AI & automation systems
Currently going deep on AI integrations: LLM-backed product features, custom workflow automations with n8n, and agentic pipelines that take over the repetitive parts of shipping so the team can stay on the interesting parts.
- AI integrations
- n8n
- Agentic workflows
- Automation
Services
From the first wireframe to the last Core Web Vital
Most projects need more than one discipline. These are the areas I take full ownership of, and hovering a card shows how I actually work in it.
Mobile
Mobile apps
Production Flutter apps with clean architecture, offline-first data and pixel-tight UI.
Web
Web engineering
Next.js and React front-ends with real SEO, real performance budgets and real caching.
Design
UI/UX design
End-to-end interface design: user flows, wireframes and interactive Figma prototypes, plus the design system and handoff specs your engineers build from.
3D / Motion
3D & motion
Three.js, React Three Fiber and GSAP: interactive scenes that stay smooth on mid-range phones.
SEO
SEO systems
Technical audits, structured data, Core Web Vitals and content architecture that ranks.
Systems
Design systems
Reusable component libraries and tokens so a product looks intentional on every screen.
Available for H2 2026 Contracts
Haveaproduct,adeadline,andanimpossible-lookingbrief?
Open for projects, collaborations and virtual coffee chats. Send the technical requirements, Figma drafts, or napkin sketch, and I will reply with an architectural breakdown, realistic milestone roadmap, and high-impact execution plan.