Mobile learning and community for students

First three months after launch
Course completion 27% → 62% Forum activity +41%
Mobile learning and community for students

First three months after launch
Course completion 27% → 62% Forum activity +41%
Problem
NSLS was adding about 20,000 members a year across iOS, Android, and web, and most of them arrived on a phone. The app already had courses, events, and chapter conversations. They just did not know about each other. Moving between them meant finding a way back instead of moving forward.
Research
I talked with students, chapter advisors, and the support team before changing anything. Interviews, focus groups, A/B tests, support feedback, and analytics all pointed at the same seam: learning on one side, community on the other. Prototype reviews with student volunteers refined the navigation and the language.
One A/B test put influencer live sessions in a reel rail at the top of the app against TikTok-style video ads interrupting the feed. 76% of participants responded positively to the rail.

One familiar way forward.
Shared navigation. Visible progress. A next action in the same place.
Decision
I brought course progress, chapter conversations, and events into one mobile experience. With a semester deadline, I aligned product, engineering, and QA around these core journeys first.

Course discovery and progress stay together.

Chapter conversations sit alongside learning.
Explore the mobile experience








Outcome
Course completion rose from 27% to 62% in the first three months after launch.
75%of new users accessed the platform through mobile.
+41%forum activity in the same three-month window.
Source: internal analytics, first three months after launch. Other changes may also have contributed.
What I’d measure next: results by new, active, and returning students.
See how I brought AI workflows into Dialpad.