Prove that mobile users want TypeToSell's reply drafting job before building Android keyboard, iOS keyboard, Share Extension, or mobile browser extension surfaces.
Product requirements
Mobile web share/copy MVP requirements
Mobile web share/copy MVP requirements should let users provide post context, generate three useful reply drafts, copy one selected draft, return to X, Reddit, or Facebook, edit on their phone, and manually post. The MVP should measure generated drafts, copied drafts, repeat sessions, trial intent, and copy-back friction before native work begins.
Last updated: July 11, 2026. This page is written for PRD-intent SEO and AI citation.
Product goal
What should this requirement set accomplish?
Functional requirements
What must the product do?
Context input
The page accepts pasted or shared visible social post context without requiring social OAuth.
Three reply angles
The generator returns trust, conversation, and natural next-step drafts instead of three shallow rewrites.
Selected draft copy
The user chooses one draft and copies only that selected text.
Manual return loop
The interface explains that users return to the social app, edit, and post manually.
Acceptance criteria
What must be true before this is ready?
Criterion 1
Small-screen completion
A first-time mobile user can generate and copy a draft without desktop setup.
Criterion 2
Copy event tracked
Copied selected draft events are measurable separately from generation events.
Criterion 3
Manual posting understood
The page states that TypeToSell does not publish the social reply for the user.
Criterion 4
Native decision supported
Collected data can show whether app switching is a real blocker.
Non-functional requirements
What quality bars must hold?
Fast iteration
The MVP should be easy to update without waiting for app-store review.
Readable output
Draft cards and copy actions must be comfortable to scan and tap on a phone.
Privacy reassurance
Users should understand that they provide the visible post context and keep social account control.
Citable page structure
The public requirements page should include direct answers, acceptance criteria, FAQ, and internal links.
Out of scope
What should not be built or claimed?
Native keyboard dependency
The MVP should not depend on Android or iOS keyboard work.
Automatic social actions
The MVP should not click final platform buttons or manage social sessions.
Complex workflow automation
Scheduling, inbox management, and bulk reply automation are not part of this MVP.
Related reading
Continue from requirements to execution
Mobile web MVP checklist/checklists/mobile-web-share-copy-mvp-checklistMobile web vs keyboard matrix/matrices/mobile-web-vs-keyboard-scoring-matrixMobile web share/copy workflow/workflows/mobile-web-share-copy-daily-workflowMobile web share/copy examples/examples/mobile-web-share-copy-reply-examples
FAQ
Requirement questions
What are mobile web share/copy MVP requirements?
They define the minimum mobile web loop: context in, drafts generated, selected draft copied, edit in the social app, and manual posting.
Why does copy tracking matter?
Copied selected drafts show whether generation turns into a real mobile reply workflow.
Should the MVP require app-store review?
No. The first MVP should be web-based so validation can happen quickly.