Relevant bibliographies by topics / API usability

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'API usability'

Author: Grafiati
Published: 4 June 2021
Last updated: 1 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'API usability.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "API usability"

1

Daughtry, John M., Umer Farooq, Brad A. Myers, and Jeffrey Stylos. "API usability." ACM SIGSOFT Software Engineering Notes 34, no. 4 (July 6, 2009): 27–29. http://dx.doi.org/10.1145/1543405.1543429.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Myers, Brad A., and Jeffrey Stylos. "Improving API usability." Communications of the ACM 59, no. 6 (May 23, 2016): 62–69. http://dx.doi.org/10.1145/2896587.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Scheller, Thomas, and Eva Kühn. "Automated measurement of API usability: The API Concepts Framework." Information and Software Technology 61 (May 2015): 145–62. http://dx.doi.org/10.1016/j.infsof.2015.01.009.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Rama, Girish Maskeri, and Avinash Kak. "Some structural measures of API usability." Software: Practice and Experience 45, no. 1 (September 3, 2013): 75–110. http://dx.doi.org/10.1002/spe.2215.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Tello-Rodríguez, Maribel, Jorge Octavio Ocharán-Hernández, Juan Carlos Pérez-Arriaga, Xavier Limón, and Ángel J. Sánchez-García. "A Design Guide for Usable Web APIs." Proceedings of the Institute for System Programming of the RAS 33, no. 1 (2021): 173–88. http://dx.doi.org/10.15514/ispras-2021-33(1)-12.

Full text
Abstract:
Cloud computing trends such as Software as a Service (SaaS) enable providers to host complex applications over the Internet, making them available to external consumers through an Application Programming Interface (API). The success of a SaaS, and in some sense any distributed system, is greatly influenced by its API. Highly usable APIs improve the efficiency of the development process and its quality, ensuring that programmers continue to appreciate other aspects of the API while increasing their productivity. Different studies state that the design phase within the development process of an API is the most appropriate to address usability issues. Therefore, usability should be considered as an explicit criterion in the design of an API. In this paper, we propose a design guide for web APIs with an emphasis on usability, using the best practices of usable web APIs design. Our design guide is based on an adaptation of the design science research methodology (DSRM), and it is complemented with a systematic literature review and gray literature analysis concerning methods, techniques, and tools used to develop usable APIs.
APA, Harvard, Vancouver, ISO, and other styles
6

Ependi, Usman. "HEURISTIC EVALUATION FOR MOBILE APPLICATION (STUDI KASUS: APLIKASI DEPO AUTO 2000 TANJUNG API API PALEMBANG)." Simetris : Jurnal Teknik Mesin, Elektro dan Ilmu Komputer 8, no. 2 (November 1, 2017): 563. http://dx.doi.org/10.24176/simet.v8i2.1525.

Full text
Abstract:
Heuristic evaluation merupakan salah satu bentuk usability testing perangkat lunak yang dinilai oleh pengguna (evaluator). Dalam melakukan heuristic evaluation instrumen penilaian terdiri dari sepuluh (10) pernyataan dengan lima pilihan jawaban dalam skala severity ratings. Dalam penelitian ini heuristic evaluation terhadap aplikasi Depo Auto 2000 Tanjung Api-Api Palembang yang dilakukan oleh 4 evaluator. Hasil dari heuristic evaluation dikelompokkan kedalam masing-masing instrumen yaitu visibility of system status dengan nilai 0,75, match between system and the real world dengan nilai 0,25, user control and freedom dengan nilai 0,25, consistency and standards dengan nilai 0,75, error prevention dengan nilai 1, recognition rather than recall dengan nilai 1,25, flexibility and efficiency of use dengan nilai 0,25, Aesthetic and minimalist design dengan nilai 0,25, help users recognize, diagnose, and recover from errors dengan nilai 1 dan Help and documentation dengan nilai 0. Dari hasil heuristic evaluation yang dilakukan menunjukkan bahwa evaluator memberikan nilai 0 dan 1 aplikasi Depo Atuo 2000 Tanjung Api-Api Palembang. Hasil penilaian tersebut menunjukkan bahwa aplikasi yang buat tidak ada masalah usability dan hanya memiliki cosmetic problem sehingga aplikasi Depo Auto 2000 Tanjung Api Api Palembang dapat dinyatakan layak untuk didistribusikan kepada pengguna akhir (end user).
APA, Harvard, Vancouver, ISO, and other styles
7

