lecture.studio

Install

Download the DMG, drag the app into Applications, verify the checksum, and update later.

Lecture Studio ships as a signed and notarized disk image. There is no installer and nothing is written outside the app bundle until you choose a library folder.

Download and install#

  1. Download the DMG from the download page or from the GitHub releases. The stable link /download/latest always points at the newest release.
  2. Open the DMG. The window shows the app and a shortcut to Applications.
  3. Drag Lecture Studio onto Applications.
  4. Eject the disk image and open the app from Applications or Spotlight.

Builds from 0.1.1 on are signed with an Apple Developer ID and notarized by Apple, so the app opens without a Gatekeeper warning. If macOS still asks, the download was altered or the release predates notarization; download it again from the links above.

Verify the download#

Every release page lists the SHA-256 of its DMG. To compare:

shasum -a 256 ~/Downloads/LectureStudio-0.1.8.dmg

The printed hash must match the one on the release page.

Update#

There is no in-app updater yet. To update, download the new DMG and drag the app over the old one in Applications. Your library folder, settings and chat history are untouched: they live outside the app bundle.

Uninstall#

Move Lecture Studio from Applications to the Trash. What stays behind, and where:

WhatWhere
Your library (decks, sources, assets)The folder you chose. It is yours; the app never moves it.
Chat history~/Library/Application Support/LectureStudio/chats/
Settings (library path, panel layout, sort order, project id, subject)The app's preferences in ~/Library/Preferences/
Oberik project keyThe macOS Keychain, item com.akademi.lecture-studio

Delete those by hand if you want a clean slate.

Build from source#

The app is open source. With Xcode 16 or later and Node.js 20 or later:

git clone https://github.com/ekremcet/lecture-studio.git
cd lecture-studio
scripts/build.sh     # bundles the JS core, then swift build
swift run            # launches the app

A source build keeps the Oberik project key in a file under Application Support instead of the Keychain, because an unsigned binary would trigger a Keychain consent dialog on every rebuild.