You have an idea for a modern mobile app. There is a structure, layout, and a finished design. It’s time to put the idea into action. Along the way, you won’t bypass the need to draft a development specification. The quality of the future mobile app build and how much it costs to develop it (among other things) depends on how detailed the processes are in the technical manual.
What role does the TOR play in application development
Even if you are confident in your ability to explain on your fingers what is needed from technical experts, having a ToR will help avoid misunderstandings related to different visions on the part of the customer and the contractor. Even if it seems like everyone understood each other in the discussion.
In the sphere of mobile application development, the ToR performs the role of a service contract: in addition to the characteristics of the future product, it describes the terms and conditions of the contractor’s work (method and technologies of implementation, terms, payment procedure). If after handing over the project it turns out that the application is assembled in violation of some conditions of the document, the customer may not pay for the work until the performer corrects the errors.
As a contract, TK is legally enforceable. Unless agreed to by the parties, the terms of that document cannot be changed – adding new ones or deleting old ones – once the contractor has started work on it. Once approved, the ToR becomes the bible of the workflow.
Stages of developing the terms of reference for an application
Drafting a competent instruction has its own instructions on how to write it. If the specification developer follows the requirements for writing a specification, it will increase the chances that the final product will be successful.
Ideological stage
The first thing that should become clear to the experts is what the goal of the product they are working on is. And the phrase “To make the business profitable” is not enough.
Marketing research
It all starts with research (field or desk research ):
- analyzing the market as a whole – gives an understanding of the conditions in which the product will operate, determines the saturation with offers and correlation with the demand for similar products;
- competitive comparison with similar offers – conducted to identify the weaknesses and strengths of the product. The identified data forms the basis of the picture of its positioning in the minds of the target audience;
- drawing up a portrait of the target user – the data collected in the previous two stages allows you to outline what needs the application covers. CA research is about identifying the users who may have these needs. By creating a portrait of your target customer, you can find out what motivates them to fulfill those needs. The result will be an understanding of how to motivate him to install the app on his mobile device and use it for as long as possible.
Defining the application’s operating mechanisms
There are goals. The next step is to understand how the product will accomplish these goals. Mechanisms and technologies used in the application are stipulated, questions from the “How?” sector are addressed:
- How is the structure of the application organized?
- How is the information displayed in the interface?
- How are application functions implemented (what technologies are used to implement them)?
- How is the monetization of the mobile app done?
- How (in what direction) is the product further developed?
The last point will outline the application’s update program, which will protect against future problems implementing these updates. Simply put, it will protect you from “It works – don’t touch it” situations.
Search for examples of similar implementation
No matter how original a product is, it is somehow just a new reading of something already realized. It can be some trick that competitors have – a working feature, without which the target audience will not accept such a product.
Giving examples of implementation is a good tone in TOR writing. No matter how accessible and detailed the instruction describes how the product should work, and a selection of examples will guarantee that the performer will understand exactly what the customer wants to get from it.
It is worth separating the concepts of plagiarism and reinventing the wheel. They differ in that a “bicycle” is a copy of an existing product, while plagiarism is a new reading of it, looking at it from an unfamiliar angle.
Tip: It’s better if the role model is successful. Repeating what failed is a risky venture, most likely unnecessarily risky.
Flies separate, cutlets separate
Alas, to understand what format of the terms of reference will be ideal for a particular case, you must first compose it. There is no universal instruction template. But there are common points that unite all formats of technical documentation:
- Specifics. If there is a background requirement – this condition should not be in the form of “White Background”. These must be specific RGB or HEX color code parameters. If there is a font requirement – it’s not “Classic font with medium sized serifs” but the exact name “Times New Roman size 18pt” etc.
- Separation of Powers. A designer and a programmer are involved. This means that the former is strictly responsible for what the application interface looks like, while the latter is responsible for how to implement it in code. And they shouldn’t have a headache for each other’s responsibilities.
- Facts instead of estimates. No “beautiful,” “useful,” “readable.” A self-respecting developer realizes that everyone has his own concepts and estimates, and agreeing to work with such TOR is agreeing to work for free and satisfy the whims of the customer until he gets tired of it.
- The clause is “at the discretion of the developer.” It is impossible to take into account all the nuances of the finished product, and it is counterproductive to delay because of the solution of every detail that the customer simply did not think of. For this case there is a clause “All unspecified details are at the discretion of the developer”. This way the project will be safe from delinquencies.
How a professional ToR differs from an ordinary one
At first glance, any specialist can compose a mobile application development instruction. It’s often the case that documentation is handled by a designer or even a copywriter. But a competent TOR requires experience and technical knowledge.
The Terms of Reference alone
You can’t just pick up, read a few articles on the internet and understand the topic. At best, a technical specification based on such knowledge will be formal (i.e., useless) and will not reflect all the requirements to the product. At worst, the result will be of even lower quality, as if the developer worked without TOR at all.
In which cases the customer can create the ToR himself:
- conventionally simple project. If the application is more like a static web page, without complex functions and tricky scripts, then a superficial acquaintance with the process of working on a mobile application, and a tracing of examples of technical specifications on the Internet will be enough for the customer;
- you already have development experience and delegate the task to a contractor. If you have a track record of full-stack development, you speak the same language as the other technical staff;
- you have a trusted executor reading your mind. In this case, you can close all controversial issues with the line “Anything not described in the assignment is at the discretion of the developer”.
The described conditions are an ideal situation, a frankly rare case in the practice of working on mobile products. That’s why another experience is common in the field – delegating TOR writing to an experienced team.
Development of terms of reference by a team of specialists
Several specialists from different fields – designers, marketers, technical developers – are involved in drafting professional TOR. All this allows you to prepare the right documentation that will take into account all parties in the realization of a new mobile application:
- Technical Component. Developers are responsible for ensuring that the app meets technical standards. It’s about valid product code, server-side and internal optimization. The developer will make suggestions on which the implementer will realize a product that works quickly and runs smoothly on any of today’s mobile devices;
- Trending design. The designer will be able to make suggestions in the TOR to develop a design that will take into account not only current visual trends, but also user-friendliness;
- Thoughtful marketing. Marketers will make sure that the future app is exactly what the target audience expects to see in its place. They will determine who the key user of the application is, make his portrait, find out his motives and needs related to the future software product and make remarks in the TOR, allowing developers to implement it in accordance with the expectations of consumers.
It is costly to assemble a team just to draw up a competent terms of reference. Therefore, there are special agencies that provide technical documentation services for mobile app development.
How to choose your contractor according to the terms of reference
- Above we have mentioned only the designer, developer and marketer who are involved in drafting the TOR as standard. But each case may require a different team of specialists responsible for different areas of development. Therefore, the contractor providing TOR writing services should have employees, not just assembled in teams for project work, but a proven, permanent team of professionals of all possible specializations in the field of application development, who will actively participate in the TOR project for the future mobile application.
- Optimally, if the contractor, who draws up the TOR is a developer himself, is a full-cycle company – from market research and development of the concept of the future product or service to, directly, the realization of the finished product in life. This approach ensures that the contracting team members are able to assess all the opportunities and risks of launching a new brand and, at any stage of the process, take actions that will bring success to the future brand.
- The next requirement is that the selected team of specialists understands the goals of the client’s application, in what conditions it will have to exist – in the market in general, and in a particular niche. This means that experience in different projects and cases of working on well-known brands are important for the team. If an agency has brands in its portfolio that you, as an average consumer, have not heard of – what are the chances that such a team will make your product known?
- About fame. A specialist, starting to work in some sphere, first of all, creates his own trademark. Whether it’s personal branding (i.e., branding as a person) or presenting their product or service, a contractor should first create a recognizable name for themselves before offering their services to clients. A successful personal example is the only example that is beyond doubt and question.
TOR development for mobile application from KOLORO agency
KOLORO Agency is a team of specialists with experience in bringing brands to the market and turning them into stars of their niche, into leading brands. We have released over 1,000 products since our inception, with daily revenue exceeding $1 billion. This is more than the budget of some countries in the world.
A mind is good, but two is better. And if these are the minds of a team of professionals who love their work, the result of their work is brands with a beautiful history, successful positioning and a memorable name.
We take the success of our customers’ products as our own, and this is a credo for KOLORO employees, a goal, a source of inspiration and personal motivation for everyone.
We help business owners get their satisfied customers. Marketing and creativity within our team are woven into a special synthesis that allows us to create products that inspire.
Want to be the owner of a brand that inspires? Please consult our managers by phone +38 (044) 223 51 20 or e-mail: hi@koloro.ua.
Case examples can be viewed here.
