About whichapp.report
whichapp.report is a decision-tree publication for choosing between consumer apps. We write conditional recommendations — if you want X, use [app] — across nine consumer-app categories. We do not write listicles. We do not accept affiliate compensation. The publication's only revenue source is reader-funded.
The thesis
The dominant format in consumer-app journalism — the listicle — actively misleads because it implies a partial order over a set of products that are usually not, in fact, partially ordered. The "best" calorie tracker depends on whether you want photo workflow, database depth, micronutrients, adaptive macros, or simplicity; calling one of them "best" misleads four out of five users. Our format addresses this by making the condition explicit. Each branch in our decision trees starts with "if you want X" — naming the user condition — and only then does the recommendation appear.
The editorial team
Five editors, each with documented credentials in the categories they cover. The team is intentionally small — we don't believe in expanding coverage beyond what we can review with rigor.
Yuki Saeki-Marlowe, BS, MS
Editor-in-Chief
Yuki Saeki-Marlowe (she/they) is the editor-in-chief of whichapp.report.
Florencia Rasmussen-Ito, MS, BS
Health & Habit Apps Editor
Florencia Rasmussen-Ito (she/her) is the health and habit apps editor at whichapp.report.
Ezekiel Wamala, BS, MEng
Senior Tech Editor (Productivity & Notes)
Ezekiel Wamala (he/him) is the senior tech editor at whichapp.report and owns coverage of productivity, note-taking, workout, and AI-assistant categories.
Mateusz Kowalczyk-Brand, CFA, MBA, BA
Finance Apps Editor
Mateusz Kowalczyk-Brand (he/him) is the finance apps editor at whichapp.report and owns the publication's coverage of budgeting, expense-tracking, and personal-finance app decisions.
Aria Henderson-Ojo, MLIS, BA
Reading & Lifestyle Apps Editor
Aria Henderson-Ojo (they/them) is the reading and lifestyle apps editor at whichapp.report and owns the publication's coverage of reading-tracker, language-learning, and podcast-app decisions.
How we work
Every decision tree is constructed from the same four-step framework documented on our methodology page: identify the use cases driving the decision, name the architectural commitments each major app makes, match commitments to apps, and write explicit anti-recommendations for every branch. Each tree is reviewed by an editor outside the writer's vertical before publication.
Our changelog is a public log of every content update — what changed, when, and who signed off. We refresh decision trees quarterly and announce every refresh in the changelog so readers can audit our cadence.
What we don't do
- We don't accept affiliate compensation. See our no-affiliate disclosure. No app developer pays us a commission for clicks, signups, or any other action.
- We don't accept sponsored placements. No app developer has paid for inclusion in any decision tree on this site.
- We don't accept review-unit subscriptions. Our editors maintain personal subscriptions to the apps they cover when relevant; the subscriptions are paid for by the publication, not by the developers.
- We don't write listicles. Every piece on this site is a decision tree, a glossary entry, or a trust page.
Contact
Editorial: editor@whichapp.report
Corrections: corrections@whichapp.report
Mailing: see contact page.
The site itself
whichapp.report is built with Astro. The source has no JavaScript on most pages (the decision-tree SVGs are static, the prose is server-rendered), which keeps the site fast and durable. Hosted on AWS. Designed by the editor-in-chief; engineered with grumbling.