Have an idea? Send it to feedback@clapdiet.com, with "Feature request" and a
few words in the subject line.
There is no in-app suggestion form and no public request board, so there is
also no voting and no queue position to check. Every email is read.
What makes a request easy to act on
Start with the problem, not the feature
The most useful requests describe what you were trying to do and where it broke
down. That leaves room for a better answer than the one you had in mind.
> "I prep meals on Sunday for the whole week, but I can only log food for
> today, so I have to remember to come back and log each day."
Then suggest what would help
Be as specific as you like.
> "A week view where I can put meals on future days."
Say who it helps
Just you, or a whole way of using ClapDiet? Both are fine, and they get thought
about differently.
A worked example
> Idea: Planning meals for the week ahead
>
> Problem: I cook for the week on Sundays but can only log today, so my
> logs are always catching up with what I actually ate.
>
> What would help: A week view I can add meals to in advance, which then
> becomes today's log when the day arrives.
>
> Who: Anyone who batch-cooks. It would also make the shopping list
> obvious.
What happens to it
It is read, and it goes on the list that shapes what gets built. What we will
not do is tell you it is "on the roadmap" — we do not publish a roadmap, and a
help article naming features as coming soon is a promise rather than an answer.
You may not get an individual reply, and no reply does not mean no.
If it already exists
Some of the most common requests are things ClapDiet already does, in a place
that is easy to miss. Worth a search of this help centre first — and if you
looked and did not find it, that is itself worth telling us, because a feature
nobody can find is its own kind of missing.
Related Articles: