Inside a Fifth Third editorial review

A Fifth Third editorial review is three to eight hours of focused reviewer time spread over four working days. Here is what happens between submission and a Wednesday drop.

Day 1 — triage

The on-call editor triages the submission. Basic hygiene checks: does the package build, does it install on a factory-fresh Pixel, does the module data sheet match the actual behaviour on first launch. About a quarter of submissions bounce at triage.

Day 2 — deep review

The reviewer for the target shelf runs the module for the full session — three hours for a utility, eight hours for a camera. Notes are captured against a shared template: install size, permission footprint, offline behaviour, first-run experience, obvious accessibility issues, dark-mode support.

Day 3 — jury vote

The four-person jury meets and votes. A module needs three of four to move to the Wednesday drop. Split votes send the submission back to the developer with a written set of change requests.

Day 4 — signing ceremony

The two ceremony-key holders sign the batch. The signed manifest is published to /security-whitepaper. The workspace app on every enrolled device picks up the new manifest within the hour.

What the reviewer looks for

Small install footprint. No unnecessary permissions. Documented behaviour that matches actual behaviour. A privacy dashboard that is honest. A UI that survives 200 % system font scale and a low-vision colour probe. A settings screen that exports and imports in a common format.

What sinks a submission

Hidden network calls, unrequested background wakeups, dark patterns in the upgrade flow, missing export path, an install size that grows unpredictably, opaque permission requests. Any one of these is enough to bounce the submission at day 2.

If you are considering a submission for a future Fifth Third batch, write to the editorial team at support@fifththirdstore.org with a two-paragraph pitch.