How can you test a mobile app prototype with actual users?

Low fidelity can be also looked at as no fidelity. Look at the early experiments of John Maeda to understand this. Also understand that you can reduce fidelity later in the process to get equally useful feedback.

You can consider adopting an iterative approach. Start with low-fidelity prototypes in the early stages, gather feedback, and progressively move towards higher fidelity as the design matures.

1) Outline the goals and objectives of the user testing 2) Identify diverse audience to uncover major usability issues. 3) Make sure to include real world scenarios and convert them to tasks. 4) Your testing environment should be stable and reliable and your prototype should test ready. 5) Record all the feedback and understand the patterns and trends from the comments of user. 6) Dont forget reiterate and refine the process if you feel you need to tweak a design. 7) Analyze all data that is collected and move to improvement phase if it needed. 8) Share all your findings to the D team, the highlights and lowlights. 9) The design process is the crucial of all the steps. Keep it intact.

Meiner Erfahrung ist es wichtig die Userinen abzuholen, also was für Feedback m?chte man? Zum Prototyp oder zur UX des Prototypen. Umso realistischer der Prototyp umso besser das Feedback. Und natürlich was ist das Ziel der Befragung

La fidélité du prototype va dépendre de votre objectif, mais surtout du public auquel il est destiné. En effet, plus la cible a un niveau d’expertisé élevé, plus l’abstraction sera possible. En effet, il sera plus facile pour un public expert de se projeter. Aussi suivant l’objectif du test, une haute fidélité des prototypes sera nécessaire.

Mir fehlen hier standardisierte Messinstrumente zur Messung von Usability und/oder User Experience: System Usability Scale (SUS) sowie User Experience Questionaire (UEQ). In frühen Entwicklungsstadien würde ich zudem von zuviel messen abraten; es sind ja keine summativen Tests. Test mit der Stoppuhr bei einem sehr bedingt-funktionalen Prototypen machen wenig Sinn. Es geht um Exploration und Iteration beim Einsatz von low-fidelity-Prototypen. Und bevor ich es vergesse: Der NPS misst nicht UX! Sondern die Weiterempfehlungsbereitschaft.

Having a clear and agreed-upon hypothesis before creating a prototype is beneficial because it provides direction and purpose to the design and development process, helping you make informed decisions about fidelity, target audience, and research questions.

In addition to pinning down specific objectives and metrics for testing, it's important to set a cadence of testing that comports with the "share early and often" adage. Hearing from users only once during development, for example, won't ensure you get a result that meets user needs. Sharing and gaining feedback throughout the development process is critical.

Defining clear objectives and metrics is crucial in ensuring meaningful insights from user testing. Low-fidelity prototypes often focus on basic comprehension and concept validation, while high-fidelity prototypes aim to gather feedback on user satisfaction and overall experience. Metrics like task completion rate, time on task, and error rate help gauge usability and efficiency. Satisfaction scores and Net Promoter Scores (NPS) provide insights into user delight and the likelihood of users recommending the app. Aligning these metrics with prototype fidelity and UX goals helps in setting realistic expectations and understanding the user experience at different development stages.

The mobile app testing objectives encompass usability, UX, feature-specific testing, navigation, visual design, accessibility, performance, error handling, and user engagement. Usability Assessment evaluates overall usability, while UX Evaluation assesses satisfaction. Feature-Specific Testing measures success rates. Navigation testing evaluates structure, Visual Design and Branding assess aesthetics, and Accessibility checks for compliance. Performance Testing examines responsiveness. Error Handling and Recovery assesses error management. User Engagement and Retention aims to understand engagement with metrics like user engagement and feedback on app use influencers.

If your resources are limited - stick to the 5-user rule. Conducting user tests with only 5 people can reveal nearly as many usability issues as testing with a larger group of participants. Following this rule will almost always get you close to user testing's maximum benefit-cost ratio.

Verhalten und Einstellungen, Kundenstatus, Erfahrungen im Umgang mit dem Produkt / UI sind deutlich relevanter als Demografische Merkmale. Machen Sie sich zudem bewusst: wenn Sie nach Personas rekrutieren, wird da NIE genau die "Manuela" und der "Dieter" sitzen. Die echten Menschen werden alle dicker, gr??er, jünger, ?lter sein und auch andere Haarfarben als ihre Personas haben.

