Tildi is early enough that what gets built next is still genuinely open. This is how to send a request, what to put in it so it is useful, and where to look afterwards to see what happened to it.
01
Before you write
See whether it is already on the roadmap
The roadmap is written in three horizons, and the thing you are about to ask for may already be sitting in one of them. Worth thirty seconds: it changes what is useful to say.
Now is what the web room already does today.
Next is the two-to-three month working horizon.
Later is what is being explored, without a date attached.
02
Where to send it
Open the contact form and choose “Feature request”
The contact page is the one route in. Under “What can we help with?” there is a Feature request option: picking it is what tags the message so it does not arrive looking like a support question.
Fill in your name, your email, and the request itself.
Choose Feature request from the “What can we help with?” list.
Prepare email opens your own mail app with the message written and addressed: nothing is sent until you send it.
03
What to include
Describe the message you were trying to write
The most useful requests start with the situation rather than the solution. A feature described on its own has to be guessed at; a message you could not get right is something we can test against.
Who you were writing to, and what the message had to do.
Where Tildi stopped short: the wrong register, a missing intention, a version you could not use.
What you did instead, and what a good outcome would have changed.
Where you were writing: the web room, a phone browser, or somewhere Tildi is not yet.
04
What to include
Only paste the words you are happy to email
This is the natural place to paste the whole draft, and it is worth pausing first. Tildi does not add your drafts to its application database, but an email you write to us is an ordinary email, and it sits in an inbox like any other.
Paraphrasing the message usually carries everything we need.
Change the names if the situation is what matters.
A short quote of the version that came back is fine, and often the clearest evidence.
05
After you send
What happens to it
A real person reads every message that arrives. There is no public vote count and no ticket number, because neither would tell you anything true this early: the roadmap is the answer instead, and it moves as things move.
Requests that keep arriving are what reorder the Next horizon.
Something that does not fit is said plainly rather than left in a queue.
iPhone, keyboard, and share-sheet availability is announced on the roadmap first.