golden-camera

byManish Rohan James

A mobile app, Time Travel, MVP TECH DOC — TimeLens --- Goal AR camera. Overlay past life. Fast. Stable. Shareable. --- Platforms Android first Later iOS --- Stack Client Unity ARCore C# Assets Low-poly 3D models 1–5 MB each Backend None (MVP) --- Modules 1. Camera + AR Session Initialize ARCore Plane detection (horizontal) 2. Placement Engine Tap → place anchor Auto-scale by distance 3. Era Engine Enum: Jurassic Ice Age Early Humans Map → asset bundle 4. Creature Controller Idle animation Loop animation Simple movement (optional) 5. Overlay Engine Sky tint Fog Ground texture decal 6. Capture Module Screenshot Video recording (basic) --- Data (local JSON) { "eras": [ { "name": "Jurassic", "creatures": ["brachiosaurus", "trex"], "skyColor": "#87CEEB", "fog": 0.2 } ] } --- Performance targets FPS: 30+ Load time: <3s APK size: <150MB --- --- PRD — PRODUCT REQUIREMENTS --- Problem Learning history boring. No immersion. --- Solution AR time travel camera. See past world instantly. --- Target users Kids (10–16) Curious adults Content creators --- Core features Must-have AR camera Era switch Creature placement Capture + share Nice-to-have Info popups Sound effects --- User flow Open app → Camera opens → Select era → Tap ground → Creature appears → Capture → Share --- Success metrics Day 1 retention >30% Avg session >2 min Shares per user >1 --- Non-goals Scientific accuracy Multiplayer Backend sync --- --- SYSTEM DESIGN --- High level User device only. No server. --- Flow Camera feed → ARCore tracking → Plane detection → Anchor placement → Load 3D asset → Render scene --- Key components AR Engine Motion tracking Environment understanding Renderer Unity scene Lighting + shaders Asset Loader Local bundle load Lazy load per era --- Storage Local: Assets Config JSON --- Risks Device compatibility FPS drops Bad plane detection --- --- ARCHITECTURE --- Layers 1. Presentation UI (era select, buttons) 2. AR Layer Session manager Plane detection Anchor system 3. Domain Era manager Creature manager 4. Data Local config Asset bundles --- Diagram (simple) UI Layer ↓ AR Session Manager ↓ Placement Engine ↓ Creature Controller ↓ Renderer (Unity) --- State management States: INIT SCANNING PLACED CAPTURE --- Scaling later Add: Remote asset CDN User accounts Analytics --- Hard constraints Keep it light Avoid backend early Focus on smooth AR --- Brutal focus 1 creature 1 era working demo Ship fast.

HomeEra SelectAR Camera
Home

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document
Page 1 of 7

System Requirements Document (SRD)

golden-camera

1. Introduction

The golden-camera project is an innovative mobile application designed to bring history to life through augmented reality (AR). By overlaying realistic, immersive visuals of past eras onto the real world, users can experience time travel in a unique and engaging way. This document outlines the system requirements for the project, ensuring that the application delivers high-quality, near-realistic outputs while maintaining performance and usability.

This SRD has been updated to reflect the need for outputs that are close to realistic, as pre-resolved by the API supervisor.

Page 2 of 7

2. System Overview

The golden-camera app is an AR-based time travel camera that allows users to explore historical eras by placing creatures and environmental elements into their surroundings. The app is designed for Android devices initially, with plans to expand to iOS in the future.

Key features include:

  • Realistic AR visuals of creatures and environments.
  • Era selection with dynamic overlays (e.g., sky tint, fog, ground textures).
  • Capture and sharing functionality for user-generated content.

The app is lightweight, backend-free (for the MVP), and optimized for smooth performance on a wide range of devices.

3. Functional Requirements

As a User:

  • I should be able to open the app and immediately access the AR camera.
  • I should be able to select an era from a predefined list.
  • I should be able to tap on the ground to place a creature in the AR scene.
  • I should see realistic animations for the placed creature, including idle and loop behaviors.
  • I should be able to capture screenshots and record videos of the AR scene.
  • I should be able to share captured content directly from the app.

