OrbOblivion

• 

  OrbOblivion

Inspiration We've all felt the dread of 50+ unread notifications across email, Slack, and WhatsApp — knowing something important is buried but not knowing what. As analytics and consulting students at UNSW, we watched peers miss critical deadlines and networking opportunities simply because their inboxes became overwhelming noise. We thought: what if managing obligations felt less like drowning and more like navigating a universe you actually control? What it does OblivionOrb transforms your notifications into a physics-based solar system. Each message or task becomes a glowing orb orbiting around you — sized by urgency, colored by relationship, and accelerating as deadlines loom. Orbs collide when crises converge. Our AI clones your writing voice to draft replies you approve with one tap, detects burnout from your response patterns, and enforces smart "oblivion bubbles" that mute low-priority noise while syncing to your calendar. How we built it We used React Native with Three.js for the 3D orbital physics engine on the frontend. On the backend, we fine-tuned Llama models for tone cloning and message prioritization. Burnout detection runs on-device ML to keep data private. We integrated with Google Workspace and calendar APIs to pull in obligations and sync break windows to real schedules. Challenges we ran into Getting the physics to feel intuitive rather than gimmicky was tough — early versions had orbs flying everywhere chaotically, which ironically added more stress. Tone cloning accuracy took extensive iteration; early drafts sounded robotic. Balancing privacy with cross-platform sync was a constant tension, and scoping the feature set to something demoable meant killing some ideas we loved. Accomplishments that we're proud of The orbital collision alerts genuinely surface conflicts we'd otherwise miss. Our tone cloning hit 90% approval rates in user testing, meaning people trusted the AI to sound like them. Most personally, teammates started actually using the burnout detection during the hackathon itself — which says everything about the problem we're solving. What we learned Visualization matters more than we expected — people made better decisions just by seeing their obligations spatially rather than in a list. We also learned that burnout detection isn't just a feature, it's a responsibility; deciding when to interrupt someone versus protect their focus is a genuinely hard design problem. And we learned that physics engines and notification APIs don't play nicely together at 3am. What's next for OblivionOrb We're building AR desk overlays so your orbs float in your physical workspace, adding team-level views for managers to spot delegation opportunities, and expanding integrations to Microsoft Teams and WhatsApp. Longer term, we want to introduce "orbit history" — a time-lapse of your communication patterns that helps you understand your work habits over weeks and months, not just react to today's chaos.

Built With

• lovable