How to draw up a technical assignment to develop a mobile application

‍

Technical specifications (TOR) is a document that describes all the requirements for a mobile application: from project goals and user profile to functionality, design, deadlines and budget. This document becomes the basis for the work of developers, designers, analysts and testers.

‍

Why the terms of reference for developing a mobile application are not just a formality:

• It helps to build transparent communication between customers and contractors.
  ‍
  
• It reduces the risk of mistakes and misunderstandings.
  ‍
  
• It allows you to accurately assess the timing and cost of the project.
  

‍

It gives the team a clear understanding of what result they are going to.

A good technical specification is not a wishlist, but logical and structured documentation that guides the team from idea to product. It covers both business goals and technical features, and helps each team member understand what needs to be created, how it will work and why it is needed. This document serves as a basis for planning, evaluating, monitoring and successfully implementing the project. Let's consider the key sections that must be in the specifications in order for the mobile application to be exactly what the customer intended it to be.

‍

1. General information about the project

‍

Application goals and objectives

‍

• The application is designed to solve specific user and business problems. This could be automating orders, simplifying feedback, increasing loyalty, or expanding sales channels. A clear goal statement helps guide development and assess the success of the project.
  ‍
  
• The application should perform a practical function: help the user save time, quickly receive the necessary service or information, place orders without unnecessary steps. From a business point of view, it should improve processes, increase sales and improve customer experience.
  

‍

Target audience

‍

A clear understanding of the target audience helps to adapt the application to the real needs of users. Indicate age (e.g. 18—35), gender, occupation, digital literacy level, habits, and motivations—why users will launch the app, in what situations, and how often. Add behavioral scenarios: are they ready to register, will they make purchases, and interact with content.

‍

It is also important to take into account geography and language: users from megacities can expect a more complex interface and advanced logic from the application, while users from regions can expect simplicity and minimalism. This will help you build design, navigation logic, and functionality taking into account specific expectations and context of use.

‍

Platforms

‍

• Indicate which platforms the app is being developed for: Android, iOS, or both. Is it necessary cross-platform development (like Flutter)? Determine the minimum OS versions, supported devices (smartphones, tablets), and how to adapt to them.
  ‍
  
• Do you need cross-platform development? It (based on Flutter, React Native, etc.) allows you to create one app for Android and iOS, saving time and budget. However, it's not for everyone: it's important to consider performance requirements, native UI, and access to system features.
  ‍
  
• Specify the minimum versions of operating systems that the application must support — this affects the choice of technologies and audience reach. For example, Android 9.0+ and iOS 13+. The lower the version, the more users are covered, but the compatibility requirements are higher.
  

‍

2. Functional requirements

‍

This is the very terms of reference for developing a mobile application, in other words, the core. It details the functions that the application should perform at the start and in the future: from basic tasks (registration, search) to complex scenarios. Usage scenarios, priorities and dependencies between modules are specified.

‍

Main functionality

• The main functionality of the application is its key features, without which it is impossible to achieve project goals. Here it is important to list the minimum required set of options: registration, payment, notifications, personal account, etc. Each feature should be described in terms of user benefit and usage scenario.
  ‍
  
• Registration and authorization. This is a basic feature that provides the user with access to personalized functionality. It is important to specify what methods are provided: email, phone number, social media login, biometrics. The logic behind password recovery and identity verification should be described.
  ‍
  
• Personal account. This is a personalized section where the user manages personal data, orders, settings and notifications. Indicate what features it includes: activity history, password change, saved items, profile settings.
  ‍
  
• Catalog search. The search should be easy and fast. Specify what parameters can be searched (name, category, filters), whether smart search with hints or autocomplete will be implemented. Consider ways to make your search results relevant and fast.
  ‍

‍

• Push notifications. Notifications allow you to quickly inform the user about the status of orders, promotions, messages or events in the app. Specify when and how they are sent, whether you can turn off or adjust the frequency, and whether deep links are supported.
  ‍
  
• Online payment. It is important to specify which payment systems are supported: bank cards, Apple Pay, Google Pay, e-wallets. You should describe the payment scenario, the security of transactions, the need to save the card, and the possibility of a refund.
  ‍
  
• Support chat. The built-in chat allows the user to quickly get help with the application, check the order status or solve a problem. Specify whether it will be a bot, live operator or hybrid, and what channels are supported (text, attachments, voice).
  ‍

‍

For each function, it is desirable to describe user story — a scenario in which a user interacts with the application:

“A user logs into the app, selects an item, adds it to the cart and pays with a bank card.”‍

‍

Additional functionality

• Integrations with social networks, CRM, maps, analytics systems.
  ‍
  
• Multilingualism (localization).
  ‍
  
• The ability to work offline.
  

‍

Restrictions

• The application size is up to 100 MB.
  ‍
  
• The launch time is no more than 3 seconds.
  ‍
  
• Work with a weak Internet connection.

‍

3. Technical requirements

‍

Here it is important to describe exactly how the functionality will be implemented, taking into account technology, architecture, security and loads.

‍

Technology stack

‍

Indicate the programming languages in which development will be carried out: Swift, Kotlin, Flutter, React Native, etc. Justify your choice — for example, Swift for iOS provides better performance, while Flutter is suitable for cross-platform use. Specify what libraries, frameworks, and SDKs you plan to use, and why you need them (for example, Firebase for push and analytics).

‍

Server side

‍

Describe whether the server architecture will be used. Check whether you need your own backend or third-party services. Specify the database type: SQL (e.g. PostgreSQL, MySQL) for structured data, or NoSQL (MongoDB, Firebase) for flexible structures. It is also important to describe how to store and share data: REST API, GraphQL, WebSocket, and other technologies.

‍

Safety

‍

Security is critical for any application. Describe what data protection methods will be implemented: encrypting data on the device and during transfer, storing tokens, prohibiting the use of root/jailbreak devices. Specify authentication methods: login/password, biometrics, two-factor authentication. Also specify how protection against leaks and attacks will be provided.

‍

Productivity

‍

The application should be stable even under high load. Describe the expected number of users, the amount of data being processed, and how to scale. Specify your goals for download time (for example, no more than 2 seconds), offline support, and response speed. It is also important to include stress tests and performance monitoring at the launch stage and in the future.

4. Design and UX/UI

‍

Design concept

‍

Define visual style: minimalism, material design or corporate identity. Refine your color palette, fonts, graphics, icon preferences, and visual accent preferences. This will set the tone for the entire interface and increase the app's visibility.

‍

Prototypes and mockups

‍

Check if there are ready-made layouts or if they are being developed from scratch. It is important to specify the tools (Figma, Sketch, etc.) and those responsible. Add reference examples: which apps are inspiring in terms of interface and user journey.

‍

Adaptability

‍

The app should be displayed correctly on different devices and resolutions. Specify whether you need to support tablets, horizontal mode, and adaptation to different pixel densities. This will affect the design system and approach to layout.

‍

5. Development stages and deadlines

‍

Project phases

‍

1. Collection and analysis of requirements. At this stage, the team and the customer form a common understanding of goals, functions and limitations. Market research and competitors are being conducted, user scenarios are created, and key business processes are recorded.
   ‍
2. Prototyping. At this stage, interactive screen layouts are created. This helps to test the interaction logic, refine the structure and make sure the interface is user-friendly before starting development.
   ‍
3. Development. This is the main stage where the team implements interfaces, logic and functions in accordance with the technical specifications. It is important to establish version control, use a task management system, and comply with architectural principles.
   ‍
4. Testing. This stage includes checking all functions for errors, bugs, stability and compliance with technical specifications. Manual and automated testing is carried out on different devices.
   ‍
5. Publication to stores. The final stage, which includes preparing descriptions, screenshots and icons for the App Store and Google Play. It is important to take into account the requirements of the platforms and be moderated.

‍

timescales

‍

Each phase of the project should be accompanied by a rough estimate of the terms: for example, 2 weeks for analytics, 3 weeks for design, and 5 weeks for development. This helps you plan and track progress.

‍

feedback

‍

Regular meetings and interim iterations make it possible to monitor the progress of the project, quickly clarify tasks and make changes in a timely manner. Feedback helps the team adapt functionality to real requirements.

‍

6. Budget and resources

‍

Budget assessment

• Calculate the cost of each stage: analytics, design, development, testing, publishing. Take into account specialists' hourly rates and possible overhead costs.
  ‍
• Additional costs may include paying for cloud hosting, licenses for third-party services, analytics systems, sending push notifications, and maintaining server infrastructure.

‍

The team

‍

To implement the project, you will need a team: analyst, designer, developer, tester and project manager. You should also determine in advance what external services and tools will be used: CRM, payment gateways, cloud solutions, and API services.

Here is a short example of a technical specification for developing an application for a food delivery service:

‍

Project name: FoodNow

‍

goal: provide users with a convenient service for ordering food from restaurants with the ability to pay online.

‍

Platforms: Android (version 9.0+), iOS (version 13+).

‍

Features:

• Registration/authorization
  ‍
  
• Restaurant catalog
  ‍
  
• Filters by kitchen, rating
  ‍
  
• Add to cart
  ‍
  
• Payment via Apple Pay, Google Pay
  ‍
  
• Push notifications about order status
  ‍
  
• Order history
  

‍

Additionally:

• Integration with 1C
  ‍
  
• Russian and English language support
  ‍
  
• APK size up to 80 MB
  

‍

Budget: from 1.5 million rubles, implementation period — 3 months

1. Be specific

‍

Avoid language like “user-friendly interface”. Better: “The main page displays three blocks: catalog, promotions, profile.”

‍

2. Engage your team

‍

Work on technical specifications with technical specialists, a designer, and a business analyst. This will speed up the process and increase the accuracy of the document.

‍

3. Don't be afraid to finalize the technical specifications

‍

This is a living document. After interviews with users or new ideas, you can review some of the requirements.

‍

4. Use tools

‍

1. For prototyping: Figma, Adobe XD
   ‍
2. For planning: Trello, Jira, Notion
   ‍

Terms of reference for creating a mobile application — this is not just a document, but the strategic basis for the entire project. It depends on him how accurately the team will understand the task and how successfully the product will be implemented.

‍

If you want your application to be of high quality and in demand, start with technical specifications. And if you don't know how to write it correctly, we will help you.

‍

At Beetrail, we work with businesses at all stages: from analyzing an idea and preparing it to launching an app in stores.

‍

Are you ready to turn your idea into a real project? Contact us and we will prepare a technical assignment for the development of a mobile application that will become a solid foundation for the future product.