Independent Products
Independent software · Case study
Independent Products
From a real need
to working
software.
I design and develop applications for my work and home. I carry each product from its purpose and workflow through UX, visual design, data integration, implementation, and continued improvement.
16 products. One connected practice.DESIGN DEVELOP REFINE
Design Engineer
5 categories
& development
to present
01 / The starting point
Software shaped by problems I needed to solve.
A vehicle break-in led to Secure. A failed Bluetooth keyboard led to TypeBridge. Reviewing project media led to Visual Image Browser and Forge. Each application began with something I needed to understand or do, then grew through design, development, and actual use.
The challenge was to make the interface, data, controls, and application behavior work together around a clear task. A person needs to know what they can do, what the software is doing, and what result to expect.
I work in Xcode and VS Code. My process includes AI assistance alongside direct code review, modification, integration, debugging, and functional testing. I remain responsible for the product decisions and resulting behavior.
02 / The collection
Sixteen applications.
A purpose behind each one.
Explore the products by category.
Select any app for its purpose, ownership, and workflow.
Showing all 16 products.
PC Health and Mac Health are presented as one family. Secure is the camera-system foundation within AEGIS.
16 / 16 featured products03 / Selected work
Where design decisions
become application behavior.
A closer look at the problems, choices,
and working interfaces behind the collection.
StackLensConnect observations to useful decisions.
StackLens starts with a website URL and organizes publicly observable signals. An inspection of my own site shows how the application turns technical information into findings and suggested next steps.
Separate Anatomy from Analyst. Anatomy supports structural inspection; Analyst organizes strengths, concerns, and an action plan.
A website URL and publicly observable signals.
Separate the site's structure from findings and suggested actions.
Make it easier to understand what deserves attention.
Secure → AEGISFrom a security need to a home-control system.
A vehicle break-in led me to build Secure around monitoring, recording, and footage review. AEGIS expands that foundation into accounts, access, weather, service availability, and continued operation.
Monitoring expanded into a broader system with invite-only accounts, Standard, Main, and Admin roles, weather, service availability, and configured remote access.
Observe, record, return.
Secure connects viewing areas, day and night monitoring, sensing conditions, recording timeframes, and footage saved to selected drives.
Make each control mean something.
Stopping a viewing session, closing a window, and quitting have distinct consequences. Those differences belong in the experience because they affect ongoing operation and recorded material.
Connect access and context.
AEGIS brings camera workflows into the same product context as household access, system attention, and the information needed to act.
Interaction across devices
Keep the destination clear.
Make the response useful.
Related needs. Different product boundaries.
TypeBridgeA new input path when
the keyboard fails.
When my Bluetooth keyboard stopped working, I needed another way to use my computers. I designed and developed TypeBridge to direct input from the device in my hand to the computer I need to control.
Typing, pointer control, and sharing each have a focused workspace. The destination remains visible across all three.
Scroll across to explore Type, Mouse, and Share.
When delivery is uncertainA closer look at the recovery decision
Recovery feedback
Check the result before trying again.
The recovery screen explains that an action may have arrived and that nothing resends automatically. I added a check of the receiving computer before another attempt could repeat an action.
DeskBridgeCarry a working session
across devices.
I built DeskBridge for Mac-to-PC and PC-to-Mac control, typing, and file transfer, then created an iOS application in Xcode for iPhone access. Tailscale is part of the configured outside-home access setup.
The workspace brings device selection, connection state, remote interaction, and session controls into one working context.
Keep the next step visible.
A saved computer remains available, while “Not connected,” “Offline,” and the Connect action make the current session state clear.
Give each task a place.
Devices, Sessions, Transfers, and Security organize the work around choosing a machine, operating it, moving files, and reviewing access.
Separate settings from measurements.
Session controls describe what the person can configure. Stream details show measurements when available and remain empty in the disconnected view.
Flexible workspace.The expanded sidebar makes task names and example Asus and Mac saved connections visible. The compact rail in the main workspace leaves more room for the remote computer.
their session context.Clipboard sync, remote input, reconnect, file actions, and stream information are grouped by purpose. The interface keeps configuration and connection feedback distinct.
ForgePrepare media.
Keep control of the work.
I needed a direct way to reduce image and video file sizes within my own workflow. Forge gives that recurring production task a focused place, with controls connected to the output I need.
Visual Image Browser complements that work by helping me locate and review images, GIFs, and videos in selected project folders.
Actual project files move from review to preparation, with an interface shaped around the next task.

Principle Atlas
Design-system knowledgeProduct judgment
Define completion around the intended task.
An early Principle Atlas implementation collected sources and summaries, but the experience did not yet provide the structured guidance I wanted. I revised the product direction around browsing, understanding, and applying that knowledge.
“A successful build is one checkpoint. The product still has to help someone do the intended work.”
The revision connected information architecture to a more meaningful standard for product completion. The application view below brings systems, categories, source tracking, and coverage information into a shared workspace.
The selected design system provides context, categories organize the guidance, and source links keep the supporting material close. Coverage and change indicators give review work a visible place in the experience.
04 / A connected practice
Purpose, information,
control, and response.
The same questions guide the work,
even when each product has a different answer.
Start with a useful task
Define the need, the action someone wants to take, and what completion means. That purpose sets the product's boundaries.
Give data a clear role
Connect each file, reading, account record, or observed signal to a question the application helps someone answer.
Design the state and response
Make the destination, progress, result, or uncertainty understandable. Feedback is part of the implemented interaction.
Refine through use
Investigate failures and confusing behavior, revise the implementation, and return to the experience to check the result.
The interface makes the system understandable.
I use hierarchy, labels, grouping, spacing, typography, and emphasis to express relationships. In data-heavy products, the presentation connects information to a useful question. In remote tools, it keeps the destination and response clear. Visual quality and application behavior contribute to the same task.
05 / Practical outcomes
Tools I can use for the work that created them.
The collection gives me direct ways to review media, process files, control computers, monitor recordings, understand system readings, and manage information. Continued use creates the next product decision: a state to clarify, a workflow to improve, or a boundary to reconsider.
Practical problems translated into product scope
Design decisions carried into application behavior
Information organized around actions and decisions
Ongoing responsibility for testing and refinement
Design and development, connected.
I design the experience, develop the behavior, and improve the product through use.
This collection complements my work across AppFuzer, Nike, Zillow, and other professional settings with a direct view of my application-development ownership and technical judgment.
Selected implementation details remain private. I can discuss relevant decisions and tradeoffs in an interview.