Compress-it started from recurring file-size limits in presentations, websites, and sharing moments, then kept improving as new real needs appeared.
File limits usually appear at the worst time: when sending an email, uploading to a site, preparing a deck, or trying to share media quickly. Existing tools often add ads, limits, registration, privacy questions, or slow processing right when the task should be simple.
I do not come from a formal coding background, so the challenge was not only building the tool. It was learning how to break the problem into steps, decide what mattered first, and keep improving the product when a new file type or size exposed a gap.
I used AI as a build partner to map the compression process and create a web tool for common image needs. When heavier files showed the limits of the browser, I also explored a desktop direction instead of forcing one version to solve every case.
Compress-it became a weekly helper for preparing assets and working around file limits. More importantly, it changed how I approach tool building: when something blocks the work, I can shape a focused tool around the need instead of giving up on the task.