ClientMVPPrivate2026

Folio

Folio is a shared React application for school and tutoring-center management that runs the same codebase in the browser, as a Tauri desktop app, and prepared for Tauri Android. It covers first-run school setup, role-based staff authentication, students, class scheduling, attendance tracking, billing, teacher payouts, and reporting, with almost all of it real and SQLite-backed rather than mock data. Built as a client engagement for a private school.

Folio

About This Project

A private tutoring/school client needed one system to replace scattered spreadsheets and manual processes for scheduling, attendance, billing, and teacher payouts, usable both on a front-desk browser and as an installable desktop app.

Built a single React codebase that ships as a web app and a Tauri desktop app (with Android on the roadmap), backed by a real SQLite data layer covering students, classes, attendance, billing, and payouts rather than a demo-only mock layer.

A working management platform handling day-to-day attendance, billing, and scheduling for the client's tutoring center, with a shared codebase that avoids maintaining separate web and desktop implementations.

Role

Full-stack Developer

Year

2026

Status

Private

Type

Client

Technology Stack

TauriReactTypeScriptViteTailwind CSSRustSQLite

Project Story

The Challenge

A private tutoring/school client needed one system to replace scattered spreadsheets and manual processes for scheduling, attendance, billing, and teacher payouts, usable both on a front-desk browser and as an installable desktop app.

The Approach

Built a single React codebase that ships as a web app and a Tauri desktop app (with Android on the roadmap), backed by a real SQLite data layer covering students, classes, attendance, billing, and payouts rather than a demo-only mock layer.

The Outcome

A working management platform handling day-to-day attendance, billing, and scheduling for the client's tutoring center, with a shared codebase that avoids maintaining separate web and desktop implementations.

Insights & Takeaways

Highlights

  • One React codebase runs as a browser app, a Tauri desktop app, and is Android-ready via Tauri mobile.
  • Real SQLite-backed data model across students, classes/scheduling, attendance, billing, and teacher payouts — not placeholder data.
  • Role-based staff authentication and first-run school setup flow for onboarding a new center.

Challenges

  • Keeping one React codebase behaving correctly across three different runtime targets (browser, Tauri desktop, Tauri Android) without forking logic per platform.
  • Modeling attendance, billing, and payout workflows accurately enough to replace the client's existing manual/spreadsheet process outright.

Lessons Learned

  • Targeting Tauri desktop and Android from day one, on top of the browser build, pays off specifically when the same non-technical staff need to use whichever device is in front of them.

Related Work