Development and architecture
core dev
The main developer responsible for the concept, code, and assembly of utilities.
- Windows desktop tools,
- scripts and automation,
- internal tools for business.
SmallSoft is not a corporation or a giant team. It is a small project and a few people who love to make neat, understandable, and useful utilities for real tasks.
We ourselves work extensively with files, websites, documents, and automation. Hence SmallSoft’s philosophy: “one utility — one clear task.” No imposed telemetry, cumbersome installers, or enormous menus.
Each program in the catalog appeared not just for the sake of it, but because of a specific problem: we needed to check the website for broken links, compile a PDF from multiple scans, and organize the chaos in our file folders — that’s how 404Finder, MassPDF, FileSorter, and other utilities were born.
We strive to adhere to several simple principles in each tool:
The project is backed by one main developer and several people who help with testing, ideas, interface, and texts.
core dev
The main developer responsible for the concept, code, and assembly of utilities.
real world use
Several people who use the utilities “in battle” and help find weak spots.
docs & UX
Sometimes those who help pack utilities join the work: descriptions, screenshots, pages.
We don’t strive to do “everything for everyone.” SmallSoft is a set of neat tools, not just another combine harvester.
A program should solve one problem well, not ten problems poorly.
No hidden “surprises” inside the utilities.
We make what we use ourselves.
No aggressive marketing or intrusiveness.
Most programs were born out of very specific tasks. The approximate path looked like this:
Our utilities are useful for those who value their time and dislike redundant systems.
Need quick tools at your fingertips: website testing, file management, minor automation tasks.
When you haven’t grown into a “corporate system” yet, but chaos is already getting in the way of your work.
Those who like order in their files, documents, and processes — and appreciate neat utilities.
Feedback helps us understand what utilities are needed next and what needs to be improved. Write a few lines — it’s really helpful.