Rauf, Irum, Elena Troubitsyna, and Ivan Porres. "A systematic mapping study of API usability evaluation methods." Computer Science Review 33 (August 2019): 49–68. http://dx.doi.org/10.1016/j.cosrev.2019.05.001.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Tschannen, Philipp, and Ali Ahmed. "Bitcoin’s APIs in Open-Source Projects: Security Usability Evaluation." Electronics 9, no. 7 (June 30, 2020): 1077. http://dx.doi.org/10.3390/electronics9071077.

Full text
Abstract:
Given the current state of software development, it does not seem that we are nowhere near vulnerability-free software applications, due to many reasons, and software developers are one of them. Insecure coding practices, the complexity of the task in hand, and usability issues, amongst other reasons, make it hard on software developers to maintain secure code. When it comes to cryptographic currencies, the need for assuring security is inevitable. For example, Bitcoin is a peer-to-peer software system that is primarily used as digital money. There exist many software libraries supporting various programming languages that allow access to the Bitcoin system via an Application Programming Interface (API). APIs that are inappropriately used would lead to security vulnerabilities, which are hard to discover, resulting in many zero-day exploits. Making APIs usable is, therefore, an essential aspect related to the quality and robustness of the software. This paper surveys the general academic literature concerning API usability and usable security. Furthermore, it evaluates the API usability of Libbitcoin, a well-known C++ implementation of the Bitcoin system, and assesses how the findings of this evaluation could affect the applications that use Libbitcoin. For that purpose, the paper proposes two static analysis tools to further investigate the use of Libbitcoin APIs in open-source projects from a security usability perspective. The findings of this research have improved Libbitcoin in many places, as will be shown in this paper.
APA, Harvard, Vancouver, ISO, and other styles
9

Lee, Jung-Eok, and Eung-Bong Lee. "A Study on the Construction and Usability Test of Meta Search System Using Open API." Journal of the Korean Society for information Management 26, no. 1 (March 30, 2009): 185–214. http://dx.doi.org/10.3743/kosim.2009.26.1.185.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Masurovsky, Alexander, Paul Chojecki, Detlef Runde, Mustafa Lafci, David Przewozny, and Michael Gaebler. "Controller-Free Hand Tracking for Grab-and-Place Tasks in Immersive Virtual Reality: Design Elements and Their Empirical Study." Multimodal Technologies and Interaction 4, no. 4 (December 12, 2020): 91. http://dx.doi.org/10.3390/mti4040091.

Full text
Abstract:
Hand tracking enables controller-free interaction with virtual environments, which can, compared to traditional handheld controllers, make virtual reality (VR) experiences more natural and immersive. As naturalness hinges on both technological and user-based features, fine-tuning the former while assessing the latter can be used to increase usability. For a grab-and-place use case in immersive VR, we compared a prototype of a camera-based hand tracking interface (Leap Motion) with customized design elements to the standard Leap Motion application programming interface (API) and a traditional controller solution (Oculus Touch). Usability was tested in 32 young healthy participants, whose performance was analyzed in terms of accuracy, speed and errors as well as subjective experience. We found higher performance and overall usability as well as overall preference for the handheld controller compared to both controller-free solutions. While most measures did not differ between the two controller-free solutions, the modifications made to the Leap API to form our prototype led to a significant decrease in accidental drops. Our results do not support the assumption of higher naturalness for hand tracking but suggest design elements to improve the robustness of controller-free object interaction in a grab-and-place scenario.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "API usability"

1

Blommendahl, Simon. "An analysis of API usability and Azure API management." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-131750.

