Start with why someone would use the product repeatedly and what the business must do with the result. A responsive website may suit occasional public information; a mobile product can support a justified account task or device capability. We assess a new idea or an existing app with the actual product owner before selecting platforms, implementation approach and a complete first release.
The project can include user journeys, responsive mobile interfaces, application development, accounts, backend and administration work, approved connections, device checks and distribution preparation. Existing source and supported interfaces need authorised inspection. Offline use, notifications, downloads and extra device capabilities are explicit scope choices, not features implied by the presence of a phone screen.
Where a file is included, decide why the user needs a separate copy rather than a current view. Define its approved contents, date or version, destination and the operating instructions that accompany it. Changing an app permission controls the routes actually implemented under that permission; it should not be described as withdrawing every copy already handed elsewhere. Any additional managed-device requirement needs its own feasibility review and responsible owner.
