Tech Domain · Book DevProjects
129 projects in Tech Domain · Book Dev
Published counts URLs that respond; each project label shows its evidence level.
Browse by domain
Browse by outcome
129 projects in Tech Domain · Book Dev · page 1 of 6
Compare a small set of properties before you commit to a purchase.
Property comparisons often mix asking price, rent, yield, and cash commitment without one clear decision surface.
Turn one broad growing season into the next useful field visit.
Crop decisions become hard to act on when crop notes, growing windows, and the next task live in separate places.
Run trading strategies on paper before a single dollar is at risk.
Testing DCA, grid, and prediction-market strategies with real capital meant no proof they worked before money was on the line.
See every project's schedule in one calendar, not six different apps.
Juggling deadlines across projects meant switching between a bloated Google Calendar and ad-hoc reminders with no single visual view.
Turn a one-time workflow into a checklist you can run again in seconds.
Recurring workflows like deployments and content publishing meant recreating the same steps by memory every time.
Give every project a contact form without paying a third-party service per site.
Embedding third-party form tools across 100+ projects meant external tracking and monthly fees multiplying with every new project.
Sell a digital download without building a full storefront around it.
Selling SVG bundles, templates, and presets needed a simple checkout, not the overhead of a full e-commerce platform.
Let people support free tools without putting them behind a paywall.
Free tools in the portfolio had no way to accept voluntary support, and setting up payment links per project wasn't practical at scale.
See every error across 100+ apps in one place instead of waiting for user reports.
With 100+ deployed apps, the only way to learn about a bug was a user reporting it days later.
Run a giveaway with a winner-selection process people can actually trust.
Picking giveaway winners by hand looked biased and didn't scale to repeated promotions.
Break a big goal into milestones without the overhead of enterprise OKR software.
Goal-setting tools were either bloated OKR platforms or plain checklists, with nothing built for tracking milestones in between.
See a habit streak the way GitHub shows a contribution graph.
Habit trackers were mobile-only or required an account just to track something as simple as a daily streak.
Generate a client invoice without signing up for accounting software.
Freelancers needed a quick professional invoice, but existing tools were either too complex or locked behind a subscription.
Adapt a kanban board to how a project actually works, not a fixed template.
Different projects needed different workflows, and most task boards forced everything into the same rigid column structure.
Start a focus session without installing an app or making an account.
Pomodoro timers were either native apps or web tools bloated with sign-up flows just to start a 25-minute timer.
Give a client a branded project showcase without building one from scratch each time.
Client projects needed a professional presentation separate from the main portfolio, and building one per client took hours of manual setup.
Get a browser reminder without creating an account first.
Reminder apps were mobile-only or gated behind sign-up, adding friction to something as simple as a timed alert.
Let a client pick a service tier instead of waiting on a custom proposal.
Every freelance inquiry meant writing a custom proposal from scratch, which slowed down how fast a lead could become a client.
Find a reused code pattern in seconds instead of digging through old repos.
Frequently reused code — Docker configs, CI templates, CSS utilities — was scattered across repos and gists with no fast way to find it again.
Show service uptime publicly instead of fielding outage emails one by one.
With 100+ services running, users had no way to check if something was actually down without emailing to ask.
Know who's working on what without asking around.
As collaborations grew, there was no single source of truth for who was on a project or how to reach them.
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.
Most projects are standalone Next.js apps deployed independently on Vercel. Mobile apps are built with Flutter.