nexa
ExploreServicesAboutTeamFAQBlogContact
GitHubStart a project
Blog · Process

The features we said no to in an image and PDF tool

Quick Image PDF Resizer could have become an editor. Keeping a written list of things it will not do kept it fast and easy to explain.

Ethan

Tech Lead · Mobile & Web

January 8, 20262 min read

On this page

  1. The one-sentence purpose
  2. The decision log
  3. How a request moves through the log
  4. Why write it down at all
  5. The log is not permanent

Utility apps grow by default. Someone who resizes images also wants to crop them, then add text, then apply filters, and soon the app is a worse version of a full editor. For Quick Image PDF Resizer we kept a written decision log instead. This post shares it, lightly edited.

The one-sentence purpose

Quick Image PDF Resizer

Make files the right size and format for wherever they need to go, quickly, on the device.

Every request gets checked against that sentence. If it helps the job, it is a candidate. If it changes the job, it needs a real discussion.

The decision log

RequestDecisionReason
Resize to an exact file sizeYesThe core job: upload limits are usually in kilobytes
Convert HEIC to JPGYesFormat compatibility is part of "the right format"
Merge and split PDFsYesForms often need pages combined or removed
Simple cropLaterHelps the job, but only once resize is polished
Filters and colour tweaksNoEditing, not preparing a file
Text and stickersNoA different app entirely
Cloud folders and accountsNoBreaks "on the device"
Edit text inside PDFsNoHard to do well; heavier tools exist

Requests we heard

  1. Filters and colour adjustments
  2. Text and stickers
  3. Cloud folders and accounts
  4. Editing text inside PDFs

What shipped

  1. Resize and compress
  2. Convert formats
  3. Merge, split and extract PDF pages
  4. Everything processed on the device
The log is what kept the right-hand column short.

How a request moves through the log

  1. Request arrivesReview, email or our own wish
  2. Check the sentenceHelps the job, or changes it?
  3. Log a decisionYes, later or no, with one reason
  4. Revisit rarelyOnly with new evidence
The decision is written down once, so the same debate does not happen twice.

Why write it down at all

Saying no is easy when you are tired and hard when a request is reasonable. A written log takes the decision away from whoever happens to be in the conversation, and the one-line reasons stop the same debate recurring every few weeks.

A short app is easy to explain in one sentence. That sentence is also the store listing.

The log is not permanent

A few items have moved from "later" to "yes" when enough people needed them for the core job. Each move was a decision, not a drift, and the app still does what its name says.

Mentioned in this post

Quick Image PDF Resizer

Case study

Work with us

Need an app like Quick Image PDF Resizer built?

Our services

Keep reading

All posts
  • AI can design an app now. Are designers redundant?
    Read post

    Design

    AI can design an app now. Are designers redundant?

    AI makes the first draft of a screen cheap. That shifts design work to what matters most: understanding users and choosing what is right for them.

    Tina· Oct 10, 20266 min read
  • AI in software development: turn change into an advantage
    Read post

    Engineering

    AI in software development: turn change into an advantage

    AI does not replace technical thinking. With the right process, it frees teams to focus on the decisions that make products better.

    Ethan· Oct 9, 20264 min read
  • Adding AI to an app without a surprise bill
    Read post

    Engineering

    Adding AI to an app without a surprise bill

    Most of the cost of an AI feature is decided before the first request. Model routing, caching, context size and hard limits, in order of impact.

    Ethan· Oct 7, 20267 min read
nexa
ExploreServicesAboutTeamFAQBlogContact

© 2026 Nexa Tech. All rights reserved.

Web · Mobile · Open source