Developers are questioning your mobile design decisions. How will you defend your choices?

Pour rassurer les développeurs sur les choix de conception, on ne doit pas négliger de présenter une documentation claire qui explique les choix de conception qui ont été faits en réponse aux résultats de la recherche sur les utilisateurs. Il est également important de fournir des prototypes qui permettent aux développeurs de comprendre facilement le fonctionnement de certains processus.

While there is another way, this one is probably the most prevalent. Do yourself a favour and have all of your design decisions backed by prototype evaluations. Sometimes, though, there is the opportunity to develop the design together with the developers. Though this may take longer to achieve a first result, this can decrease the amount of subsequent iterations. This way co-ownership undermines the basis for disagreements.

Design based on understanding user needs often outperforms competitors. For example, when creating an app for busy parents, thorough interviews were conducted to understand their schedules, tech preferences, and pain points. This research informed design decisions, from navigation to fonts. When developers question these decisions, the author explains that they are tailored to optimize the user's experience and ease of use, demonstrating that the choices are not arbitrary but based on real data and behaviors.

It can make sense to establish workshops for the whole team in which basic principles of the respective departments are presented independently of a current project. This can help to enforce a common understanding that each division considers different yet well-funded perspectives.

Adherence to design principles like simplicity and consistency is crucial for any design. In a financial app, uniform buttons were made across screens, simplifying the visual experience and creating consistency. This reduced cognitive load on users, allowing them to navigate intuitively without relearning controls. Emphasizing simplicity enhances usability and reduces errors, particularly when evidence shows it reduces user onboarding time and improves satisfaction. This approach resonates well with teams.

Understanding and respecting technical constraints is crucial for creating seamless user experiences, especially on mobile devices. In a past project, I designed an interactive image gallery with smaller thumbnails to balance aesthetics and performance. This decision prevented lag on slower devices and aligned design and development priorities. Emphasizing the user impact of performance-based decisions often aligns design and development priorities, as even the most stunning design can be ineffective if it slows down the app.

Start by understanding specific concerns—whether they relate to workflow, features, data models, frontend, or timelines. Listen carefully and use user research and business insights to explain your design rationale. Address valid concerns with clear data, demonstrating how the design meets user needs and business goals. While filtering out biased opinions, stay open to suggestions and collaborate on finding solutions that improve the experience while accommodating technical constraints.

The author describes a successful collaboration with developers on a complex dashboard redesign. They used their questions to encourage a collaborative dialogue, resulting in an efficient solution that met user needs. The author emphasizes the importance of respecting developers' technical input and fostering a balanced, innovative, and user-friendly product. This approach allowed for a more balanced and innovative outcome.

The author emphasizes the importance of an iterative approach in mobile design, stating that initial designs are rarely final. Instead of defending the original design, they propose revisions based on feedback, simplifying the process. This approach allows for adjustments over time, making initial designs a foundation rather than a fixed vision. The author also emphasizes the value of all feedback and the ongoing improvement process in this iterative philosophy.

Make sure that the way the user feedback was collected doesn’t allow for any ambiguous interpretations. I.e. suggestive questions can be used to gain preferred insights, biasing the whole endeavour. Thus, use neutral questions and deliver a clear comparison towards alternative designs.

User testing significantly impacts the design process, as it helps identify and address user issues. For instance, in a health app project, early testing revealed a small button size issue, prompting the need for a redesign. Positive feedback validates these changes. Sharing specific test results can help developers understand the necessity of design choices and emphasize the importance of crafting an effective experience. User feedback serves as the ultimate proof, ensuring the work aligns with actual needs and preferences.