Nate B Jones distinguishes five common shapes for personal software: a local tool, a hosted web application, a native phone application, a background service and a hardware-bound system. The right choice follows from where the work happens, what must remain private and how often the user needs access.
Nate B Jones argues that building is only the beginning. Personal software still needs clear file ownership, security boundaries, testing and a maintenance plan, especially when it handles sensitive information or runs continuously without direct supervision.
Nate B Jones presents the framework as a way to avoid defaulting every idea into a web app. Choosing the smallest suitable shape can reduce complexity while preserving control over data and long-term operation.
Watch the original on YouTube