Does a saved task from the same document explain Craft’s note-to-action workflow better than an open composer?
- Audience
- US English iPhone prospects who use notes for personal plans or work actions, with existing Craft users analysed separately.
- Control
- The captured first three frames after offline and sync wording is verified and corrected consistently across variants.
- Treatment
- Replace only frame three with an authentic saved task from the document shown in frame two, using the current supported task destination. Keep other creative, metadata and access fixed.
- Method
- Verify the source-document relationship, task persistence and offline/reconnect behaviour. Run randomized store-sized comprehension research and eligible App Store product page optimization.
- Primary measure
- Correct understanding of where the task is saved and how it relates to the document; platform-reported download conversion in the store experiment.
- Guardrails
- No invented automatic source link, guaranteed AI accuracy or belief that remote sync occurs without connectivity. Track first document and task creation separately if available.
- Decision rule
- Set the useful effect, sample requirement and acceptable qualified-activation tradeoff before launch. Keep control if the saved state creates incorrect expectations or the result is inconclusive.
- What could muddy the result
- Desktop familiarity, paid-plan access, new AI features, seasonal planning interest and users arriving from existing shared documents may affect response.