As an Admin:

  • I should be able to update the list of eras and associated assets via local JSON files.
  • I should be able to test the app for performance metrics like FPS and load time.
Page 3 of 7

4. User Personas

1. Kids (10–16 years old):

  • Curious learners who enjoy interactive and visual experiences.
  • Likely to share content with friends on social media.

2. Curious Adults:

  • History enthusiasts or casual users interested in exploring past eras.
  • Appreciate realistic visuals and immersive experiences.

3. Content Creators:

  • Social media influencers and AR enthusiasts.
  • Focused on creating shareable, visually appealing content.

5. Visuals Colors and Theme

Page 4 of 7

Color Palette:

The golden-camera app will use a unique color palette inspired by historical and natural tones to enhance the immersive experience:

  • Background: #F5F3E7 (Soft Sand)
  • Surface: #D9CBA0 (Ancient Parchment)
  • Text: #3B3A36 (Charcoal Black)
  • Accent: #A67C52 (Bronze Gold)
  • Muted Tones: #8E9A9B (Weathered Stone)

This palette creates a warm, earthy aesthetic that complements the historical theme of the app.

6. Signature Design Concept

"Living Time Portal" Landing Page

The home screen of the golden-camera app will feature an interactive "time portal" animation. Users will see a glowing, swirling vortex in the center of the screen, with fragments of historical scenes (e.g., a dinosaur tail, an ancient campfire, or an ice age glacier) briefly appearing and disappearing within the portal.

Details:

  • Animation: The portal will have a dynamic, particle-based animation that reacts to user input. Swiping across the screen will cause the portal to "shift" and reveal glimpses of different eras.
  • Transitions: When an era is selected, the portal will "expand" outward, transitioning seamlessly into the AR camera view.
  • Micro-interactions: Subtle haptic feedback will accompany user interactions, such as tapping or swiping.
  • Sound Design: A soft, ethereal hum will play in the background, with era-specific sound effects (e.g., dinosaur roars or icy winds) triggered during transitions.

This design ensures that the app makes a bold first impression, immersing users in the concept of time travel from the moment they open it.

Page 5 of 7

7. Non-Functional Requirements

  • Performance:

    • Maintain a minimum FPS of 30+ during AR sessions.
    • Ensure load times are under 3 seconds.
    • Keep the APK size below 150MB.
  • Compatibility:

    • Support Android devices running Android 8.0 (Oreo) or higher.
    • Ensure compatibility with a wide range of hardware configurations.
  • Usability:

    • Provide an intuitive and user-friendly interface.
    • Minimize the number of steps required to access core features.
  • Reliability:

    • Ensure stable AR sessions with minimal crashes or glitches.

8. Tech Stack

Frontend:

  • React Native (for future mobile app development).

Backend:

  • None (MVP phase).

Database:

  • Local JSON (for storing era configurations and assets).
Page 6 of 7

AR Framework:

  • Unity with ARCore.

Assets:

  • Low-poly 3D models (1–5 MB each).

AI Tools (Future Consideration):

  • Google Nano Banana (for generating realistic textures and animations).

9. Assumptions and Constraints

Assumptions:

  • Users will primarily use the app in well-lit environments for optimal AR performance.
  • The target audience has access to mid-range or high-end Android devices.

Constraints:

  • The MVP will not include backend functionality or multiplayer features.
  • The app must remain lightweight and performant to meet APK size and FPS targets.
Page 7 of 7

10. Glossary

  • AR (Augmented Reality): Technology that overlays digital content onto the real world.
  • Era: A historical time period represented in the app (e.g., Jurassic, Ice Age).
  • Anchor: A fixed point in the AR environment where digital objects are placed.
  • MVP (Minimum Viable Product): The simplest version of the app that delivers core functionality.
  • FPS (Frames Per Second): A measure of how smoothly the app runs.
Home design preview
Home: Open App
AR Camera: Test Session
AR Camera: Check FPS
Era Select: Verify Eras
Era Select: Update Assets