space-spec System Requirements Document

1. Introduction

The space-spec project is designed to address the challenges faced by film and television productions when actors interact with phones and tablets on camera. Traditional methods such as green screens and static mockups often require costly post-production work. This project aims to provide a mobile application that allows for scripted iOS interactions on physical devices, ensuring a seamless and believable on-set experience.

2. System Overview

The space-spec system comprises two main components:

1. Crew Control: An off-camera workspace for crew members to create productions, configure scenes, edit simulated interfaces, connect devices, rehearse interactions, trigger cues, and monitor devices used on camera.

2. Performance Mode: A locked, full-screen runtime on the actor’s device that renders camera-ready simulations without editor controls, notifications, or unapproved navigation. Actor input is constrained through scripted typing, guided gestures, deterministic transitions, and approved interaction paths.

The system supports iOS simulations, including messaging, video calls, web browsing, social feeds, email, maps, media galleries, notifications, lock screens, and other extensible interface templates. It operates entirely offline during filming, with optional cloud support for pre/post-production tasks.

3. Functional Requirements as Story Points

• As a Crew Member, I should be able to create and configure scenes in the Crew Control workspace.
• As a Crew Member, I should be able to edit simulated interfaces and connect devices.
• As a Crew Member, I should be able to rehearse interactions and trigger cues.
• As a Crew Member, I should be able to monitor devices currently used on camera.
• As an Actor, I should be able to use the Performance Mode to interact with camera-ready simulations without distractions.
• As a System, I must support iOS simulations including messaging, video calls, web browsing, social feeds, email, maps, media galleries, notifications, and lock screens.
• As a System, I must operate locally without requiring cloud services during filming.
• As a System, I should provide optional cloud infrastructure for preparation, backup, collaboration, and synchronization before or after filming.

4. User Personas

• Crew Member: Responsible for setting up and managing the on-set prop phone interactions.
• Actor: Uses the Performance Mode to interact with the simulated iOS environment during filming.

5. Core User Flows

• Crew Member configures scene -> edits simulated interface -> connects device -> rehearses interaction -> triggers cue -> monitors device.
• Actor uses Performance Mode -> interacts with simulation -> follows scripted interaction paths.

6. Visuals Colors and Theme

• primary: #1a1a1a (dark gray for high contrast)
• primary_light: #333333 (lighter gray for hover states)
• secondary: #4d4d4d (supporting gray)
• accent: #ffcc00 (yellow for CTAs and active states)
• highlight: #ff9900 (orange for hover states and notifications)
• bg: #000000 (black for background)
• surface: #1a1a1a (dark gray for cards/panels)
• text: #ffffff (white for primary text)
• text_muted: #cccccc (light gray for secondary text)
• border: #666666 (subtle gray for borders)

7. Signature Design Concept

Interactive Film Set Simulation

The landing page of the space-spec application will feature an interactive film set simulation. Users can click and drag to explore a 3D model of a film set, where each element (e.g., cameras, lights, actors) is interactive. Hovering over an element reveals its role in the production process, and clicking on it provides detailed information and options for interaction. This concept will be implemented using @react-three/fiber for 3D interactions, providing an immersive experience that mirrors the on-set environment.

Landing Hero Motion Brief

The hero section will depict a dynamic film set where a virtual camera pans across a bustling scene. As it moves, various elements like actors and crew members animate to show their roles. The animation will loop every 10 seconds, showcasing the transformation from a static set to a vibrant filming environment. This will be achieved using motion/react for smooth transitions and animations.

8. Interaction Model & Motion Direction

• Interaction Model: Parallax
• The landing page will feature layered depth via scroll, with decorative elements translating at different speeds to create a sense of depth. Real content will scroll naturally, enhancing the storytelling aspect of the page.

9. Non-Functional Requirements

• The system must ensure reliable and deterministic playback across repeated takes.
• It must provide low-latency control of one or more performance devices.
• The system should allow for fast recovery, resetting, and emergency concealment.
• It must maintain accurate continuity through versioning and take records.
• The interface should be actor-proof, preventing accidental deviations.
• The system should have a dark, high-contrast, production-oriented interface suitable for busy sets.

10. Tech Stack

• Frontend: React for Web
• Backend: Python, FastAPI
• Database: MySQL or MariaDB, using Alembic for migrations
• Local Orchestration: Docker, docker-compose
• Server-side Orchestration: Kubernetes

11. Assumptions and Constraints

• The application must operate entirely offline during filming.
• Optional cloud support is available for pre/post-production tasks but is not a runtime dependency.
• The interface must be suitable for high-contrast, low-light environments typical of film sets.

12. Glossary

• Crew Control: The workspace for crew members to manage on-set interactions.
• Performance Mode: The actor's interface for interacting with simulated iOS environments.
• iOS Simulations: Simulated interfaces that mimic iOS applications for filming purposes.