- Home
- Projects
- Explore by Domain
- Tech Domain · Book Dev
Tech Domain · Book DevProjects
129 projects in Tech Domain · Book Dev
Published counts projects that are running; internal tools have no public demo. Each label shows its evidence level.
Browse by domain
Browse by outcome
129 projects in Tech Domain · Book Dev · page 2 of 6
Add a task in seconds without opening an account-gated app.
Existing task managers were feature-rich but overkill for jotting down something quick without syncing to a cloud account.
See at a glance which endpoints answer, on one quiet board.
Commercial uptime monitors charge per site, which adds up for a portfolio of many small domains.
Find a published note or draft in one small reading list.
Drafts and published notes were scattered, with no single list to browse.
Keep the next action visible across a small freelance opportunity pipeline.
A pipeline is only useful when the current stage and next action can be read without dashboard noise.
Keep recurring solo-operations work outside the operator's memory.
Recurring solo-operations work depended on remembering the right steps in the right order.
Study strategic principles through short campaign-pattern briefs instead of scattered book excerpts.
Military history and strategic-thinking resources were spread across books and sites with no single searchable place to study them.
Carry one clear book promise through a focused editorial campaign.
Turning one book idea into a sensible order of things to publish was easy to lose across separate notes and channels.
Practise reading an A/B split before paying for an experimentation tool.
Enterprise A/B testing tools are priced for teams, and a solo builder rarely gets to practise reading a split before running one.
Read a quick summary of an events export without setting up an analytics stack.
Answering a simple question about an events export (how much, when, which segment) usually means a spreadsheet or a full analytics tool.
Show what a per-link click report could look like before wiring up real tracking.
URL shorteners often show a raw click counter, with no simple read of which link drew attention over a time window.
Show how a 'most visited' board could guide visitors to the useful pages.
A portfolio with many projects gives visitors no signal about which pages are worth their time.
Check a page's basic on-page SEO in seconds instead of reading the markup by hand.
Checking titles, descriptions, headings and alt text by hand on every new page was slow and easy to skip.
Keep everything you are watching, reading or playing in one list with status and progress.
Progress on shows, books and games was spread across separate apps and memory, with no single list of what was in progress or done.
Show visits as dots on a map instead of a country-code table, as a design study.
Standard analytics show country tables with no visual way to read where visits gather.
Find a past newsletter issue by topic instead of scrolling an inbox.
Past newsletter issues were hard to find again once they had left the inbox.
Show how a calmer reading desk for AI and dev news could work.
Staying current on AI and web-dev news meant scanning many feeds by hand with no simple read/saved state.
Keep press mentions and pitches in one findable list.
Press mentions and pending pitches were scattered across LinkedIn, email and notes.
Follow a staged learning path instead of piecing one together from scattered lists.
Career learning paths were spread across blog posts and lists, with no staged view of what to learn first.
Share a structured book review instead of a scattered Goodreads note.
Book recommendations lived across social posts and personal notes with no structured way to share what a book was actually good for.
Keep release notes in a readable list instead of digging through commits.
Release notes were buried in commits or missing, with no simple list of what changed.
Show how daily reflections could be kept apart from polished blog writing.
Daily reflections and idea sketches had no home that wasn't either a public blog post or a private notes app.
Run a link-in-bio page without a third-party service's branding on it.
Social bios only allow one link, and third-party link aggregators added their own branding and tracking to the workaround.
Most projects are standalone Next.js apps deployed independently on Vercel. Mobile apps are built with Flutter.