How to write an “ideal” TOR for a mobile application?

Question

iPhone

It is necessary to write a technical specification for an application for android and iPhone, and then maybe a wine phone.
That is, it is necessary to formulate requirements in terms understandable to all developers.
In the "ideal" TOR it is expected:

• description of business logic in the form of a use-cases diagram or something like that
  
• detailed operation scenarios
  
• functional requirements, transformed into a specification of specific tasks for programmers
  
• description of the interface in terms of "screens" and buttons - last
  
• interconnection and conditionality of all the above moments
  
• specification of the functioning of the elements - left at the system design stage (together with) by the developer
  

If you have examples, ideas or expectations - please share.

Answer 1

Usually, the following structure is used for such TOR:
1) goals, tasks - this part then partially goes to interface designers, designers, etc.
2) diagrams, general tech. descriptions, architecture, description of entities
3) description of each screen with a detailed indication of what kind of field, interaction options, data source - these are almost ready-made for developers in themselves
4) description of requirements that are not expressed by schemes and were not described in the previous section . There may be a description of the integration, an xml example, etc.
Although it’s different for everyone, however, for myself many years ago I chose just such a grouping of material