UniVerse

UniVerse is a macOS desktop application built as a hackathon project to unify academic information from multiple systems (e.g., Canvas, Workday) into one workspace, with an integrated AI assistant named "Uni". The app aims to reduce time spent navigating fragmented tools and improve focus on learning. It was developed by two team members over a weekend using Electron, React, TypeScript, and AI agents like GPT-5.6 and Codex.

The project is self-reported as a prototype for a student-focused productivity tool. No revenue, customers, or traction data are provided beyond the authors' own account. The product’s positioning centers on simplifying academic workflows through integration and AI grounding, but there is no evidence of commercial adoption or monetization strategy.

The description states that UniVerse is a macOS app that connects to academic systems like Canvas and Workday. It syncs course data, assignments, syllabi, and grades, and uses AI (powered by GPT-5.6) to answer questions based on this context.

Key features include:

• A home page ranking work by deadlines and grade weights
• Grade views showing which classes need attention
• Study tools such as flashcards, quizzes, summaries, and study plans
• Registration planning that reads degree requirements
• Schedule comparison based on class conflicts and gaps
• Calendar exports for assignments, exams, and study blocks
• A focus mode tied to specific assignments

The app is built with Electron, React, TypeScript, Vite, and SQLite. AI components are implemented using GPT-5.6 and Codex.

Inference The product is a desktop application designed for macOS users, likely targeting students enrolled in institutions using Canvas or similar LMS platforms.

The authors claim UniVerse unifies campus tools with AI to help students focus on learning. They describe it as an alternative to the fragmented experience of juggling multiple systems like Canvas, Workday, and ChatGPT.

Their positioning emphasizes:

• Integration: One workspace for all academic information.
• AI grounding: Uni answers questions using course materials without re-uploading files.
• Student-centric design: Reducing time spent managing schoolwork so students can focus on learning.

The tagline “Put Your Studies in Orbit” suggests a metaphorical alignment with student workflows and academic orbits — implying a sense of structure and movement toward goals.

Inference The positioning reflects a desire to solve the problem of information fragmentation in higher education, but lacks any indication that this has been validated by users or markets beyond the authors’ own experience.

The description states that UniVerse is intended for students, particularly those enrolled at institutions using Canvas and Workday (e.g., Washington University in St. Louis). The app currently works best with WashU's systems, but the authors intend to expand support to other LMS platforms like Blackboard, Moodle, and Brightspace.

There is no evidence of segmentation beyond student users or specific institutional types. No mention of faculty, administrators, or institutions outside of those using Canvas or Workday.

Inference The primary ICP appears to be undergraduate students in U.S. universities using Canvas-based LMSs, though the authors express intent to broaden support.

The description states that UniVerse will remain free, with no intention for profit. The goal is described as improving university education rather than monetizing the tool.

There is no mention of:

• Revenue streams
• Paid features or tiers
• Subscription models
• Licensing or enterprise options

Inference No business model has been defined beyond a free, open-source or non-commercial approach.

The app was built in one weekend using:

• Technologies: Electron, React, TypeScript, Vite, SQLite
• AI tools: GPT-5.6 and Codex
• Development process: Use of AI agents to generate initial code layers (main process, renderer, IPC contracts, database layer)
• Architecture: Shared types between components; React interface cannot directly access Node/Electron/SQLite
• Design approach: Frameless window, native macOS vibrancy/translucency, custom orbit branding

The authors note challenges with integrating different data sources (Canvas vs. Workday), handling various file formats (PDFs, Word docs, HTML), and managing time constraints during development.

Inference The technical stack and architecture suggest a rapid prototyping approach using modern web technologies and AI-assisted development. However, there is no evidence of scalability or long-term maintainability beyond the hackathon version.

The project was submitted to the OpenAI 2026 hackathon, indicating it is a prototype or proof-of-concept. No evidence exists of:

• User adoption
• Customer feedback
• Revenue generation
• Market traction
• Product usage metrics

The authors describe their work as a weekend effort, with time constraints leading to feature cuts and prioritization.

Inference The project shows early-stage development maturity but lacks any signs of real-world use or market validation.

There is no mention of existing competitors in the description. However, based on the stated functionality (LMS integration, AI assistant, study tools), potential comparisons might include:

• Canvas itself
• Notion or Obsidian for personal knowledge management
• Study apps like Quizlet or Anki
• Productivity tools such as Todoist or Calendly integrated with LMS

No competitive analysis is provided, nor is there evidence of market research or differentiation strategies.

Inference The competitive landscape is unknown, but the described features suggest overlap with existing academic productivity tools. No clear positioning relative to competitors exists in the description.

• Unproven market demand: No evidence of user testing or real-world usage.
• Limited scope: Currently only supports WashU's systems; expansion plans are speculative.
• No monetization strategy: Free tool with unclear path to revenue.
• Dependency on AI tools: Reliance on GPT-5.6 and Codex may not be sustainable or scalable.
• Technical fragility: Rapid prototyping approach may lack robustness for long-term use.
• Lack of institutional partnerships: No evidence of collaboration with schools or LMS providers.

Inference The project is highly speculative, with no demonstrated traction or commercial viability. Risks include technical debt, scalability issues, and lack of clear value proposition beyond a hackathon demo.

1. What specific pain points do students at WashU experience that UniVerse addresses?
2. How does the app handle data privacy and security for student information?
3. Are there any plans to integrate with other LMS platforms beyond Canvas?
4. What are the technical limitations of the current architecture, especially around scalability or performance?
5. How would you monetize UniVerse if it were to become a full product?
6. Have you tested the app with actual students from WashU or other schools?
7. What is the long-term vision for maintaining and updating the app after the hackathon?
8. How do you plan to ensure compatibility with future updates from Canvas, Workday, or other systems?