A one-stop app to learn all about smartphone skills and internet safety. The best choice for seniors looking to improve their tech literacy. With written and video tutorials, and exercises to give you hands-on experience, TechEase appeals to every kind of learner. TechEase also features many accessibility options, and a robust help section in case you get lost or forget something.
As of June 8th 2021, our current completed app meets the following MVP requirements:
- An accessible, high contrast, user-friendly interface.
- Easy to understand controls, navigation, and menus.
- A help button available on every page.
- Some accessibility options, including text-to-speech and dark mode.
- Dynamically loading tutorial lists that cover the most important apps and functions.
While some of these will continue to evolve as we continue to work on the app, in its current state these requirements are mostly met and their implementations are functional. Remaining MVP tasks are listed below.
- Video player
- Dark mode switch
- Overall app design
- Dynamic tutorial content loading
- Written tutorials
- Toggle button for text-to-speech
- Text-to-Speech reading off buttons
- Functional accessibility screen
- API integration
- Practice tutorial functionality
- Persona 1: A first-time user with no experience of how smartphones work.
- Persona 2: An Intermediate user with a basic understanding of smartphones, but doesn't know how to use the internet.
- Persona 3: An Intermediate user with moderate experience having difficulty installing and uninstalling apps.
- Persona 4: An Advanced user with a solid foundation wants to learn about internet safety.
- Pain Point 1: Fear of making mistakes.
- Pain Point 2: Overwhelming amount of information and choices.
- Pain Point 3: Inconsistent navigation.
- Pain Point 4: Size of UI features.
- Need 1: Considerate UI designs.
- Need 2: Consistency.
- Need 3: Hands-on experience and knowledge.
- Need 4: Confidence.
-
Scenario 1: A user is texted a family photo from his grandchildren and he would like to make it the background wallpaper of his smartphone. He starts thinking about how he would change his background wallpaper, but he is not sure where to start. He would feel bad asking his family for help again, as he worries he is bothering them with something they consider a simple task. Frustrated, the user decides to take care of other chores instead. This is not the first time where he has been confused about how to complete a task with his smartphone. The user is then recommended the TechEase app by his daughter. Through the help of the app, the user is able to teach himself how to find answers to his tech problems on his own. He then uses the app and learns how to set his image as a wallpaper for his phone. The user is pleased that he can now change his smartphone’s background wallpaper and doesn’t need to call his family for help. He feels more independent and confident in his ability to use a smartphone.
-
Scenario 2: An elderly user was gifted her very first smartphone for Christmas, and she doesn't know the first thing about how to operate it. Even after having it explained to her multiple times, she still struggles with basic functions such as typing and texting, and she also struggles with small icons and buttons. The son of the user then installs the app TechEase on the user's phone. After being taught how to access the app, the user slowly works through the tutorials on how to text. It takes quite a bit of time, and a few visits to the help menu. After a while, she becomes quite capable of texting. Emboldened by her progress the user pushes through more and more tutorials. And then, she is able to send pictures through texting. After better understanding how to text, the user feels much more confident and capable when using her smartphone.
There are a handful of opportunities that exist among our competitors. Some existing applications have not been well-received, so their audiences may be looking for alternatives. By creating a more accessible application, these users may decide to try and stick with our application. The services offered by Papa were very broad, but the people providing the services were not always reliable. On the other hand, the information available in an eBook is more reliable because it is consistent, but it might not always be up-to-date and could even be defunct. The scope of a static document is also more limited. An app in the marketplace, Empowerji, provides easy video tutorials for users to watch, but most are locked behind a paywall, preventing users from accessing these resources for free. In contrast, YouTube and the internet are essentially free to use. Another app in the marketplace, Easy Tablet Help for Seniors, teaches older users how to use their tablet, but due to its limited nature, the help the app provides may not be applicable to smartphones or the internet.
Our app addresses these issues by being more refined in its goals and more easily accessible to a range of users. Accessibility was also one of our app's most important goals, and utilizing high contrast colors and large buttons and fonts should make it easier for older users to use. Having our app be available on the app store should make it easier to ship updates for our app to make sure it doesn’t become out of date like eBooks. Our app focuses on phone and internet tutorials for older users, unlike competitors that focus on tablets exclusively or real-world physical help. We also wanted to make sure we included internet related tutorials, since internet usage and safety were important target areas for seniors and aren't talked about in competing apps or services. If our planned monetization model comes to fruition, then our app would also be able to bypass the paywall barrier that one of our competitors had. Since our goal is to try and get a sponsorship for the app, we can offer the full app’s worth of information to older users immediately and not need them to also figure out in-app purchases before learning more basic phone tasks.
Prioritized list of functional components that describe the implementation from an end-user perspective.
- P0: User can find tutorials for different skills.
- P0: User can always return to the Home screen if they need to.
- P1: User can change their accessibility settings.
- P1: User can practice what they learned in the tutorial lesson while still inside the app.
- P1: User can watch a video to learn more about a skill.
- P1: User can see how to navigate screens with scroll bars.
- P2: User can get a hint if they become stuck during practice.
- P2: User can complete multiple tutorials.
- P3: User can contact someone if they need assistance or information.
- P3: User can make a video fullscreen to see the content better.
https://marvelapp.com/prototype/7ecje2g
Android Icon:
iOS Icon:
Icon Only:
- Our app will use Google Firebase to store data into its real-time database.
- Youtube API will be widely used for video tutorials.
- We will use Google cloud Speech-to-Text API for text-to-speech and voice commands in our Application.
- We will use Google Maps API to mimic Google Maps' functionality, so users can practice how to use Google Maps.
Due to time constraints, we were not able to do many usability studies on our high-fidelity prototype, particularly from participants in our target audience. However, we were still able to get feedback from two participants who have experience teaching seniors how to use technology. Their feedback falls into the three categories below.
The participants liked the overall design and layout of our prototype. Everything was clearly marked and the navigation worked like how it should. Nothing surprised the participants, as they knew what would happen if they pressed a certain button. They enjoyed the calming color scheme and how it was not jarring or distracting to look at. They thought the buttons were spaced nicely apart and the icons on the buttons helped to enhance what each button meant. Lastly, they appreciated the wide range of accessibility options in our prototype’s settings, as well as the help button always being present on each screen.
The participants found the limited number of screens in our prototype a challenge. They wanted to press all of the buttons, but we only implemented a few of them for proof of concept. Additionally, most of the tutorial text was placeholder text, not what the tutorial would actually say. As a result, the participants could not accurately say if the written or video tutorials would be useful. They do think the texting practice tutorial would be useful for seniors learning technology, but they would have liked to see the entirety of the tutorial implemented. They wanted to see what the live instructions would look like as the tutorial progressed.
Something that could be updated is filling out the help screen more, particularly the “Phone Controls” section. Some of the questions the participants raised about seniors using the app could be answered if we explicitly said what that particular section teaches the users. For instance, one participant asked if seniors would know how to turn the volume up on their phone. That question could be answered if we put a mini tutorial on how to turn up the volume in the “Phone Controls” section. Additionally, one participant asked if the app would render well for colorblind users. Adding a color blindness option in the accessibility settings might be useful for those users, especially since our color palette includes yellow, green, and blue, which might not render as well for them. Finally, for any potential usability studies we do in the future, adding more screens for each button would be helpful for participants to see what they would learn in each tutorial. More screens would be particularly useful in the practice tutorial sections.
A lot of apps nowadays try to go the freemium route, where the app is free to use, but then comes with ads and some paid way to turn ads off. These kinds of ads are (in our opinion) very predatory and rely on people clicking somewhere they don't want to by mistake to download alternative apps they don’t need. Since one of the main selling points of our app is that it would be able to teach seniors with little tech experience how to stay safe on the internet and avoid scams, it seems counterintuitive to monetize our app with such a system. If users get shown large ads up front without knowing what they are, they might click on ads thinking it is part of the actual app before ever learning their true purpose. This is why we believe an upfront paid app is probably more appropriate than a free app with ads. The only problem with this is the same problem that plagued most apps: an initial paid barrier limits the user base pretty significantly right off the bat. Another suggestion to combat this might be a limited free version of the app, that only has some of the total content, but then doing this puts us in a situation where we’ve put a paywall in front of most of the content, which is the issue with some of our competitors. The last suggestion for monetization would be to get a sponsorship for our app. Working closely with a larger company that shares the same interests as us might allow us to gain funding for the app without needing to place ads or charge customers, and instead use it as a form of mobile marketing for the sponsor itself. Though this is probably the most difficult route to take, since the sponsor would need to agree to help fund it and not want to place ads in the app, we believe this to be the best possible route we could take for monetization.
For measuring activity of our app, we believe it would be fair to look at daily usage even at small intervals of time. The purpose of our app is to have readily available tutorials for users to peruse at their leisure. There is a high chance that our app gets used once in a day, and only for a few minutes in order for the user to learn how to do some task, and then they stop using the app for that day. As new users learn to use the app and become more comfortable with their phones, their usage might start out with much longer, more frequent sessions, but then slow down over time. Session length for our app might not be very long, since as we mentioned users might just use it for a few minutes to learn a task and then close it, but continued usage across a month might be more indicative of high retention. The worst-case scenario with our users would be spending too long in a single session, not being able to solve their issues, and not coming back to it when another problem arises. Other important metrics would be download numbers as well as user reviews. One of the things we noticed when researching competitors was that their apps weren’t very widely downloaded, or had mixed to negative user reviews. Being able to achieve larger downloads as well as more positive reviews would prove our app as ideal among users.
We had ideas of an app that when auto-detecting your phone, had an option to apply an overlay that would guide you through the process of learning some app or task. With tutorials set up the way we have now, there's always the chance that a user's phone won't match up directly with a tutorial causing confusion, and this overlay idea might help that. If we had more time / expertise, we would have liked to explore this option idea further and it's something we want to keep in mind for the future. Other more attainable stretch features would be adding more phone controls to our help menu. We want the help menu to give the most basic of phone controls to those who need it before trying out the tutorials. It would include more information on how tapping and swiping works as well as basic controls like volume, closing and opening apps, etc. We also wanted to try adding different color options in our accessibility menus to help color blind users. Our current color scheme that uses mostly green, yellow, and blue might present an issue to those with certain forms of color blindness.