- Home
- โปรเจกต์
- สำรวจตามสายงาน
- Tech Domain · Book Dev
Tech Domain · Book Devทั้งหมด
129 โปรเจกต์ในสายTech Domain · Book Dev
ตัวเลขเผยแพร่แล้วนับงานที่ใช้งานอยู่ เครื่องมือภายในไม่มีเดโมสาธารณะ ส่วนป้ายบนการ์ดบอกระดับหลักฐานของงาน
เลือกดูตามสายงาน
เลือกดูตามผลลัพธ์
129 โครงการ ในสาย Tech Domain · Book Dev · หน้า 1 จาก 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.
Keep personal events on one simple month calendar, with no account.
Juggling deadlines across projects meant switching between a bloated Google Calendar and ad-hoc reminders with no single visual view.
Run a recurring workflow from a ready checklist instead of from memory.
Recurring workflows like deployments and content publishing meant recreating the same steps by memory every time.
Try a contact form and inbox flow without signing up for a form service.
Third-party form tools add external tracking and per-site fees to every small project.
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.
Read an error trail from signal to context on one board.
Without a central view, bugs in small deployed apps surface only when a user reports them.
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.
Tick off a goal's milestones and see its progress, with no account and no backend.
Goal-setting tools were either bloated OKR platforms or plain checklists, with nothing light for tracking milestones in between.
Check off daily habits on a 14-day grid without creating an account.
Habit trackers were mobile-only or required an account just to track something as simple as a daily streak.
Draft a Thai-baht invoice and print it without signing up for accounting software.
Freelancers needed a quick invoice draft, but existing tools were either too complex or locked behind a subscription.
Move a task from to-do to done on a simple local board.
Full project-management tools were overkill for moving a handful of tasks through to-do, doing and done.
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.
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 upcoming reminders in view without creating an account.
Reminder apps were mobile-only or gated behind sign-up, adding friction to something as simple as a timed alert.
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.
Find and copy a reusable code pattern in seconds from one small catalog.
Frequently reused code — Docker configs, CI templates, CSS utilities — was scattered across repos and gists with no fast way to find it again.
Lay out service health and incidents on one page people can check.
Without a status page, users had no way to check if something was down without emailing to ask.
Keep who's involved, and their role, in one place.
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.
โปรเจกต์ส่วนใหญ่เป็นเว็บแอป Next.js แยก deploy อย่างอิสระบน Vercel ส่วนแอปมือถือพัฒนาด้วย Flutter