- Home
- Projects
129 projects in this portfolio, currently collected under Tech Domain · Book Dev — from web tools and mobile apps to internal systems.
Published counts URLs that respond; each project label shows its evidence level.
Browse by outcome
120 projects · page 4 of 5
Take a break with a classic game, no ads and no account.
Browser mini-games for a quick mental break were hard to find without wading through ads or paywalls first.
Revisit a course concept without re-watching the whole course.
Notes from online courses were scattered across Notion, Docs, and local files, making it slow to find a specific concept again.
Search across 45+ knowledge domains from one place instead of 45 separate repos.
Knowledge was scattered across 45+ domain-specific repositories with no unified way to search or cross-reference between fields.
Follow a learning path with prerequisites, not a random string of tutorials.
Self-directed learning meant jumping between tutorials and docs with no clear progression, leaving gaps in the foundation.
Track a reading goal without creating an account for it.
Reading trackers were mobile-only or required sign-up just to log a book and see a streak.
Find a dev reference instantly instead of remembering which browser tab it's in.
Developer references — cheat sheets, tool links — were bookmarked individually across browsers, hard to find mid-debug.
Keep one useful phrase in view long enough to say it, choose it, and use it.
Language practice becomes diffuse when the phrase, its context, and the learner's next action live in separate surfaces.
See why the answer works instead of receiving a number with no path to it.
Math explanations lose their teaching value when the givens, diagram, and next reasoning step are separated or hidden behind a result.
Browse cognitive biases and behavioral patterns without a psychology degree.
Psychology knowledge stayed locked in textbooks and journals, inaccessible to non-academics curious about human behavior.
Look up case law and compliance basics without a database subscription.
Legal research for small businesses and freelancers required expensive database subscriptions just to check basic compliance requirements.
Keep a permanent record of a launch instead of losing it to a social feed.
Project launches and milestones had no home besides ephemeral social media posts that were hard to reference later.
Track a collaboration request without losing it in an inbox.
Collaboration requests arrived through email, social media, and GitHub issues with no unified way to track or evaluate them.
Add comments to a page without a third-party tracker riding along.
Third-party comment systems added tracking, ads, or fees across 100+ pages just to let readers leave a comment.
Give users a place to discuss a project, not just file a bug.
Portfolio users had no way to discuss projects or share use cases — GitHub issues were only built for bug reports.
Show which repos actually matter, not just a raw list.
A GitHub profile lists repos but tells no story about which ones matter or how they connect to real work.
Let a visitor say hello without the weight of a formal contact form.
Visitors had no lightweight way to leave feedback — a contact form felt too formal and social media too public.
Build what users actually vote for, not what seems like a good idea.
Feature requests arrived through scattered channels with no way for the community to signal what mattered most.
Give a historical thread enough context to make the next object worth opening.
Historical browsing often jumps between dates without giving each object enough context to form a question.
Generate a Thai-compliant contract without paying for a lawyer's first draft.
Freelancers and small businesses needed legal templates but couldn't justify lawyer fees for basic Thai-specific documents like NDAs.
Get an entry point into philosophy without starting with a 400-page textbook.
Philosophical knowledge stayed locked in dense academic texts with no accessible starting point for a curious reader.
Compare religious traditions side by side with neutral, academic framing.
Understanding comparative religion meant reading multiple dense texts with no structured, neutral way to compare beliefs and practices.
Make the variable visible so the observation can be discussed.
Science concepts are easier to discuss when the input, response, and observation are visible together.
Most projects are standalone Next.js apps deployed independently on Vercel. Mobile apps are built with Flutter.