It started with a simple request

I buy games and software from different websites, sometimes in bundles. I want a small application where I can keep my activation keys and see which ones I have already used. Can you build something like that?

The discovery questions and answers below are an illustrative reconstruction based on the implemented product, not a transcript or client testimonial.

Ask the questions that shape the product

Where do the keys live today?

In spreadsheets, emails and text files. I sometimes forget what I have already activated.

The problem is fragmented information. A searchable collection needs a clear status for each individual code.

Which devices need access?

Just my Windows computer. I do not need an account or synchronisation.

We chose a local desktop application. No cloud backend, registration or internet connection is needed for the core workflow.

What does a bundle represent?

A purchase containing several titles. But I also buy individual games and sometimes receive another key for a title I own.

Titles, individual key records and optional bundles are separate concepts. Bundle names are reusable, and opening a bundle shows its records.

How will the app know a key was used?

I can mark it after activation. If I choose the wrong record, I need to correct it.

Copying never marks a code used. Status changes are explicit and reversible without losing the key, bundle, notes or dates. The app does not verify redemption online.

What if a code expires or has not arrived?

Some codes have a deadline. Sometimes I know the title but do not yet have the code.

Expiry is optional and uses a calendar date. Needs attention includes missing codes and unused keys expiring today through the next seven days.

How should the collection be protected and moved?

Keep it on my computer, but let me export it and import it again.

The database is encrypted locally. Codes stay concealed during browsing. JSON transfer requires an explicit export or a reviewed import; exported codes are readable and need careful storage.

Turn answers into testable user stories

  1. Organise my collection

    As a collector, I want to save each code with its title, platform and optional bundle so I can find it without searching old emails.

    What must work: Two keys for the same title remain separate records, and an individual purchase needs no bundle.

  2. Know what is still available

    As a user, I want to distinguish available, used and expired records so I know what needs my attention.

    What must work: Copying leaves the status unchanged. Used and already expired keys do not appear as upcoming expiry reminders.

  3. Find the right record

    As my collection grows, I want to search and filter by title, platform, bundle and status so I can select the correct copy.

    What must work: Opening a bundle scopes the Library to that bundle; choosing a title retains that scope.

  4. Correct ordinary mistakes

    As a user, I want to edit details and reverse an accidental used status without damaging the record.

    What must work: Confirmation restores availability and clears the used date while preserving other information. A past expiry still displays as expired.

  5. Keep control of my data

    As the owner, I want protected local storage and a deliberate way to transfer my collection.

    What must work: Browsing does not reveal codes. Import review explains additions and duplicate skips; cancellation changes nothing.

One complete journey, from purchase to use

  1. Create a bundle such as Indie Weekend and add Hollow Knight with its code. Leave expiry empty if there is no deadline.
  2. Add another copy from a different purchase. The title can be the same; the key record and its source remain distinct.
  3. Open the bundle or search the Library. Inspect the intended record and explicitly reveal or copy its code.
  4. Activate it on the relevant platform, then mark the record used in Pixel Pocket. The app records the user’s decision.
  5. Correct a mistake through the inspector. Export the collection when needed and review an import before confirming it.

Choose a complete first experience

The first useful outcome was dependable key management: add a record, preserve its source, find it again and record its use. We organised the interface around Overview, Library, Titles and Bundles, with smart views for available, expiring and missing keys.

The implemented application adds editing, saved views, batch actions, appearance settings and reviewed JSON import/export. An encrypted local database and explicit reveal/copy actions support the privacy requirement. The desktop layout adapts to a smaller window without changing the collection model.

Cloud synchronisation, automatic storefront redemption checks and a complete encrypted portable backup-and-restore system remain outside this implementation. Compatible JSON transfers collection data; it does not preserve appearance preferences or saved views.

Look beyond a screen that looks finished

The important checks follow the original problem: separate copies of a title must stay separate; editing one record must preserve the others; expiry must retain the selected calendar day; and a cancelled import must leave the collection unchanged.

The project includes regression coverage for database workflows, dates, status changes and data preservation. Those checks complement interface review; they do not replace native Windows release testing or establish a complete security audit.

A small application with a clear purpose

Pixel Pocket gives a private client one place to manage their activation keys, keep bundle information and see what remains available. No account is needed, and the collection stays on the device.

The project value is €500. Its value lies in a useful, coherent workflow shaped around one person’s needs. A customer does not need to arrive with a technical specification: describing the situation is enough to begin asking the right questions.