Skool Buddy - A Conceptual App
Shaping the Future of Student Life
Starting university is exciting, but it often leaves students navigating unfamiliar systems and feeling disconnected. Skool Buddy was my concept for an iOS platform that turns those first uncertain steps into opportunities to connect, share, and belong.
Week 1
Week 2
Week 3
Week 4
Week 5
Week 6
Week 7
Week 8
Week 9
Understand:- Specify context of use
Gather Requirements
Design / Build
Evaluate designs
Evaluate designs
Final design development
Final design development
Initial Problem
A Gap in Student Support Systems
University life presents unique challenges, especially for new and international students adapting to unfamiliar cultures and campuses. Existing orientation programs often fall short in providing continuous support. There’s a clear need for a way students can connect, access resources, and foster a sense of belonging even before arriving on campus, one that continuously supports students, enhances social ties, and promotes an inclusive campus experience.
The Solution
A Student First Platform for Connection
Onboarding
Home
School
Community
Messages
Settings
School
This section welcomes users with a splash screen and brief onboarding, highlighting key app features like messaging, community forums, events, and academic resources. It also offers a quick snapshot of frequently used functions, so students can jump into their most relevant tasks right away, reinforcing the app’s ease of use and centralizing everything they need in a single, convenient place.
Understanding Students in Transition
Understanding how today’s platforms serve (and fail) students was key to identifying the gaps Skool Buddy needed to address.
Competitive Analysis
Exploring the existing Landscape
Platform
University Forums
University Forums
Useful
Useable
Findable
Credible
Desirable
Accessible
Valuable
UX factors
Reviewing platforms such as Facebook, LinkedIn, university forums, and orientation programs revealed common shortcomings: limited ongoing support, a poor balance between social and academic features, scattered resources, and weak privacy controls.
User Interview
Meeting with students
Interviews with five university students in Brighton showed the different roles social media plays in; staying in touch with friends, academic collaboration, and networking. However, they also revealed gaps in cultural adaptation, time management, and consistent access to campus resources.
Understanding Who We’re Designing For
To turn insight into design, I distilled research into three representative personas that reveal priorities, pain points, and the opportunities Skool Buddy must address.
Problem Statement
Defining What Students Really Need
Task Scenario
Envisioning real life use cases
To ground the design in everyday reality, I mapped scenarios that show how students might pursue their goals before any solution existed. Each story traces steps, contexts, and decisions. Revealing pain points, workflow preferences, and opportunities where design could make their journey smoother.
Context for all scenarios
Each scenario is anchored in the shared challenges students face when adapting to university life.
Physical Enviroment
Students frequently access the platform on the go (campus, dorms, coffee shops) with occasional library or home use.
Frequency of Task
Most tasks occur weekly or monthly, timed around academic needs and social events.
Time Constraint
Students often juggle course deadlines, part-time jobs, and personal obligations, leaving limited windows to plan and socialise.
Concurrency of Task
They may simultaneously manage multiple responsibilities—e.g., checking schedules, chatting with peers, and accessing campus resources.
Prioritisation & Scheduling
Tasks are slotted around top priorities (exams, job shifts), requiring efficient reminders or notifications.
Resource Conflicts
Internet reliability, device battery life, and personal bandwidth can all impact app usage.
Activity Type
Interactions can be solo (browsing events) or group-based (coordinating a study group).
Known Problems
Students might overlook notifications, encounter schedule clashes, or feel unsure about verifying event info and group credibility.
Creating requirements for the solution
Clear requirements keep design anchored in what students truly need. To capture both function and experience, I used the Volere specification template, enhanced with Shneiderman’s Five Usability Attributes. This framework ensured every design choice connected back to genuine student goals, balancing usability, efficiency, and emotional impact.
Card Sorting
From Complexity to Clarity
Students were already juggling too many tools, calendars here, chats there, resources buried somewhere else. To avoid recreating that chaos, I ran a card sorting exercise that revealed how students instinctively expect information to be grouped. The result was four main sections; Home (quick overview), School (everything related to their study and classes), Community (the people they can interact with), and Messaging. Creating the backbone of the app. This step wasn’t just about structure; it was about creating a navigation model that reduces friction and gives students confidence that everything they need lives in one place.
Card sorting insights were translated into this information architecture, defining how students would move through the app. The structure balances academic tools, community spaces, and messaging. Creating a clear backbone for design and navigation.
Improved Information Architecture
With the structure in place, the next step was to sketch how these flows could take shape on screen, turning abstract groupings into tangible design directions.
From Sketches to Student-Centred Screens
Wireframes & Sketching
Exploring Ideas on Paper
With the structure mapped out, I began sketching early layouts to explore how students might interact with the app. These quick drawings allowed me to test different flows, capture first impressions of usability, and make low-cost changes before committing to wireframes or high-fidelity designs.

