Julia Indriani Lubis, Rizky Anggraini Siregar

Analisa Kemudahan Penggunaan Aplikasi AdaKami Dengan Menerapkan Metode Technology Acceptance Model (TAM)

Introduction

Analisa kemudahan penggunaan aplikasi adakami dengan menerapkan metode technology acceptance model (tam). Analisis kemudahan aplikasi AdaKami pakai metode TAM, atasi keluhan user soal penarikan & error pembayaran. Hasilnya, AdaKami relatif mudah digunakan (68.4% PEOU).

Abstract

The problem in this research is that the AdaKami application often gets complaints from users, such as not being able to use or withdraw money even though the limit is high, difficulties in the application where errors often occur in the payment system, and users are subject to fines for late payments. To overcome these problems, research This method uses the Technology Acceptance Model (TAM) to analyze the ease of the AdaKami application. With this article, users can understand how to use the AdaKami application. We hope that the data collection carried out can help users use the features contained in the application. Overall, the PEAOU variable is included in the strongly agree category and it can be concluded that using the AdaKami application is relatively easy. With the results obtained by the PEOU variable of 68.4%.

Review

This research, titled "Analisa Kemudahan Penggunaan Aplikasi AdaKami Dengan Menerapkan Metode Technology Acceptance Model (TAM)," aims to investigate user experience and ease of use of the AdaKami application. The abstract highlights a pertinent problem: frequent user complaints regarding various functionalities, including fund withdrawal issues, payment system errors, and penalties for late payments. To address these concerns, the study employs the well-established Technology Acceptance Model (TAM) to specifically analyze the perceived ease of use (PEOU) of the application. The stated objective is to help users understand the application and utilize its features effectively, suggesting a practical orientation for the research. From the abstract, a key strength is the direct focus on a real-world problem affecting users of a specific application, making the research highly relevant and potentially impactful. The choice of TAM is appropriate for assessing user acceptance and perceived ease of use. However, the abstract presents some points that require clarification for a robust academic review. There's an initial mention of a "PEAOU variable" categorized as "strongly agree," followed by a concluding statement that the "PEOU variable" achieved 68.4%, leading to the conclusion that the application is "relatively easy." This shift between "PEAOU" and "PEOU" needs to be clarified, along with the interpretation of 68.4% in the context of the "strongly agree" category. Furthermore, the abstract's framing of the research output as helping users "understand how to use" the application and "use the features" might suggest an instructional guide rather than a rigorous academic analysis of user acceptance, potentially blurring the lines between a user-focused resource and a scholarly study. To enhance the academic contribution of this work, the authors should provide a more precise articulation of their methodology, including details about data collection methods, sample characteristics, and how TAM constructs were operationalized. It is crucial to resolve the inconsistency between "PEAOU" and "PEOU" and provide a clearer interpretation of the 68.4% finding in relation to the overall ease of use and its "strongly agree" categorization. The practical implications for AdaKami developers, derived from the TAM analysis, could also be explicitly discussed, moving beyond merely helping users understand the application to offering concrete recommendations for improving its design and functionality. Future work could consider integrating additional models or factors alongside TAM to provide a more comprehensive understanding of user acceptance, perhaps exploring perceived usefulness or trust, which might be particularly relevant given the payment system issues highlighted.

Full Text

Comments

You need to be logged in to post a comment.