Putting your app to the test
When creating an app, design, or product of any kind, getting a prototype into the hands of the user is a must. It may seem weird to let people see what you are working on before it is even done. However, doing so will create a better final product overall.
Running an app through its paces is crucial to iron out any wrinkles that may exist within it. The best way to do this is by completing user testing with actual users in your target audience. They will catch things that you won’t as a designer and will break things in ways that you never thought they could.
Last week, I created wireframes and user flows for an app I am working on for Newtown, CT. This app will serve as a companion to the town’s municipal site, where residents and visitors alike can find any and all information they need.
These sketches are my first low-fidelity prototype for the app, and they give as a glimpse into what the final thing will actually look like.
So how do you test an app that doesn’t actually function? You make the paper prototypes functional.
The old-school way to do this was by just showing users the sketches and having them navigate through the app as if it were functioning on a phone. However, an app called POP allows us to take things to another level.
In this app, we can take photos of our sketches and add basic functions to them so they can work on a phone. This gives life to the prototype and allows the user to interact with it in the same manner they would be using the final app.
Now that the app is functioning, I ran it through two user tests. In these tests the users completed three basic tasks: signing up for emergency notifications, viewing things to do in town and creating a calendar event based on it, and viewing the news/weather on the app.
After completing the two user tests I found that a lot of things were working well on the app. During their initial explorations, both users found the app intuitive. They each found features that were useful to them and other aspects that they felt made the experience positive.
Taking them through the three flows was also mostly successful. That being said, neither test was 100% perfect. The following key insights are takeaways from the tests that can be used to improve the next version of the app:
Consider the makeup of the resident’s page. Both users noted that they could have also seen the emergency notifications being located in community resources instead of public safety, and one of them even attempted to navigate there instead. Although it probably wouldn’t hurt to have this be accessible in both locations, it does bring up the question of how necessary community resources is as a section. Alternatively, maybe things just need to be somewhat restructured.
Navigation and calendar features are effective. Both users noted that being able to navigate to locations and create calendar events in the phone’s native apps was the best way to do it. However, in the happenings page, it may be necessary to make these buttons more prominent.
Showing widgets with information on the home page is effective. Both users liked having news and weather on the home page. Adding similar widgets to other parent pages to make information more accessible should be considered.
Ultimately, the tests went well, but I’ll need to reiterate and add more implementation before moving on with creating a high-fidelity prototype. But that’s the whole point of this process. If you want to view the full document detailing these tests or the app prototype, they can be found below.
Hi! My name is Peyton McKenzie.
I am a professional graphic designer, photographer and content creator.
I encourage you to explore my portfolio to get a better idea of the work I create. If you are interested in working with me or have inquiries of any kind, don’t hesitate to reach out over email.
