Sketch, Wireframe, Mockup, Prototype - What Are They and Examples
Explaining and distinguishing four important terms in UI/UX design and software development: Sketch (quick idea drafting on paper or whiteboard), Wireframe (basic skeleton describing app flow), Mockup (adding design elements like colors and fonts to wireframe), and Prototype (interactive sample). With specific examples and appropriate tools for each design stage.

Related Posts
Discover more content you might enjoy

1DevTool: The Developer Cockpit I Built Because I Was Drowning in Windows
I was running Claude Code, Codex, and Gemini CLI in three different terminals, plus VS Code, Chrome, Postman, and TablePlus — just to ship one feature. So I built 1DevTool: one window per project, every AI agent in one place, everything persists.

Server Compass: Why I Built a Desktop App to Turn Any $5 VPS Into My Own PaaS
I was tired of paying $20+/month for Vercel and Railway, but also tired of self-hosted panels eating 2GB of RAM on my $5 VPS. So I built Server Compass — a desktop app that connects to any VPS over SSH and gives you the full power of a managed PaaS, with zero server overhead and one-time pricing.

Accidentally Building a Blogging Platform
I hadn't written blog posts for a long time and realized I was too dependent on AI. To rebuild my writing habit and think more clearly, I decided to build a writing platform: write.rocks.

Vibe Coding - Rebuilding My Blog from Scratch and Rebranding to khoa.blog
Detailed walkthrough of rebuilding a blog from scratch with vibe coding, from data migration to implementing new features, helping readers understand the personal blog development process.

The Fastest Way to Succeed
Sometimes the simplest answer is the most correct one. This short but powerful post reminds us that there are no shortcuts to success - there's only one word: Practice. Persistence and continuous training are the secrets to overcoming all challenges.

Day 25 - Profitable MVP in 30 Days - Never Give Up
Day 25 of the profitable MVP challenge where I admit ReadingPointer's failure - user retention is extremely low and no one cares about the paid features. Sharing lessons learned including targeting users with higher willingness to pay, challenges of building cross-browser extensions, and difficulties turning scientific methods like speed reading into products.