Full text
Abstract:
In today’s computer environments the systems are getting bigger and more complex for each day that passes by. The motivating factor for this is that the customer wants to achieve more and more with their computer systems than before. The only way to really solve this task is to use even more APIs (Application program interfaces) in their systems.     When using more APIs in a system, there is a chance that the specific system provides the same type of API twice, which of course, is a waste of storage and resources. In addition, the more APIs a system contains, the bigger the risk is for mismanagement of these APIs. In the worst case, this can result in security breaches or data leaks.  This thesis investigates specific APIs provided for a customer of Sigma IT Consulting. The aim is to evaluate and organize the APIs according to their usability criteria. The main focus of the evaluation is the available documentation which will be evaluated by a questionnaire survey distributed to senior software developers at Sigma IT Consulting in Växjö. Conclusions will then be drawn depending on the result from the survey, and we can then see if Azure API management (which is a service to make a system more user – friendly) is accurate in its way of organizing with the API usability as the main focus! Unfortunately, Azure API management did not have any possibility what so ever to customize the API placement in a system, and the only way the APIs are organized is in alphabetical order. Therefore, a prototype with even more sorting functionality than Azure API management will also be presented in this thesis.
APA, Harvard, Vancouver, ISO, and other styles
2

Kapari, Marianna. "Usability, accessibility andresponsive web design utilizingGoogle Maps API." Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-363984.

Full text
Abstract:
This Master’s thesis describes the development and evaluation of a responsive, map-based website intended to support book sharing in public places. The book sharing concept focuses on allowing a user to locate a book in a public place, register it online and share it again once they have finished reading it. In order to measure the usability of the website, two tests were conducted, which compared the website with another website for book sharing. The first test was conducted using questionnaires, with 24 participants, where as the second test focused on observations and interviews with four participants. Moreover, in order to measure the accessibility of the thesis website, an expert evaluation and an evaluation using accessibility evaluation tools were conducted. The results from the usability tests showed a need for improvements, for instance in the form of supporting documentation and addition of undo/redo options. The results of the expert review were positive while theresults ofthe accessibility tools showed compatibility issues depending on the browser that the website is accessed with.
APA, Harvard, Vancouver, ISO, and other styles
3

Malmkvist, Hampus. "Developing an API wrapper with usability in mind." Thesis, Linköpings universitet, Interaktiva och kognitiva system, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-93637.

Full text
Abstract:
When you are creating new software today, more often than not you will use API’s. Users choosing between different API’s would probably look at functionality but also accessibility and ease of use. It would therefore seem motivated for API providers to create usable and accessible API’s.This thesis is about the things that make an API more usable, and then those things are used in practice to increase the usability of CloudMe’s API. CloudMe’s core API is documented to increase usability and a wrapper for the API is developed to allow people more ways to use CloudMe’s service. The APIwrapper is created in Java and was developed thoroughly with regards to usability.
APA, Harvard, Vancouver, ISO, and other styles
4

Kahlert, Björn [Verfasser]. "API-Usability der auf Templatemetaprogrammierung basierenden Softwarebibliothek „SeqAn“ / Björn Kahlert." Berlin : Freie Universität Berlin, 2015. http://d-nb.info/1080522174/34.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Chhetri, Yam. "Classifying and recommending knowledge in reference documentation to improve API usability." Thesis, McGill University, 2013. http://digitool.Library.McGill.CA:80/R/?func=dbin-jump-full&object_id=114542.

Full text
Abstract:
Reference documentation is an important source of information on API usage. Programmers, however, can easily overlook reference information because of its tedious nature, and because the information they seek can be buried among irrelevant or boiler-plate text. We propose to detect and recommend fragments of API documentation relevant and important to a task. We categorize pieces of information in API documentation based on the type of knowledge they contain. From the pieces that contain knowledge worthy of recommendation, we extract the composition and the pattern of words, and use the patterns to automatically find new pieces that contain similar knowledge. In an evaluation study, with a training set of manually-classified reference documentation of about 1 000 API elements, we could issue recommendations with about, on average, 90% precision and 69% recall.
La documentation de référence est une source importante d'information sur l'usage d'une API. Cependant, les programmeurs peuvent négliger cette information que l'information recherchée se trouve enfouie au milieu de texte passe-partout et sans pertinence. Nous proposons de détecter et recommender les fragments de documentation d'API pertinents à une tâche donnée de façon automatique. Nous catégorisons les morceaux d'information dans la documentation d'API en fonction du type de savoir qu'ils renferment. À partir des morceaux de savoir digne de recommendation, nous extrayons des patrons de mots, puis utilisons ces patrons pour trouver automatiquement de nouveaux morceaux qui renferment un savoir similaire. Nous présentons les résultats d'une évaluation expérimentale de notre système effectuée à partir de plus de 1 000 morceaux d'API, où nous trouvons que notre système offre de recommendations adéquates 90% du temps avec un taux de rappel de 69%.
APA, Harvard, Vancouver, ISO, and other styles
6

