Skip to content

Apps

The stage as an app of its own

plannedForTeaching staff

The slide editor as a standalone app for phone, tablet, web and computer — the same core, split off as a versioned copy.

Why#

Build and give presentations, even without a learning platform — with everything the stage can do, on every device.

How it works#

  1. 1The core has already been built as a self-contained module: slide model, elements, history, templates, suggestions, timing to the voice — without ties to courses, roles or database.
  2. 2The split-off follows as a versioned copy with an adoption log; there is no automatic synchronisation.

Settings and switches#

No switch of its own in the feature catalogue — the feature belongs to its surroundings.

What is already in place#

  • A core without imports from outside its folder — no interface framework, no database, no course or role model; a guard checks this.
  • It runs unchanged in any JavaScript environment: web, phone, tablet, computer — without dependence on screen, clock or randomness.
  • Every edit is a command in a plain, storable format; the history stores state and command.
  • The interface depends only on the core and on an adapter (rendering, upload, AI, beam, figures, storage, back to template) and can come along.

Planned scope#

The standalone version is to be able to do everything the stage can do — on all major platforms for phone, tablet, web and computer —, and to process every movement in the core as a command: mouse, finger, gesture in front of the camera, phone, voice, second device.

How the adoption works#

  • copy the core's folder and record the version together with the source state
  • create an adoption log: source and target version, adjustments, deviations of the interface, test results, changes not yet adopted
  • copy the tests along and run them there
  • write a converter of its own for its own templates — or none

Related features#