StudentOS product banner: academic command center for university students
02 / software

StudentOS

Product exploration · Paused before beta

An academic OS prototype: classes, tasks, calendar, focus, and Ask AI in one workspace. Advanced far enough to expose a hard product decision, then paused before paid beta.

View on GitHub

An academic OS, explored far enough to pause

StudentOS was built as a student-first planner: home, calendar, focus, and Ask AI on React Native. It is a product exploration paused before a paid beta, not a live closed beta with users.

Home

Weekly progress, streak, and what matters today.

Calendar

Classes, exams, and vacations across day, week, and month.

Focus

Timer and stopwatch with music inside the study loop.

Ask AI

Study coach for planning and academic help.

∥Paused
1Academic OS concept
OTPSchool-email path designed

Why it exists, and why it stopped

Students do not lack apps. They lack continuity. Building far enough revealed a model problem: useful AI coaching has a marginal cost, and Apple distribution is not free. I refused a portfolio beta that burns money without a monetization path.

Fragmented student stack
NotionCalendarCanvasNotesGmailRemindersDriveGroup chats
Intended academic workspace
StudentOS
Pause before paid betaI would not fund Apple fees or AI API usage for free testers just to write “beta” on a portfolio.
Architecture vs economicsAn AI study coach that feels useful introduces cost per user. Without monetization, scale is a liability.
Keep the learningStudentOS remains the case study for vision, academic job-to-be-done, and the hard stop before burn.

How far it went

Problem framing → academic OS design → Expo build path → pause before distribution spend. Resume only if the model is clear.

Expo UIReact Native screens, navigation, and motion.
Client stateZustand store + AsyncStorage for local continuity.
API + authExpress API, JWT sync, school-email OTP join path.
Ask AIServer-proxied study coach, the cost center that forced the pause.
01

Name the fragmentation

Map the student week: classes, deadlines, focus, and the cost of juggling five tools.

02

Design the academic OS

Home as the next-action surface, then calendar, focus, profile, GPA, and Ask AI as connected jobs.

03

Build the prototype deep

Ship enough of the loop on Expo to feel the product, including the AI coaching path.

04

Pause on purpose

Stop before Apple spend and AI burn. Treat that stop as a product decision, not a failure.

Screens · Product
StudentOS school-email OTP sign-in screen
01Auth path

School-email OTP path designed for a future beta, not a live cohort today.

StudentOS home command center
02Home

Weekly progress, streak, and the next academic action in one place.

StudentOS calendar screen
03Calendar

Classes, exams, and vacations visible across day, week, and month.

StudentOS focus timer screen
04Focus

Study blocks with timer and music: deep work inside the product loop.

PlatformReact NativeExpoSDK 54StagePaused explorationLicenseMIT

Highlights

  • Academic objects: classes, tasks, exams, vacations
  • Home command center with weekly progress and next actions
  • Focus timer / stopwatch with music in the product loop
  • Ask AI study coach via server proxy (the cost center)
  • School-email OTP path designed, not a live tester cohort
  • Paused on purpose before Apple fees and API burn

Tech Stack

  • React Native
  • Expo Router (SDK 54)
  • TypeScript
  • Zustand + AsyncStorage
  • Express API + SQLite
  • EAS Build / Submit

Getting Started

Prerequisites

  • Node.js 20+
  • npm
  • Expo Go if you want to run the prototype

Run the app

  1. Clone the StudentOS repository.
  2. Run npm install (and npm --prefix server install if using the local API).
  3. Start with npm run start:go and scan the QR code in Expo Go.
  4. Treat this as a prototype exploration, not a public beta.

Build

npm run start:go

Project Structure

app/           # Expo Router screens
components/    # Shared UI
src/           # Domain logic
server/        # Express API + SQLite
store/         # Native distribution docs
screenshots/   # Product captures

Roadmap

  • Resume only if monetization and AI cost model are clear
  • Keep the academic OS vision documented as product learning
  • Do not run a vanity beta that burns distribution or API budget

Trade-offs

DecisionPause before Apple distribution fees and AI API spend on free testers
TradeoffAcademic depth over becoming another Notion
ConstraintUseful AI coaching has a marginal cost without monetization