Armknecht, Jonathan Blake. "A Developer Usability Study of TLS Libraries." BYU ScholarsArchive, 2020. https://scholarsarchive.byu.edu/etd/8685.

Full text
Abstract:
Transport Layer Security (TLS) is a secure communication protocol between a client and a server over a network. The TLS protocol provides the two endpoints with confidentiality through symmetric encryption, endpoint authentication using public-key cryptography, and data integrity using a MAC. However, studies show that security vulnerabilities within TLS connections are often caused by developers misusing TLS library APIs. We measure the usability of four TLS libraries by performing a developer user study. Participants were given code that connects to google.com through HTTP, and tasked with using a TLS library to change the code so that it connects securely to Google through HTTPS. Our results help show what makes a library usable and what problems arise for developers using these TLS libraries. We found that the main way to ensure a TLS library is usable is to focus on having clear documentation. From our results, we provide suggestions on how to create usable documentation.
APA, Harvard, Vancouver, ISO, and other styles
7

Bennhage, Dennis, and William Utbult. "Design av Användbara API : Formativa Utvärderingsmetoder Applicerade på Utvecklingsprocessen." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-166691.

Full text
Abstract:
Användbarheten hos ett API kan vara en viktig faktor för en slutanvändares produktivitet, eller framgången en mjukvaruprodukt. Det finns ingen enskild definition av, eller metod för att uppnå användbarhet. Många riktlinjer kan vara teoretiska och svårapplicerade. Detta arbete sammanfattar definitioner av och utvärderingsmetoder för användbarhet. En av dessa metoder anpassas och används för en formativ utvärdering som del av utvecklingsprocessen av ett nytt API för röstchatt i webben. API:et specificeras och implementeras i en första version som utvärderas med testanvändare för att hitta användbarhetsproblem. Förbättringsförslag för API:ets vidareutveckling ges baserat på funna problem. Avslutningsvis diskuteras utvärderingsmetoderna utifrån resurserna som krävs för genomförande.
The usability of an API can be an important factor for the productivity of end users, or the success of a software product. There is no single definition of, or method to achieve, usability. Many guidelines can be theoretical and difficult to apply. This paper summarises usability definitions and evaluation methods. One of these methods is adapted and used for a formative evaluation as part of the development process of a new API for web based voice chat. The API is specified and implemented in a first version which is evaluated with test users to find usability problems. Improvement proposals for the further development of the API are given based on found problems. In closing, the evaluation methods are discussed based on the resources required for execution.
APA, Harvard, Vancouver, ISO, and other styles
8

Chivi, Daniel, and Gran Joakim Östling. "Administration av API-drivna enheter och tjänster för slutanvändare : En fallstudie av API-tjänster." Thesis, KTH, Skolan för kemi, bioteknologi och hälsa (CBH), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-223347.

