<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Amara Gunarso on Medium]]></title>
        <description><![CDATA[Stories by Amara Gunarso on Medium]]></description>
        <link>https://medium.com/@amaragunarso?source=rss-ea16b0eb56c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CWDQXsWFuvL3t1ohnE2zdA.png</url>
            <title>Stories by Amara Gunarso on Medium</title>
            <link>https://medium.com/@amaragunarso?source=rss-ea16b0eb56c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:52:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amaragunarso/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[User Experience Evaluation of Low-Cost Carrier Airline App using Usability Testing Method]]></title>
            <link>https://medium.com/@amaragunarso/user-experience-evaluation-of-low-cost-carrier-airline-app-using-usability-testing-method-cc259f3e3226?source=rss-ea16b0eb56c------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc259f3e3226</guid>
            <category><![CDATA[mobile-app-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-interface]]></category>
            <dc:creator><![CDATA[Amara Gunarso]]></dc:creator>
            <pubDate>Thu, 27 Jul 2023 07:10:41 GMT</pubDate>
            <atom:updated>2023-07-27T07:11:32.056Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BSDCAoufg2V12UlFQp0OxQ.png" /></figure><h3>Hi! I’m Amara🙇‍♀️</h3><p>This article is written based on my own personal experience of booking a flight for a holiday. During the process, I encountered several issues with the app experience. Due to my curiosity and keen interest in evaluating the products I use, I decided to choose this app as a case study. Through this study, I aim to identify areas that need improvement using Usability Testing and redesign the app using the Law of UX, which could be beneficial for enhancing the app.</p><h3>Overview</h3><p>The high interest of Indonesian society in using Low-Cost Carrier services has driven airlines that provide such services to be more clever in finding ways to outperform other airlines. In an effort to facilitate customers in using the services provided, airline service offerings are often presented through their mobile applications equipped with various features.</p><p>By launching its own mobile application, airlines also have several benefits that can be felt, such as being able to help increase customer loyalty by providing offers that can be adjusted to previous transactions, increasing profit margins because when making sales on the OTA (Online Travel Agent) the airline needs to pay fees for sales on the platform, and can make it easier for airlines to control branding.</p><h3><strong>Citilink</strong></h3><p>Citilink is one of the Low-Cost Carrier airlines in Indonesia that also provides sales through its airline application. The features provided by the Citilink Application also vary, namely Flight Bookings, Online Check-In, as well as Booking. There are also other features that are currently under development. It is aimed that by launching the mobile application, users can make reservations, find out the flight status and even check in using only with the application.</p><h3>Problems</h3><p>However, user reviews obtained from the application reveal issues with the User Experience aspect of the application. Compared to the other application that provides the same service, the Citilink app ratings are considered low. Therefore, it is necessary to redesign the application’s user interface in order to improve the user experience of the Citilink application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*WdJRGP4Vhbk372Salo0OMg.png" /><figcaption>Citilink App Rating</figcaption></figure><h3>Usability Testing</h3><p>Therefore, a redesign of the User Interface of the Citilink application is necessary to improve the User Experience using the Usability Testing method. The metrics used in this research consist of :</p><ol><li>Performance Metrics</li><li>Self-Reported Metrics</li><li>Retrospective Think Aloud.</li></ol><p>From this research, a redesign of the user interface of the Citilink application is produced, using the principles of the Laws of UX and addressing the user experience issues identified during the Usability Testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2xzDxYoGKUk0fnkN31U6EA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nsssj8etm9N51DTZyqbcBA.png" /></figure><p>The method used to improve user experience in this study was usability testing, with the target users as mentioned below</p><p>● 2 respondents from Generation X, 4 from Generation Y and 4 from Generation Z</p><p>● Never used Citilink App to book and check flights.</p><p>● Equal representation of 5 males and 5 females.</p><blockquote><em>These respondents were tasked with completing given work scenarios to assess their level of success in using the Citilink application. </em>The number of respondents in this study was determined based on <em>Jakob Nielsen’s</em> (2012) recommendation, which suggests that <em>conducting usability testing with 5 individuals is sufficient to identify approximately 80% of usability problems in a system.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/542/1*xDcobwLtiv7aBZdHqAAe0w.png" /><figcaption><strong>Task Success Rate Percentage</strong></figcaption></figure><p>Through the calculation of the Task Success Rate, the effectiveness of the three scenarios <strong>has not succeeded in achieving 100% success.</strong> Based on the percentage of effectiveness per scenario, it can be seen that<strong> scenario 6 only has a success percentage of 30%, followed by scenarios 1 and 5 with a value of 60%.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/484/1*eheyS64DYA-_E3UP4xjG9Q.png" /><figcaption><strong>Time-Based Efficiency Percentage</strong></figcaption></figure><p>Based on the calculation of Time-Based Efficiency it can be seen that the percentage level efficiency on task 6 has the lowest value with a value of 14.38%. There are also two other tasks that have percentages efficiency below 50%, namely on task 1 and task 5. Low level efficiency on the three tasks because in the three scenarios concerned, the respondent failed to complete the scenario and the time needed to work on the scenario tended to be long.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*Lk_1Xi83wC32To_jGTDpTg.png" /><figcaption><strong>Total Error per Scenario</strong></figcaption></figure><p>Calculation error obtained based on errors made in the process of working on a given scenario. As seen in Figure above, the number of errors experienced in completing scenarios on the Citilink Application. The scenario with the highest number of errors lies in task 6 with 99 errors, followed by task 1 with 54 errors and task 2 with 21 errors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*-5ypqvPsWvT2G0a1SRYvtQ.png" /><figcaption><strong>Pareto Chart of RTA Results</strong></figcaption></figure><p>Based on retrospective think-aloud (RTA) which was carried out at the end of the scenario work by asking respondents to share their experiences while working on a given scenario, data processing was carried out using a Pareto Chart which showed 80% of the problems found in the Citilink Application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*9wnV4iM_Ft-KHaN3JNVsSg.png" /><figcaption><strong>Single Ease Question Score</strong></figcaption></figure><p>To determine the level of difficulty or ease of scenarios given to respondents, an SEQ questionnaire was assessed with scores in the range 1–7. In this assessment, respondents have a rating range of 1 to 7, meaning that the higher the score given, the easier the scenario is to work on. From the SEQ score obtained in this study can be seen that the results obtained for the eight scenarios are still relatively low when compared to the average reference score of Sauro, 2012 with a score of 5.5.</p><p>In knowing the usability level of the Citilink Application, measurements are made using the System Usability Scale with a rating range from 1 to 5. The higher the score given to this measurement, the better the usability level of the Citilink Application. Based on the data processing that was carried out in the previous chapter, an average value for the System Usability Scale in the Citilink Application was obtained at 38.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/1*6noGxesmVkMZyL4Qz_DKWA.png" /><figcaption><strong>PSSUQ Value</strong></figcaption></figure><p>Then the calculation of the PSSUQ questionnaire was also carried out to find out the level of satisfaction of respondents towards the Citilink application. In contrast to the previously analyzed questionnaire, this questionnaire has a range of values from 1 to 7. However, the higher the value given by the respondent, the lower satisfaction they feel related to the application used. The average PSSUQ score obtained based on the assessment that has been carried out shows that the resulting value is above the existing standard. Therefore, even though the PSSUQ value generated in this study is greater than the predetermined standard value, it means that the satisfaction experienced by users in using this application is still lacking, so improvements are needed to the Citilink application to increase the level of user satisfaction in using this application.</p><h4>Design Process</h4><p>After evaluating the user experience of the Citilink application using Usability Testing, found several problems experienced by respondents and related to user experience of users. With all the problems found, a redesign was carried out for the application interface design based on the Laws of UX using Figma software and by adding a prototype so that new interface verification tests could be carried out on respondents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*z3DYT90PXf7Wrufup4bTzw.png" /><figcaption><strong>Scenario 1 Interface Design using Jacob Laws</strong></figcaption></figure><p>These enhancements were guided by the design principles known as the Laws of UX. Specifically, in response to the problem highlighted by respondents concerning the visibility of account elements, the authors relocated these elements from the top section to the tab bar area, aligning with the principles outlined by <strong>Jacob Laws</strong> in the <strong>Laws of UX</strong>. <strong>Jacob Laws</strong> in <strong>Laws of UX</strong> emphasizes the importance of designing interfaces that align with user habits, especially in applications offering similar services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*88gHC6MHygI0ksWX6wN24Q.png" /><figcaption><strong>Scenario 2 Interface Design using Von Restorff Law</strong></figcaption></figure><p>In scenario 2, a modification was implemented to the flight date selection system. Originally, it was an automatic process without the option for users to manually edit the date. To enhance user experience and reduce time spent on the process, an additional button was introduced, allowing users the opportunity to edit the date as needed. The authors also incorporated the principles outlined in the Laws of UX when redesigning the interface for scenario 2. Specifically, the Von Restoff Law was applied, incorporating visual feedback for date selection and flight schedule selection to highlight the elements that have been chosen by the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*5hcjERHe6Twb71ETNNMAAQ.png" /><figcaption><strong>Scenario 3 Interface Design</strong></figcaption></figure><p>From the perceived problems in scenario 3, a redesign of the interface design is then carried out by referring to the Laws of UX. The size of the drop-down on the application is enlarged as well as by expanding the touchpoint area to increase user awareness which is related to the Fitts Law. The author also added the free baggage details for each flight schedule that is displayed on the select flight page using Hick’s Law so users can directly compare options and access information easily which will make decision-making more efficient.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*hHnIhqbQ5JqLmH-T06K69g.png" /><figcaption><strong>Scenario 4 Interface Design</strong></figcaption></figure><p>The interface design was subsequently redesigned by incorporating the principle of Hicks Law, which involved adding descriptive labels to the filter and edit elements. The aim was to enhance users understanding of the functionality of these features. By adhering to the Hicks Law principle, the goal was to reduce the time required for users to accomplish their desired tasks. Adding descriptive labels to icons can aid users in quickly recognizing and comprehending the purpose of each element. It is essential for icons in a system to effectively represent their intended functions, ensuring ease of understanding for users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*2HXhfO2a0Is-C1Wzyy759g.png" /><figcaption><strong>Scenario 5 Interface Design</strong></figcaption></figure><p>During the redesign of the Scenario 5 interface, a new feature was introduced that enables users to save their Boarding Passes obtained from the corresponding flight. The addition of this boarding pass download feature in the interface design was based on the findings from the previous usability testing. It was discovered that three respondents were unable to complete the scenario as they were unable to locate a method for saving their boarding passes. Furthermore, these respondents were unfamiliar with the concept of saving boarding passes through screenshots. Therefore, the improvements of the boarding pass download feature aimed to address these usability issues identified during testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/1*iMTjmh5spbK8PCYxfEAs1A.png" /><figcaption><strong>Scenario 6 Interface Design</strong></figcaption></figure><p>Based on usability testing that has been done, it is known that the shape of the button used and the location of the button placement makes the user less understand the function of the button. Therefore a redesign of the interface design was carried out based on the principles of Parkinson’s Law by changing the plus button that directs the user to the add flight page to become a Button with the title “View Other Orders” on the My Bookings page.</p><p>When the button “View Other Orders” is clicked, respondents will be directed to the input page of the Boarding Pass Code and Last Name of the account owner so that orders that have been made on other accounts can be added to the user’s application. Whereas if the user clicks on the Button Create Flight Schedules Respondents will be directed to the flight booking page.</p><h4>Verification Test</h4><p>To assess the success rate of task completion on the redesigned interfaces, respondents were asked to work on the same scenario as in the initial usability testing conducted using the application’s design prior to the redesign.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*YAcSA5KFSSegrT5-KQk3Pw.png" /><figcaption><strong>Comparison of Task Success Rate</strong></figcaption></figure><p>The percentage comparison of the Task Success Rate between working on scenarios using the old interface design and the new interface design is displayed in the provided image. The results indicate that, with the new design prototype, respondents achieved a 100% success rate in completing the entire scenario. A significance test, specifically the Wilcoxon Signed Rank test, confirmed significant improvements in Task 1, Task 5, and Task 6 when comparing the performance of the design before and after the redesign. Consequently, it can be concluded that the interface design redesign successfully enhanced users’ ability to complete scenarios with greater success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*NoAZvWRabuKZ-ejxbMfXRA.png" /><figcaption><strong>Comparison of Efficiency Before and After Redesign</strong></figcaption></figure><p>Then after doing a comparison between the processing time for each scenario, a comparison is also made efficiency which is obtained based on the formula time-based efficiency use time on task and task success rate respondent. It can be seen that there is an increase efficiency on the execution of each task which will mean the design interfaces Applications that are new to the application can make it easier for respondents to do the tasks given.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/506/1*ZEKdxqjspoybcE1Bxf6TJg.png" /><figcaption><strong>Comparison of the Number of Errors Before and After Redesign</strong></figcaption></figure><p>In the calculation of the error in the design after the redesign, it can be seen that there is a decrease in the amount of error experienced by respondents during the work of the entire scenario. The biggest decrease is seen in scenario 6 which contains the challenge of working on adding flight bookings and making refunds on related flights. Through the significance test Wilcoxon Signed Rank then it is known that in Task 1, Task 2, and Task 6 there are significant changes that are felt in working out scenarios using the new design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*99oF0Y6pjAxmWmt4bgtRrA.png" /><figcaption><strong>Comparison of SEQ Scores Before and After Redesign</strong></figcaption></figure><p>The results of the SEQ score on the design after the improvement obtained appear to have increased when compared to the SEQ score on the interface design before the improvement. The greater the score generated on the SEQ value, the easier the scenario will be to work on. From the results of the significance Paired T-Test that has been done, there is a significant difference between the SEQ values obtained from the interface design before and after redesign. Therefore, the results indicate that the interface design after redesign will make it easier for respondents to work on scenarios.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/554/1*0TxlVFTPLtc6rikzPsyVCw.png" /><figcaption><strong>Comparison of SUS Scores Before and After Redesign</strong></figcaption></figure><p>Based on the usability measurements of the two interface designs, it is evident that there was an improvement in the SUS (System Usability Scale) score from the initial design to the design after the implemented enhancements. The initial SUS score obtained was below 68, indicating that the existing design fell below the threshold for good usability. However, after conducting usability testing using the interface design after the improvements, an SUS score of 86 was achieved, placing it in the acceptable category.</p><p>The results of the Paired T-Test, conducted to assess the significance between the two sets of data (initial design and design after improvement), indicate significant differences. This is supported by the increase in the SUS score obtained from the initial design before improvement to the design after the implemented enhancements.</p><h4>Conclusion</h4><ul><li>The objective of this study is to provide recommendations for redesigning the user interface of the Citilink application using the Usability Testing method. The data collection process involved selected respondents working on scenarios and measuring various metrics, including Performance Metrics, Self-Reported Metrics, and Retrospective Think-Aloud.</li><li>The Usability Testing revealed several issues based on the measurement of Performance Metrics. The respondents did not achieve a 100% success rate in completing the given scenarios, and the completion time was prolonged. The Self-Reported Metrics, assessed through questionnaires, indicated problems related to usability or user experience. This was further supported by conducting interviews using the Retrospective Think-Aloud method to identify the challenges encountered by respondents during the scenario execution.</li><li>Based on the obtained evaluation results, a redesign of the Citilink application’s User Interface was carried out. The redesign was guided by the principles outlined in the Laws of UX theory. Once the redesigned User Interface was created, a verification test was conducted. Respondents were asked to rework the same scenario using a new design prototype created in Figma.</li><li>The results of the verification test were then compared with the results obtained from the initial Usability Testing on the design before the improvements. Consequently, improvements were made to the Citilink application’s interface design, and it was determined that there was an enhancement in user experience based on the results of working on scenarios using the redesigned application prototype.</li></ul><p>Thank you for reading!😊✨</p><p>I warmly welcome your feedback💖</p><p>© 2023 Amara Gunarso. All Rights Reserved.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc259f3e3226" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing App to Help Children with Down Syndrome Improve Their Expressive Communication Skills]]></title>
            <link>https://medium.com/@amaragunarso/designing-app-to-help-children-with-down-syndrome-improve-their-expressive-communication-skills-7ec70b749695?source=rss-ea16b0eb56c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ec70b749695</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ui-ux-case-study]]></category>
            <dc:creator><![CDATA[Amara Gunarso]]></dc:creator>
            <pubDate>Sun, 04 Dec 2022 11:46:35 GMT</pubDate>
            <atom:updated>2022-12-08T12:05:27.551Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N1C1I8mqWHTMI4gv0NtciA.png" /><figcaption>Komka — Komunikasi untuk semua</figcaption></figure><h4>Introducing, Komka!🥳</h4><p>Komka is an iOS application to help children with Down Syndrome improve their expressive communication through imitating techniques -<em>that enable users to practice their pronunciation</em>- and arrange words -t<em>o practice their ability to arrange words into the right order</em>-.</p><h4>Role and Responsibilities in the Team</h4><p>This project was done as a group for our Macro Challenge at Apple Developer Academy. My role as a UI/UX Designer in this team is more focused on conducting the User Interview with our Target User and Experts, Creating the App Wireframe, be it Lo-Fi and Hi-Fi, Prepare the whole illustration assets that will be needed. For the research phase, we did our research together as a team starting from desk research till creating the User Flow of the app.</p><h4>Overview✨</h4><p>As a human, we realize that communication matters in our daily life</p><p>Communication will facilitate one another in conveying the things they would like to express to the people around them as well</p><p>However, not everyone is born and gifted with the same communication skills. Few others were born with special needs, making it challenging to convey and express what they’d like to communicate.</p><p><strong><em>Even Siri needs accuracy in pronouncing words to be able to process our commands😊</em></strong></p><p>Therefore, Our team is interested in raising Down Syndrome as a topic for our group challenge at Apple Developer Academy.</p><h4>How did we begin?😚</h4><p>The research will be separated into two methods: Desk Research using Literature and Interviews with our target users and Experts. For our target users, we interviewed Parents of Down Syndrome Children to know the pain points they usually find. A Caretaker’s existence matters, especially when the Children with Down Syndrome are still unfamiliar with using the new App.</p><p><em>Hence, We crafted two Personas that comprise Children with Down Syndrome between the ages of 7–12 years and</em> their Caretakers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G9a8og-d7pcxOP0tjG-AqA.png" /></figure><p>Besides that, to address more from another POV, we also gain findings from experts that come from Education and Medical Backgrounds.</p><h4>Then… what did we find?🤫</h4><p>From our desk research &amp; interview with parents of down syndrome children and experts in Physical and Rehabilitation Medicine, we gathered some key insights :</p><p>Children with Down syndrome tend to understand instructions but struggle to convey what they feel. — <strong>Potential User</strong></p><ol><li>Some of <strong><em>the</em></strong> <strong><em>Parents of Down Syndrome children</em></strong> we interviewed took their children for speech therapy to improve their communication.</li><li>There is some indication that the speech accuracy of children with Down Syndrome <strong><em>will improve</em></strong> by implementing treatment that focuses on listening and production practice</li><li>The trainer most often uses the imitation technique and communication temptations.</li><li>However, They <strong><em>can not </em></strong>rely solely on the therapy itself, and they must practice their expressive communication skills at home using simple exercises because it is a continuous process for individuals with Down syndrome to be able to communicate clearly.</li></ol><p>The problems we found through Research were then observed further using HMW, which helped me get dozens of solution concepts that might be relevant to our Application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UZbrQsc7RfQvqy6nEqkblw.png" /><figcaption>POV — How Might We — Solution Concept</figcaption></figure><p>Therefore, we created the <strong><em>Information Architecture</em></strong> and <strong><em>Navigation Architecture</em></strong> to visualize our app flow and make it easier to understand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*scYF4GDnDmFHNC4n6behsQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*3hypkKWRcfvXM6oHs7O_cw.png" /><figcaption>Information Architecture and Navigation Architecture</figcaption></figure><h4>Lo-fi and Hi-fi Wireframe🌴</h4><p>As we already map the flow and architecture for our App, we continue to start the design process by creating the Low Fidelity Design and then the High Fidelity Design. This wireframe will make it easier for the tech team to find out in more detail the functions of the components used in the application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qguqfdmc02dd5eWB1ATsqQ.png" /><figcaption>Lo-fi Wireframe</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oEuFw2mC0a2OVIYDYS_UFQ.png" /><figcaption>Hi-fi Wireframe</figcaption></figure><h4>Here are the features that we provide in our App🌸</h4><h4>1. Gender Input</h4><p>Before we continue to the scenario, we were asked to choose our gender. the illustration that would appear on the next page will determine the illustration content that the user will use in the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4NB-4sKLw2pbKrEJNF3vxQ.png" /><figcaption>Choose Gender</figcaption></figure><h4>2. Scenario Selection</h4><p>The next page will show the user that the app will consist of 3 levels: Easy, Medium, and Hard. The objective of each level is different where on the easy level we want to focus on teaching verbs to the Children, on the medium level we want to focus on Noun, and the Hard level, we want to focus on Adverbs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vjuyflBtD8tGSx3M5evu3g.png" /><figcaption>Scenario</figcaption></figure><h4>3. Multiple Choice</h4><p>To increase the critical thinking of the users, this feature will encourage the users to respond based on the illustrated scenarios. We also provide an audio button that allows users to listen to the sound of the illustrations provided.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Pifd2T-eFiWDo6KDCb2VQ.png" /><figcaption>Multiple Choice</figcaption></figure><h4>4. Full Sentences</h4><p>The Full Sentences page will show the user the correct answer from the Multiple Choice. This page also aims to boost the user’s confidence in learning while familiarizing them with the sentences since they will learn how to pronounce each word on the next page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8u9l1SOsqEXRuQVC2-K8dA.png" /><figcaption>Full Sentences</figcaption></figure><h4>5. Sideway Approach</h4><p>In addition, we implemented a Sideway Approach to help users imitate the word’s correct pronunciation. As you can see on the left is a video that we created to show the pronunciation of the word shown and on the right is a camera for the user so they can follow the pronunciation easily. On this page, users will learn how to pronounce by splitting the word (for example Saya — will be split into “Sa” and “Ya”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zTFt6DjQeVfswdPESq1PEQ.png" /><figcaption>Sideway Approach + Imitation Technique</figcaption></figure><h4>6. Sound Practice</h4><p>After the user learns the “Sa” and “Ya”, on the next page the user will practice pronouncing the complete word “Saya” but without showing the video of the correct pronunciation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GR2H_QvIZ8tTrlji9QBiqw.png" /><figcaption>Sound Practice</figcaption></figure><h4>7. Arrange Words</h4><p>The next page will allow the user to arrange words in the right order. Based on the research that we’ve done, according to experts, arranging words in the right order is not easy for children with special needs. They need to learn and familiarize each word first. Therefore, besides providing the words in the box to be arranged, we also provide an audio button that enables users to listen to the correct arrangement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-K4XYJsv5VmfIQ92XZY7Dg.png" /><figcaption>Arrange Word</figcaption></figure><h4>8. Rewards</h4><p>After completing the scenario, the user can choose the badge as a reward that will be saved on the collection item page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cm3s3heJW0W5zvTdOULX-A.png" /><figcaption>Reward Page</figcaption></figure><h4>It doesn’t stop there😉</h4><p>To validate our Solution, we conducted User Testing for our App Prototype on 3 Children with Down Syndrome, an age range between 7–17 years old, to complete the given scenario.</p><p>We measured our design on User Testing based on these metrics.</p><ul><li>Success rate (whether users can perform and finish the scenario).</li><li>Users can understand the meaning of the illustration given.</li></ul><p>From the results of the User Testing, We’ve got some feedback that we map into the STAR method for future improvements to our App.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*YMhTwc_Tnkx8pP1JTXJ6sQ.png" /><figcaption>STAR Method</figcaption></figure><h4>Lesson Learned</h4><p>Through this challenge, I learned a lot from every step I faced.</p><p><strong>1. Be Aware of Your Surroundings</strong></p><p>Sometimes when we want to build an app, we need help in prioritizing the topic we choose. We often need to be more aware of simple problems near us that need help. Therefore, within this challenge, I learn how empathizing really matters in the research phase.</p><p>I had the opportunity to meet new people from different backgrounds and gain many fruitful lessons. I also was able to interview parents of Children with Down Syndrome from Yayasan POTADS and communicate directly with my friends&#39; brother, Al, a Child with Down Syndrome who was very warm and helpful during our User Testing. The opportunity to see things from another’s perspective and feel their emotions definitely will help you in recognizing the problems that need to be solved.</p><p><strong>2. Know your Target User</strong></p><p>When designing an App, we need to know “who is the app for?”. After knowing who’ll be our users, it will help us to set the style guide of our App. As our target users are Children with special needs, we need to consider their familiarity with our app style more. Things that need to be considered include but are not limited to font style -<em>which impacts their readability,</em> design elements to not be overloaded so that the children won’t get distracted, and many more.</p><p><strong>3. Iteration is a normal thing</strong></p><p>After conducting UT with our target user, the feedback we obtained will be used later as input for future improvements. This iteration process can be a step to ensure that the development carried out by the team is following current user needs.</p><p>Try KOMKA <strong>Prototype</strong> and <strong>TestFlight</strong> here!</p><p><a href="https://testflight.apple.com/join/QksvNLii">Join the Komka beta</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2Fjtpq9x8wCUoEPiz9DmkaKg%2FKomka-Prototype%3Fpage-id%3D0%253A1%26node-id%3D901%253A2377%26viewport%3D-2217%252C-5121%252C0.46%26scaling%3Dscale-down%26starting-point-node-id%3D1325%253A3327&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2Fjtpq9x8wCUoEPiz9DmkaKg%2FKomka-Prototype%3Fpage-id%3D0%253A1%26node-id%3D901%253A2377%26viewport%3D-2217%252C-5121%252C0.46%26scaling%3Dscale-down%26starting-point-node-id%3D1325%253A3327&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Faec46225-1792-483c-a3f4-9cc1d5cb5c62%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/7dfdb31ee7403e33ce86cc6b98e8d249/href">https://medium.com/media/7dfdb31ee7403e33ce86cc6b98e8d249/href</a></iframe><p>Thank you for reading!😊✨</p><p>I warmly welcome your feedback💖</p><p>© 2022 Amara Gunarso. All Rights Reserved.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ec70b749695" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>