Answer.

History of the Issue

In the process of developing mobile applications, situations often arise where the business and development interpret requirements differently, leading to significant rework and timeline shifts. This is due to the rapid changes in the mobile segment and the differences between user expectations and backend interactions.

Problem

The main difficulty lies in the ambiguity of business requirement phrasing, insufficient detail in user scenarios, and heterogeneity of platforms (iOS, Android), which leads to technological discrepancies and inadequate UX. Furthermore, platform-specific limitations and differences in navigation patterns are often overlooked.

Solution

To minimize misinterpretations, the system analyst should:

• Conduct separate interview and workshop sessions with key stakeholders to gather requirements.
• Use visualization (user flow, mockups/wireframes) and develop scenarios considering the specifics of each mobile platform.
• Formalize requirements using the Gherkin template or structure them through user stories with acceptance criteria.
• Specify non-functional requirements for responsiveness, offline mode, security, and power consumption.

Key Features:

• Clear separation of requirements by platform to account for differences in UX and technical limitations.
• Use of prototyping to agree on scenarios with the business.
• Accurate documentation of error handling scenarios and critical user interaction paths.

Tricky Questions.

Can requirements be simply "translated" from a web project to a mobile application?

No, web requirements do not consider features of mobile navigation, screen limitations, background operation scenarios, and integration with native services. Analysis and refinement are needed.

Is it necessary to fix requirements for push notifications at an early stage, or is it just a detail of implementation?

Requirements for push notifications are critical for UX and business logic. They must be established in advance: formats, sending conditions, user actions.

Can the same scenarios be implemented identically on Android and iOS?

Not always. The platforms have different navigation patterns, integration capabilities, restrictions, and security solutions, which affect the implementation of the same scenarios.

Typical Mistakes and Anti-patterns

• Ignoring UX/design features of the platforms.
• Generalizing requirements (“like on the website”), leading to misunderstandings.
• Documenting requirements only in textual descriptions without visualization.

Real-life Example

Negative Case: Requirements were described by analogy with a web project without clarifying mobile UX and push notification specifics. Pros: Quick start of work. Cons: Rework after release, negative user feedback, redesigns in the interface.

Positive Case: The analyst conducted workshops, prepared interactive prototypes, agreed on the push strategy, and outlined offline work scenarios. Pros: Fast transition to implementation, agreed UX. Cons: Took slightly more time at the analysis stage.