Full text
Abstract:
I dagsläget tenderar många att använda tjänster som hanteras separat. Arbetet undersöker om det är möjligt att sammankoppla ett fåtal tjänster i en gemensam webbapplikation för att underlätta kommunicering mellan tjänsterna samt att förbättra användarvänligheten. Företaget A Great Thing har i åtanke att skapa en webbapplikation som tillåter användare att med hjälp av deras applikation skapa agenter som sköter händelser från användarens begäran, exempelvis “spela upp en låt vid en viss tid”. Metodiken som tillämpats har dels varit en fallstudie och dels användarbaserade metoder i form av enkätundersökning samt ett användartest. Ytterligare undersöktes hur kommunikationen går mellan tjänsters API, och de nödvändiga parametrar som utbyter data. Slutligen evalueras den framtagna prototypen enligt vissa riktlinjer inom användarvänlighet. Examensarbetets resultat är i form av en webbprototyp med fokus på användarvänlighet, implementering av API:er, användartest på faktiska användare samt statistik på efterfrågan av tjänster. Vidare har även en marknadsundersökning utförts för att belysa ekonomiska vinstmöjligheter genom API-distribution. Slutsatsen dras att det är möjligt att sammankoppla API:er och dess tjänster för att uppnå ett användarvänligt gränssnitt samt hur nödvändiga parametrar disponeras på ett effektivt vis. Vidare är förhoppningen att utomstående läsare skapar en förståelse om hur sammankopplingen går till på ett strukturerat och informativt tillvägagångssätt. Även hur olika tekniska metoder inom användarvänlighet kan tillämpas vid konstruktion av prototyper.
Nowadays people tend to use services and appliances that are managed seperately. This thesis examines the possibility of connecting different services into one main web application to faciliate communication between these services. A Great Thing have embraced the need of connecting applications to a single device and therefore, wants to create a web application integrated with the use of agents. These agents are built to manage the events a user request. For example ”Play a song at a specific time”. The methodology applied has partly been a case study and partly user-based methods in form of a survery and a user test. Further research was conducted on communication between service API:s and the necessary parameters that exchange data. Finally, the developed prototype was evaluated according to some usability guidelines. The thesis’s results are presented in the form of a web prototype focused on usability, implementation of APIs, user test of actual users and statistics of demanded services. In addition, a market research has been conducted to highlight economic benefits through API distribution. The conclusion is drawn that it is possible to link API:s and their services to achieve a user-friendly interface and how to use different parameters in an efficient way. Furthermore, the hope is that external readers will understand how the connection between API:s works in a structured and informative approach. Also how different technical methods for usability can be applied in construction of prototypes.
APA, Harvard, Vancouver, ISO, and other styles
9

Bellomo, Michel. "Crospen API: un formalismo per la descrizione di interfacce con metodo CROSS." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2019. http://amslaurea.unibo.it/19634/.

Full text
Abstract:
Lo scopo della tesi è di fornire un processo di produzione user-centered e un formalismo che lo descriva ponendosi come alternativa a basso costo a processi che non prevedano attenzioni per l'utente e l'usabilità del sistema. La tesi descrive per primo lo stato dell'arte in quanto a metodi formali e semi-formali nell'interazione uomo macchina. Successivamente si introduce il metodo CROSS che modifica il processo goal-oriented incentrando l'analisi dei requisiti sulle categorie di utenti dette ruoli, i concetti che manipolano e con quali operazioni. Segue la definizione di Crospen Api, un'estensione dello standard OpenAPI che descriva i prodotti di CROSS, con particolar enfasi del diagramma del sistema, creato seguendo il metodo. Si mette infine alla prova il lavoro, confrontando un sistema reale con una specifica che voglia ripensarne l'interfaccia evitando alcuni degli errori di usabilità.
APA, Harvard, Vancouver, ISO, and other styles
10

D'Arpa, Andrea. "Cross Standard Generator." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2020. http://amslaurea.unibo.it/20528/.

Full text
Abstract:
Lo scopo di questo lavoro è quello di teorizzare un metodo per poter generare in modo automatico applicazioni web basate su operazioni standard su basi di dati, utilizzando un documento di livello comprensibile ad un calcolatore, e contemporaneamente abbastanza astratto da poter essere facilmente interpretabile dall'uomo. Dopo un primo capitolo introduttivo, nel secondo capitolo vengono analizzati dei generatori di interfacce utente andando ad analizzare i rapporti tra le interfacce e l'usabilità del prodotto. Il terzo capitolo invece indaga il processo orientato agli obiettivi (goal-oriented) CROSS per la creazione di software user-centered. Si osservano qui le differenze con un modello goal-oriented tradizionale. Vengono analizzate le cause di inusabilità che CROSS vuole contrastare, per poi, dopo una panoramica andare a vedere nel dettaglio quelle che sono le componenti CROSS: Concetti, Ruoli, Operazioni e Strutture e Schemi.Il quarto capitolo presenta CROSPEN API, il formalismo di rappresentazione e documentazione di Applicazioni Web che rispetta il processo di creazione CROSS. Viene dunque analizzato OpenApi, e successivamente viene spiegata la sua estensione CROSPEN API. Il quinto capitolo presenta lo strumento in se, raccontando le varie idee di sviluppo, l'implementazione dei concetti e le tecnologie impiegate nella sua realizzazione. Vengono analizzate le quattro componenti dell'applicazione: Crosser ( strumento di parsing del file CROSPEN API), Crossback (strumento di generazione del server), DBG (strumento di generazione della base di dati e delle funzioni per la sua gestione ) e CrossVue (il generatore di interfacce utente).Il sesto e ultimo capitolo ha il compito di trarre le conclusioni sul lavoro svolto e di raccontare i propositi di implementazione futuri.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "API usability"

