Ui analysis in android

May 10, 2017Download as PPTX, PDF0 likes163 views

Presented in 2012, these slides showcase an analysis over UI in Android applications. By showing examples, other apps and heuristics, it draws some guidelines for the development of mobile apps that have not lost their relevance.

Interface analysis in Android
applications
Eng. Vítor de Almeida

Heuristics Evaluation
• Heuristics: Experience-based techniques for
problem solving, learning and discovery
– Less of a rule, more of a guideline
• Classic set of heuristics by Jakob Nielsen (1)
– Rule set is not carved in stone

Heuristics Evaluation
• 1. Visibility of system status
• 2. Match between system and the real world
• 3. User control and freedom
• 4. Consistency and standards
• 5. Error prevention
• 6. Recognition rather than recall
• 7. Flexibility and efficiency of use
• 8. Aesthetic and minimalist design
• 9. Help users recognize, diagnose, and recover from
errors
• 10. Help and documentation

Heuristics Evaluation
• 1. Visibility of system status

Heuristics Evaluation
• 2. Match between system and the real world
Consulte a documentação que veio com
seu telefone para instruções adicionais
Leia as instruções que vieram
com seu telefone
Seu telefone está se comunicando
com os servidores do Google para
acessar a sua conta. Esta operação
pode demorar cinco minutos.
Seu telefone está contactando o Google.
Esta operação pode demorar 5 minutos.

Heuristics Evaluation
• 3. User control and freedom
Default
functionality
Data
selection
Scroll /
Sibling
Rearrange
data
Zoom In / Text
selection
Zoom
In
Zoom
out

Heuristics Evaluation
• 4. Consistency and standards

Heuristics Evaluation
• 5. Error prevention

Heuristics Evaluation
• 6. Recognition rather than recall

Heuristics Evaluation
• 7. Flexibility and efficiency of use

Heuristics Evaluation
• 8. Aesthetic and minimalist design

Heuristics Evaluation
• 9. Help users recognize, diagnose, and
recover from errors

Heuristics Evaluation
• 10. Help and documentation

Other Interface Analysis
tools
• Fitts's Law analysis
• Cognitive Walkthrough
• Streamlined Cognitive Walkthrough
• Usability Testing

Fitts's Law
• T = a + b log2(1 + D/W) T' = k*(D'/W')

Cognitive Walkthrough
• First/Next atomic action user should take
• How will user access description of action?
• How will user associate description with
action?
• All other variable actions less appropriate?
• How will user execute the action?
• If timeouts, time for user to decide before
timeout?
• Execute the action. Describe system response.
• Describe appropriate modified goal, if any.

Streamlined Cognitive
Walkthrough
• Will the user know what to do at this step?
• If the user does the right thing, will they
know that they did the right thing, and are
making progress towards their goal?

• 1. Jakob Nielsen Ten Usability Heuristics - http://www.useit.com/papers/heuristic/heuristic_list.html
• 2. Fitts law - http://en.wikipedia.org/wiki/Fitts's_law
• Android developer's Design guide - http://developer.android.com/design/index.html

Evaluation techniques can be used at all stages of the design process to test interfaces and identify problems. There are two main categories of evaluation: expert analysis and user participation. Expert analysis includes cognitive walkthroughs, heuristic evaluations, and review-based evaluations. User participation evaluations involve testing with users and can be done in laboratories, fields studies, or experiments. A variety of techniques exist within each category to gather both qualitative and quantitative feedback. Choosing an evaluation method depends on factors like the design process stage, desired objectivity, and available resources.

Usability EvaluationSaqib Shehzad

��

The document discusses various methods for evaluating the usability of interfaces and software systems. It describes the goals of evaluation as assessing functionality, interface effects, and identifying specific problems. Both analytical and empirical testing methods are covered. Analytical methods include heuristic evaluation, consistency inspection, and cognitive walkthrough. Empirical methods involve observation/monitoring of users and experimentation. Key aspects discussed for evaluation include iterative testing, formative vs. summative approaches, and the DECIDE framework.

Delhi it professionalsSushil Bharwani

��

This document discusses heuristic evaluation, a discount usability testing technique developed by Jacob Nielsen. Heuristic evaluation involves having a small group of 3-5 evaluators independently examine a user interface and identify any usability issues based on 10 design heuristics. Evaluators then aggregate their findings and assign severity ratings to identify the most critical problems. Heuristic evaluation is less costly than other usability testing methods but can still find several usability issues. The document outlines the phases of heuristic evaluation and describes the 10 design heuristics that evaluators use to examine a user interface, such as providing feedback on system status, using familiar language and metaphors, and enabling user control and freedom of use.

