Discover what matters. Find your people. Make campus yours.
Turning relevant campus discoveries into confident, real-world participation.
Read project documentation (opens in a new tab)I developed CampusConnect around the gap between finding an event and taking part. Relevant discovery is the start: students also need practical scheduling, clear expectations and a comfortable way to show up. The broader product connects that student journey with organizer tools that keep event information useful, current and actionable.
The implementation account comes from Rico’s product documentation. The public repository documents the product and research but does not publish application source. Earlier usability and beta findings are reported separately from the expanded platform scope.
Start with reliable event coverage in one campus community, then expand within clear institutional data boundaries.
I began with 24 student interviews and 120 survey responses. The research separated discovery friction across fragmented channels, decision friction around fit and expectations, and participation friction when an event feels unfamiliar.
In this sample, 81 students struggled to find relevant events, 76 reported recommendations that missed their interests, schedules or goals, and 69 felt uncomfortable attending unfamiliar events. These are project-specific findings, not estimates for the whole student population.
The product also depends on the supply side: organizers need a practical reason to publish and maintain reliable event information. Their workflow is part of the participation problem.
81/120 respondents struggled to consistently find relevant campus events.
76/120 cited interests, schedules or goals that recommendations did not match.
69/120 respondents felt uncomfortable attending unfamiliar events.
A useful recommendation needs to fit a student’s interests, their actual availability, and their confidence about taking the first step.
Use interest and schedule fit to offer three useful starting suggestions. Filter eligibility, time and other hard constraints before ranking relevance, while leaving room for exploration.
A smaller choice set reduces browsing breadth but gives students a more manageable decision.
Explain what to expect, highlight beginner-friendly formats and offer mutual-opt-in Go Together groups or newcomer welcomes. Students can use discovery without social features.
Social support introduces moderation and privacy responsibilities; it should never be a forced step.
Pair reviewed event publishing with registration, attendance workflows and useful feedback. AI-assisted event extraction produces a draft for human confirmation.
Better supply requires organizer onboarding and ongoing data-quality work, not just a recommendation model.
Keep views, saves, RSVPs and supported check-ins distinct. Use attendance evidence and reporting coverage to assess whether discovery leads to action.
Attendance is only measurable where a reliable, permitted confirmation workflow exists.
Useful discovery depends on fresh events. Better organizer workflows make that supply more reliable.
Keep discovery, ordinary planning and participation accessible. Give organizations publishing, registration and basic reporting value.
Advanced reporting, authorized integrations, administration, onboarding and support form the institutional value proposition. This describes the model, not a verified customer or revenue result.
Explore the product thinking through a small, interactive illustration. The example content below is fictional and is not a screenshot or a live product integration.
Explore an interest, understand the fit, and keep one next step.
A low-pressure introduction to student design projects.
Bring an idea, explore a project, or meet a collaborator.
A small-group introduction to places and people on campus.
Choose a perspective to explore the product decisions. The examples are fictional and describe the supplied product scope.
A fictional transfer student is interested in technology and entrepreneurship but does not yet have a campus network.
Receive three beginner-friendly suggestions matched to stated interests and availability.
Review the workshop format, membership rules and newcomer guidance before committing.
Attend independently or opt into an event-specific group, then follow the organizer for future activities.
Opt into a small event group. Only students who choose this event’s social feature are included.
You are not part of a group. Browsing and saving do not opt you in.
Explore the broader platform scope described in Rico’s product account.
Personalized recommendations, natural-language discovery, event filters, intelligent club exploration, explanations of fit and event freshness. Constraints are checked before ranking, with room to explore new interests.
Saved events, organizer-supported registration, reminders and commuter time windows. Calendar connection is optional; a portable calendar event is an alternative. A save, an RSVP and attendance remain different states.
Go Together provides event-specific, mutual-opt-in groups and newcomer welcomes. Campus Circles supports recurring activities. Social participation stays optional, with clear visibility, leave, block and report controls.
Verified organizer roles, reviewed event publishing, AI-assisted drafts, recurring sessions, capacity, waitlists and attendance workflows. The account describes signed QR check-in credentials, idempotency and offline reconciliation.
Organizer reporting, recommendation evaluation and aggregate institutional insights. Role-based access and reporting thresholds separate useful campus trends from individual student preferences and unrelated activity.
Normalize permitted feeds and organizer submissions, preserve authoritative sources and track when facts were last confirmed.
Semantic interpretation enriches discovery while generated summaries remain separate from verified times, venues and eligibility facts.
Use stated interests, goals, availability and optional feedback. Students can reset personalization; sensitive attributes are not inferred.
Remove canceled, expired or ineligible records and enforce selected hard constraints. An unknown schedule is distinct from a confirmed conflict.
Combine structured fit, semantic relevance, participation effort, event reliability and exploration so familiar or popular organizations do not dominate.
Connect recommendations to real event records and stated preferences. Missing information remains uncertain and points back to the organizer.
Assess relevance judgments, event correctness, participation signals and visibility across organizations with appropriate aggregation.
React, TypeScript, Vite, Tailwind, Cloudflare Workers and D1 are documented in the public README. The broader recommendation, social, organizer and institutional architecture is described in Rico’s supplied account; source and operational deployments have not been independently inspected. Portfolio visuals and interactions are clearly labeled illustrations.
The wider architecture is owner-described; public application source is not yet available for review.
Across tested iterations · 15 usability tests
Active / eligible participants · 40%
The README reports 15 usability tests, task completion increasing from 70% to 90%, and discovery time decreasing 36% across tested iterations. These observations are not a randomized causal estimate. Exact coverage of the expanded platform features has not been supplied.
An earlier beta involved 100 students. Four-week retention was 30 active participants out of 75 eligible participants, or 40%. The full eligibility definitions and participant-level data are not public; the cohort is not presented as proof of every newer feature.
The expanded measurement approach compares relevant discovery, clearer event information and optional newcomer support. Recommendation quality, attendance coverage, data freshness, smaller-organization visibility and trust need their own measures. No new experiment, friendship or belonging outcome is claimed.
Count student-initiated activities supported by a verified check-in or another permitted participation confirmation. Define the active-student denominator independently and report attendance-measurement coverage alongside the result.
A metric definition, not a reported outcome. A view, save or RSVP is never counted as completed participation. Participation alone does not establish friendship or belonging.
Discovery, confidence and participation form one product journey. The organizer experience matters because student trust depends on the quality of the opportunities supplied.
Publish a product walkthrough and source snapshot, map research and beta results to the versions tested, and evaluate the expanded participation experience with explicit cohort and attendance-coverage definitions.
Reviewed November 10, 2026. Repository documentation is attributed to its author; implementation claims are distinguished from research findings and planned capabilities.
Project README & reported study results (opens in a new tab)The expanded scope comes from Rico’s product account. The corrected survey finding is 69/120 (57.5%) for discomfort attending unfamiliar events. Public app releases, active institutional integrations, signed customers, revenue and audited accessibility conformance are not established by the supplied artifacts.
Download the content verification record