FEEDBACK
First, a safe way to hear your feedback.
Once feedback collection is approved, we plan to use observations from real use to guide bug fixes, usability improvements and new app ideas.
WHAT TO SHARE
The kinds of feedback we plan to listen to
You do not need a finished solution. Describing a moment and what could have been easier is a useful beginning.
Bugs
Situations where an app stops or behaves differently from what you expected.
What you were doing when it happened
Usability difficulties
Places where a feature or sequence is unclear and the next step is hard to find.
What guidance would have helped
Everyday friction
Tasks that work, but feel cumbersome or require repeated effort.
Which steps are often inconvenient
Feature suggestions
Additions that could make an existing app more useful in everyday life.
What the addition would make easier
New app ideas
Everyday problems that could be the starting point for a new small app or tool.
What frustration you would like a small tool to ease
IMPROVEMENT LOOP
When collection opens, feedback can lead to improvement.
If feedback submission is approved, we plan to use the following states to explain review and outcomes. This is not an active intake service or a promise of processing.
Received
Check that the feedback arrived safely.
Under review
Understand the context and how to reproduce the problem.
Planned
Define the scope and priorities for improvement.
In progress
Make and check a small, manageable change.
Depending on the review, the process would end in one of two states.
- ImplementedConnect the result to an update.
- ClosedRecord the reasoning even when a suggestion is not implemented.
CURRENT STATE
Feedback collection is not open
Preparing to receive feedback safely.
There is no feedback submission or storage feature yet. We will open collection after the following criteria are approved, without asking for personal information before it is needed.
You cannot enter or submit information on this page.
What needs to be ready before collection opens
- Safe receipt and storageDefine the backend, public and private data boundaries, and how storage failures are handled.
- Privacy principlesConfirm the minimum information needed, its purpose, retention period and deletion request process.
- Abuse preventionSet spam prevention and rate limits to protect the service and its participants.
- Operational responsibilityClarify administrator permissions, status changes and responsibility for responses and closure.
KEEP EXPLORING
Explore the work and the ideas behind it.
Check the current state of our apps or read why SHIFT AFTER takes small everyday frustrations seriously.