Heuristic evaluationSem Gebresilassie

��

Non functional requirements. do we really care…?OSSCube

��

Non Functional requirements are an essential part of a project’s success, sometimes it becomes less focused area as everyone tries to make project successful in terms of functionality. This recorded webinar uncovers what can happen if Non Functional requirements are not addressed properly. What are the after impacts? You also learn the importance of Non Functional requirement, their identification, implementation and verification.

Requirement EngineeringJonathan Christian

��

The document discusses various aspects of requirements engineering including processes, techniques, challenges, and importance. It describes requirements elicitation, analysis, specification, validation, and management. Key points covered include feasibility studies, types of requirements, characteristics of good requirements, requirements traceability and evolution. Diagrams like use cases, activity diagrams and data flow diagrams are presented as examples of requirements specification outputs.

Heuristic evaluation principlesChetan Manchi Prahlada

��

ICS3211_lecture 03 2023.pdfVanessa Camilleri

��

This document provides an overview of week 2 of an intelligent interfaces course. It discusses theoretical frameworks for human-computer interaction (HCI), including information processing models. Intelligent interfaces aim to enhance flexibility, usability and power of interaction by exploiting knowledge of users, tasks and context. Theories that view HCI as information processing and as socially embedded processes are examined. Methods for evaluating information processing like signal detection and chronometry are also outlined.

05 REQUIREMENT ENGINEERING for students ofAssadLeo1

��

Unit 2 SEPM_ Requirement EngineeringKanchanPatil34

��

The document discusses core principles of software engineering and requirements engineering. It outlines seven principles proposed by David Hooker for software engineering which focus on adding value to users, keeping designs simple, maintaining vision, considering future maintainers and users, planning for reuse, and applying thorough thought. It then describes the key tasks in requirements engineering as inception, elicitation, elaboration, negotiation, specification, validation and management. Data modeling is also discussed including defining data objects, attributes, relationships, modality and cardinality.

REQUIREMENT ENGINEERINGSaqib Raza

��

SD West 2008: Call the requirements police, you've entered design!Alan Bustamante

��

The document discusses best practices for separating requirements and design, as including too much design detail in requirements documentation can lead to increased rework, unrealistic customer expectations, and unnecessary constraints on developers, and it provides recommendations such as using control-agnostic use cases and defining data elements in a shared glossary rather than within use cases.

The art of project estimationReturn on Intelligence

��

The document discusses various techniques for project estimation including three point estimation, Delphi method, planning poker, function point analysis, use case points, and PERT diagrams. It provides details on each technique including how they are conducted, their advantages and disadvantages, and when each is best applied. The key aspects that estimators need to consider for large scale projects are work partitioning challenges, increasing communication overhead with larger teams, and understanding how fast the project can realistically be completed based on its size.

Design and Evaluation techniques unit 5KrishnaVeni451953

��

Heuristic evaluationDikshyanta Dhungana

��

Heuristic evaluation is a usability inspection method where experts evaluate a design against recognized usability principles called heuristics. It was developed by Jakob Nielsen in 1994 and involves experts inspecting a design to identify any violations of 10 predefined heuristics. Some of these heuristics include ensuring the system status is visible, matching the design to real world expectations, and preventing errors from occurring. Heuristic evaluation provides quick feedback to designers and can identify issues, though it requires experienced evaluators and may miss some major usability problems.

FutureOfTesting2008vipulkocher

��

The document discusses present problems and future solutions for software testing. It notes that science fiction ideas often become reality and proposes several futuristic testing ideas that could one day exist, such as self-testing code, integrated software monitoring systems, and automated distributed testing services. It also outlines challenges in testing like determining when enough testing has been done, estimating testing time, and getting developers involved in testing. The document envisions an integrated testing environment that maps requirements, design, code, and tests to automate much of the testing process.

Game Design 2: Expert Evaluation of User InterfacesDavid Farrell

��

This document discusses expert evaluation methods for assessing game designs without end users. It describes cognitive walkthroughs where experts think like users to evaluate if goals and actions are clear. It also discusses heuristic evaluations where experts assess how a design conforms to predefined usability guidelines like Nielsen's heuristics. Both methods are alternatives to user testing that are quicker and cheaper. A minimum of three to five expert evaluators is typically recommended to find different usability issues.

Software Engineering MethodologiesNesrine Shokry

��

This document discusses software engineering methodologies. It begins by defining software and software engineering. It then covers the software development life cycle including processes like requirements analysis, design, development, testing and maintenance. It describes various methodologies like waterfall, prototyping, iterative development and agile. Waterfall is a linear sequential model while agile focuses on rapid iteration, customer collaboration and responding to change. The document compares agile and plan-driven methods, noting their different suitability based on factors like project length, team experience and requirements stability.

Evaluating User InterfacesNancy Jain

��

Guerilla Human Computer Interaction and Customer Based DesignQuentin Christensen

��

SRE.pptxKalsoomBajwa

��

Requirements engineering is the process of establishing the services a system should provide and the constraints under which it should operate. It involves several key tasks: inception to understand the problem domain; elicitation to gather requirements; elaboration to refine and model requirements; negotiation to prioritize requirements; specification to document requirements; validation to verify requirements; and management to track requirements throughout the project. The goal is to clearly define what the customer wants in order to establish a solid foundation for software development.

Software engineering Unit 2(Updated)2.pptxsinghpriyansh0510

��

System Life CycleMomina Mateen

��

The document discusses the systems development life cycle and its key phases including systems analysis, design, development and testing, and implementation. It provides details on the various techniques used in systems analysis such as questionnaires, interviews, observation, and documentation reviews. The document also covers the design phase including designing input/output screens, reports, file structures, and validation routines.

Requirement Elicitation Techniques/MethodsSUFYAN SATTAR

��

Precise and Complete Requirements? An Elusive GoalLionel Briand

��

The document discusses the challenges of achieving precise and complete requirements upfront in software development projects. It notes that while academics assume detailed requirements are needed, practitioners find this difficult to achieve in reality due to limited resources, uncertainty, and changing needs. The document provides perspectives from practice that emphasize starting with prototypes and visions rather than detailed specifications. It also summarizes research finding diverse requirements practices across different domains and organizations. The document concludes that while precise requirements may be desirable, they are often elusive goals, and the focus should be on achieving compliance and delivering working software.

Chapter3 KaiEnTee1

��

This document discusses evaluation techniques for user interfaces, including cognitive walkthroughs and heuristic evaluation. It provides details on how to conduct a cognitive walkthrough, which involves experts walking through a design to identify potential usability issues. It also describes Nielsen's 10 usability heuristics for heuristic evaluation, such as visibility of system status and user control. Examples are given to illustrate how each heuristic can be applied.

Methodology Selection Strategy Ajeng Savitri

��

This document discusses methodology selection strategy for systems analysis and design. It explains that there is no single framework appropriate for every software project, and the methodology needs to be adapted to the specific team and product. It outlines important factors to consider like clarity of requirements, technology familiarity, system complexity, schedule constraints. The methodology should guide the team's process but allow flexibility. The success of the methodology is measured by timely delivery of quality product increments that satisfy stakeholders.

LiveOps para games usando o FirebaseVítor Bruno de Almeida

��

Como criar e integrar a tecnologia dos chatbotsVítor Bruno de Almeida

��

Os chatbots estão com força total e muitas pessoas apostam neles como uma tecnologia que pode revolucionar o mercado dos apps. Os chatbots já são utilizados para fazer compras, chamar um táxi e muito mais e, após o último Google I/O, a tecnologia deve se espalhar ainda mais. Nesta talk iremos mostrar, de forma aplicada, como a criação de um chatbot funciona e como ele pode ser integrado a produtos, como o Google Assistant e, em especial, a um aplicativo Android, trazendo mais valor para a solução como produto e diferenciais de UX ao app.

Ui analysis in android

1. Interface analysis in Android applications Eng. Vítor de Almeida

2. Importance of interface

3. Interface analysis

4. Interface analysis

5. Interface analysis

6. Interface analysis

7. Interface analysis

8. Heuristics Evaluation • Heuristics: Experience-based techniques for problem solving, learning and discovery – Less of a rule, more of a guideline • Classic set of heuristics by Jakob Nielsen (1) – Rule set is not carved in stone

9. Heuristics Evaluation • 1. Visibility of system status • 2. Match between system and the real world • 3. User control and freedom • 4. Consistency and standards • 5. Error prevention • 6. Recognition rather than recall • 7. Flexibility and efficiency of use • 8. Aesthetic and minimalist design • 9. Help users recognize, diagnose, and recover from errors • 10. Help and documentation

10. Heuristics Evaluation • 1. Visibility of system status

11. Heuristics Evaluation • 2. Match between system and the real world Consulte a documentação que veio com seu telefone para instruções adicionais Leia as instruções que vieram com seu telefone Seu telefone está se comunicando com os servidores do Google para acessar a sua conta. Esta operação pode demorar cinco minutos. Seu telefone está contactando o Google. Esta operação pode demorar 5 minutos.

12. Heuristics Evaluation • 3. User control and freedom Default functionality Data selection Scroll / Sibling Rearrange data Zoom In / Text selection Zoom In Zoom out

13. Heuristics Evaluation • 4. Consistency and standards

14. Heuristics Evaluation • 5. Error prevention

15. Heuristics Evaluation • 6. Recognition rather than recall

16. Heuristics Evaluation • 7. Flexibility and efficiency of use

17. Heuristics Evaluation • 8. Aesthetic and minimalist design

18. Heuristics Evaluation • 9. Help users recognize, diagnose, and recover from errors

19. Heuristics Evaluation • 10. Help and documentation

20. Other Interface Analysis tools • Fitts's Law analysis • Cognitive Walkthrough • Streamlined Cognitive Walkthrough • Usability Testing

21. Fitts's Law • T = a + b log2(1 + D/W) T' = k*(D'/W')

22. Fitts's Law ∞ ∞

23. Fitts's Law

24. Cognitive Walkthrough • First/Next atomic action user should take • How will user access description of action? • How will user associate description with action? • All other variable actions less appropriate? • How will user execute the action? • If timeouts, time for user to decide before timeout? • Execute the action. Describe system response. • Describe appropriate modified goal, if any.

25. Streamlined Cognitive Walkthrough • Will the user know what to do at this step? • If the user does the right thing, will they know that they did the right thing, and are making progress towards their goal?

26. Usability Testing

27. • 1. Jakob Nielsen Ten Usability Heuristics - http://www.useit.com/papers/heuristic/heuristic_list.html • 2. Fitts law - http://en.wikipedia.org/wiki/Fitts's_law • Android developer's Design guide - http://developer.android.com/design/index.html

Editor's Notes

#2: - Não damos a devida importância em análise de interface - Uma UI bem feita aumenta a intuitividade, eficiência e conforto de um produto, traduzindo-se em maior aceitação e uso do mesmo. - Preconceito com UI entre developers que, possivelmente, é a parte mais valorizada pelo usuário - Uso de conceitos antigos ou inadequados para desenvolvimento e avaliação de interfaces - Contextualizar, atualizar e adaptar regras para a nossa realidade (Android, 2012) Tópicos da apresentação: - Básico em análise de interfaces - Novos paradigmas introduzidos a partir do Android 3.0 - Uso das guidelines de interface do Android
#4: - Erros bizarros de interface ilustram como a preocupação com o usuário nunca foi uma preocupação de developers - Preocupação com intefaces bem planejadas é uma tendência mais atual e de importância grande, podendo determinar o sucesso ou fracasso de um produto - Erros de interface não são exclusivos de software
#5: - Nokia N Gage - Provavelmente um dos maiores responsáveis pelo declínio da Nokia, o N Gage prometia e não cumpria. - Sidetalking: Microfone e speaker na lateral do aparelho (Não engordura a tela), gerou inclusive um meme com um site dedicado onde usuários postavam fotos 'sidetalking' com namorada, monitores, estátuas, etc... - Formato de croissant, taco ou algo semelhante - Necessidade de remover a bateria para trocar de jogo - Oakley Thump Sunglasses - Controles do áudio de difícil acesso - Capacidade de apenas 256MB - Preço de $495 (Um ipod de 40GB na época saia por $399) - Incapacidade de ouvir músicas sem usar óculos escuros - Mas não se limita apenas ao mundo da tecnologia!
#9: - Numa análise baseada em heurísticas, tomamos algumas regras pré-estabelecidas para determinar a eficácia de uma interface - A análise baseada em heurísticas é amplamente adotada por ser uma alternativa que apresenta bons resultados a um custo operacional baixo - Duas análises baseadas no mesmo conjunto de heurísticas podem produzir resultados bem diferentes, mas são resultados que se completam - As regras são linhas gerais, devemos nos orientar por elas mas sempre com bom senso e tomando em conta outros fatores como o público-alvo e o meio ambiente envolvido
#11: Visibilidade do estado do sistema: O sistema deve sempre manter o usuário ciente do que está acontecendo, utilizando-se de feedback apropriado em um tempo razoável.
#12: Correspondência entre o sistema e o mundo real: O sistema deve falar a língua do usuário, usando palavras, frases e conceitos que sejam familiares ao usuário, ao invés de termos orientados ao sistema. Convenções do "mundo real" devem ser seguidas, fazendo a informação aparecer numa ordem natural e lógica.
#13: Controle do usuário e liberdade: O usuário vai usar funções do sistema por engano e vai precisar de uma "saída de emergência" para escapar do estado atual sem ter que passar por todo o fluxo inverso. Dar suporte a "desfazer" e "refazer".
#14: Consistência e padrões: O usuário não deve ser obrigado a adivinhar se palavras, situações ou ações diferentes significam a mesma coisa. Convenções da plataforma devem ser seguidas.
#15: Prevenção de erros: Melhor do que uma boa mensagem de erro é um design cuidadoso que previna que o erro aconteça. Elimine condições propícias ao erro ou faça com que o usuário se certifique da ação que ele irá realizar antes de proceder.
#16: Reconhecimento ao invés de recordação: Minimize a carga de memória do usuário fazendo com que objetos, ações e opções estejam visíveis. O usuário não deve ser obrigado a se lembrar de informações de uma parte do dialogo para outra parte. Instruções para o uso do sistema devem estar visíveis ou serem facilmente recuperáveis sempre que apropriado.
#17: Flexibilidade e eficiência do uso: Aceleradores, invisíveis para o usuário novato, podem acelerar a interação para usuários experientes de forma que o sistema possa atender a ambos tipos de usuário. Permitir que usuários personalizem ações frequentes.
#18: Estética e design minimalista: Diálogos não devem conter informação irrelevante ou raramente necessária. Cada unidade de informação extra num diálogo compete com unidades relevantes de informação e diminuem sua visibilidade.
#19: Ajudar o usuário a reconhecer, diagnosticar e se recuperar de erros: Mensagens de erro devem ser expressas em língua nativa (nada de código), indicar o problema precisamente e construtivamente sugerir uma solução.
#20: Ajuda e documentação: Mesmo que seja melhor que o sistema possa ser usado sem documentação, pode ser necessário providenciar um "ajuda" e documentação. Qualquer informação dessa natureza deve ser de fácil acesso, focada na tarefa do usuário, listar passos concretos para serem seguidos e não ser grande demais.
#21: Uma análise heurística é rápida, barata e eficiente, porém não resolve todos os problemas nem da garantia nenhuma sobre o resultado final. Existem outros tipo de análises, algumas baratas, outras nem tanto, que completam a análise de UI
#22: A Lei de Fitts mostra que o tempo (T) gasto para se clicar em um alvo varia proporcionalmente à distância até o alvo e inversamente com a largura desse alvo em relação à direção do deslocamento Em um mundo 2D, entendemos a largura como a área do alvo
#23: - Em computadores, para otimizar o tempo gasto por um usuario para acessar um certo item na tela, segundo a lei de fitts, o tamanho deve ser aumentado e a distancia deve ser diminuida. Objetos colocados nos cantos da tela tem, na prática, um tamanho infinito pois o mouse não ultrapassa a lateral das telas, assim, arrastando o mouse numa velocidade grande não se erra o alvo. Outro ponto ideal seria a posição atual do cursor, assim o usuário precisa apenas clicar.
#24: - Em dispositivos touch, essa relação muda. Os cantos estão longe de serem ótimos para se acertar um toque. - Em verde está a área que o usuário presta mais atenção visual. Região ótima para eye-candy e informações. - Em vermelho está a área que o usuário menos presta atenção. Por estar em uma região inferior, é uma região que o usuário tem maior facilidade de alcançar para o toque, tornando esta região ótima para controles de navegação, por exemplo. - Seta roxa seria o eixo ótimo para destros, branco o eixo ótimo para canhotos.
#26: Bolado para viabilizar o walkthrough cognitivo em ambientes corporativos. Consiste em 2 testes objetivos para cada cenário de uso do aplicativo. Equipe de testes deve ser preparada para aplicar estes passos corretamente.
#27: A partir de análises anteriores e do perfil do usuário são preparados alguns cenários de testes. Os testes são realizados, geralmente, em ambientes controlados, onde podem ser notadas as reações do usuário aos comportamentos do sistema. Podem ser feitos em ambientes abertos, dependendo do que exatamente se quer testar. Outros testes possíveis - Entrevistas - Benchmarking - Comparação com produtos competidores

�ݺ�ߣ

Ui analysis in android

Recommended

More Related Content

Similar to Ui analysis in android (20)

More from Vítor Bruno de Almeida (6)

Ui analysis in android

Editor's Notes