1

Ley, Barbara L. Mothers, Fathers, and the Pregnancy App Experience. University of Illinois Press, 2017. http://dx.doi.org/10.5406/illinois/9780252039577.003.0006.

Full text
Abstract:
This chapter examines the “usability” of pregnancy apps, particularly in terms of their usefulness and user satisfaction, to understand their appeal to a growing number of expectant parents, most—but not all—of whom are women. To this end, the chapter analyzes the aesthetic, therapeutic, and technical design of nine pregnancy apps available in the iTunes store. It also looks at the user reviews that accompanied the apps. On the one hand, the chapter reveals that the architecture and design of pregnancy apps enhance satisfaction among many expectant parents, especially women, by providing them with a range of support tools, options for personalization, and the ability to access support whenever and wherever they need it. On the other hand, the gendered and heteronormative assumptions built into the apps' designs perpetuate hegemonic discourses regarding pregnancy and parenting that can leave some expectant parents, especially fathers, frustrated with their app experience.
APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "API usability"

1

Zeier, Alexander, Alexander Wiesmaier, and Andreas Heinemann. "API Usability of Stateful Signature Schemes." In Advances in Information and Computer Security, 221–40. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-26834-3_13.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Grill, Thomas, Ondrej Polacek, and Manfred Tscheligi. "Methods towards API Usability: A Structural Analysis of Usability Problem Categories." In Human-Centered Software Engineering, 164–80. Berlin, Heidelberg: Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-34347-6_10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Scheller, Thomas, and Eva Kühn. "Usability Evaluation of Configuration-Based API Design Concepts." In Lecture Notes in Computer Science, 54–73. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-39062-3_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Pierce, Taylor, and Dave Wooldridge. "Testing and Usability: Putting Your Best Foot Forward." In The Business of iOS App Development, 239–74. Berkeley, CA: Apress, 2014. http://dx.doi.org/10.1007/978-1-4302-6239-8_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Wooldridge, Dave, and Michael Schneider. "Testing and Usability: Putting Your Best Foot Forward." In The Business of iPhone and iPad App Development, 253–87. Berkeley, CA: Apress, 2011. http://dx.doi.org/10.1007/978-1-4302-3301-5_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Lemmens, Rob, Vyron Antoniou, Philipp Hummer, and Chryssy Potsiou. "Citizen Science in the Digital World of Apps." In The Science of Citizen Science, 461–74. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-58278-4_23.

Full text
Abstract:
AbstractIn this chapter, we highlight the added value of mobile and web apps to the field of citizen science. We provide an overview of app types and their functionalities to facilitate appropriate app selection for citizen science projects. We identify different app types according to methodology, data specifics, and data collection format.The chapter outlines good practices for creating apps. Citizen science apps need to ensure high levels of performance and usability. Social features for citizen science projects with a focus on mobile apps are helpful for user motivation and immersion and, also, can improve data quality via community feedback. The design, look and feel, and project identity are essential features of citizen science apps.We provide recommendations aimed at establishing good practice in citizen science app development. We also highlight future developments in technology and, in particular, how artificial intelligence (AI) and machine learning (ML) can impact citizen science projects.
APA, Harvard, Vancouver, ISO, and other styles
7

Johansen, Johanna, and Simone Fischer-Hübner. "Making GDPR Usable: A Model to Support Usability Evaluations of Privacy." In Privacy and Identity Management. Data for Better Living: AI and Privacy, 275–91. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-42504-3_18.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Fox, Sarah, and Daniel A. Epstein. "Monitoring Menses: Design-Based Investigations of Menstrual Tracking Applications." In The Palgrave Handbook of Critical Menstruation Studies, 733–50. Singapore: Springer Singapore, 2020. http://dx.doi.org/10.1007/978-981-15-0614-7_54.

