01 · E-commerce website
Welllifehouse
Next.js
E-commerce experience for Welllifehouse, built with Next.js — product browsing, cart and checkout flows.
- Role
- [Add role]
- Year
- [Add year]
Open to opportunities — freelance & full-time
I build
thoughtful
digital products.
I build thoughtful digital products — from fast web experiences to mobile apps and the infrastructure behind them.
Bangladesh · Remote-friendly
React / Next.js / Flutter
Full-Stack Developer
Shihab Hossain
Web · Mobile · Infrastructure
Focus
Web · Mobile · Deployment
& the glue in between
01Selected Work
Shipped & shipping.
Real projects, real domains. Role, year and outcomes stay editable until Shihab supplies them — nothing here is invented.
02 · Website
Shwapnomart
Next.js
Next.js build for shwapnomart.com.
- Role
- [Add role]
- Year
- [Add year]
03 · Website
GetWayBD
WordPress
WordPress website for getwaybd.com.
- Role
- [Add role]
- Year
- [Add year]
04 · Website
Safeing House
Next.js
Next.js website for safeinghouse.com.
- Role
- [Add role]
- Year
- [Add year]
05 · Website
Ikhlas IT
Next.js
Next.js website for ikhlashit.com.
- Role
- [Add role]
- Year
- [Add year]
06 · Android application
Welllifehouse Android App
Flutter
Flutter application for the Welllifehouse e-commerce experience on Android.
- Role
- [Add role]
- Year
- [Add year]
No public link yet
In progress
07 · Web app
Talknest
Next.js
Upcoming Next.js project. Currently in progress — details will be published when it launches.
- Role
- [Add role]
- Year
- [Add year]
talknestbd.comLaunching soon
Artwork is abstract & replaceable — real screenshots drop into src/components/ProjectArt.tsx
02About
A builder who cares about the details.
Software is a craft — make it fast, make it honest, and make it something people enjoy using.
— Shihab Hossain
I'm Shihab Hossain, a full-stack developer working across the whole stack — from React and Next.js interfaces down to Node.js services, Flutter apps, and the Ubuntu servers, reverse proxies and Cloudflare rules that keep everything fast and online.
My approach is simple: understand the problem, design a solution that can be maintained, ship it in reviewable pieces, and measure what actually happened. I'm comfortable owning a feature from database to deploy — or dropping into one part of a team and doing that part properly.
I care about the unglamorous things that make products feel premium: performance, accessibility, predictable deployments, and honest communication about what is done and what is not.
Clarity before code
I like to understand the actual problem — users, constraints, trade-offs — before choosing tools.
Boring, reliable architecture
Typed code, small modules, documented decisions. The interesting part is the product, not the plumbing.
Ship, then refine
Small, safe releases with honest feedback loops beat big-bang rewrites.
Off duty
Shihab, away from the keyboard — the human behind the commits.
03Capabilities
What I can take off your plate.
Four focused areas, end to end — from the first wireframe to the running server.
Web Development
Marketing sites, e-commerce and web apps built with React & Next.js — server-rendered, accessible, fast on mid-range Android phones.
React · Next.js · TypeScript · Tailwind CSS
Mobile Apps
Cross-platform Android apps with Flutter — from UI and state management to store-ready builds and release handling.
Flutter · Android · Material UI
Backend & APIs
REST APIs and services with Node.js, Python or Rust — data modelling, auth, queues and integrations that stay maintainable.
Node.js · Python · Rust · PostgreSQL · Redis · Kafka
Deployment & Infrastructure
VPS & Ubuntu server setup, Docker, Nginx/Caddy, Dokploy, Cloudflare — plus n8n automations that remove repetitive manual work.
Docker · Kubernetes · Nginx · Caddy · Dokploy · n8n
Not sure which area fits your project? Describe it and I'll tell you honestly whether I'm the right person for it.
Scope my project04Tech Stack
The toolbox, organised.
Technologies I work with day to day. Grouped by discipline — no badge walls, no inflated self-ratings.
01Frontend
- React
- Next.js
- TypeScript
- JavaScript
02Backend
- Node.js
- Python
- Rust
03Mobile
- Flutter
- Android app development
04Data & Messaging
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Kafka
05Infrastructure
- Docker
- Kubernetes
- VPS & Ubuntu server setup
- Nginx
- Caddy
- Dokploy
- Cloudflare
06Automation
- n8n
Depth varies by area — ask me where I'm strongest, honestly.
05Experience
Where I've worked.
Latest engagement
Genex Infosys Ltd.— Grameenphone Digital
Role: [Add job title / role]
Dates: [Add start & end dates]
Duration: 6 months
Worked with the Genex Infosys Ltd. / Grameenphone Digital team for six months.
- [Add responsibility or achievement 1]
- [Add responsibility or achievement 2]
- [Add responsibility or achievement 3]
Role, dates and details are editable placeholders — supply real values in src/data/portfolio.ts
06Education
Foundations in electronics & CS.
01 / Education
BSc in Computer Science & Engineering
Northern University Bangladesh
[Add graduation year if you want it shown]
02 / Education
Diploma in Electronics
Bogura Polytechnic Institute
[Add completion year if you want it shown]
03 / Education
SSC
Dhawagirl High School
[Add completion year if you want it shown]
07How I Work
A process you can follow.
Six repeatable stages — the same discipline for a landing page or a multi-service platform.
Discovery
Goals, constraints, users, and what success actually looks like — before any code.
Architecture
Data model, routes, integrations, and deployment shape — designed to stay boring and maintainable.
Implementation
Typed, component-driven builds with reviewable milestones instead of one big reveal.
Testing
Critical paths exercised; accessibility, responsiveness, and edge cases checked.
Deployment
Dockerised services on VPS/Ubuntu with Nginx or Caddy, Dokploy, and Cloudflare in front where needed.
Iteration
Measure, learn, refine — small safe releases over risky rewrites.
08Blog
Notes from the build.
Short, honest notes on deploys, forms and infrastructure — the things I actually run. No newsletter pretense, just the archive.
2 min read
My deploy button is git push — and that's the point
This site goes live by pushing to GitHub. The Vercel build, the logs and the rollback all live in one place — here is the workflow and why I keep it that way.
Read the note
2 min read
A contact form that fails honestly
Most contact forms lie. Here is the pattern behind this site's form: server-side validation, a honeypot, and a 'not configured' state that tells the truth instead of faking success.
Read the note
09Featured Case Study
Welllifehouse, under the hood.
Template — awaiting real details
Welllifehouse — e-commerce built with Next.js
Next.js · Role: [Add role] · Year: [Add year]
- Challenge
- [Add the challenge]
- Process
- [Add the solution]
- Result
- [Add the outcome]
This is a working template, not a written case study. Shihab: replace the three placeholders in src/data/portfolio.ts (challenge / solution / outcome) and it becomes a real story.
10Beyond the Code
Off screen, honestly.
No invented hobbies here — this section is reserved for Shihab to fill in.
[Add interest #1]
[Add a short, honest line about it]
[Add interest #2]
[Add a short, honest line about it]
[Add interest #3]
[Add a short, honest line about it]
Edit the three entries in src/data/portfolio.ts — keep it real, keep it short.
11Currently Exploring
On the horizon.
Suggested focus areas — edit these to reflect what I'm actually exploring right now.
- [Editable] Rust for backend services & tooling
- [Editable] Kubernetes for small-team deployments
- [Editable] n8n automations for business workflows
- [Editable] Performance budgets on content-heavy Next.js sites
13FAQ
Honest answers, up front.
Services, process, timelines, maintenance and collaboration — no fine print.
Websites and e-commerce with React/Next.js or WordPress, Android apps with Flutter, backend APIs and services (Node.js, Python, Rust), and the deployment side — VPS/Ubuntu setup, Docker, Nginx or Caddy, Dokploy and Cloudflare. If your project needs something adjacent, ask — I'll tell you honestly whether it's a fit.
Discovery → architecture → implementation → testing → deployment → iteration. You get a short plan up front, reviewable milestones instead of a single big reveal, and honest status updates when something slips — which is normal in software.
It depends on scope — a brochure site and a multi-service platform are different animals. After a short discovery I'll give you a realistic estimate with clear assumptions. I don't promise fixed timelines for open-ended work, and I won't pretend an unclear brief has a clear deadline.
Yes, on request. Scope and terms are agreed per project before work starts — content updates, monitoring, small features, or on-call fixes. I'll always tell you what I can commit to rather than agree to everything and disappear.
Async-first: clear written updates, milestone demos, shared docs and a single source of truth for tasks. Time-zone overlap is arranged for calls. You always know what happened this week and what happens next.
A short brief: goal, audience, references you like, must-have features, and who makes decisions. Existing content, branding and access to any accounts (hosting, domain, CMS) should be ready by kickoff to avoid stalls.
Yes — after a short technical audit I'll tell you whether I can be productive there. I won't rewrite your stack for the sake of it, and I'll flag risks plainly if the codebase needs love first.
14Contact
Have a project in mind? Let's build it.
Tell me about the outcome you want — a faster site, a launch-ready app, infrastructure that doesn't wake you at 3am. I'll reply with a straight answer: how I'd approach it, or whether I'm not the right fit.
I read every message and reply as soon as I can.