Practical Software Builder
I build real-world apps, experiment with AI-assisted development, and document the decisions, problems, and lessons behind each project.
01 // Featured Projects
Voice-first project memory powered by AI.
A mobile app for capturing project ideas, voice memos, and text notes, then turning them into summaries, action steps, reports, coding-agent handoffs, and other structured project outputs.
Guest photo sharing for weddings and events.
A QR-based event photo platform where guests can upload photos from an event, event creators can manage private galleries, accept payments, protect events with passcodes, and download all guest photos as a zip file after the event.
Stay in flow across phone, Mac, and Windows.
A private cross-device productivity system that connects my Android keyboard, Mac notch dropdown, and Windows utility through shared text sync. It helps me move project context, prompts, and useful text between devices without breaking focus.
02 // How I Build
I use AI-assisted development to move faster, but the goal is not just generating code. I focus on understanding the problem, shaping the product flow, testing the result, cleaning up what becomes messy, and documenting what I learn from each build.
Most of my projects begin with a problem I have actually felt — losing project context, moving text between devices, or making event photo sharing easier.
I try to understand the user flow before building: what someone needs to do, where the friction is, and what the simplest useful version should include.
I aim for a working product first, then improve the structure, interface, and reliability through iteration.
I use AI-assisted coding tools to prototype, explore implementation options, and move faster while staying focused on understanding what the code is doing.
The first version is rarely the cleanest version. I try to improve messy areas, reduce fragile code, and keep the project easier to change over time.
Each project becomes a record of what I learned: decisions, mistakes, fixes, trade-offs, and what I would improve next.
03 // Latest Build Notes
ProjectDrop / AI workflow
ProjectDrop started as a way to capture voice notes and text ideas, but the coding-agent handoff feature changed the direction of the product.
Read noteFlowDock / Product design
The first version was about moving text between devices. The more useful idea was reducing the friction of switching between phone, Mac, and Windows while keeping project context close.
Read noteQR Event Photo Platform / Architecture
Starting with HTML/CSS was useful at first. Migrating to a modern stack taught me why architecture choices matter early.
Read note04 // Learning Log
SQL / Database fundamentals
Learning relational database design helped me understand how real apps connect users, projects, events, uploads, and permissions without everything becoming messy.
Read entryBackend fundamentals / MVC
Working through Flask made the MVC pattern feel more practical: routes receive the request, coordinate the logic, and decide what view or response should come next.
Read entryAI workflows / Product thinking
Building with LLM APIs has shown me that useful AI features need structure, constraints, and clear output formats - not just a prompt box and a response.
Read entry05 // About
I’m Scott — a practical software builder who likes turning real problems into working tools.
Most of my projects start from friction I’ve felt myself: losing project context, switching between devices, organising notes, or simplifying a workflow that should feel easier. I use this site to document those builds, the technical ideas I’m learning, and the lessons that come from each iteration.
I’m especially interested in AI-assisted workflows, mobile tools, full-stack products, and software that helps people stay organised, focused, and moving.
06 // Contact