Cataloging 22 Apps So I Stop Losing Track

Cataloging 22 Apps So I Stop Losing Track

As a solo developer and studio operator, keeping track of all the applications and extensions you’ve built can be a daunting task. This is especially true when you’re juggling multiple projects across different platforms like Tauri for desktop tools, Chrome extensions, and web-based landing pages. To stay organized and ensure nothing falls through the cracks, I’ve been meticulously cataloging my work in APPS_CATALOG.md. Here’s how this process has evolved and what it means for managing a diverse portfolio of projects.

The Cataloging Process

Creating an exhaustive list of all applications and extensions is crucial for maintaining clarity and efficiency. My APPS_CATALOG.md file serves as the central repository where I document every product, including its status (submitted vs in-development), platform specifics, and any relevant links or references. This approach ensures that no matter how many projects are in motion, I can quickly reference what’s been completed and what needs attention.

For instance, when working on a new Tauri desktop tool like gnomad-slate, the catalog helps me keep track of its development stages, from initial concept to final deployment. Similarly, for Chrome extensions such as gnome-capture or midnight-gnomad, having this centralized documentation allows me to manage updates and user feedback more effectively.

Tools and Extensions

The apps I’ve built span a variety of functionalities and platforms:

• Tauri Desktop Tools: These include gnomad-slate for note-taking and project management, and gnomad-desktop-assistant for task automation.
• Chrome Extensions: A suite of extensions like gnome-capture, gnome-kan-do, and midnight-gnomad offer features ranging from screenshot capture to productivity enhancements.

Each entry in the catalog includes detailed information about the tool’s purpose, current status, and links to its source code or live demo. This level of detail is invaluable when collaborating with others or revisiting projects after a period away.

Landing Pages and Integration

In addition to documenting individual applications, I’ve also created landing pages for each product on davidcole.cloud/apps. These pages serve as public showcases where users can learn about the features and benefits of each tool. For example:

• Slate: A Tauri-based note-taking application with a sleek interface.
• Webcanvas Preview: An experimental web-based canvas editor using modern JavaScript frameworks.

Update (Jun 2026): Slate and Webcanvas both shipped major desktop updates — Slate three platforms and Webcanvas Windows alpha.

By integrating these landing pages into my catalog, I ensure that all relevant information is easily accessible to both users and potential collaborators.

Lessons Learned

One of the key lessons from this process has been the importance of maintaining clear documentation throughout development. Initially, I found myself scrambling to remember details about various projects as they progressed through different stages. By adopting a systematic approach with APPS_CATALOG.md, I’ve significantly reduced confusion and improved my ability to manage multiple projects simultaneously.

However, there’s always room for improvement. In the future, I plan to implement more automated tools that can help update the catalog in real-time as new features are added or bugs are fixed. This would further streamline the process and ensure that all information remains current without requiring manual updates.

Next Steps

Looking ahead, my next step is to enhance the integration between APPS_CATALOG.md and other project management tools I use. By creating bidirectional links and automating certain update processes, I aim to make the catalog even more dynamic and responsive to changes in my development workflow. This will not only help me stay organized but also provide a better experience for anyone who relies on these resources.

In summary, cataloging 22 apps has been an essential exercise in maintaining clarity and efficiency as a solo developer or studio operator. By keeping detailed records of each project’s progress and features, I can ensure that no effort goes unnoticed and every tool reaches its full potential.