Aiming for **social impact* track*

Inspiration

I'm a freshman, and my first quarter at UCR has mostly been me figuring out UCR. Which dining hall has something I actually want to eat? Is Lot 30 full again? Where is MSE 116? Is there a study room open at Orbach right now? Every one of those answers exists, but they're spread across a dozen websites that were never built for a phone.

UCR does have a campus app, but it's mostly a list of links that open those same websites. No widgets, no notifications, nothing that feels like it belongs on an iPhone, and many students I asked at this hackathon said they don't use it.

I realized this isn't just a freshman problem. Transfer students get one quarter less to learn the campus than I did. Grad students live in a different set of buildings and schedules. Commuters care about parking more than anyone. So I designed Belltower to be useful no matter what year you're in or how you get to campus: open it, and the thing you need is already there.

What it does

Belltower puts everything a UCR student checks in a day into one fast, native iOS app.

  • Today: one screen for your day. Parking at your lot, a free study room you can tap to reserve, how busy the gym is, your next meal, your classes and the events you're going to, plus weather.
  • Dining: today's and tomorrow's menus for Glasgow, Lothian, Noods and Savor, with full nutrition labels, allergens and ingredients. Filter for vegetarian, vegan, gluten free or high protein, and hide nine common allergens. The current app doesn't show nutrition at all.
  • Classes: browse every course with live seats, waitlists, prerequisites and section times. Build a schedule with a week grid, unit total and time conflict warnings, then copy your CRNs straight into R'Web.
  • Events and Clubs: three weeks of campus events and the full HighlanderLink club directory, with search, filters and a daily "Discover" pick. Yes, it flags club events with free food.
  • Parking: live open spaces by lot, with a warning when UCR's counts are out of date.
  • Library: seven days of study room availability at Rivera and Orbach.
  • Map: buildings, food, restrooms, water stations, bike racks and safety resources, with walking directions.
  • Gym: live SRC headcounts by area.
  • Safety: campus status, one tap (with confirmation) to call 911 or UCPD, and the recent UCPD crime log on a map.

It also lives outside the app: six widgets for the Home Screen and Lock Screen (dining, events, study rooms, parking, gym, safety) and ten Siri shortcuts that work with zero setup. "Hey Siri, what's for dinner at Glasgow in Belltower" just works.

There's no account and no sign in. Belltower reads public campus data directly on your phone and keeps your schedule, saved clubs and preferences on your device.

How I built it

Belltower is built with Expo SDK 58, React Native and Expo Router, using native tabs, SwiftUI components and Liquid Glass so it looks and feels like an Apple app instead of a website in a wrapper. The widgets (WidgetKit) and Siri shortcuts (App Intents) are written in Swift and share data with the app through an App Group.

There's no server. Each feature talks to the public system UCR already runs:

  • Dining from UCR's FoodPro menu system, parsed on device
  • Classes from Banner, with outage status from Status.io
  • Events from events.ucr.edu, clubs from HighlanderLink
  • Parking from openspaces.ucr.edu, study rooms from LibCal
  • The campus map from Concept3D, gym counts from Connect2
  • Safety from campusstatus.ucr.edu and the UCPD crime log
  • Weather from Open-Meteo

Every source is cached for offline use, and the parsers are covered by tests that run against recorded responses, including the ugly cases: malformed pages, closed dining halls, missing nutrition data and stale parking counts.

I built Belltower on my own, so I picked a no server architecture and on device parsing to keep everything small enough for one person to build, test and ship in a hackathon.

Challenges I ran into

  • Nine data sources, zero APIs built for apps. FoodPro is an old ASP site, Banner only returns results after you "select a term" in a cookie based session, and every source has its own format and failure modes. Writing parsers that fail gracefully instead of showing garbage took more time than any screen.
  • No backend, on purpose. Keeping everything on device protects privacy and means nothing to host, but it also means widgets and Siri can't call into the JavaScript app. I had to mirror parts of the data logic in Swift and keep both versions in sync.
  • Stale data is worse than no data. A parking count from an hour ago could send you to a full lot, so every live feature shows when its data was last updated and warns you when it's out of date.
  • Tooling at 9am. I lost my first hour to an Xcode beta trying to download a multi gigabyte simulator over hackathon WiFi, and to a terminal that was still sitting inside a project folder I had deleted. Switching to stable Xcode and building to a real iPhone got me moving.

Accomplishments that I'm proud of

  • I built it solo, in one day. Nine live data sources, six widgets, ten Siri shortcuts and a full native app, from an empty folder this morning to running on my phone tonight.
  • It's actually useful today. I've been using it on my own phone during this hackathon to check dining menus and parking.
  • It covers nearly every public UCR system a student touches, in one app, with no login.
  • It feels native: Liquid Glass, Dynamic Type, dark mode, haptics and a customizable tab bar, so a commuter can put Parking first and a grad student can put Classes first.

What I learned

  • Most of the real work in a "simple" app is in the data: knowing when it's wrong, when it's stale, and what to show when it fails.
  • How to share data between a React Native app, WidgetKit and App Intents through an App Group, and how to keep logic written in two languages consistent.
  • Designing for every student instead of just myself changed the product. The customizable tab bar, the Today screen and the commuter features came directly from thinking about people with a different UCR experience than mine.

What's next for Belltower

  • TestFlight now, App Store next. The goal is for Belltower to be on the home screen of every UCR student, not just to win this weekend. I'm planning to keep building it after this hackathon.
  • Seat alerts during registration, so you get notified when a full class opens up.
  • Better onboarding for new students, with first week guides for freshmen and transfers.
  • Accessibility routes on the map, and more dining locations.
  • Working with UCR Dining, Transportation and Student Life to make the data more reliable, since every one of them benefits when students can actually find what they offer.

Built With

Share this project:

Updates

Submission history