MOBILE APP PROJECT BRIEF mobiluygulama.app · Disket Teknoloji LTD. ŞTİ. Guide: https://mobiluygulama.app/en/app-project-brief/ This template is for preparing a quote request; it is not a commitment to any price, timeline or service. You can mark fields you do not know yet as "to be clarified in discovery". Do not include passwords, private API keys or real customer data. 1. PROJECT AND BUSINESS GOAL Project name: Problem to be solved: How this is done today: Assumption the first release will validate: 2. TARGET USERS User roles and what each role will do: Target devices / iOS / Android: App languages: 3. MAIN USER FLOW Starting point: Core action: Successful outcome: Cancellation, error, lost connection and permission cases: 4. FIRST RELEASE SCOPE Essential features: Features that can be left for later: Work explicitly out of scope: 5. EXISTING SYSTEMS AND INTEGRATIONS Existing API / ERP / CRM: Payment, identity, notification or other providers: Documentation links (must not contain secret keys): Offline use requirements: Team that will manage data and content: Admin panel requirements and roles: 6. DESIGN AND CONTENT Existing design / prototype / brand materials: Missing content and who will provide it: Person who will sign off the design: 7. BUDGET, TIMELINE AND DEPENDENCIES Planned budget range: Target date and the reason for it: Third-party approvals / accounts / client inputs: Separate planning of development handover and store release: 8. DELIVERY AND ACCEPTANCE Scope of design, mobile code, API, panel, testing and release preparation: Example acceptance criteria: Person who will provide test data and feedback: Expected ownership of source code, store and server accounts: 9. AFTER LAUNCH Maintenance and support expectations: Party responsible for external service / server costs: Core flow to measure when assessing success: 10. OPEN QUESTIONS Topics to clarify in the discovery call: Brief version / date: