How groundupworks/flying-photo-booth works
Project Type and Purpose
• This is a multi-module Android mobile project delivering two distinct photo-booth applications (“Flying PhotoBooth” and “PartyPhotoBooth”) plus a shared library module (“lib-photo-booth”).
• Each app module provides UI flows (Activities & Fragments), business logic (Controllers & Helpers), and app-specific resources (graphics, layouts, HTML). The shared module encapsulates core photo-booth functionality (arrangements, filters, camera & beam helpers, framework base classes).
File Structure
• Top-level modules:
• flying-photo-booth/ – Android app #1
• party-photo-booth/ – Android app #2
• lib-photo-booth/ – Shared Android library
• Common build files: build.gradle, settings.gradle, Gradle wrapper
• Each app has: AndroidManifest.xml, res/, src/com/groundupworks/… (Activities, Fragments, Controllers, Helpers), graphics/, html/, proguard.cfg
• Tests for party app under yksp-tests/
README for Additional Insights
• Describes core features: photo capture workflow, swipe-to-retake, filters/arrangements, share endpoints (Facebook, Dropbox, GCP, Android Beam)
• Mentions dependency on Android SDK and Wings (external sharing service API)
a. Main Components
• Module Layer
– FlyingPhotoBooth App
– PartyPhotoBooth App
– CoreLibrary (lib-photo-booth)
• Runtime Components (for each app)
– UI Layer: Activities & Fragments
– Controller Layer: ShareController, PhotoStripController, BaseController
– Service/Helper Layer: CameraHelper, BeamHelper, ImageHelper, StorageHelper, PreferencesHelper, KioskService (party app)
– Processing Layer: Arrangement classes, Filter classes
– Data Layer: local file storage, Gallery, SharedPreferences
– External Services: Android Beam, Facebook API, Dropbox API, Google Cloud Print, Wings backend
b. Relationships & Interactions
• FlyingPhotoBooth & PartyPhotoBooth modules both depend on CoreLibrary
• Controllers orchestrate capture (via CameraHelper), apply filters/arrangements, save to storage, and invoke sharing helpers
• KioskService (Party app) holds the app in foreground and enforces passcode protections
• yksp-tests invoke capture flows against PartyPhotoBooth module
c. Architectural Patterns & Principles
• Modularization: Shared core library for reuse and separation of concerns
• MVC-like layering: Fragments (View), Controllers (Conductor), Helpers/Filters (Model/Service)
• Dependency Injection via Application subclass (MyApplication) initializing frameworks
• Gradle multi-project build orchestrates modules and dependencies
d. Key Technologies & Frameworks
• Android SDK (Activities, Fragments, Services)
• Gradle (multi-module build)
• Android Beam, Bluetooth remote integration
• Facebook SDK, Dropbox SDK, Google Cloud Print API
• Java-based image processing within lib-photo-booth
Essential Details to Capture
• Module dependencies: both apps → lib-photo-booth
• Core workflow:
1) User triggers capture (UI)
2) Controller uses CameraHelper → returns bitmaps
3) Controller applies arrangement/filter via lib module
4) StorageHelper saves strip, updates Gallery
5) ShareController invokes appropriate sharing helper (Facebook, Dropbox, GCP, Beam)
6) Background retry scheduler if share fails
• Party app kiosk extension: KioskService & passcode fragments controlling app foreground