En primer momento podemos hacer test de usabilidad baratos con plataformas como Maze, eligiendo pocas personas que representen a nuestro público objetivo. A futuro, con prototipos de alta fidelidad podemos hacer entrevistas con usuarios.

Consider unconventional methods of recruitment like niche online forums or community events, not just the usual social media or referral channels.

Don’t be afraid to share the prototype around the team, soliciting feedback before you send things out often can already pin point areas in the flow or prototype that may not be intuitive or clear. Use this opportunity to refine the prototype early on and build more confidence before it reaches your user segments.

Selecting the appropriate testing method and tool for your mobile app prototype involves considering factors like budget, objectives, and prototype fidelity. Moderated testing offers direct guidance and interaction with testers, while unmoderated testing allows for more independent exploration. Remote testing provides flexibility in reaching diverse user groups, whereas in-person testing enables closer observation of user reactions and non-verbal cues. Tools like Figma, InVision, Marvel, UserTesting, Lookback, or TestFlight offer various functionalities for prototype testing, each with its strengths in facilitating different testing methods and capturing user feedback efficiently.

To successfully cater to your audience, it is essential to carefully choose: Moderated testing can reveal various requirements, such as the difficulties older generations face with navigation and the design preferences of students. Remote testing helps you reach more people, from Kashmir to Kerala. It's important to make sure the testing tools are easy to use and accessible to everyone, from basic phone users to those with advanced gadgets. In-person sessions, such as observing the reactions and emotions of users, can provide invaluable insights. However, it is important to bear in mind that this method has geographic limitations. To create a successful product, it is important to find a balance between different testing methods.

You will never choose the best method without testing them. Gather professional opinions but "test your test tools". Why not? And always be connected with the recent innovations, don't fear the evolution baby.

Remote testing is a method that involves testing your app prototype with users who are located in different places, using online tools or platforms. Remote testing can help you to reach a larger and more diverse audience, as well as to save time and money. Some examples of remote testing tools are Lookback, UXtweak, and Loop 11. In-person testing is a method that involves testing your app prototype with users who are physically present in the same location, using devices or simulators. In-person testing can help you to observe the users’ behavior and reactions, as well as to ask questions and get immediate feedback. Some examples of in-person testing tools are TestFlight, Android Studio, and Xcode.

Enjoyed your section on prototyping tools. Recently used ProtoPie for user testing and was impressed. It's user-friendly, great for creating realistic interactions, and supports effective collaboration. ProtoPie really helped in quickly gathering user feedback, essential for our project's success. Highly recommend it for anyone in UX --- This version is straightforward and to the point, focusing on the key benefits of ProtoPie.

Absolutely, meticulous preparation for test sessions is vital. Having a detailed test script, consent forms, necessary devices, recording tools, and note-taking aids streamlines the testing process. Clear communication with testers about the test's purpose, duration, and expectations sets the right context. Encouraging testers to articulate their thoughts aloud and share honest feedback helps uncover valuable insights. Observing their interactions attentively without influencing or leading them ensures unbiased feedback. Using open-ended questions during the test allows for a deeper understanding of their preferences, pain points, and behaviors.

Machen Sie unbedingt einen Pretest bzw. dry run mit ca. 10% Ihrer Stichprobengr??e. Planen sie zudem nach den ersten beiden Interviews eine l?ngere Pause ein und ggf. noch Modifikationen am Leitfaden / Testgegenstand vorzunehmen. Vergessen Sie nicht, bei moderierten Studien m?glichst viele Stakeholder dazu zubewegen, die Interviews still mitzuverfolgen - entweder im Beobachtungsraum oder via Web-Streaming. Das führt zu wirklichen AHA-Erlebnissen bei allen Beteiligten. Sofern m?glich, sollten sich die Personen mindestens 2 Interviews anschauen, damit der Eindruck weniger subjektiv wird.

