Why a launcher and sticky notes belong together.
The idea behind QuickPeach: a small place to act on something or keep it nearby.
QuickPeach combines a keyboard launcher with sticky notes. At first, those might seem like two unrelated features. A launcher helps you do something. A note helps you remember something. But they meet at a similar moment: you are already working, and something small needs your attention.
Sometimes that means running a command. Sometimes it means keeping a line of text nearby. Sometimes it is a thought that matters enough to capture but not enough to turn into a document.
The design starts with those small interactions rather than a large workspace.
Two kinds of interaction
The launcher is for something you want to do now. You bring it up, type a query, and choose an action. Its interface needs to make the next step obvious.
The sticky note has a different purpose. It holds something beyond the current interaction. You are not necessarily searching for it or acting on it immediately; you just want it to remain available.
That difference matters. A launcher should not ask you to organize everything before you can use it. A sticky note should not require you to know exactly what a thought will become before you can save it.
Putting them together gives QuickPeach a useful distinction: some things are actions, and some things are material you want to keep around. They do not need to behave the same way to belong in the same product.
Why start with a hotkey and a query bar?
A hotkey gives the launcher a direct entry point. The query bar gives the interaction a clear focus: type what you are looking for or what you want to do.
I want that first interaction to remain small. Opening the product should not mean deciding where to navigate before doing the thing that brought you there.
That also creates a constraint on the interface. The input needs to be easy to find, its state needs to be clear, and the results need to make sense in relation to what was typed. The surrounding design should support that interaction rather than compete with it.
The small interface is not the entire goal. The goal is to avoid adding unnecessary steps around a small task.
Why give the notes a different visual character?
The sticky notes are the less structured part of the product. They are meant for text that can remain informal: a reminder, a snippet, or a thought still being worked out.
That is where the paper-like appearance and handwriting treatment fit. They give the notes a different character from the query bar without making them feel like a separate application.
The distinction should remain functional. The launcher needs to read clearly as an input for actions. The notes need to remain comfortable to read and edit. A visual metaphor is useful only while it helps those jobs.
The same applies to the peach color. It can give QuickPeach a recognizable appearance, but it does not explain the product by itself. The relationship between the launcher and the notes matters more than the story behind a hex code.
Keeping the idea clear as the product grows
The design question I want to keep returning to is straightforward: does this feature help someone do a small thing or keep something useful nearby?
That is a more useful constraint than trying to make the product look minimal. An interface can look simple while still asking too much of the person using it.
For QuickPeach, the starting point is one hotkey, a query bar, and sticky notes. The work is in making those pieces feel connected without erasing what makes each one useful.