I was the fourth and final designer on the project, and I arrived for the Closed Alpha stage.
I was responsible for launching this product, creating consistency from the multiple designers it had been through.
I added personalization, delight, and accessibility to the experience.
On launch day, over 1000 Creators adopted the Thinkific mobile app feature.
The Thinkific app hit the Top Charts (in the #30's) on opening day of the App Store, ahead of our B2B competitors, and even some other learning adjacent apps like Khan Academy and Coursera.
Thinkific is a B2B SaaS platform offering online courses and communities for a broad range of industries, accessible to students through a web app in the browser. Unlike open marketplace-style apps like Skillshare, Coursera, and Masterclass, Thinkific is more like an island (similar to Shopify or Squarespace).
Based on our company vision, we knew that our Creators really wanted their own custom app, with their own logo and name, but didn't were not ready to pay the high fees.
The solution was for us to create a Thinkific generic app, included in all paid plans.
We had to launch the app very quickly, since we were already last to the market.
Some Creators were leaving Thinkific or not choosing the platform because we didn't have a mobile app option.
Our app's primary user is the person who consumes content.
Learners were eager and passionate about the courses they purchased. They are adult-improvers.
Their reasons for wanting an app:
1. Scenario-based learning
Though they prefer to learn on desktop, they want an app for various scenarios like playing a video or listening to audio in the car while driving, going for a walk, or doing multi-tasking with housework at home.
2. Ease of access
They also find value in using Thinkific's Community interactions for mobile, like reading and quickly replying to post discussions.
The Thinkific mobile app is for the Creator who doesn't want to pay the high monthly fee for their own Branded app. They may also be getting started in their online teaching journey.
Their reasons for adopting a generic Thinkific mobile channel:
1. To offer a companion app to the current learning experience on desktop
2. To communicate with their students more easily, so that student engagement, course completion, and retention are higher
During our Closed Alpha, we conducted evaluative research on the app, and the biggest issue was that Learners had the most difficulty with the first screen: Find Your School.
Meet the dreaded subdomain screen.
It was the beginning that felt like a dead end.
The term "subdomain" was too technical for both Personas.
Most Learners had never seen the subdomain, because the Creator typically used a custom domain name.
Our competitors had a better login design experience.
All a Learner had to do was enter their email and/or password.
After authentication, the app would log the student into all of the schools (from multiple Creators) they were enrolled in.
That solution was too expensive and complex for us to build at the time. We had to look within our own system capabilities and find a timely solution.
We also noticed when we tested one of our competitors' apps, that the login wasn't working, and it was confirmed with several negative app reviews.
Solution 1: A school search, where Learners could type in the name of the school or keywords (if they couldn't remember the full name). A list of results would appear.
Solution 2: Enter the school's domain, which ensures only 1 unique result.
Solution 3: The Learner enters their email, and they have to check their email to find out which schools have the mobile app enabled, then they would get logged into the one school they clicked on.
Our back-end developer said that they could combine the first and second options. They were the easiest to implement, because the we could ask the database for the school name and custom domain name already. They couldn't do keywords specifically, but if the word was already in the school name or domain name, it would show up. The third solution was a little confusing and had a lot of room for error/ more variables to think about.
We showed this hi-fidelity mockup (image below) to Product Leadership and asked if this felt like we were encroaching on forbidden "marketplace" territory, like Skillshare and Udemy. They said no, because weren't actively encouraging a Learner to discover new schools. There was a chance that a Learner would click on the other schools out of curiosity, but the chances were slim, because our Researchers told us that Learners often buy from Creators they already know through social media.
We were willing to make the trade off for a better user experience.
We implemented this version a sprint before the beta launch, and I personally followed up with our Learners to see how their experiences went. They said they were able to find their schools much easier. Success!
We launched the app during a rebrand, so I changed the visual design of the screen to match the new look and feel of Thinkific. Marketing suggested that I use this mobile phone image, but I really wanted to convey that it was a platform of multiple Creators, rather than for one specific Creator.
Because of the small screen real estate, multiple Creator images became too busy.
I decided on using the design pattern of the last three screens and animated each Creator coming into the screen with After Effects.
I then used Lottie's Bodymovin plugin to export it as a .json file, which made handoff and development incredibly fast and easy.
We also tested the accessibility usability score (AUS) of the app with real assistive technology users from a company called Fable.
We received an AUS score of 65 from a screenreader user. The average for this segment is 56.
We received an AUS score of 80 from a screen-magnification user. The average for this segment is 72.
We didn't have much quantitative data to measure the impact of our changes, since we launched the changes during our closed Alpha group of 20 schools. I'm relieved that we focused on this crucial part of the flow before going live to all of our Creators, because 1000+ schools joined in the first week of launching the app. After a month, we only had 6 UX feedback tickets related to the Find Your School screen.
Because we launched an MVP, we had a lot more features to add and bugs to fix.
Apple reviews fluctuated a lot, and we increased it to 4.7 stars as of August 2023.
If you'd like to learn more about this case study, feel free to send me an email request.