What you need to know
- Review comments should identify a specific build.
- Treat application sign-in as a separate acceptance item.
A build can keep its own address
Automattic opened Spacefast on November 9. Its launch announcement describes app hosting with SQL storage, custom domains and a permanent URL for each published version, alongside rollback. Built-in application authentication is listed as coming soon. The service also offers controls for sharing a hosted project.
Our editorial interest is the review process: a comment becomes more useful when everyone can identify the exact build it concerns.
Review the version people actually saw
Consider a proposed review of a small event-registration tool. One person checks the confirmation screen, another checks whether a long event name fits, and a third reviews the cancellation wording. If the developer changes the tool halfway through those checks, three reasonable observations may describe three different experiences.
A useful review brief would name the build, describe the task and specify the expected result. A screenshot could accompany the observation, but it should not substitute for a reproducible path through the application. The same brief can then be applied to the next revision.
Separate the decision from the revision
For that hypothetical team, an approval should answer a narrow question: did this particular build meet the stated requirements? Subsequent changes deserve their own review, even when their appearance is similar. A working visual change can still alter the wording or order of a form.
We would also keep application sign-in as a separate acceptance item. A review of a shared demonstration should establish which identities and data the finished application will handle before that demonstration becomes a working service. The useful artifact is a build with a clear review outcome and an explicit list of unfinished work.


