Specifications for a mobile application

A specifications document, also known as a Functional Specifications Document (FSD), is a document that provides a detailed presentation of all the information necessary to carry out a project.

Used across various sectors, it serves as the reference document that project stakeholders follow to achieve a result that matches initial expectations.

Whether for in-house development or through an agency, drafting a specifications document is indispensable. Take it from our experience. 😉

According to a report by The Standish Group dating from 2015 (the 2020 report has not yet been published), the primary reason for IT project failure is an incomplete specifications document.

In addition to detailing the project for your service provider, the FSD constitutes a legally binding contractual document that protects you in the event of misunderstandings with your development agency.

Take the time to draft a clear and exhaustive specifications document. By doing so, you will significantly reduce the risk of receiving a deliverable that does not meet your expectations. You will also help your provider accurately estimate the time and budget required for your mobile application (see our mobile development offer).

Note: At Aventique, you can consult us with a simple expression of needs. This will allow you to get an initial estimate of the cost and timeline. We can subsequently help you finalize a formal specifications document.

Objectives of a Functional Specifications Document

• It allows you to obtain quotes and create competition between different service providers.
• It serves as a working foundation that gives providers the opportunity to propose innovative solutions for your needs while respecting your constraints (price/deadlines/objectives…).
• It constitutes a basis for comparison between deliverables and your expectations.
• It helps you avoid damaging oversights.
• It provides a clear vision of the real scope of work and resources needed for the project.
• It anticipates potential conflicts with your provider by clarifying everything from the start with a reference document.

Thus, the specifications document is the first step of any mobile development project.

Request a quote

 

The document is generally quite substantial, ranging from 10 to 50 pages, and includes the following elements:

1. Presentation of the project context
2. Application design
3. Features and technical specifications
4. Project timeline and stakeholder responsibilities

Let’s look at each element in more detail.

Presentation of the project context

1. Your Company

First, present your company by mentioning:

• Date of establishment;
• Core business;
• Products and services;
• Key characteristics;
• Founder profiles, if relevant;
• Number of employees;
• Presentation of main competitors;
• Target audience;
• Growth strategies.

The application must integrate into your company’s context. This is why the provider needs to know more about you to design an app that reflects your business and meets its objectives.

2. Problem Statement

Address the problem that led you to consider developing a mobile application. Then, explain why you believe this application will solve that problem.

3. Current Situation

If you already have a website or a mobile app, explain the current situation. Here are several points to cover depending on your situation:

• Is there an existing application or website? If so, describe the solution.
• Current statistics (monthly traffic, bounce rate, conversion rate, number of registered users, number of downloads…).
• Type of monetization.
• Payment methods used.
• Platforms used for notifications, behavioral analysis, etc.
• Documents concerning the existing brand identity.
• Number and profile of people working on this project.

4. Application Objectives

Explain your goals—what you want to achieve with this application. For example, your objectives might be to build customer loyalty, increase the average basket size, or launch a new service.

5. Describe the application you wish to develop

Describe the application you want to develop without getting into specific features yet.

Example: We wish to launch an e-commerce application that will complement our online sales site. The application will feature the products sold on our website.

6. Operating Systems

Do you want an Android or iOS application, or one that runs on both systems?

Generally, two technological possibilities are available for mobile development:

1. Native: Native apps are developed specifically for a specific operating system.
2. Hybrid: Hybrid or cross-platform applications, unlike native apps, are developed once and are compatible with both iOS and Android.

Naturally, each option has its advantages and disadvantages.

7. Application Business Model

• Type of monetization (freemium, subscription, advertising, etc.).
• Payment methods you wish to use.

Application Design

In this second step, you must provide and specify the graphical aspects of the application.

1. Provide existing materials

If you have a logo, a brand identity guide, etc., they should be included in this part of the document.

Otherwise, specify whether you are entrusting the creation of the logo and identity to the agency or handling it independently.

2. Functional Mockup (Wireframe)

Image source: Icons8.com

Wireframing is the step that involves defining, through simplified drawings, the screens that will make up your application. It helps stakeholders get a more precise idea of the app’s structure and different screens.

Don’t dwell on aesthetic details. The goal of the wireframe is to determine the placement of various components on your screens.

3. Sources of inspiration

Feel free to list a few applications whose design inspires you; this will help your provider understand what you like and dislike.

Features and Technical Specifications

1. Features

During this essential step, you will need to precisely describe your mobile application’s various features.

You can use the Wireframe created previously to note the related features next to each screen.

2. Back Office

The back office, often in the form of a website, allows you to manage your mobile application. For example, you can perform the following tasks via the back office:

• Update texts or images,
• Launch push notifications,
• Modify prices,
• Manage user accounts (delete, add, extend a subscription…),
• Export data.

Specify your back-office needs. It is often tempting to want to manage everything, but ask yourself about your actual needs. It is always possible to evolve your back office later.

3. Constraints

Will the application be used offline?

Project Timeline and Stakeholder Responsibilities

1. Expected Services

To be as precise as possible and avoid misunderstandings, describe the expected services in detail. Is it a graphical redesign? Technical modifications? Development of a new application?

2. Resources

In the case of internal development, listing your resources will help you define your challenges.

List your constraints as well. For example, your resources might be the people working on your project, and your constraints might be the lack of a designer to create the application mockups.

3. Budget

Be as specific as possible so that the quotes you receive are consistent with your actual budget.

4. Expected Deadlines

If you have a launch date for your application, mention it here. If not, we advise letting the providers propose their own timelines.

5. Who to contact for which question?

Designate key contact persons within your company. These contacts will guide the provider throughout the application development.

Conclusion

Your provider cannot read your mind, so try to communicate as much information as possible.

Key points to remember:

• The specifications document defines the objectives, constraints, and features of a new application.

• It also incorporates other elements, such as the company profile, employees, and target audience.

• A complete specifications document allows for effective project management by controlling budget and time and avoiding setbacks.

You might be asking these questions