Setting your success criteria and having a proper test plan and strategy is critical. If not you’ll end up with a variety of feedback and no clear outcome or strategy for moving forward. Important functionality can be overlooked which will lead to re-work.

Algo extremamente necessário é a comunica??o, assim, um pouco mais de detalhes sobre esse tópico. - Explique o propósito, a dura??o e as expectativas do teste. - Certifique-se de que os testadores saibam o que você está tentando aprender e o que você espera que eles fa?am. - Seja claro e conciso em suas instru??es. Evite usar jarg?es ou termos técnicos que os testadores possam n?o entender. - Fa?a perguntas abertas e de sondagem. Isso ajudará você a entender as experiências e opini?es dos testadores. Você pode fornecer aos seus testadores um guia de teste que inclua informa??es sobre o propósito do teste, os tipos de tarefas que eles ser?o solicitados a realizar, e o tipo de feedback que você está procurando.

deixar os testadores falarem abertamente, além das perguntas que v?o guiar o teste, permite que novas ideias ou perspectivas surjam. Talvez alguém traga algo potencialmente transformador para seu produto/servi?o. O melhor caminho s?o testes e valida??es sem os testadores saberem exatamente o q est?o validando. Entendem o contexto mas n?o o ponto principal. Isso faz com que seja validado o que ele realmente usa e n?o o que o testador acha que usa.

In my projects, analyzing and reporting findings from mobile app prototype testing is pivotal for informed decision-making. My team and I employ qualitative and quantitative methods to extract meaningful insights. In my projects, I utilize analytics tools, observe user interactions, and gather feedback to identify patterns and pain points.

Le rapport est une étape clé car il va forger une vision commune pour l’ensemble de l’équipe de conception. Dès lors, il faut être vigileant à ne pas faire des comptes rendus trop techniques afin que l’ensemble de l’equipe arrive facilement à interpréter les résultats. Il m’est arrivé de croiser des experts en UX qui rédigeaient des rapports incompréhensibles pour les clients finaux, rendant les resultats inexploitables pour le commun des mortels.

Analyzing and reporting findings from user testing is crucial for deriving actionable insights. Reviewing and organizing collected data to identify recurring themes, patterns, and insights aligned with testing objectives and metrics is key. Highlighting the strengths, weaknesses, opportunities, and threats observed in the prototype helps in understanding areas of improvement and potential innovation. Creating a comprehensive report summarizing findings with visualizations enhances clarity and communication of results. Sharing this report with stakeholders and team members ensures alignment on identified issues and proposed improvements.

The goal at this is form an inference. Dig through the findings and sort them thematically. Data will challenge any assumptions you’ve made in the beginning (this is perfectly fine??) You might also discover previous lines of opportunity, don’t hesitate to raise this in the executive summary or findings as well.

In other words, you need to make an affinity diagram to synthesize the data. As mentioned in the post, finding the pattern is the key. Also look for how many times same or similar subjects popped up. It worth of mentioning Kano Model.

Encourage participants to provide open-ended responses and suggest their own ideas to uncover additional insights that can contribute to an enhanced user experience. Gathering diverse perspectives during testing can greatly enhance the results. ??

I believe that it is important to keep an open mind and be ready to accept alternative views and potentially unexpected findings that can help to improve the product and its adoption. While such outcomes can demand additional efforts and resources, it is critical to make a decision about what is more important — getting an MVP to market asap, or keep improving it before going to market. This decision will depend on numerous factors, and will vary from product to product, depending on context and circumstances.

Keep an open mind. You might be frustrated with the results you get from your testing, but if people are not on-board, and enjoying your design(s), then you have just successfully tested your prototype. The next iteration will be better.

é fundamental evitar vieses. Todos nós temos algum e sempre tentamos fazer com que outras análises e opini?es acabem confirmando o que queremos. Ter mais de uma pessoa contribuindo em processos de teste pode ser relevante para garantir melhores resultados, especialmente se nos focarmos em times diversos e inclusivos.

Considero que uma boa usabilidade precisa ter pouco de empatia e ser prática. Levar ao usuário uma linguagem clara e intuitiva para que entenda a aplica??o e n?o desista de usa-lá.