From there, I translated the best directions into low-fidelity wireframes, mapping out content placement, navigation patterns, and user flows. These wireframes served as a blueprint for testing usability before investing in high-fidelity des
Wireframes & Sketching
Refining Flows Into Testable Screens
From sketches, I gradually shaped wireframes into higher fidelity so they could be tested as if they were real without committing to final visuals. This approach gave students something concrete to interact with, revealing whether flows worked, where friction appeared, and which optional ideas were worth carrying forward. The focus here wasn’t on polish, but on confidence: validating structure before investing in a full design system.
Getting Started (onboarding, login, profile setup)
Testing Usability With Real Students
From Challenges to Solutions
Meet Skool Buddy
Skool Buddy brings together everything students need to feel at home on campus, from connection, resources, and community into one student first platform. What began as scattered tools and isolated experiences is now streamlined into five core spaces that support learning, social life, and belonging.
Messaging
Stay Connected Effortlessly
One-to-one and group chats keep peers, study groups, and school contacts all in one place. No more juggling multiple apps — conversations that matter stay easy to find and manage.
What can students do
How Skool Buddy Fits Into Students Life
Starting university is a turning point filled with excitement — and uncertainty. From admission to the first weeks on campus, students are juggling new systems, new people, and a new environment. Skool Buddy is designed to guide them through this transition, step by step, turning challenges into moments of confidence.
Getting Started (onboarding, login, profile setup)
Joining the App
From the moment they’re admitted, students can join Skool Buddy, select their university, and set up their profile. This early start helps them connect even before stepping foot on campus.
Getting Started (onboarding, login, profile setup)
Onboarding With Ease
A simple onboarding flow introduces the app’s main spaces, helping students know where to find schedules, resources, and peers right away. No time is wasted trying to learn yet another complex system.
Getting Started (onboarding, login, profile setup)
Accessing School Resources
Once inside, the Campus section becomes their go-to hub: schedules, course overviews, weekly plans, and assessments are all in one place. They can discover study groups, follow discussions, and keep track of deadlines without jumping between platforms.
Getting Started (onboarding, login, profile setup)
Exploring the Community
Curious about life at their new school, students dive into the Community feed. Here they see what peers are talking about, explore groups to join, and check upcoming events — helping them settle into campus culture before day one.
Getting Started (onboarding, login, profile setup)
Staying Connected Through Messaging
Finally, they open Messaging to check in with classmates, chat in study groups, or reach out to school services. Communication becomes easy and centralised, reducing the stress of managing multiple channels.
This journey shows how Skool Buddy grows with the student — from their first admission letter to their first connections and beyond. What once felt scattered and overwhelming becomes a seamless, supportive experience that empowers them to thrive both academically and socially.
Reflection & Next Steps
Growing Beyond the Concept
While design is never truly “finished,” this project represents the first academic iteration of Skool Buddy. Building and testing the prototype revealed valuable lessons and opened doors for future exploration:
Adherence to Apple human interface guidelines for iOS 15
In testing for accessibility the final prototype was tested with the ally contrast checker plugin on Figma
WCAG compatibility of AA
In testing for accessibility the final prototype was tested with the ally contrast checker plugin on Figma
Excellent Completion Rate
one of the result was the people that used the app were able to understand the flow of the app and were able to navigate the app well
8 users said they would use this app regularly
10 users were given the prototype to use without instructions but explanation on the use of the app to use it how it will fit into their daily lives and 8 of them said they would use it regularly if it worked as explained
User engagement rate of 80%
8 out of the 10 users proposed the main reason they would be using the app is because of the features and flow of using the app while the design of the app was considered to be clean and easy to understand
Relative Reduction in meal planning time
Compared to the normal way most users use in preparing a meal if this app is used properly it show a potential to act as a personal kitchen assistant and reduce the time it takes in creating a meal either if its a single mal or a weeks plan
This stage focused on solving the student view, laying the foundation for a broader ecosystem. The journey ahead is iterative, but the vision remains clear: creating a unified, supportive platform that adapts to the evolving needs of university life.
Final Note






























