- Home
- Projects
Count page views and project clicks with PostHog (EU servers)? It loads only if you choose Allow. Privacy
23 projects in this portfolio, currently collected under Tech Domain · Book Dev — from web tools and mobile apps to internal systems.Focus: Growth & Conversion
Published counts projects that are running; internal tools have no public demo. Each label shows its evidence level.
Browse by outcome
23 projects in Growth & Conversion
Show honestly what a small digital shop has built before it opens.
Selling SVG bundles, templates, and presets needed a simple checkout, not the overhead of a full e-commerce platform.
Prototype a tip-jar flow for free tools before connecting a payment provider.
Free tools in the portfolio had no way to accept voluntary support, and setting up payment links per project wasn't practical at scale.
Keep each giveaway and its status in one searchable list.
Small giveaways run from scattered notes leave no clear record of what is open, drafted or closed.
Present a small set of projects from one data file instead of hand-built pages.
Presenting projects meant hand-building pages instead of rendering them from one data source.
Keep one clear list of the services you offer and which are available.
Freelance offers lived in scattered notes, with no single list of what was available.
Turn a scattered compliment into displayed social proof without editing HTML by hand.
Client testimonials arrived through emails and messages with no structured way to collect and publish them as social proof.
Try a simple seat-selection and reservation flow without a ticketing platform.
Full ticketing platforms charged per-ticket fees that ate into margins on small workshops and consulting sessions.
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.
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.
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.
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.
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.
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.
Keep certifications as tidy records with status, not a loose line on a resume.
Certifications listed as plain text were hard to keep current or tell apart by status.
Most projects are standalone Next.js apps deployed independently on Vercel. Mobile apps are built with Flutter.