Full text
Abstract:
Abstract Fox and Epstein interrogate and reimagine menstrual tracking technology, focusing on mobile applications designed to document and quantify menstrual cycle data. While such technology promises to provide users with new insights and predictions, the authors highlight how these apps are inscribed with particular visions of menstruation and encourage users to extract intimate information about their bodies. Apps regularly assume, for instance, that all possible users are women, heterosexual, and monogamous, have a “normal” cycle, and use tracking techniques exclusively to gauge fertility. Fox and Epstein present two case studies: (1) examining core issues of usability and inclusion in the design of existing applications; and (2) using participatory approaches to highlight the lived experiences of menstruators and introduce alternatives to dominant menstrual app protocols. In offering this two-part analysis, they point to important openings for exploring how these technologies might support the needs of a multiplicity of menstruating bodies.
APA, Harvard, Vancouver, ISO, and other styles
9

Bacchin, Davide, Patrik Pluchino, Valeria Orso, Marcello Sardena, Marino Malvestio, and Luciano Gamberini. "Development and Testing of a Usability Checklist for the Evaluation of Control Interfaces of Electrical Medical Beds." In Digital Human Modeling and Applications in Health, Safety, Ergonomics and Risk Management. AI, Product and Service, 3–19. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-77820-0_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

"Incorporating Usability into the API Design Process." In Usability of Complex Information Systems, 251–78. CRC Press, 2010. http://dx.doi.org/10.1201/ebk1439828946-21.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "API usability"

1

Daughtry, John M., Umer Farooq, Jeffrey Stylos, and Brad A. Myers. "API usability." In the 27th international conference extended abstracts. New York, New York, USA: ACM Press, 2009. http://dx.doi.org/10.1145/1520340.1520403.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Farooq, Umer, Leon Welicki, and Dieter Zirkler. "API usability peer reviews." In the 28th international conference. New York, New York, USA: ACM Press, 2010. http://dx.doi.org/10.1145/1753326.1753677.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

O'Callaghan, Portia. "The API walkthrough method." In Evaluation and Usability of Programming Languages and Tools. New York, New York, USA: ACM Press, 2010. http://dx.doi.org/10.1145/1937117.1937122.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Endrikat, Stefan, Stefan Hanenberg, Romain Robbes, and Andreas Stefik. "How do API documentation and static typing affect API usability?" In ICSE '14: 36th International Conference on Software Engineering. New York, NY, USA: ACM, 2014. http://dx.doi.org/10.1145/2568225.2568299.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Dubochet, Gilles, and Donna Malayeri. "Improving API documentation for Java-like languages." In Evaluation and Usability of Programming Languages and Tools. New York, New York, USA: ACM Press, 2010. http://dx.doi.org/10.1145/1937117.1937120.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Piccioni, Marco, Carlo A. Furia, and Bertrand Meyer. "An Empirical Study of API Usability." In 2013 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM). IEEE, 2013. http://dx.doi.org/10.1109/esem.2013.14.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Murphy-Hill, Emerson, Caitlin Sadowski, Andrew Head, John Daughtry, Andrew Macvean, Ciera Jaspan, and Collin Winter. "Discovering API usability problems at scale." In ICSE '18: 40th International Conference on Software Engineering. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3194793.3194795.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Dekel, Uri, and James D. Herbsleb. "Improving API documentation usability with knowledge pushing." In 2009 IEEE 31st International Conference on Software Engineering. IEEE, 2009. http://dx.doi.org/10.1109/icse.2009.5070532.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Bore, C., and S. Bore. "Profiling software API usability for consumer electronics." In 2005 Digest of Technical Papers. International Conference on Consumer Electronics, 2005. ICCE. IEEE, 2005. http://dx.doi.org/10.1109/icce.2005.1429764.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Myers, Brad A. "Human-Centered Methods for Improving API Usability." In 2017 IEEE/ACM 1st International Workshop on API Usage and Evolution (WAPI). IEEE, 2017. http://dx.doi.org/10.1109/wapi.2017.2.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "API usability"

1

Treadwell, Jonathan R., James T. Reston, Benjamin Rouse, Joann Fontanarosa, Neha Patel, and Nikhil K. Mull. Automated-Entry Patient-Generated Health Data for Chronic Conditions: The Evidence on Health Outcomes. Agency for Healthcare Research and Quality (AHRQ), March 2021. http://dx.doi.org/10.23970/ahrqepctb38.

Full text
Abstract:
Background. Automated-entry consumer devices that collect and transmit patient-generated health data (PGHD) are being evaluated as potential tools to aid in the management of chronic diseases. The need exists to evaluate the evidence regarding consumer PGHD technologies, particularly for devices that have not gone through Food and Drug Administration evaluation. Purpose. To summarize the research related to automated-entry consumer health technologies that provide PGHD for the prevention or management of 11 chronic diseases. Methods. The project scope was determined through discussions with Key Informants. We searched MEDLINE and EMBASE (via EMBASE.com), In-Process MEDLINE and PubMed unique content (via PubMed.gov), and the Cochrane Database of Systematic Reviews for systematic reviews or controlled trials. We also searched ClinicalTrials.gov for ongoing studies. We assessed risk of bias and extracted data on health outcomes, surrogate outcomes, usability, sustainability, cost-effectiveness outcomes (quantifying the tradeoffs between health effects and cost), process outcomes, and other characteristics related to PGHD technologies. For isolated effects on health outcomes, we classified the results in one of four categories: (1) likely no effect, (2) unclear, (3) possible positive effect, or (4) likely positive effect. When we categorized the data as “unclear” based solely on health outcomes, we then examined and classified surrogate outcomes for that particular clinical condition. Findings. We identified 114 unique studies that met inclusion criteria. The largest number of studies addressed patients with hypertension (51 studies) and obesity (43 studies). Eighty-four trials used a single PGHD device, 23 used 2 PGHD devices, and the other 7 used 3 or more PGHD devices. Pedometers, blood pressure (BP) monitors, and scales were commonly used in the same studies. Overall, we found a “possible positive effect” of PGHD interventions on health outcomes for coronary artery disease, heart failure, and asthma. For obesity, we rated the health outcomes as unclear, and the surrogate outcomes (body mass index/weight) as likely no effect. For hypertension, we rated the health outcomes as unclear, and the surrogate outcomes (systolic BP/diastolic BP) as possible positive effect. For cardiac arrhythmias or conduction abnormalities we rated the health outcomes as unclear and the surrogate outcome (time to arrhythmia detection) as likely positive effect. The findings were “unclear” regarding PGHD interventions for diabetes prevention, sleep apnea, stroke, Parkinson’s disease, and chronic obstructive pulmonary disease. Most studies did not report harms related to PGHD interventions; the relatively few harms reported were minor and transient, with event rates usually comparable to harms in the control groups. Few studies reported cost-effectiveness analyses, and only for PGHD interventions for hypertension, coronary artery disease, and chronic obstructive pulmonary disease; the findings were variable across different chronic conditions and devices. Patient adherence to PGHD interventions was highly variable across studies, but patient acceptance/satisfaction and usability was generally fair to good. However, device engineers independently evaluated consumer wearable and handheld BP monitors and considered the user experience to be poor, while their assessment of smartphone-based electrocardiogram monitors found the user experience to be good. Student volunteers involved in device usability testing of the Weight Watchers Online app found it well-designed and relatively easy to use. Implications. Multiple randomized controlled trials (RCTs) have evaluated some PGHD technologies (e.g., pedometers, scales, BP monitors), particularly for obesity and hypertension, but health outcomes were generally underreported. We found evidence suggesting a possible positive effect of PGHD interventions on health outcomes for four chronic conditions. Lack of reporting of health outcomes and insufficient statistical power to assess these outcomes were the main reasons for “unclear” ratings. The majority of studies on PGHD technologies still focus on non-health-related outcomes. Future RCTs should focus on measurement of health outcomes. Furthermore, future RCTs should be designed to isolate the effect of the PGHD intervention from other components in a multicomponent intervention.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'API usability' for particular source types:
Journal articles Dissertations / Theses
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography